Hello Will and people,
Not sure if I am posting to the list correctly as I have used a mailing list
since the 90s, but today have reverted to largely email-only correspondence, so
...
My intent to was reply to the November "[yoshimi] Re: Opinions Please" thread,
as let's definitely consider me a beginner of sorts with Yoshimi.
I have uses also sort of editors, DAW in past decades as musician, one with
traditional instrument input, old tape multi-track, analog equipment input,
synths and digital, with more advanced or complex setup usually done by more
technically competent associates. But as PC user dating way back, I am familiar
with basic use of DAW, editors, used to use Cubase for example with vst and
synths. Yet my direction in digital aspires to be as minimal as possible but
harnessing and creating rich sound.
Today, I am a total minimalist and a user linux primarily for several years. I
installed Yoshimi many months back while my daily distribution was Arch Linux.
Long story short - switched to CentOS for professional reasons as my daily for
interim (which regarding CentOS repos to my knowledge, there was no Yoshimi and
otherwise I was too lazy to build it, seriously)... I am back on Arch as my
daily, and part of my switchback recently (and I am not kidding) was actually
Yoshimi was simply available in the aur. Being lazy and as sketcher of melodies
and texture, I simply needed the ability to repo-install as convenience and
plop a launcher on my panel for easy quick use.
Dumping some further feedback enumerated below, as I'd very much like to help
and communicate from a newbie perspective, but also in helping, regarding
refining Yoshimi if possible. Thus, I joined this emailing list to keep abreast
of dev and perhaps participate if warranted...
#1
My use of Yoshimi will likely be major as a primary sound synthesis/creation
instrument. Beyond a small kit/a couple other tools, Yoshimi will likely serve
as my sole synth now. I generally make music in two ways: (a) For one type of
project, I compose use notation and have my own methods of translating sounds.
This is includes all sort of things from using soundfonts, very distilled
manipulations via editor, parsing through basic waveforms using development
languages, like javascript or really a wide range. (b) sometimes in conjunction
with the aforementioned I use more traditional realtime synth work, and this is
really, at this point where Yoshimi comes in.
I heading into a project that I am focusing on impromptu realtime playing
recording using Yoshimi and a midi-controller. If possible progress to more
advanced controller usage. The importance on this statement as one-type of
newer user is that I want to keep things as simple as possible. Yoshimi +
controller. Period. Whatever limitations there are - fine. Whatever features
exist now - fine. If future progress can be added or refined to expand Yoshimi
potential while keeping it a simple front-end = my interest here I guess,
beyond perhaps aiding in more instrument sets.
In other words, I am thinking I am going to be, without much interest in other
as Yoshimi stands right now, a 100% dedicated Yoshimi user and using it for at
least one of my projects, in a significant manner.
The interface and simple plugin and play and record fits my need perfectly. If
I could use an advanced midi controller (with various other features), now or
in future, fantastic. This is my perspective after using it for awhile now and
as a (time-based) beginner, I guess. It's very simple and i recognize and
appreciate it as it currently stands.
#2
I have been using Yoshimi and some of the great instrument sets to make
impromptu melodies, which is just great and fulfills a major need of mine. I am
very interested in, if lazy - excuse, how instruments are added or implemented
here, and I would enjoy perhaps contributing from my own library if possible.
#3
As a beginner here, I bothered to join the mailing list obviously as I am
interested but want to mention that my main process and tools are now and will
likely remain on the digital-sourced and created frontier: (1) my typical
compositional methods, (2) audacity - plain and simple, it's lightweight, meets
my needs for other work that needs layering and basic editing, (3) Yoshimi one
of my my main synths.
#4
Arch linux user. [Sidenote: would be great if it were packaged for CentOS repos
as well]
- Fyi, opening Yoshimi on my arch build installed from aur repo, Alsa looks to
be set as the preferred/default midi and audio. From my view or experience,
Jack or Alsa - I suppose I have used either/or relating to various audio
applications. I never really think about or had to think about, as I never ran
into any problems using my own custom arch install. Alsa seems to be the
default for most, at least what I have used.. I would prefer Alsa though as a
default for reasons of common audio driver.
I am currently using a chiclet key smaller type of keyboard as the
midi-controller. I was just looking to maybe buy a budget midi controller
keyboard with hopefully 32 keys at least at 40-75$ range, that would interface
like my keyboard as option. Honestly not sure I need one but, but interested
in expanding and employing such a tool if it could use more options.
But on that front, I do not want to involve additional software or external
dependencies (outside what would be tagged along with Yoshimi package install,
similar to currently simplicity). Again, my process or use of Yoshimi is
desired to be: Midi-Controller/Keyboard > Yoshimi + mouse/keyboard > audacity
(record) > wav. I am not looking for an extensive editing suite or DAW. Yoshimi
as a simple synth instrument + potential major brand midi-controllers would be
ideal of course if it were doable in "lite"-manner.
What I liked about Yoshimi after launching after install and discovery (and
being familiar with prior Windows software etc from year past) was its
simplicity and clear, ease of use at the most basic and necessary level. Just
select a instrument and play/record.
THE FUTURE?
#5a
There's an introduction from me anyway as a "beginner user" of Yoshimi. If the
instruments are based on fonts, please let me know. It's been awhile but there
are other font packaging packages out there that I used and have a good special
library at my disposal. If possible (again, sorry to lazy to dig around, but
feel free to let me know) this message I suppose is also and inquiry into
participation, development needs and goals, or I how I could possibly help out
- such as building intruments sets etc. I will likely be using Yoshimi as my
primary digital synth, with particular interest right now and into the
forseeable future AND with additional heavy interest concerning direct midi
controlling/input, learning about it with Yoshimi, keeping tabs on testing/dev
etc.
#5b
Also, I explained my setup above for the reference to Will's question, as there
may be simply novices or musicians with need for certain basic features and
integration like mine. It's a perspective anyway for minimal end user type.
Yoshimi is already the favorite linux synth I have found, and really the best
I've encountered otherwsie, and I feel enthusiastic about it. I prefer straight
interface and no nonsense functionality (probably why audacity fulfills my
need, outside of the EQ,ing element that I have been to lazy to mesh with yet
or ascertain if it is sufficient for me).
Not to clutter the mailing list, but any proffered advice on Yoshimi use
related to #5c aka midi controller use with a basic setup: pc/linux > advanced
midi-controller -OR- simple midi-controller/keyboard advanced features would
totally be of as interest as well, in other words end-user discussion/advice
via the mailing list if that is acceptable!
# There's a monster message for you to digest, some feedback, user scenario,
desires and dreams.
# Excuse and poor grammer or mispelling -- told ya I'm lazy on that front or
regarding docs.
