Is that a bug, am I doing something wrong, or is there some logic to it? If you want the user to enter a string of their choice, why would you enter something for them? It’s always going to be wrong.
You are one parameter short. Audacity will read that as:
“” which is one string but there needs to be two parameters separated by a space.
If you add a space at the end it will work.
Alternatively you could write:
;control text "Some text" string "<space>" "<space>"
or
;control text "Some text" string "" "" ""
or
;control text "Some text" string<space><space><space>
Don’t be confused just use if you want two empty strings rather than
(which is the one that doesn’t work).
I can see your intention with
you are wanting to write:
but with so many escaped and non-escaped characters flying around it is difficult to work out exactly how Audacity will interpret
My assumption is that Audacity is interpreting
as one string.
This is held out by the following:
;control text "Some text" string """1""" "2"
All of the “extra” double quote pairs around the “1” are stripped out and it behaves the same as:
It’s a bug in the “;control …” string parser of the Audacity Nyquist interface. Empty strings (two double-quotes in a row with no other character in-between) are not recognized as strings and silently removed from the token list.
audacity/src/effects/nyquist/Nyquist.cpp, function EffectNyquist::Parse, lines 195…197
if (tok != wxT("")) {
tokens.Add(tok);
}
This means that “” is ignored and if you want a blank string then you must write two double-quotes with minimum one space character in-between.