Thread: [Audacity-devel] GUI support for VST committed
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
Menu
▾
▴
audacity-devel
|
From: Leland <le...@au...> - 2009-05-20 06:50:17
|
I just committed the resurrected GUI support for VST effects. This time it's using the VeSTige VST header. I'm sure there will be issues found since there are MANY VST effects in the wild, so we might have to tweak it here and there. I was also hoping folks could give it a try and give feedback on layout and such. I have an option to add to Preferences that disables the GUI and falls back to a plain text based dialog. Doing this will allow us to get rid of the vst-bridge, while still leaving an option for VI users. Please note that this is not VSTGUI support. That's a different animal and is not needed by a VST host. The effects are looked for in the Audacity "VST", "plugins", and "plug-ins" directories. On the Mac, /Users/<user>/Library/Audio/Plug-Ins/VST and /Library/Audio/Plug-Ins/VST are also searched. On Windows, registry key HKLM\Software\VST\VSTPluginsPath is also searched. Holler if you find something that's broken... Leland |
|
From: Gale A. <ga...@au...> - 2009-05-20 16:16:01
|
| From Leland <le...@au...> | Wed, 20 May 2009 01:49:59 -0500 | Subject: [Audacity-devel] GUI support for VST committed > I just committed the resurrected GUI support for VST effects. This time > it's using the VeSTige VST header. > > I'm sure there will be issues found since there are MANY VST effects in > the wild, so we might have to tweak it here and there. I was also > hoping folks could give it a try and give feedback on layout and such. > > I have an option to add to Preferences that disables the GUI and falls > back to a plain text based dialog. Doing this will allow us to get rid > of the vst-bridge, while still leaving an option for VI users. Thanks, Leland. OK, so are we free to mention this to users the next time one complains they don't get the fancy display they were expecting in their VST effect, or that it did not work? Is the intention this will be in the 1.3.8 Release barring technical problems? > Please note that this is not VSTGUI support. That's a different > animal and is not needed by a VST host. So we are not distributing the VSTGUI code that (possibly) we could have done, or anything of Steinberg - just the reverse-engineered LMMS headers? And when we update FAQs we do not need to mention anything about "downloading the VST SDK"? And we still have a policy of pretending Beta does not exist on the FAQs on the main site, so any updates about this will only be on the version of the FAQs here: http://www.audacityteam.org/manual/index.php?title=FAQ until 1.4 comes out? > The effects are looked for in the Audacity "VST", "plugins", and > "plug-ins" directories. > > On the Mac, /Users/<user>/Library/Audio/Plug-Ins/VST and > /Library/Audio/Plug-Ins/VST are also searched. > > On Windows, registry key HKLM\Software\VST\VSTPluginsPath is also searched. So if Windows users have plug-ins in: * The path specified by the VST_PATH environment variable, if different * C:\Program Files\Steinberg\VSTPlugins they will now not have their plug-ins detected, which they would have done using the vst-bridge? There are some older VST plug-ins on Mac aren't there (I forget what they are called right now). Will these still be expected to work? Thanks Gale |
|
From: Leland <le...@au...> - 2009-05-20 18:31:32
|
Quoting Gale Andrews <ga...@au...>: > > | From Leland <le...@au...> > | Wed, 20 May 2009 01:49:59 -0500 > | Subject: [Audacity-devel] GUI support for VST committed > > I just committed the resurrected GUI support for VST effects. This time > > it's using the VeSTige VST header. > > > > I'm sure there will be issues found since there are MANY VST effects in > > the wild, so we might have to tweak it here and there. I was also > > hoping folks could give it a try and give feedback on layout and such. > > > > I have an option to add to Preferences that disables the GUI and falls > > back to a plain text based dialog. Doing this will allow us to get rid > > of the vst-bridge, while still leaving an option for VI users. > > Thanks, Leland. > > OK, so are we free to mention this to users the next time one complains > they don't get the fancy display they were expecting in their VST effect, > or that it did not work? > I don't see why not...as long as the thing works as expected. > Is the intention this will be in the 1.3.8 Release barring technical > problems? > I would assume so. > > > Please note that this is not VSTGUI support. That's a different > > animal and is not needed by a VST host. > > So we are not distributing the VSTGUI code that (possibly) we could > have done, or anything of Steinberg - just the reverse-engineered > LMMS headers? And when we update FAQs we do not need to mention > anything about "downloading the VST SDK"? > Correct and correct. Nothing from Steinberg is included in the tree and no VST SDKs will be required to build Audacity with VST support builtin. > And we still have a policy of pretending Beta does not exist on the > FAQs on the main site, so any updates about this will only be on > the version of the FAQs here: > http://www.audacityteam.org/manual/index.php?title=FAQ > > until 1.4 comes out? > I don't know, if that's the policy, then I don't think this would change it. > > > The effects are looked for in the Audacity "VST", "plugins", and > > "plug-ins" directories. > > > > On the Mac, /Users/<user>/Library/Audio/Plug-Ins/VST and > > /Library/Audio/Plug-Ins/VST are also searched. > > > > On Windows, registry key HKLM\Software\VST\VSTPluginsPath is also searched. > > So if Windows users have plug-ins in: > > * The path specified by the VST_PATH environment variable, if > different > > * C:\Program Files\Steinberg\VSTPlugins > > they will now not have their plug-ins detected, which they would have > done using the vst-bridge? > Both paths will be searched, VST_PATH before the Registry path. > There are some older VST plug-ins on Mac aren't there (I forget what > they are called right now). Will these still be expected to work? > They will "probably" not work. But, I admit that I haven't tried them. Recall that we only support back to 10.3 and I'd wager that a lot of those older ones pre-date that. I will try to track some down though so we can have a definitive answer. But, if users need the older ones, then they will have to stick with the vst-bridge as I won't be adding support for them in the tree. Leland |
|
From: Gale A. <ga...@au...> - 2009-05-20 16:37:51
|
| From Leland <le...@au...> | Wed, 20 May 2009 01:49:59 -0500 | Subject: [Audacity-devel] GUI support for VST committed > I just committed the resurrected GUI support for VST effects. This time > it's using the VeSTige VST header. So far only tried compiling ANSI Release (on Windows) with one error as below. I deleted build directory and C:\Program Files\audacity_HEAD\audacity\win\Projects\Audacity\Release, and deleted audacity.sln so am using the current one from CVS: LoadVST.cpp ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2065: 'LSTATUS' : undeclared identifier ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2146: syntax error : missing ';' before identifier 's' ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2065: 's' : undeclared identifier Gale |
|
From: Vaughan J. <va...@au...> - 2009-05-20 23:43:55
|
Gale Andrews wrote: > | From Leland <le...@au...> > | Wed, 20 May 2009 01:49:59 -0500 > | Subject: [Audacity-devel] GUI support for VST committed > >> I just committed the resurrected GUI support for VST effects. This time >> it's using the VeSTige VST header. >> > > So far only tried compiling ANSI Release (on Windows) with one error as > below. I deleted build directory and > C:\Program Files\audacity_HEAD\audacity\win\Projects\Audacity\Release, > and deleted audacity.sln so am using the current one from CVS: > > LoadVST.cpp > ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2065: 'LSTATUS' : undeclared identifier > ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2146: syntax error : missing ';' before identifier 's' > ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2065: 's' : undeclared identifier > > Confirmed. http://msdn.microsoft.com/en-us/library/bb773534(VS.85).aspx says it's used in the declaration in shlwapi.h, but it's not. Rather it's LWSTDAPI_(LONG) SHRegGetUSValueA(...) but when I declare the s var as LWSTDAPI_(LONG), I get: LoadVST.cpp ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2598: linkage specification must be at global scope ..\..\..\src\effects\VST\LoadVST.cpp(198) : warning C4229: anachronism used : modifiers on data are ignored ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2491: 's' : definition of dllimport data not allowed ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2205: 's' : cannot initialize extern variables with block scope Do we need another header, Leland? - V |
|
From: Leland L. <pro...@ho...> - 2009-05-20 18:35:48
|
Quoting Gale Andrews <ga...@au...>: > > | From Leland <le...@au...> > | Wed, 20 May 2009 01:49:59 -0500 > | Subject: [Audacity-devel] GUI support for VST committed > > I just committed the resurrected GUI support for VST effects. This time > > it's using the VeSTige VST header. > > So far only tried compiling ANSI Release (on Windows) with one error as > below. I deleted build directory and > C:\Program Files\audacity_HEAD\audacity\win\Projects\Audacity\Release, > and deleted audacity.sln so am using the current one from CVS: > > LoadVST.cpp > ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2065: 'LSTATUS' : > undeclared identifier > ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2146: syntax error : > missing ';' before identifier 's' > ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2065: 's' : undeclared > identifier > That's odd...I wonder why it didn't get included... To get around it, just change the "LSTATUS" to "int" on line 198 and I'll check it out when I get home. Leland |
|
From: <ll...@vi...> - 2009-05-20 18:52:49
|
Quoting Gale Andrews <ga...@au...>: > > | From Leland <le...@au...> > | Wed, 20 May 2009 01:49:59 -0500 > | Subject: [Audacity-devel] GUI support for VST committed > > I just committed the resurrected GUI support for VST effects. This time > > it's using the VeSTige VST header. > > So far only tried compiling ANSI Release (on Windows) with one error as > below. I deleted build directory and > C:\Program Files\audacity_HEAD\audacity\win\Projects\Audacity\Release, > and deleted audacity.sln so am using the current one from CVS: > > LoadVST.cpp > ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2065: 'LSTATUS' : > undeclared identifier > ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2146: syntax error : > missing ';' before identifier 's' > ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2065: 's' : undeclared > identifier > That's odd...I wonder why it didn't get included... To get around it, change the "LSTATUS" to "int" on line 198 and I'll check it when I get home. Leland |
|
From: Martyn S. <mar...@go...> - 2009-05-20 23:41:25
|
I had the same problem and couldn't figure out the 'right' solution so I swapped 'LSTATUS' to 'LONG' and it worked. A missing 'include'? I've had some success and have seen the 'GUI' interface on two VST thing so far (TAL Phaser and Flanger) but the normal 'sliders' on others (Freeverb). Nice one, Leland! TTFN Martyn Gale Andrews wrote: > | From Leland <le...@au...> > | Wed, 20 May 2009 01:49:59 -0500 > | Subject: [Audacity-devel] GUI support for VST committed >> I just committed the resurrected GUI support for VST effects. This time >> it's using the VeSTige VST header. > > So far only tried compiling ANSI Release (on Windows) with one error as > below. I deleted build directory and > C:\Program Files\audacity_HEAD\audacity\win\Projects\Audacity\Release, > and deleted audacity.sln so am using the current one from CVS: > > LoadVST.cpp > ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2065: 'LSTATUS' : undeclared identifier > ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2146: syntax error : missing ';' before identifier 's' > ..\..\..\src\effects\VST\LoadVST.cpp(198) : error C2065: 's' : undeclared identifier > > > Gale > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables > unlimited royalty-free distribution of the report engine > for externally facing server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Leland <le...@au...> - 2009-05-21 00:11:46
|
Quoting Martyn Shaw <mar...@go...>: > I had the same problem and couldn't figure out the 'right' solution so > I swapped 'LSTATUS' to 'LONG' and it worked. A missing 'include'? > > I've had some success and have seen the 'GUI' interface on two VST > thing so far (TAL Phaser and Flanger) but the normal 'sliders' on > others (Freeverb). > That's correct. Some VST effects don't provide a GUI, so the normal slider dialog will be display instead. But, they aren't quite normal if you happen upon the right effects, like the MDA ones. You'll notice that there's a little more information along the right side after the sliders. These values are supplied by the effect, so can contain words in addition to number. This was not possible when using the vst-bridge. Leland |
|
From: Vaughan J. <va...@au...> - 2009-05-21 08:09:03
|
Martyn, I like your Gordian Knot approach. SFX Machine Pro seems to work, too. - V |
|
From: Gale (A. Team) <ga...@au...> - 2009-06-11 03:24:59
|
Leland (Audacity Team) wrote: > I just committed the resurrected GUI support for VST effects. This time > it's using the VeSTige VST header. > > I'm sure there will be issues found since there are MANY VST effects in > the wild, so we might have to tweak it here and there. I was also > hoping folks could give it a try and give feedback on layout and such. Leland, having tried the GSnap VST for Windows (see the thread about AutoTalent), I find that GSnap has two entries in the Effect menu (whether VST GUI mode is on or not), if vst-bridge.dll is in the Plug-Ins folder. Was this expected? One Gsnap entry says just "GSnap" (this is the one added when the bridge is present - it's tabular, with the crippled functionality we're used to, and appears irrespective of mode). The other entry says "GVST:GSnap" and has the GUI when GUI is enabled, and a more functional tabular interface when it isn't. Most other VST's I tried before now (for example the Kjaerhus Classic series) just appear once whether the bridge is present or not. These ones have no prefix and colon in the name. I think this may be something of an issue if people install 2.0 into C:\Program Files\Audacity so keeping the bridge in their Plug-Ins folder. I "think" the plan is the default installation folder will be C:\Program Files\Audacity (Unicode) for the Unicode 2.0 release. Can/should we suppress the duplicate instances when the bridge is present? Or could the installer look for and remove the bridge from C:\Program Files\Audacity\Plug-Ins? That may not be appreciated if people are trying 2.0 out installed into another folder. Gale -- View this message in context: http://n2.nabble.com/GUI-support-for-VST-committed-tp2944625p3059880.html Sent from the audacity-devel mailing list archive at Nabble.com. |
|
From: Leland <le...@au...> - 2009-06-11 05:55:52
|
Gale (Audacity Team) wrote: > Leland (Audacity Team) wrote: >> I just committed the resurrected GUI support for VST effects. This time >> it's using the VeSTige VST header. >> >> I'm sure there will be issues found since there are MANY VST effects in >> the wild, so we might have to tweak it here and there. I was also >> hoping folks could give it a try and give feedback on layout and such. > > Leland, having tried the GSnap VST for Windows (see the thread about > AutoTalent), I find that GSnap has two entries in the Effect menu (whether > VST GUI mode is on or not), if vst-bridge.dll is in the Plug-Ins folder. Was > this expected? > Unfortunately, yes. There's no way for the bridge or the new VST fella to know about each other, so there will most like be dups. > > I think this may be something of an issue if people install 2.0 into > C:\Program Files\Audacity so keeping the bridge in their Plug-Ins folder. I > "think" the plan is the default installation folder will be C:\Program > Files\Audacity (Unicode) for the Unicode 2.0 release. Can/should we suppress > the duplicate instances when the bridge is present? Or could the installer > look for and remove the bridge from C:\Program Files\Audacity\Plug-Ins? That > may not be appreciated if people are trying 2.0 out installed into another > folder. > If we think the new VST code is good enough, the how about we have the Ladspa loader specifically look for and ignore the vst-bridge.dll? This way ppl can pop back and forth between versions and they won't get any dups in 2.0. Leland |
|
From: Richard A. <ric...@go...> - 2009-06-12 19:05:49
|
On Thu, 2009-06-11 at 00:55 -0500, Leland wrote: > If we think the new VST code is good enough, the how about we have the > Ladspa loader specifically look for and ignore the vst-bridge.dll? This > way ppl can pop back and forth between versions and they won't get any > dups in 2.0. +1 (wrapped in a platform check so that it only applies to Windows?) Richard |
|
From: Leland L. <lll...@gm...> - 2009-06-12 19:17:36
|
On Fri, Jun 12, 2009 at 2:05 PM, Richard Ash < ric...@go...> wrote: > On Thu, 2009-06-11 at 00:55 -0500, Leland wrote: > > If we think the new VST code is good enough, the how about we have the > > Ladspa loader specifically look for and ignore the vst-bridge.dll? This > > way ppl can pop back and forth between versions and they won't get any > > dups in 2.0. > > +1 (wrapped in a platform check so that it only applies to Windows?) > It would apply to OSX as well, since the VST GUI support works there too. Do we use the vst-bridge on Linux??? I never considered that before... Leland |
|
From: Richard A. <ric...@go...> - 2009-06-13 19:29:12
|
On Fri, 2009-06-12 at 14:16 -0500, Leland Lucius wrote: > +1 (wrapped in a platform check so that it only applies to > Windows?) > > It would apply to OSX as well, since the VST GUI support works there > too. Do we use the vst-bridge on Linux??? I never considered that > before... Effectively no, because there are pretty much no VST plug-ins compiled for Linux, given the header licensing issues. There are other bridges which run the plug-in under wine to try and enable the use of windows VST plug-ins under Linux, but they aren't relevant to this debate. So it may not need a platform check given that the bridge should never show up on Linux. Richard |
|
From: Alexandre P. <ale...@gm...> - 2009-07-17 14:08:46
|
On Sat, Jun 13, 2009 at 11:02 PM, Richard Ash wrote: > On Fri, 2009-06-12 at 14:16 -0500, Leland Lucius wrote: > >> +1 (wrapped in a platform check so that it only applies to >> Windows?) >> >> It would apply to OSX as well, since the VST GUI support works there >> too. Do we use the vst-bridge on Linux??? I never considered that >> before... > > Effectively no, because there are pretty much no VST plug-ins compiled > for Linux http://www.anticore.org/jucetice/?page_id=7 Alexandre |
|
From: Gale (A. Team) <ga...@au...> - 2009-07-17 20:21:40
|
Leland (Audacity Team) wrote: > I just committed the resurrected GUI support for VST effects. This time > it's using the VeSTige VST header. > > I'm sure there will be issues found since there are MANY VST effects in > the wild, so we might have to tweak it here and there. I was also > hoping folks could give it a try and give feedback on layout and such. A user has reported this package: http://antress.webng.com/ I tried "ModernBooster" and "ModernDeEsser" and they both crashed on Preview and applying the Effect. Also I'm not sure what the B/W controls on ModernBooster are supposed to do, but clicking and/or dragging them has no visible effect for me. Gale -- View this message in context: http://n2.nabble.com/GUI-support-for-VST-committed-tp2944625p3277587.html Sent from the audacity-devel mailing list archive at Nabble.com. |
|
From: Leland <le...@au...> - 2009-07-17 20:29:16
|
Okay, I'll look at it when I get home. Leland On Fri, Jul 17, 2009 at 3:21 PM, Gale (Audacity Team) <ga...@au... > wrote: > > Leland (Audacity Team) wrote: > > I just committed the resurrected GUI support for VST effects. This time > > it's using the VeSTige VST header. > > > > I'm sure there will be issues found since there are MANY VST effects in > > the wild, so we might have to tweak it here and there. I was also > > hoping folks could give it a try and give feedback on layout and such. > > A user has reported this package: > http://antress.webng.com/ > > I tried "ModernBooster" and "ModernDeEsser" and they both crashed on > Preview > and applying the Effect. Also I'm not sure what the B/W controls on > ModernBooster are supposed to do, but clicking and/or dragging them has no > visible effect for me. > > > Gale > > -- > View this message in context: > http://n2.nabble.com/GUI-support-for-VST-committed-tp2944625p3277587.html > Sent from the audacity-devel mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Leland <le...@au...> - 2009-07-18 04:59:01
|
Gale (Audacity Team) wrote: > A user has reported this package: > http://antress.webng.com/ > > I tried "ModernBooster" and "ModernDeEsser" and they both crashed on Preview > and applying the Effect. Also I'm not sure what the B/W controls on > ModernBooster are supposed to do, but clicking and/or dragging them has no > visible effect for me. > Haven't figured out what's wrong yet, but those B/W controls work for me. They change the led meter above them. That really doesn't happen for you? Leland |
|
From: Gale A. <ga...@au...> - 2009-07-18 06:55:35
|
| From Leland <le...@au...> | Fri, 17 Jul 2009 23:58:51 -0500 | Subject: [Audacity-devel] GUI support for VST committed > Gale (Audacity Team) wrote: > > A user has reported this package: > > http://antress.webng.com/ > > > > I tried "ModernBooster" and "ModernDeEsser" and they both crashed on Preview > > and applying the Effect. Also I'm not sure what the B/W controls on > > ModernBooster are supposed to do, but clicking and/or dragging them has no > > visible effect for me. > > > Haven't figured out what's wrong yet, but those B/W controls work for me. They > change the led meter above them. > > That really doesn't happen for you? Not with the "mousemu" mouse emulator I normally use (it lets numpad keys mimic a real mouse). With a real mouse if I click repeatedly until I get tired I can manage to increment the counters by 1. The control only appears as a white push button type of control for me. This is on XP and Vista. Also I note that when you drag the dB controls, the hand cursor disappears so you can't see what you are doing (real and emulated mouse). Gale |
|
From: Leland <le...@au...> - 2009-07-18 07:42:37
|
Gale Andrews wrote: > | From Leland <le...@au...> > | Fri, 17 Jul 2009 23:58:51 -0500 > | Subject: [Audacity-devel] GUI support for VST committed >> Gale (Audacity Team) wrote: >>> A user has reported this package: >>> http://antress.webng.com/ >>> >>> I tried "ModernBooster" and "ModernDeEsser" and they both crashed on Preview >>> and applying the Effect. Also I'm not sure what the B/W controls on >>> ModernBooster are supposed to do, but clicking and/or dragging them has no >>> visible effect for me. >>> Just committed a fix. The plugin was requesting time information and we were returning NULL, which is valid. Unfortunately, the plugin doesn't seem to like that, so not we return a valid ptr to an empty (zeroed) time info block. >> Haven't figured out what's wrong yet, but those B/W controls work for me. They >> change the led meter above them. >> >> That really doesn't happen for you? > > Not with the "mousemu" mouse emulator I normally use > (it lets numpad keys mimic a real mouse). With a real > mouse if I click repeatedly until I get tired I can manage > to increment the counters by 1. The control only appears > as a white push button type of control for me. This is > on XP and Vista. > So your's doesn't look like this? http://homerow.net/audacity/ModernBooster.png > Also I note that when you drag the dB controls, the hand > cursor disappears so you can't see what you are doing > (real and emulated mouse). > This happens here too, but I think it's planned. All under the control of the plugin. Leland |
|
From: Leland <le...@au...> - 2009-07-18 07:48:35
|
Leland wrote: > Gale Andrews wrote: >> | From Leland <le...@au...> >> | Fri, 17 Jul 2009 23:58:51 -0500 >> | Subject: [Audacity-devel] GUI support for VST committed >>> Gale (Audacity Team) wrote: >>>> A user has reported this package: >>>> http://antress.webng.com/ >>>> >>>> I tried "ModernBooster" and "ModernDeEsser" and they both crashed on Preview >>>> and applying the Effect. Also I'm not sure what the B/W controls on >>>> ModernBooster are supposed to do, but clicking and/or dragging them has no >>>> visible effect for me. >>>> > Just committed a fix. The plugin was requesting time information and we were returning > NULL, which is valid. Unfortunately, the plugin doesn't seem to like that, so not we > return a valid ptr to an empty (zeroed) time info block. > Doesn't look like the dummy time info is gonna work. It fixed the crash, but most of the effect now return silence. BttDB... Leland |
|
From: Gale A. <ga...@au...> - 2009-07-18 18:27:17
|
| From Leland <le...@au...> | Sat, 18 Jul 2009 02:42:30 -0500 | Subject: [Audacity-devel] GUI support for VST committed > Gale Andrews wrote: > > | From Leland <le...@au...> > > | Fri, 17 Jul 2009 23:58:51 -0500 > > | Subject: [Audacity-devel] GUI support for VST committed > >> Gale (Audacity Team) wrote: > >>> A user has reported this package: > >>> http://antress.webng.com/ > >>> > >>> I tried "ModernBooster" and "ModernDeEsser" and they both crashed on Preview > >>> and applying the Effect. Also I'm not sure what the B/W controls on > >>> ModernBooster are supposed to do, but clicking and/or dragging them has no > >>> visible effect for me. > >>> > Just committed a fix. The plugin was requesting time information and we were returning > NULL, which is valid. Unfortunately, the plugin doesn't seem to like that, so not we > return a valid ptr to an empty (zeroed) time info block. > > >> Haven't figured out what's wrong yet, but those B/W controls work for me. They > >> change the led meter above them. > >> > >> That really doesn't happen for you? > > > > Not with the "mousemu" mouse emulator I normally use > > (it lets numpad keys mimic a real mouse). With a real > > mouse if I click repeatedly until I get tired I can manage > > to increment the counters by 1. The control only appears > > as a white push button type of control for me. This is > > on XP and Vista. > > > So your's doesn't look like this? > > http://homerow.net/audacity/ModernBooster.png It looks exactly like that, except that clicking in those B/W controls behaves as I stated. How does it work - does it depend where you click to make it increment the counter up or down? Gale |
|
From: Leland <le...@au...> - 2009-07-18 18:36:18
|
Gale Andrews wrote: > | From Leland <le...@au...> > | Sat, 18 Jul 2009 02:42:30 -0500 > | Subject: [Audacity-devel] GUI support for VST committed >> Gale Andrews wrote: >>> | From Leland <le...@au...> >>> | Fri, 17 Jul 2009 23:58:51 -0500 >>> | Subject: [Audacity-devel] GUI support for VST committed >>>> Gale (Audacity Team) wrote: >>>>> A user has reported this package: >>>>> http://antress.webng.com/ >>>>> >>>>> I tried "ModernBooster" and "ModernDeEsser" and they both crashed on Preview >>>>> and applying the Effect. Also I'm not sure what the B/W controls on >>>>> ModernBooster are supposed to do, but clicking and/or dragging them has no >>>>> visible effect for me. >>>>> >> Just committed a fix. The plugin was requesting time information and we were returning >> NULL, which is valid. Unfortunately, the plugin doesn't seem to like that, so not we >> return a valid ptr to an empty (zeroed) time info block. >> >>>> Haven't figured out what's wrong yet, but those B/W controls work for me. They >>>> change the led meter above them. >>>> >>>> That really doesn't happen for you? >>> Not with the "mousemu" mouse emulator I normally use >>> (it lets numpad keys mimic a real mouse). With a real >>> mouse if I click repeatedly until I get tired I can manage >>> to increment the counters by 1. The control only appears >>> as a white push button type of control for me. This is >>> on XP and Vista. >>> >> So your's doesn't look like this? >> >> http://homerow.net/audacity/ModernBooster.png > > It looks exactly like that, except that clicking in those B/W > controls behaves as I stated. How does it work - does it > depend where you click to make it increment the counter > up or down? > I'm just clicking, holding, and moving the mouse up and down. Leland |
|
From: Gale A. <ga...@au...> - 2009-07-18 20:33:02
|
| From Leland <le...@au...> | Sat, 18 Jul 2009 13:36:12 -0500 | Subject: [Audacity-devel] GUI support for VST committed > Gale Andrews wrote: > > | From Leland <le...@au...> > > | Sat, 18 Jul 2009 02:42:30 -0500 > > | Subject: [Audacity-devel] GUI support for VST committed > >> Gale Andrews wrote: > >>> | From Leland <le...@au...> > >>> | Fri, 17 Jul 2009 23:58:51 -0500 > >>> | Subject: [Audacity-devel] GUI support for VST committed > >>>> Gale (Audacity Team) wrote: > >>>>> A user has reported this package: > >>>>> http://antress.webng.com/ > >>>>> > >>>>> I tried "ModernBooster" and "ModernDeEsser" and they both crashed on Preview > >>>>> and applying the Effect. Also I'm not sure what the B/W controls on > >>>>> ModernBooster are supposed to do, but clicking and/or dragging them has no > >>>>> visible effect for me. > >>>>> > >> Just committed a fix. The plugin was requesting time information and we were returning > >> NULL, which is valid. Unfortunately, the plugin doesn't seem to like that, so not we > >> return a valid ptr to an empty (zeroed) time info block. > >> > >>>> Haven't figured out what's wrong yet, but those B/W controls work for me. They > >>>> change the led meter above them. > >>>> > >>>> That really doesn't happen for you? > >>> Not with the "mousemu" mouse emulator I normally use > >>> (it lets numpad keys mimic a real mouse). With a real > >>> mouse if I click repeatedly until I get tired I can manage > >>> to increment the counters by 1. The control only appears > >>> as a white push button type of control for me. This is > >>> on XP and Vista. > >>> > >> So your's doesn't look like this? > >> > >> http://homerow.net/audacity/ModernBooster.png > > > > It looks exactly like that, except that clicking in those B/W > > controls behaves as I stated. How does it work - does it > > depend where you click to make it increment the counter > > up or down? > > > I'm just clicking, holding, and moving the mouse up and down. Hi Leland, After updating to your second VST fix, those two Antress plug-ins preview and apply the effect fine, and the B/W controls are now draggable to increment the counter, even with the mouse emulator. That certainly didn't work before, which was why I thought you had to click in a particular place. I'll let the complainant know and report back if he finds problems with any of the other plug-ins in that collection. Thanks Gale |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X