[LAU] Yoshimi Command Line

[Will Godfrey]

I have a question for any people who make use of this.

Recent work means that in the latest builds some deep access into the synth
engines is now possible with the status of all context steps being echoed to
the prompt line so you know where you are.

However this can get very long, so I'm wondering if it would be better to have
a status line followed by a normal "yoshimi>" prompt. As has already been
pointed out, this would then tend to orphan the last command actioned from the
prompt. Currently, using minimised commands from the top level:
's p add voi env fre on'

reports:
'Part 1 Kit 1 Add Voice 1 Frequency Enable Env Value 1.000000'

and gives a new prompt line:
'yoshimi Part 1 on, Addvoice on, freq Envel on>'

Bear in mind that the report is what you did, and the prompt is where you are
(although there is considerable overlap).

If you now do:
's at t 80'
the report is:
'Part 1 Kit 1 Add Voice 1 Amp Env A dt Value 80.000000'

but the prompt line is still:
'yoshimi Part 1 on, Addvoice 1 on, amp Envel>'

We need to tidy up the responses, and intend to shorten the report line to just
the control changed and its new value, as the steps to reach it will be in the
prompt. Or should they be? That's my question.

Another consideration is that the prompt is specific to the CLI but reports
might be directed to the GUI console!

Also, as well as blind users, we have at least one sighted user who runs
graphically but sends commands via the CLI wherever possible.

Finally, I'm sending this to both LAU and Yoshimi's own list as this is getting
into unfamiliar territory and I would like to get the widest possible user
views.

[Jeanette C.]

Sep 13 2018, Will Godfrey has written:
...

Post by Will Godfrey
Recent work means that in the latest builds some deep access into the synth
engines is now possible with the status of all context steps being echoed to
the prompt line so you know where you are.
However this can get very long, so I'm wondering if it would be better to have
a status line followed by a normal "yoshimi>" prompt. As has already been
pointed out, this would then tend to orphan the last command actioned from the
's p add voi env fre on'

...
The information in the prompt is very helpful, though it could be
slightly reduced by not including the status of certain items. Skip the
"on/off" info in the path. You might also try to shorten the path after
a certain level, by dropping items from the beginning. Personally, I'd
always prefer an informative prompt to a status line above the prompt.

Btw. I love the help system, it's perfect! Very impressive work!

Best wishes,

jeanette
--
* Website: http://juliencoder.de - for summer is a state of sound
* SoundCloud: https://soundcloud.com/jeanette_c
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* GitHub: https://github.com/jeanette-c
* Twitter: https://twitter.com/jeanette_c_s

I'm reaching out to you
To find that you're not there <3
(Britney Spears)

[Will Godfrey]

On Sat, 15 Sep 2018 20:07:26 +0200 (CEST)

Post by Jeanette C.
The information in the prompt is very helpful, though it could be
slightly reduced by not including the status of certain items. Skip the
"on/off" info in the path. You might also try to shorten the path after
a certain level, by dropping items from the beginning. Personally, I'd
always prefer an informative prompt to a status line above the prompt.

Although I appreciate not wanting non-essential information, the problem is
being 'on' *is* essential information - right up the chain. It is something I've
been tripped up by myself many times. For example you could be working on (say)
an addSynth filter, while a MIDI message comes along and switches the part off.
The engine still exists, and is fully editable but it's not going to do
anything. You need to know that!

Things that don't exist are error checked to prevent you trying to access
empty space, but I'm trying to keep the overhead as light as possible while
maintaining safety.

Post by Jeanette C.
Btw. I love the help system, it's perfect! Very impressive work!

:)

[Jeanette C.]

Sorry, mail must have got lost. My point in short: you can try to shorten the
state info by e.g. "+" or "-" directly in front of or after the feature in the
path. Other symbols or demarkation could be used.

Best wishes,

Jeanny
--
* Website: http://juliencoder.de - for summer is a state of sound
* SoundCloud: https://soundcloud.com/jeanette_c
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* GitHub: https://github.com/jeanette-c
* Twitter: https://twitter.com/jeanette_c_s

And when you say those words
It's the sweetest thing I've ever heard <3
(Britney Spears)

[Will Godfrey]

On Tue, 18 Sep 2018 00:15:58 +0200 (CEST)

Post by Jeanette C.
Sorry, mail must have got lost. My point in short: you can try to shorten the
state info by e.g. "+" or "-" directly in front of or after the feature in the
path. Other symbols or demarkation could be used.
Best wishes,
Jeanny

OK I think I've got a compromise in the current build.

In any context, its identifier is in full, lower ones have just the first
letter.
I like the idea of '+' instead of 'on' but it's that or nothing, clearer than
'-' and the line shifts slightly giving you another hint.

So:
yoshimi>
s p 4 on
yoshimi Part 4+>
s add
yoshimi P4+, add+
s voi 6
yoshimi P4+, A+, Voice 6>
s fil
yoshimi P4+, A+, V6, analog Filter>

Note we haven't activated Voice 6 so it won't sound but can still be edited!

/ s p 2 on
yoshimi Part 2+>
s km mu
yoshimi Part 2+, kit 1+, multi>
s ki 4
yoshimi Part 2+, kit 4, multi>
s on
yoshimi Part 2+, kit 4+, multi>
s sub on
yoshimi P2+, K4, M, Sub+>
s fil on
yoshimi P2+, K4, M, S+, analog Filter+>
s ca f
yoshimi P2+, K4, M, S+, formant Filter+>

Note that kit controls stay in full until you enter the engines, as they are
all in the part context.

Finally, thanks for the feedback :)