Code: Select all
Resizable choice controls would allow for better descriptions of the choices.
I'm not sure that it would be appropriate to use the command ";control", but an option to add a line as an interface element, yes +1.pshute wrote:How about a line control? E.g.
Code: Select all
Agreed.pshute wrote:Resizable choice controls would allow for better descriptions of the choices.
There has previously been a suggestion of a "Tools" or "Utilities" menu (and in fact there was once a "Tools" menu in an old beta version of Audacity, but it was abandoned because at that time there was only one item in that menu). Would a "Tools" or "Utilities" menu be suitable for what you have in mind?Paul L wrote:My idea might require a fourth category, perhaps called Find, so it's radical.
That may not be possible (probably isn't possible) as it goes beyond the scope of the core plug-in support structure. In order to be able to operate on audio data, that data needs to be passed to the plug-in code. We usually don't want to pass "all" of the audio data in the project as that could be many hours of data in each channel, so we just pass the relevant part of the data - the "relevant part" is defined as "the selection". In order to have access to the full track, Nyquist would probably need to move from being a plug-in scripting language to being integrated into a "module", which would probably be quite a major undertaking and probably not compatible with current Nyquist plug-ins.Paul L wrote:allow inspection of samples beyond the boundaries of the selection
Nyquist plug-ins currently have no concept of "real" (Audacity track) time. As far as a plug-in is concerned, the start of time is the beginning of the selection.Paul L wrote:return some values to indicate a modified range of selection
Not much. When there are multiple tracks (or channels) selected, "Find Zero Crossings" does not really work unless all of the selected tracks/channels happen to have zero crossing points in the same place.Paul L wrote:But for that matter, what does Find Zero Crossings mean in that case?
Any reason to not just make the selection a bit bigger?Paul L wrote:Or perhaps, if there was some arbitrary, hard limit, or Preference, for the amount of lookahead and lookbehind, it would be an acceptable compromise.
Yes, the precise endpoints of the selection are important data. I want that and some amount of context for calculations. I can't select an exact second before and behind it quickly by hand. I could in principle do mental math and use the number inputs in the selection toolbar, but that's hardly a convenience.steve wrote: Any reason to not just make the selection a bit bigger?
I see Paul's point.steve wrote:Any reason to not just make the selection a bit bigger?Paul L wrote:Or perhaps, if there was some arbitrary, hard limit, or Preference, for the amount of lookahead and lookbehind, it would be an acceptable compromise.