I'll try to add to the information in 'doc' through this week - while also
checking for bugs - with the intention of a release on Sunday or Monday. The
latest changes I made to the CLI, were the result of an ill thought out
decision at the start. Hopefully I won't need to change anything else, but just
add to what is there.
The levels that currently exist are:
top level
system effects
insertion effects
part
part effects
vector
Ones that I'm pretty sure will be added are:
scales (microtonal)
controllers
addsynth
addsynth voice
subsynth
padsynth harmonics
padsynth envelopes
In the GUI, harmonics are the default window for padsynth, but for the CLI I'll
probably reverse that. Once the sound has been set up. you are more likely to
want to play with the envelopes, and throughout the CLI I'm trying to make the
most used controls have the highest priority (and shortest abbreviations).
Any level that has a direct numerical content will be changeable simply with
"set {n}" once you are at that level.
eg. you can have 0-15 vector channels, so from top level:
"set vector" -or- "s ve"
will return the default 0 (or last used one)
"set 5" -or- "s 5"
will then switch to vector channel 5.
However, at the start you could have gone straight there with:
"set vector 5" -or- "s ve 5"
Does that clarify things more?
With the built-in help system I'm trying to provide enough information as a
reminder, while not stuffing the terminal with acres of text.
On Tue, 23 Feb 2016 06:26:05 -0500
Chris Ahlstrom <ahlstromcj@xxxxxxxxx> wrote:
I'm getting back into Yoshimi, as the sequencer now is roughly stable for
awhile, and I really need to start using it heavily. I notice that the
command-line help functionality is now very minimal.
Is there any way you can create a "Command set" text file to list
the commands? Also summarize the "levels"?
I'll probably need a bit of help rewriting the rest of the manual as well.
No hurry, I am just starting on plowing ("ploughing"?) through the
txt files.
I like the prompt system, very helpful.
-------- Will Godfrey 19:55 Mon 22 Feb --------
Now we seem to be in the clear (hopefully) there is a small adjustment I made
to the CLI recently.
The 'paths' command no longer exists. Instead we have 'add' & 'remove', so
instead of 'path add' it's 'add root'. Also you can now add and remove banks
using the same structure. 'paths show' has now been moved into lists as 'list
roots'.
These changes make roots/banks/instruments more consistent.
However, at the moment it requires a full path to be used, and doesn't offer
to
create it. There are a few other places in the code where this happens, so
what
I'm considering is a new function in MiscFuncs that will build up the
directory
structure as required. Also, I'll probably arrange it so that if you don't
put
a leading '/' on the search string it will assume '/home/{user}/'.
Something I'm less sure about is whether we should make 'banks' compulsory
for
the last part of a root path. It has been optional up to now, although
everyone
seems to accept it as the norm. If it is compulsory it actually simplifies
some
of the code and makes it more regular.
In any case, I won't do this before the new release - too tempting for
Murphy to
throw in a bug or two!
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Yoshimi source code is available from either:
http://sourceforge.net/projects/yoshimi
Or: https://github.com/Yoshimi/yoshimi
Our list archive is at: https://www.freelists.org/archive/yoshimi
To post, email to yoshimi@xxxxxxxxxxxxx
