Re: [Audacity-nyquist] Inputting exact values into Audacity Nyquist effects
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Steve <ste...@gm...> - 2009-10-21 22:34:38
|
The new patch works very well, but I don't like the reduced resolution. In some situations it is necessary for user input to have more decimal places than is possible with this patch. Is it possible to keep the benefits of this patch without loosing decimal places? Steve On Tue, 2009-10-20 at 15:19 -0600, Al Dimond wrote: > Thanks for trying that patch. There's a new patch attached. To apply > it you'll want to reverse the old one first (use patch with the -R > flag). The new patch also appears to fix the problem exhibited by the > Risset Drum plugin, which requests default values like 100 and 500 and > the dialog shows numbers like 101 and 502. More comments below. > > On Tuesday 20 October 2009 12:58:06 Steve wrote: > > I've successfully applied the patch and it makes a big improvement > > in most cases but unfortunately it introduces a new bug (which is > > probably what you are referring to in your next sentence). > > > > If we have an input: > > > > ;control test "test" real "" 1.0 0.01 2000.0 > > > > This should (ideally) display the number 1 (or 1.0000) as the > > default value, but in fact it displays 0 (zero). > > > > Actually, that is something totally different than what I was thinking > of. Are you saying that if you set 1.0 as your default and don't > touch the slider at all that you'll get 0 as the input to the control? > If that's what you're saying, I think I know why that is, and the new > patch should fix it. If it's something else I have no idea what's > going on. > > > More importantly (because it will probably break quite a few > > plug-ins); because this input is of type "real", it should > > _always_ produce a float. With the patch, this example produces > > integers unless a float is explicitly typed into the text entry. > > > > I just got your other mail on this subject. The new patch will always > put three digits after the decimal point for floats (even ones with > integral values) but that's really easy to change if you or someone > else doesn't like it. > > > > It doesn't work if you enter > > > something that doesn't look like a floating point number into the > > > text box, which should be fixed, but I just want to make sure I'm > > > doing it right in the first place. > > > If you can't build I'll try to figure out how > > > to test Nyquist stuff tomorrow. > > > > Are you aware of Leland's "Nyquist Workbench" module? It is a > > really useful tool when fiddling around with Nyquist. > > http://audacity.homerow.net/index.php?dir=modules > > > > I am now! I'll give that a try in a bit; my Lisp skills are pretty > minimal at this point but I might understand enough to do a little > debugging, and I'm always willing to try another language. > > > (as an aside, if you are developing on Windows and build NyqBench > > against the current Audacity cvs code, I would love a copy - I'm > > happy building it on Linux, but not so on Windows) > > > > I'm on Linux as well so I can't really help with that... I'd give it a > shot with the mingw32 cross compiler but I don't even have Nyquist > building for mingw32 yet (it's so far from the purpose of my mingw32 > tree that I just disabled it along with pretty much every other > optional feature or library). > > > Steve > > > > > - Al > > > > > > > (This issues is currently listed as P3 and has also been raised > > > > here > > > > > > > > http://n2.nabble.com/Re-Slider-Bug-Investigations-was-Pluck-in- > > > >Aud acity-td238683.html) > > > > > > > > Steve D > > |