Hang when scanning for VST effects on Mac
|
|
| 1 2 |
Bill Wharrie
|
Some javascript/style in this post has been disabled (why?)
I can reliably reproduce this bug. The hang apparently occurs only on Mac, but the scanning on start if plugins.cfg is empty has been reported on Windows. Audacity 1.3.10 alpha Oct 21 2009 Mac G5 dual 2 GHz, OSX 10.5.8 Virgin install, with Portable Settings folder Note: I used the Portable Settings folder so I could do these tests without messing up my working installation of 1.3.9. I did do test #6 without the portable settings folder and simulating a virgin install and the results were the same. I assume (rightly, I hope) that this demonstrates that using the portable settings folder was not a factor in the results. Sorry if this is too long. I tried to hit every case. 1) -- Effect of "Rescan VST effects" with no VST effects in the plug-ins folder Launch Audacity Check "Rescan VST effects" Quit Audacity Launch Audacity - OK Check "Rescan VST effects" Quit Audacity 2) -- Effect of "Rescan VST effects" with one VST effect in the plug-ins folder Add a VST effect to the plug-ins folder Launch Audacity - hangs Notes: - a second Audacity icon briefly appears in the Dock on launch when a hang occurs. - you cannot force quit Audacity from the Dock icon, as right-clicking on the Dock icon does not show the "Force Quit" choice. - you can switch to Audacity, and the "Audacity > Quit Audacity" menu item is there but it has no effect. The Help menu appears when you switch to Audacity but is not populated. No other menus appear. - you must use "Force Quit" from the Apple menu to force quit Audacity - the option to rescan for VST effects is now in audacity.cfg and it is impossible to launch Audacity without trashing that file or editing it so that the relevant line is "Rescan=0" Start over: trash plugins.cfg, edit audacity.cfg to the single line "NewPrefsInitialized =1", leave VST effect in the plug-ins folder. 3) -- Effect of having one VST effect in the plug-ins folder when plugins.cfg does not exist -- Launch Audacity - get "Language" prompt, then Audacity hangs, as above. Force Quit Audacity Notes: - the "Rescan" option was not active since audacity.cfg had been cleared - after force quit, plugins.cfg contains information about the VST effect - after force quit, audacity.cfg has not been altered 4) -- Effect of having one VST effect in the plug-ins folder when plugins.cfg exists but is empty -- Edit plugins.cfg, clearing all content, then save Leave the VST effect in the plug-ins folder Launch Audacity - hangs, as above Force quit Audacity. Notes: - identical to case when plugins.cfg did not exist. 5a) -- Effect of adding one VST effect to the plug-ins folder, then later adding another -- Start over: trash plugins.cfg, edit audacity.cfg to the single line "NewPrefsInitialized =1", remove VST effect from the plug-ins folder. Launch Audacity - get "Language" prompt, launches OK Check "Rescan VST Efffects" Quit Audacity Add VST effect to the plug-ins folder Launch Audacity - hangs as above Force Quit Audacity Launch Audacity - hangs, as above - the option to rescan for VST effects is now in audacity.cfg and it is impossible to launch Audacity without trashing that file or editing it so that the relevant line is "Rescan=0" Edit audacity.cfg setting "Rescan=0" and save Launch Audacity - OK, and the VST effect appears in the Effect menu 5b)-- Now test if we can add another VST effect -- Check "Rescan VST Efffects" Quit Audacity Add another VST effect to the plug-ins folder Launch Audacity - hangs Force Quit Audacity - the newly-added VST effect is not in plugins.cfg 6) -- Will Audacity pick up two newly-added VST effects? -- Start over: trash plugins.cfg, edit audacity.cfg to the single line "NewPrefsInitialized =1", leave both VST effects in the plug-ins folder. Launch Audacity - hangs, as above Force Quit Audacity - plugins.cfg contains info for only one VST effect, although there were two in the plug-ins folder. Conclusions: 1) If plugins.cfg does not exist or plugins.cfg is empty then Audacity does a scan for VST effects. If it finds one, it hangs (on Mac, not Windows), but not after writing to plugins.cfg. After that Audacity will launch and the VST effect will be available. 2) If the user checks "Rescan for VST effects", quits Audacity, adds a VST effect to the plug-ins folder then launches Audacity, they are in a bad situation (on Mac, at least). They must either trash or edit audacity.cfg for Audacity to launch. 3) It appears to be impossible (on Mac) to get Audacity to find more than one VST effect in the plug-ins folder. There are not many VST effects that work with Mac, and even fewer free ones. If you are looking for VST effects to try this with, these are what I used: Anwidasoft DX Reverb Light Scroll down to "DX Reverb Light". There's also the Blue Cat VST effects: Download the Mac VST version. I have successfully installed and used either DX Reverb Light or Blue Cat mono Chorus, so I don't think this is a problem with these effects. -- Bill ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
Gale (Audacity Team)
|
Bill, * I'm not clear what happens in 1). You see no "scanning" dialogue, but an empty plugins.cfg is created on launch, is that correct? * We've a hang problem launching Audacity if any VST plug-ins are in the Plug-ins folder for either a fresh install, or for a launch after a fresh install where rescan was enabled? * No problem on a fresh install if no plug-ins are accessible? * Any other reports of this on the Forum? Do you mean you have used Blue Cat and Anwida in other programs than Audacity? Blue Cat had a problem before with Audacity but was fixed by Leland. Just to be sure, can you try some other free VSTs for Mac: http://www.hitsquad.com/smm/mac/PLUGINS_VST/freeware/ Is this also a problem with * /Users/<user>/Library/Audio/Plug-Ins/VST * /Library/Audio/Plug-Ins/VST where Audacity would also look? As for Windows, I can see a scanning dialogue whenever launching Audacity 1.3.10 Alpha with no or an empty plugins.cfg. The plugins.cfg is created immediately on first launch. However I only see this in my own 1.3.10 Alpha Unicode Release if I download and unpack it somewhere. The dialogue does not appear on every launch of Audacity from my build folder, despite there being no VST plug-ins accessible to it or added to the plugins.cfg. Don't really understand that at the moment. This will have to wait for Leland to come on stream, obviously. I've marked the Mac issue as a P2 for now until the extent of the problem is clear, and the Windows one as a P3. Gale | From Bill Wharrie <[hidden email]> | Thu, 22 Oct 2009 15:47:59 -0400 | Subject: [Audacity-devel] Hang when scanning for VST effects on Mac > I can reliably reproduce this bug. The hang apparently occurs only on > Mac, but the scanning on start if plugins.cfg is empty has been > reported on Windows. > http://forum.audacityteam.org/viewtopic.php?f=16&t=14801 > > Audacity 1.3.10 alpha Oct 21 2009 Mac > G5 dual 2 GHz, OSX 10.5.8 > Virgin install, with Portable Settings folder > > Note: I used the Portable Settings folder so I could do these tests > without messing up my working installation of 1.3.9. I did do test #6 > without the portable settings folder and simulating a virgin install > and the results were the same. I assume (rightly, I hope) that this > demonstrates that using the portable settings folder was not a factor > in the results. > > Sorry if this is too long. I tried to hit every case. > > 1) -- Effect of "Rescan VST effects" with no VST effects in the plug- > ins folder > Launch Audacity > Check "Rescan VST effects" > Quit Audacity > Launch Audacity - OK > Check "Rescan VST effects" > Quit Audacity > > 2) -- Effect of "Rescan VST effects" with one VST effect in the plug- > ins folder > Add a VST effect to the plug-ins folder > Launch Audacity - hangs > Notes: > - a second Audacity icon briefly appears in the Dock on launch when a > hang occurs. > - you cannot force quit Audacity from the Dock icon, as right-clicking > on the Dock icon does not show the "Force Quit" choice. > - you can switch to Audacity, and the "Audacity > Quit Audacity" menu > item is there but it has no effect. The Help menu appears when you > switch to Audacity but is not populated. No other menus appear. > - you must use "Force Quit" from the Apple menu to force quit Audacity > - the option to rescan for VST effects is now in audacity.cfg and it > is impossible to launch Audacity without trashing that file or editing > it so that the relevant line is "Rescan=0" > > Start over: trash plugins.cfg, edit audacity.cfg to the single line > "NewPrefsInitialized =1", leave VST effect in the plug-ins folder. > > > 3) -- Effect of having one VST effect in the plug-ins folder when > plugins.cfg does not exist -- > Launch Audacity - get "Language" prompt, then Audacity hangs, as above. > Force Quit Audacity > Notes: > - the "Rescan" option was not active since audacity.cfg had been cleared > - after force quit, plugins.cfg contains information about the VST > effect > - after force quit, audacity.cfg has not been altered > > 4) -- Effect of having one VST effect in the plug-ins folder when > plugins.cfg exists but is empty -- > Edit plugins.cfg, clearing all content, then save > Leave the VST effect in the plug-ins folder > Launch Audacity - hangs, as above > Force quit Audacity. > Notes: > - identical to case when plugins.cfg did not exist. > > 5a) -- Effect of adding one VST effect to the plug-ins folder, then > later adding another -- > Start over: trash plugins.cfg, edit audacity.cfg to the single line > "NewPrefsInitialized =1", remove VST effect from the plug-ins folder. > > Launch Audacity - get "Language" prompt, launches OK > Check "Rescan VST Efffects" > Quit Audacity > Add VST effect to the plug-ins folder > Launch Audacity - hangs as above > Force Quit Audacity > Launch Audacity - hangs, as above > - the option to rescan for VST effects is now in audacity.cfg and it > is impossible to launch Audacity without trashing that file or editing > it so that the relevant line is "Rescan=0" > Edit audacity.cfg setting "Rescan=0" and save > Launch Audacity - OK, and the VST effect appears in the Effect menu > > 5b)-- Now test if we can add another VST effect -- > Check "Rescan VST Efffects" > Quit Audacity > Add another VST effect to the plug-ins folder > Launch Audacity - hangs > Force Quit Audacity > - the newly-added VST effect is not in plugins.cfg > > 6) -- Will Audacity pick up two newly-added VST effects? -- > Start over: trash plugins.cfg, edit audacity.cfg to the single line > "NewPrefsInitialized =1", leave both VST effects in the plug-ins folder. > Launch Audacity - hangs, as above > Force Quit Audacity > - plugins.cfg contains info for only one VST effect, although there > were two in the plug-ins folder. > > Conclusions: > > 1) If plugins.cfg does not exist or plugins.cfg is empty then Audacity > does a scan for VST effects. If it finds one, it hangs (on Mac, not > Windows), but not after writing to plugins.cfg. After that Audacity > will launch and the VST effect will be available. > > 2) If the user checks "Rescan for VST effects", quits Audacity, adds a > VST effect to the plug-ins folder then launches Audacity, they are in > a bad situation (on Mac, at least). They must either trash or edit > audacity.cfg for Audacity to launch. > > 3) It appears to be impossible (on Mac) to get Audacity to find more > than one VST effect in the plug-ins folder. > > There are not many VST effects that work with Mac, and even fewer free > ones. If you are looking for VST effects to try this with, these are > what I used: > Anwidasoft DX Reverb Light > http://www.anwida.com/download.asp?pt=12 > Scroll down to "DX Reverb Light". > There's also the Blue Cat VST effects: > http://www.bluecataudio.com/Products/Bundle_FreewarePack/ > Download the Mac VST version. > > I have successfully installed and used either DX Reverb Light or Blue > Cat mono Chorus, so I don't think this is a problem with these effects. > > -- Bill > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Bill Wharrie
|
On 24-Oct-09, at 5:45 AM, Gale Andrews wrote: > > Bill, > > * I'm not clear what happens in 1). You see no "scanning" dialogue, > but an empty plugins.cfg is created on launch, is that correct? I never see a scanning dialog, even when I check "Rescan". Yes, plugins.cfg is created on first launch, before the hang. I assume the scan is taking place since I get the hang in the situation where plugins.cfg does not exist or is empty and there is a VST plugin in the plug-ins folder - in that case info about the plugin is added to plugins.cfg. Test #1 was to demonstrate that either on a fresh launch or with Rescan checked there is no hang if Audacity does not find a VST plugin to add to plugins.cfg. > > * We've a hang problem launching Audacity if any VST plug-ins > are in the Plug-ins folder for either a fresh install, or for a > launch after a fresh install where rescan was enabled? Or if plugins.cfg is empty. Or if Rescan is checked and a second VST effect is added after the first one has been detected. > > * No problem on a fresh install if no plug-ins are accessible? Yes. > > * Any other reports of this on the Forum? Only that one report on Windows. He was seeing the rescan dialog. The rescan on launch went away after he added one VST effect to the plug- ins folder. > > Do you mean you have used Blue Cat and Anwida in other programs > than Audacity? Blue Cat had a problem before with Audacity but was > fixed by Leland. Just to be sure, can you try some other free VSTs > for Mac: > http://www.hitsquad.com/smm/mac/PLUGINS_VST/freeware/ I successfully used the plugins in Audio Hijack Pro. > > Is this also a problem with > > * /Users/<user>/Library/Audio/Plug-Ins/VST > > * /Library/Audio/Plug-Ins/VST > > where Audacity would also look? Yes. > > As for Windows, I can see a scanning dialogue whenever launching > Audacity 1.3.10 Alpha with no or an empty plugins.cfg. The plugins.cfg > is created immediately on first launch. However I only see this in my > own 1.3.10 Alpha Unicode Release if I download and unpack it > somewhere. > The dialogue does not appear on every launch of Audacity from my build > folder, despite there being no VST plug-ins accessible to it or > added to > the plugins.cfg. Don't really understand that at the moment. Hmmm ... yes, strange. > > This will have to wait for Leland to come on stream, obviously. I've > marked the Mac issue as a P2 for now until the extent of the problem > is clear, and the Windows one as a P3. Thanks. I could ask Koz to test for this. I also get the behaviour with the 1.3.9 beta release. In the Mac Activity Monitor (which is the unix command 'top' wrapped in a GUI), I have a button labelled "Sample Process". When I click this button and look at the report it produces I see some strange things in the calling tree (if that is the right term). I could attach that report to an email to the list if that would be useful to anyone. -- Bill > > > > > Gale > > > > | From Bill Wharrie <[hidden email]> > | Thu, 22 Oct 2009 15:47:59 -0400 > | Subject: [Audacity-devel] Hang when scanning for VST effects on Mac >> I can reliably reproduce this bug. The hang apparently occurs only on >> Mac, but the scanning on start if plugins.cfg is empty has been >> reported on Windows. >> http://forum.audacityteam.org/viewtopic.php?f=16&t=14801 >> >> Audacity 1.3.10 alpha Oct 21 2009 Mac >> G5 dual 2 GHz, OSX 10.5.8 >> Virgin install, with Portable Settings folder >> >> Note: I used the Portable Settings folder so I could do these tests >> without messing up my working installation of 1.3.9. I did do test #6 >> without the portable settings folder and simulating a virgin install >> and the results were the same. I assume (rightly, I hope) that this >> demonstrates that using the portable settings folder was not a factor >> in the results. >> >> Sorry if this is too long. I tried to hit every case. >> >> 1) -- Effect of "Rescan VST effects" with no VST effects in the plug- >> ins folder >> Launch Audacity >> Check "Rescan VST effects" >> Quit Audacity >> Launch Audacity - OK >> Check "Rescan VST effects" >> Quit Audacity >> >> 2) -- Effect of "Rescan VST effects" with one VST effect in the plug- >> ins folder >> Add a VST effect to the plug-ins folder >> Launch Audacity - hangs >> Notes: >> - a second Audacity icon briefly appears in the Dock on launch when a >> hang occurs. >> - you cannot force quit Audacity from the Dock icon, as right- >> clicking >> on the Dock icon does not show the "Force Quit" choice. >> - you can switch to Audacity, and the "Audacity > Quit Audacity" menu >> item is there but it has no effect. The Help menu appears when you >> switch to Audacity but is not populated. No other menus appear. >> - you must use "Force Quit" from the Apple menu to force quit >> Audacity >> - the option to rescan for VST effects is now in audacity.cfg and it >> is impossible to launch Audacity without trashing that file or >> editing >> it so that the relevant line is "Rescan=0" >> >> Start over: trash plugins.cfg, edit audacity.cfg to the single line >> "NewPrefsInitialized =1", leave VST effect in the plug-ins folder. >> >> >> 3) -- Effect of having one VST effect in the plug-ins folder when >> plugins.cfg does not exist -- >> Launch Audacity - get "Language" prompt, then Audacity hangs, as >> above. >> Force Quit Audacity >> Notes: >> - the "Rescan" option was not active since audacity.cfg had been >> cleared >> - after force quit, plugins.cfg contains information about the VST >> effect >> - after force quit, audacity.cfg has not been altered >> >> 4) -- Effect of having one VST effect in the plug-ins folder when >> plugins.cfg exists but is empty -- >> Edit plugins.cfg, clearing all content, then save >> Leave the VST effect in the plug-ins folder >> Launch Audacity - hangs, as above >> Force quit Audacity. >> Notes: >> - identical to case when plugins.cfg did not exist. >> >> 5a) -- Effect of adding one VST effect to the plug-ins folder, then >> later adding another -- >> Start over: trash plugins.cfg, edit audacity.cfg to the single line >> "NewPrefsInitialized =1", remove VST effect from the plug-ins folder. >> >> Launch Audacity - get "Language" prompt, launches OK >> Check "Rescan VST Efffects" >> Quit Audacity >> Add VST effect to the plug-ins folder >> Launch Audacity - hangs as above >> Force Quit Audacity >> Launch Audacity - hangs, as above >> - the option to rescan for VST effects is now in audacity.cfg and it >> is impossible to launch Audacity without trashing that file or >> editing >> it so that the relevant line is "Rescan=0" >> Edit audacity.cfg setting "Rescan=0" and save >> Launch Audacity - OK, and the VST effect appears in the Effect menu >> >> 5b)-- Now test if we can add another VST effect -- >> Check "Rescan VST Efffects" >> Quit Audacity >> Add another VST effect to the plug-ins folder >> Launch Audacity - hangs >> Force Quit Audacity >> - the newly-added VST effect is not in plugins.cfg >> >> 6) -- Will Audacity pick up two newly-added VST effects? -- >> Start over: trash plugins.cfg, edit audacity.cfg to the single line >> "NewPrefsInitialized =1", leave both VST effects in the plug-ins >> folder. >> Launch Audacity - hangs, as above >> Force Quit Audacity >> - plugins.cfg contains info for only one VST effect, although there >> were two in the plug-ins folder. >> >> Conclusions: >> >> 1) If plugins.cfg does not exist or plugins.cfg is empty then >> Audacity >> does a scan for VST effects. If it finds one, it hangs (on Mac, not >> Windows), but not after writing to plugins.cfg. After that Audacity >> will launch and the VST effect will be available. >> >> 2) If the user checks "Rescan for VST effects", quits Audacity, >> adds a >> VST effect to the plug-ins folder then launches Audacity, they are in >> a bad situation (on Mac, at least). They must either trash or edit >> audacity.cfg for Audacity to launch. >> >> 3) It appears to be impossible (on Mac) to get Audacity to find more >> than one VST effect in the plug-ins folder. >> >> There are not many VST effects that work with Mac, and even fewer >> free >> ones. If you are looking for VST effects to try this with, these are >> what I used: >> Anwidasoft DX Reverb Light >> http://www.anwida.com/download.asp?pt=12 >> Scroll down to "DX Reverb Light". >> There's also the Blue Cat VST effects: >> http://www.bluecataudio.com/Products/Bundle_FreewarePack/ >> Download the Mac VST version. >> >> I have successfully installed and used either DX Reverb Light or Blue >> Cat mono Chorus, so I don't think this is a problem with these >> effects. >> >> -- Bill >> > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Bill Wharrie
|
In reply to this post
by Bill Wharrie
Some javascript/style in this post has been disabled (why?)
On 22-Oct-09, at 3:47 PM, Bill Wharrie wrote:
I just tested this on: - an iMac Core 2 Duo 2 GHz running OSX 10.4.11 - a PowerBook G4 1.67 GHz running OSX 10.4.11 and got very different behaviour. Using 1.3.9 beta. Edit audacity.cfg to just the line "NewPrefsInitialized=1". plugins.cfg is empty. Put a Blue Cat VST effect in Audacity's plug-ins folder. Launch Audacity - get "language" dialog - wait a few seconds then click "OK" - second Audacity icon flashes briefly in the Dock - dialog pops up that Audacity has quit unexpectedly - click "Close" - Audacity opens OK! - get welcome dialog. - Audacity does not pick up the VST effect in Audacity's plug-ins folder - plugins.cfg remains empty Check "Rescan VST effects" in Effects Preferences Quit Audacity Launch Audacity - identical behaviour to the above, except no language dialog. Quit Audacity - Rescan=0 in audacity.cfg Launch Audacity - identical behaviour to the above On the PowerBook running 1.3.10 alpha Oct 24 2009, identical behaviour. * As long as the VST effect is in Audacity's plug-ins folder the "Unexpectedly quit" dialog will appear every time you start Audacity. * Behaviour is different for 10.4.11 versus 10.5.8 * With 10.4.11, behaviour is the same on PPC and Intel. -- Bill ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
Leland (Audacity Team)
|
In reply to this post
by Bill Wharrie
Bill,
I've committed a patch from Ed that may fix this issue. Do you build yourself or use the nightlies? Leland Bill Wharrie wrote: > I can reliably reproduce this bug. The hang apparently occurs only on > Mac, but the scanning on start if plugins.cfg is empty has been reported > on Windows. > http://forum.audacityteam.org/viewtopic.php?f=16&t=14801 > <http://forum.audacityteam.org/viewtopic.php?f=16&t=14801> > > Audacity 1.3.10 alpha Oct 21 2009 Mac > G5 dual 2 GHz, OSX 10.5.8 > Virgin install, with Portable Settings folder > > Note: I used the Portable Settings folder so I could do these tests > without messing up my working installation of 1.3.9. I did do test #6 > without the portable settings folder and simulating a virgin install and > the results were the same. I assume (rightly, I hope) that this > demonstrates that using the portable settings folder was not a factor in > the results. > > Sorry if this is too long. I tried to hit every case. > > 1) -- Effect of "Rescan VST effects" with no VST effects in the plug-ins > folder > Launch Audacity > Check "Rescan VST effects" > Quit Audacity > Launch Audacity - OK > Check "Rescan VST effects" > Quit Audacity > > 2) -- Effect of "Rescan VST effects" with one VST effect in the plug-ins > folder > Add a VST effect to the plug-ins folder > Launch Audacity - hangs > Notes: > - a second Audacity icon briefly appears in the Dock on launch when a > hang occurs. > - you cannot force quit Audacity from the Dock icon, as right-clicking > on the Dock icon does not show the "Force Quit" choice. > - you can switch to Audacity, and the "Audacity > Quit Audacity" menu > item is there but it has no effect. The Help menu appears when you > switch to Audacity but is not populated. No other menus appear. > - you must use "Force Quit" from the Apple menu to force quit Audacity > - the option to rescan for VST effects is now in audacity.cfg and it is > impossible to launch Audacity without trashing that file or editing it > so that the relevant line is "Rescan=0" > > Start over: trash plugins.cfg, edit audacity.cfg to the single line > "NewPrefsInitialized =1", leave VST effect in the plug-ins folder. > > 3) -- Effect of having one VST effect in the plug-ins folder when > plugins.cfg does not exist -- > Launch Audacity - get "Language" prompt, then Audacity hangs, as above. > Force Quit Audacity > Notes: > - the "Rescan" option was not active since audacity.cfg had been cleared > - after force quit, plugins.cfg contains information about the VST effect > - after force quit, audacity.cfg has not been altered > > 4) -- Effect of having one VST effect in the plug-ins folder when > plugins.cfg exists but is empty -- > Edit plugins.cfg, clearing all content, then save > Leave the VST effect in the plug-ins folder > Launch Audacity - hangs, as above > Force quit Audacity. > Notes: > - identical to case when plugins.cfg did not exist. > > 5a) -- Effect of adding one VST effect to the plug-ins folder, then > later adding another -- > Start over: trash plugins.cfg, edit audacity.cfg to the single line > "NewPrefsInitialized =1", remove VST effect from the plug-ins folder. > > Launch Audacity - get "Language" prompt, launches OK > Check "Rescan VST Efffects" > Quit Audacity > Add VST effect to the plug-ins folder > Launch Audacity - hangs as above > Force Quit Audacity > Launch Audacity - hangs, as above > - the option to rescan for VST effects is now in audacity.cfg and it is > impossible to launch Audacity without trashing that file or editing it > so that the relevant line is "Rescan=0" > Edit audacity.cfg setting "Rescan=0" and save > Launch Audacity - OK, and the VST effect appears in the Effect menu > > 5b)-- Now test if we can add another VST effect -- > Check "Rescan VST Efffects" > Quit Audacity > Add another VST effect to the plug-ins folder > Launch Audacity - hangs > Force Quit Audacity > - the newly-added VST effect is not in plugins.cfg > > 6) -- Will Audacity pick up two newly-added VST effects? -- > Start over: trash plugins.cfg, edit audacity.cfg to the single line > "NewPrefsInitialized =1", leave both VST effects in the plug-ins folder. > Launch Audacity - hangs, as above > Force Quit Audacity > - plugins.cfg contains info for only one VST effect, although there were > two in the plug-ins folder. > > Conclusions: > > 1) If plugins.cfg does not exist or plugins.cfg is empty then Audacity > does a scan for VST effects. If it finds one, it hangs (on Mac, not > Windows), but not after writing to plugins.cfg. After that Audacity will > launch and the VST effect will be available. > > 2) If the user checks "Rescan for VST effects", quits Audacity, adds a > VST effect to the plug-ins folder then launches Audacity, they are in a > bad situation (on Mac, at least). They must either trash or edit > audacity.cfg for Audacity to launch. > > 3) It appears to be impossible (on Mac) to get Audacity to find more > than one VST effect in the plug-ins folder. > > There are not many VST effects that work with Mac, and even fewer free > ones. If you are looking for VST effects to try this with, these are > what I used: > Anwidasoft DX Reverb Light > http://www.anwida.com/download.asp?pt=12 > Scroll down to "DX Reverb Light". > There's also the Blue Cat VST effects: > http://www.bluecataudio.com/Products/Bundle_FreewarePack/ > Download the Mac VST version. > > I have successfully installed and used either DX Reverb Light or Blue > Cat mono Chorus, so I don't think this is a problem with these effects. > > -- Bill > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > > > ------------------------------------------------------------------------ > > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Bill Wharrie
|
On 7-Nov-09, at 11:23 PM, Leland wrote: > Bill, > > I've committed a patch from Ed that may fix this issue. Do you build > yourself or use the nightlies? > > Leland > Leland: I use the nightlies. At this point it looks like I'll have to wait until Monday morning to test it. -- Bill ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Leland (Audacity Team)
|
Bill Wharrie wrote:
> On 7-Nov-09, at 11:23 PM, Leland wrote: > >> Bill, >> >> I've committed a patch from Ed that may fix this issue. Do you build >> yourself or use the nightlies? >> >> Leland >> > > Leland: > I use the nightlies. At this point it looks like I'll have to wait > until Monday morning to test it. > Thanks, Leland ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Bill Wharrie
|
In reply to this post
by Leland (Audacity Team)
I hope this is clear in other mail clients. My original tests are quoted two levels deep. My comments on the Nov 9 Mac build are not quoted. The short answer is that this is not fixed. Scanning on startup when plugins.cfg does not exist or is empty appears to still be happening (although I never see the dialog - is this a symptom?). The hang when Audacity finds a VST plug-in still occurs. However, some things have changed. In step 5a) it appears that audacity.cfg has not been completely initialized, and the [Window] parameters cause Audacity to subsequently launch with an invisible window. Quitting and re- launching clears this and Audacity launches OK and presents a visible empty project window. In step 5b) Audacity *does* pick up the second VST effect added to the plug-ins folder, even though it still hangs. > I've committed a patch from Ed that may fix this issue. > > Leland > > Bill Wharrie wrote: >> I can reliably reproduce this bug. The hang apparently occurs only on >> Mac, but the scanning on start if plugins.cfg is empty has been >> reported >> on Windows. >> http://forum.audacityteam.org/viewtopic.php?f=16&t=14801 >> <http://forum.audacityteam.org/viewtopic.php?f=16&t=14801> >> >> Audacity 1.3.10 alpha Oct 21 2009 Mac Now Audacity 1.3.10 alpha Nov 9 2009 Mac >> G5 dual 2 GHz, OSX 10.5.8 >> Virgin install, with Portable Settings folder >> >> Note: I used the Portable Settings folder so I could do these tests >> without messing up my working installation of 1.3.9. >> >> Sorry if this is too long. I tried to hit every case. >> >> 1) -- Effect of "Rescan VST effects" with no VST effects in the >> plug-ins >> folder >> Launch Audacity >> Check "Rescan VST effects" >> Quit Audacity >> Launch Audacity - OK >> Check "Rescan VST effects" >> Quit Audacity [The point of step 1 was to demonstrate that launching with "Rescan VST Effects" checked does not cause a hang if there are no VST effects to find.] No change, which is fine. After the first restart "Rescan VST effects" is unchecked. Note that "Rescan VST effects" is active for the next launch. >> >> 2) -- Effect of "Rescan VST effects" with one VST effect in the >> plug-ins >> folder >> Add a VST effect to the plug-ins folder >> Launch Audacity - hangs >> Notes: >> - a second Audacity icon briefly appears in the Dock on launch when a >> hang occurs. >> - you cannot force quit Audacity from the Dock icon, as right- >> clicking >> on the Dock icon does not show the "Force Quit" choice. >> - you can switch to Audacity, and the "Audacity > Quit Audacity" menu >> item is there but it has no effect. The Help menu appears when you >> switch to Audacity but is not populated. No other menus appear. >> - you must use "Force Quit" from the Apple menu to force quit >> Audacity >> - the option to rescan for VST effects is now in audacity.cfg and >> it is >> impossible to launch Audacity without trashing that file or editing >> it >> so that the relevant line is "Rescan=0" Identical behaviour. >> >> Start over: trash plugins.cfg, edit audacity.cfg to the single line >> "NewPrefsInitialized =1", leave VST effect in the plug-ins folder. >> >> 3) -- Effect of having one VST effect in the plug-ins folder when >> plugins.cfg does not exist -- >> Launch Audacity - get "Language" prompt, then Audacity hangs, as >> above. >> Force Quit Audacity >> Notes: >> - the "Rescan" option was not active since audacity.cfg had been >> cleared >> - after force quit, plugins.cfg contains information about the VST >> effect >> - after force quit, audacity.cfg has not been altered Identical behaviour. > >> >> 4) -- Effect of having one VST effect in the plug-ins folder when >> plugins.cfg exists but is empty -- >> Edit plugins.cfg, clearing all content, then save >> Leave the VST effect in the plug-ins folder >> Launch Audacity - hangs, as above >> Force quit Audacity. >> Notes: >> - identical to case when plugins.cfg did not exist. Identical behaviour. > >> >> 5a) -- Effect of adding one VST effect to the plug-ins folder, then >> later adding another -- >> Start over: trash plugins.cfg, edit audacity.cfg to the single line >> "NewPrefsInitialized =1", remove VST effect from the plug-ins folder. >> >> Launch Audacity - get "Language" prompt, launches OK >> Check "Rescan VST Efffects" >> Quit Audacity >> Add VST effect to the plug-ins folder >> Launch Audacity - hangs as above >> Force Quit Audacity >> Launch Audacity - hangs, as above - Force Quit >> - the option to rescan for VST effects is now in audacity.cfg and >> it is >> impossible to launch Audacity without trashing that file or editing >> it >> so that the relevant line is "Rescan=0" >> Edit audacity.cfg setting "Rescan=0" and save >> Launch Audacity - OK, and the VST effect appears in the Effect menu Now this is odd, the empty project window does not appear to open, but it is there in the Window menu. The How to Get Help screen appears as per normal. Clicking File > New adds another item to the Window menu but no window is visible. All the menus appear to be working. You can Generate a chirp. The window is there, but you can't see it. If you click "Window > Minimize" a blank window appears to be added to the Dock. Retrieving this window from the Dock does not make it appear. ** I went back to 5a) and tried this again, and found this at the end of audacity.cfg when editing to set "Rescan=0": [Window] X=50 Y=22 Width=600 Height=455 Maximized=0 Normal_X=0 Normal_Y=0 Normal_Width=0 Normal_Height=0 Iconized=0 --------------- I also tried test 5a) with 1.3.9. The behaviour was the same as 1.3.10-alpha-Oct 21. That is, no invisible window. The [Window] section of audacity.cfg looks like this in 1.3.9: [Window] X=50 Y=22 Width=600 Height=400 Maximized=0 ----------------- Quit Audacity Launch Audacity - OK, empty project window appears, and the VST effect appears in the Effect menu. At the end of audacity.cfg I find: [Window] X=51 Y=22 Width=600 Height=455 Maximized=0 Normal_X=51 Normal_Y=22 Normal_Width=600 Normal_Height=455 Iconized=0 >> >> 5b)-- Now test if we can add another VST effect -- >> Check "Rescan VST Efffects" >> Quit Audacity >> Add another VST effect to the plug-ins folder >> Launch Audacity - hangs >> Force Quit Audacity >> - the newly-added VST effect is not in plugins.cfg Different. The info for the two VST effects is now in plugins.cfg, even though the hang occurred. 5c) Edit audacity.cfg setting "Rescan=0" Launch Audacity - OK, and both VST effects are in the Effect menu Quit Audacity >> >> 6) -- Will Audacity pick up two newly-added VST effects? -- >> Start over: trash plugins.cfg, edit audacity.cfg to the single line >> "NewPrefsInitialized =1", leave both VST effects in the plug-ins >> folder. >> Launch Audacity - hangs, as above >> Force Quit Audacity >> - plugins.cfg contains info for only one VST effect, although there >> were >> two in the plug-ins folder. Identical behaviour. -- Bill ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
Ed Musgrove-2
|
Something similar happened to me when I installed Windows 7.
One of the very first things I did was grab the current CVS HEAD and compile it. I launched Audacity then immediately closed it (I wanted to see what a brand-new Windows 7 version configuration file was). I had not installed lame, FFmpeg nor FFTW before I ran Audacity for the first time! Now I install "external" libraries: lame FFmpeg for audacity FFTW (in audacity/Plug-Ins) restart audacity, it appears to get lost, there is no project window. In each of the above case I used the installer as provided on the library's Internet homepage. I reformatted my C: hard drive, reinstalled Windows 7, launched Audacity then went to the preferences panel tab "libraries" and allowed Audacity to download then find these. Thereafter I had no problems. --Ed > -----Original Message----- > From: Bill Wharrie [mailto:[hidden email]] > Sent: Sunday, November 08, 2009 9:54 PM > To: [hidden email] > Subject: Re: [Audacity-devel] Hang when scanning for VST effects on Mac > > > I hope this is clear in other mail clients. My original tests are quoted two > levels deep. My comments on the Nov 9 Mac build are not quoted. > > The short answer is that this is not fixed. Scanning on startup when > plugins.cfg does not exist or is empty appears to still be happening (although > I never see the dialog - is this a symptom?). The hang when Audacity finds a > VST plug-in still occurs. > > However, some things have changed. > > In step 5a) it appears that audacity.cfg has not been completely initialized, > and the [Window] parameters cause Audacity to subsequently launch with > an invisible window. Quitting and re- launching clears this and Audacity > launches OK and presents a visible empty project window. > > In step 5b) Audacity *does* pick up the second VST effect added to the plug- > ins folder, even though it still hangs. > > > I've committed a patch from Ed that may fix this issue. > > > > Leland > > > > Bill Wharrie wrote: > >> I can reliably reproduce this bug. The hang apparently occurs only on > >> Mac, but the scanning on start if plugins.cfg is empty has been > >> reported on Windows. > >> http://forum.audacityteam.org/viewtopic.php?f=16&t=14801 > >> <http://forum.audacityteam.org/viewtopic.php?f=16&t=14801> > >> > >> Audacity 1.3.10 alpha Oct 21 2009 Mac > > > Now Audacity 1.3.10 alpha Nov 9 2009 Mac > > > >> G5 dual 2 GHz, OSX 10.5.8 > >> Virgin install, with Portable Settings folder > >> > >> Note: I used the Portable Settings folder so I could do these tests > >> without messing up my working installation of 1.3.9. > >> > >> Sorry if this is too long. I tried to hit every case. > >> > >> 1) -- Effect of "Rescan VST effects" with no VST effects in the > >> plug-ins folder Launch Audacity Check "Rescan VST effects" > >> Quit Audacity > >> Launch Audacity - OK > >> Check "Rescan VST effects" > >> Quit Audacity > > [The point of step 1 was to demonstrate that launching with "Rescan VST > Effects" checked does not cause a hang if there are no VST effects to > > No change, which is fine. After the first restart "Rescan VST effects" > is unchecked. > > Note that "Rescan VST effects" is active for the next launch. > > > >> > >> 2) -- Effect of "Rescan VST effects" with one VST effect in the > >> plug-ins folder Add a VST effect to the plug-ins folder Launch > >> Audacity - hangs > >> Notes: > >> - a second Audacity icon briefly appears in the Dock on launch when a > >> hang occurs. > >> - you cannot force quit Audacity from the Dock icon, as right- > >> clicking on the Dock icon does not show the "Force Quit" choice. > >> - you can switch to Audacity, and the "Audacity > Quit Audacity" menu > >> item is there but it has no effect. The Help menu appears when you > >> switch to Audacity but is not populated. No other menus appear. > >> - you must use "Force Quit" from the Apple menu to force quit > >> Audacity > >> - the option to rescan for VST effects is now in audacity.cfg and it > >> is impossible to launch Audacity without trashing that file or > >> editing it so that the relevant line is "Rescan=0" > > > Identical behaviour. > > > >> > >> Start over: trash plugins.cfg, edit audacity.cfg to the single line > >> "NewPrefsInitialized =1", leave VST effect in the plug-ins folder. > >> > >> 3) -- Effect of having one VST effect in the plug-ins folder when > >> plugins.cfg does not exist -- Launch Audacity - get "Language" > >> prompt, then Audacity hangs, as above. > >> Force Quit Audacity > >> Notes: > >> - the "Rescan" option was not active since audacity.cfg had been > >> cleared > >> - after force quit, plugins.cfg contains information about the VST > >> effect > >> - after force quit, audacity.cfg has not been altered > > > Identical behaviour. > > > > > >> > >> 4) -- Effect of having one VST effect in the plug-ins folder when > >> plugins.cfg exists but is empty -- Edit plugins.cfg, clearing all > >> content, then save Leave the VST effect in the plug-ins folder Launch > >> Audacity - hangs, as above Force quit Audacity. > >> Notes: > >> - identical to case when plugins.cfg did not exist. > > > Identical behaviour. > > > > > >> > >> 5a) -- Effect of adding one VST effect to the plug-ins folder, then > >> later adding another -- Start over: trash plugins.cfg, edit > >> audacity.cfg to the single line "NewPrefsInitialized =1", remove VST > >> effect from the plug-ins folder. > >> > >> Launch Audacity - get "Language" prompt, launches OK Check "Rescan > >> VST Efffects" > >> Quit Audacity > >> Add VST effect to the plug-ins folder Launch Audacity - hangs as > >> above Force Quit Audacity Launch Audacity - hangs, as above - Force > >> Quit > >> - the option to rescan for VST effects is now in audacity.cfg and it > >> is impossible to launch Audacity without trashing that file or > >> editing it so that the relevant line is "Rescan=0" > >> Edit audacity.cfg setting "Rescan=0" and save > ** see note below > >> Launch Audacity - OK, and the VST effect appears in the Effect menu > > > Now this is odd, the empty project window does not appear to open, but it > there in the Window menu. The How to Get Help screen appears as per > normal. Clicking File > New adds another item to the Window menu but no > window is visible. All the menus appear to be working. You can Generate a > chirp. The window is there, but you can't see it. If you click "Window > > Minimize" a blank window appears to be added to the Dock. Retrieving this > window from the Dock does not make it appear. > > ** I went back to 5a) and tried this again, and found this at the end of > audacity.cfg when editing to set "Rescan=0": > [Window] > X=50 > Y=22 > Width=600 > Height=455 > Maximized=0 > Normal_X=0 > Normal_Y=0 > Normal_Width=0 > Normal_Height=0 > Iconized=0 > > --------------- > I also tried test 5a) with 1.3.9. > The behaviour was the same as 1.3.10-alpha-Oct 21. That is, no invisible > window. > The [Window] section of audacity.cfg looks like this in 1.3.9: > > [Window] > X=50 > Y=22 > Width=600 > Height=400 > Maximized=0 > ----------------- > > Quit Audacity > Launch Audacity - OK, empty project window appears, and the VST effect > appears in the Effect menu. > At the end of audacity.cfg I find: > [Window] > X=51 > Y=22 > Width=600 > Height=455 > Maximized=0 > Normal_X=51 > Normal_Y=22 > Normal_Width=600 > Normal_Height=455 > Iconized=0 > > > >> > >> 5b)-- Now test if we can add another VST effect -- Check "Rescan VST > >> Efffects" > >> Quit Audacity > >> Add another VST effect to the plug-ins folder Launch Audacity - hangs > >> Force Quit Audacity > >> - the newly-added VST effect is not in plugins.cfg > > Different. The info for the two VST effects is now in plugins.cfg, even > the hang occurred. > > 5c) Edit audacity.cfg setting "Rescan=0" > Launch Audacity - OK, and both VST effects are in the Effect menu Quit > Audacity > > >> > >> 6) -- Will Audacity pick up two newly-added VST effects? -- Start > >> over: trash plugins.cfg, edit audacity.cfg to the single line > >> "NewPrefsInitialized =1", leave both VST effects in the plug-ins > >> folder. > >> Launch Audacity - hangs, as above > >> Force Quit Audacity > >> - plugins.cfg contains info for only one VST effect, although there > >> were two in the plug-ins folder. > > Identical behaviour. > > -- Bill > > > -- > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with Crystal > Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Leland (Audacity Team)
|
In reply to this post
by Bill Wharrie
Bill,
Do you ever get any VST effects to actually load? I can (and can't reproduce your issues below) on Intel/OSX10.6, but I can't get ANY VST plugin to load on my G5/OSX10.4 machine. I don't hang and I see where the plugin actually gets called (some debugging messages), but they never appear in the Effects menu. There is definitely something fishy afoot... Leland Bill Wharrie wrote: > I hope this is clear in other mail clients. My original tests are > quoted two levels deep. My comments on the Nov 9 Mac build are not > quoted. > > The short answer is that this is not fixed. Scanning on startup when > plugins.cfg does not exist or is empty appears to still be happening > (although I never see the dialog - is this a symptom?). The hang when > Audacity finds a VST plug-in still occurs. > > However, some things have changed. > > In step 5a) it appears that audacity.cfg has not been completely > initialized, and the [Window] parameters cause Audacity to > subsequently launch with an invisible window. Quitting and re- > launching clears this and Audacity launches OK and presents a visible > empty project window. > > In step 5b) Audacity *does* pick up the second VST effect added to the > plug-ins folder, even though it still hangs. > >> I've committed a patch from Ed that may fix this issue. >> >> Leland >> >> Bill Wharrie wrote: >>> I can reliably reproduce this bug. The hang apparently occurs only on >>> Mac, but the scanning on start if plugins.cfg is empty has been >>> reported >>> on Windows. >>> http://forum.audacityteam.org/viewtopic.php?f=16&t=14801 >>> <http://forum.audacityteam.org/viewtopic.php?f=16&t=14801> >>> >>> Audacity 1.3.10 alpha Oct 21 2009 Mac > > > Now Audacity 1.3.10 alpha Nov 9 2009 Mac > > >>> G5 dual 2 GHz, OSX 10.5.8 >>> Virgin install, with Portable Settings folder >>> >>> Note: I used the Portable Settings folder so I could do these tests >>> without messing up my working installation of 1.3.9. >>> >>> Sorry if this is too long. I tried to hit every case. >>> >>> 1) -- Effect of "Rescan VST effects" with no VST effects in the >>> plug-ins >>> folder >>> Launch Audacity >>> Check "Rescan VST effects" >>> Quit Audacity >>> Launch Audacity - OK >>> Check "Rescan VST effects" >>> Quit Audacity > > [The point of step 1 was to demonstrate that launching with "Rescan > VST Effects" checked does not cause a hang if there are no VST effects > to find.] > > No change, which is fine. After the first restart "Rescan VST effects" > is unchecked. > > Note that "Rescan VST effects" is active for the next launch. > > >>> 2) -- Effect of "Rescan VST effects" with one VST effect in the >>> plug-ins >>> folder >>> Add a VST effect to the plug-ins folder >>> Launch Audacity - hangs >>> Notes: >>> - a second Audacity icon briefly appears in the Dock on launch when a >>> hang occurs. >>> - you cannot force quit Audacity from the Dock icon, as right- >>> clicking >>> on the Dock icon does not show the "Force Quit" choice. >>> - you can switch to Audacity, and the "Audacity > Quit Audacity" menu >>> item is there but it has no effect. The Help menu appears when you >>> switch to Audacity but is not populated. No other menus appear. >>> - you must use "Force Quit" from the Apple menu to force quit >>> Audacity >>> - the option to rescan for VST effects is now in audacity.cfg and >>> it is >>> impossible to launch Audacity without trashing that file or editing >>> it >>> so that the relevant line is "Rescan=0" > > > Identical behaviour. > > >>> Start over: trash plugins.cfg, edit audacity.cfg to the single line >>> "NewPrefsInitialized =1", leave VST effect in the plug-ins folder. >>> >>> 3) -- Effect of having one VST effect in the plug-ins folder when >>> plugins.cfg does not exist -- >>> Launch Audacity - get "Language" prompt, then Audacity hangs, as >>> above. >>> Force Quit Audacity >>> Notes: >>> - the "Rescan" option was not active since audacity.cfg had been >>> cleared >>> - after force quit, plugins.cfg contains information about the VST >>> effect >>> - after force quit, audacity.cfg has not been altered > > > Identical behaviour. > > >>> 4) -- Effect of having one VST effect in the plug-ins folder when >>> plugins.cfg exists but is empty -- >>> Edit plugins.cfg, clearing all content, then save >>> Leave the VST effect in the plug-ins folder >>> Launch Audacity - hangs, as above >>> Force quit Audacity. >>> Notes: >>> - identical to case when plugins.cfg did not exist. > > > Identical behaviour. > > >>> 5a) -- Effect of adding one VST effect to the plug-ins folder, then >>> later adding another -- >>> Start over: trash plugins.cfg, edit audacity.cfg to the single line >>> "NewPrefsInitialized =1", remove VST effect from the plug-ins folder. >>> >>> Launch Audacity - get "Language" prompt, launches OK >>> Check "Rescan VST Efffects" >>> Quit Audacity >>> Add VST effect to the plug-ins folder >>> Launch Audacity - hangs as above >>> Force Quit Audacity >>> Launch Audacity - hangs, as above - Force Quit >>> - the option to rescan for VST effects is now in audacity.cfg and >>> it is >>> impossible to launch Audacity without trashing that file or editing >>> it >>> so that the relevant line is "Rescan=0" >>> Edit audacity.cfg setting "Rescan=0" and save > ** see note below >>> Launch Audacity - OK, and the VST effect appears in the Effect menu > > > Now this is odd, the empty project window does not appear to open, but > it is there in the Window menu. The How to Get Help screen appears as > per normal. Clicking File > New adds another item to the Window menu > but no window is visible. All the menus appear to be working. You can > Generate a chirp. The window is there, but you can't see it. If you > click "Window > Minimize" a blank window appears to be added to the > Dock. Retrieving this window from the Dock does not make it appear. > > ** I went back to 5a) and tried this again, and found this at the end > of audacity.cfg when editing to set "Rescan=0": > [Window] > X=50 > Y=22 > Width=600 > Height=455 > Maximized=0 > Normal_X=0 > Normal_Y=0 > Normal_Width=0 > Normal_Height=0 > Iconized=0 > > --------------- > I also tried test 5a) with 1.3.9. > The behaviour was the same as 1.3.10-alpha-Oct 21. That is, no > invisible window. > The [Window] section of audacity.cfg looks like this in 1.3.9: > > [Window] > X=50 > Y=22 > Width=600 > Height=400 > Maximized=0 > ----------------- > > Quit Audacity > Launch Audacity - OK, empty project window appears, and the VST effect > appears in the Effect menu. > At the end of audacity.cfg I find: > [Window] > X=51 > Y=22 > Width=600 > Height=455 > Maximized=0 > Normal_X=51 > Normal_Y=22 > Normal_Width=600 > Normal_Height=455 > Iconized=0 > > >>> 5b)-- Now test if we can add another VST effect -- >>> Check "Rescan VST Efffects" >>> Quit Audacity >>> Add another VST effect to the plug-ins folder >>> Launch Audacity - hangs >>> Force Quit Audacity >>> - the newly-added VST effect is not in plugins.cfg > > Different. The info for the two VST effects is now in plugins.cfg, > even though the hang occurred. > > 5c) Edit audacity.cfg setting "Rescan=0" > Launch Audacity - OK, and both VST effects are in the Effect menu > Quit Audacity > >>> 6) -- Will Audacity pick up two newly-added VST effects? -- >>> Start over: trash plugins.cfg, edit audacity.cfg to the single line >>> "NewPrefsInitialized =1", leave both VST effects in the plug-ins >>> folder. >>> Launch Audacity - hangs, as above >>> Force Quit Audacity >>> - plugins.cfg contains info for only one VST effect, although there >>> were >>> two in the plug-ins folder. > > Identical behaviour. > > -- Bill > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Leland (Audacity Team)
|
Leland wrote:
> Bill, > > Do you ever get any VST effects to actually load? I can (and can't > reproduce your issues below) on Intel/OSX10.6, but I can't get ANY VST > plugin to load on my G5/OSX10.4 machine. I don't hang and I see where > the plugin actually gets called (some debugging messages), but they > never appear in the Effects menu. > > There is definitely something fishy afoot... > plugins.cfg to be stored in Library/Application Support/audacity and Library/Application Support/Audacity. Just gotta track down the different caps. Leland ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Bill Wharrie
|
In reply to this post
by Leland (Audacity Team)
On 11-Nov-09, at 1:30 AM, Leland wrote: > Bill, > > Do you ever get any VST effects to actually load? I can (and can't > reproduce your issues below) on Intel/OSX10.6, but I can't get ANY VST > plugin to load on my G5/OSX10.4 machine. I don't hang and I see where > the plugin actually gets called (some debugging messages), but they > never appear in the Effects menu. > > There is definitely something fishy afoot... > > Leland: I can get VST effects to load but only one at a time, and only after going through the hang. See steps 3, 5a, 5b and 6. It appears that Audacity has found the first *new* VST effect (alphabetically in the plug-ins folder), written the info to plugins.cfg, then hung up. Ignore all that business about the invisible window. That is a separate issue and has been solved, I believe. I can't test on 10.6. I get different behaviour on 10.4. Look for the second Audacity icon to appear briefly in the dock. From a previous email: > I just tested this on: > - an iMac Core 2 Duo 2 GHz running OSX 10.4.11 > - a PowerBook G4 1.67 GHz running OSX 10.4.11 > and got very different behaviour. Using 1.3.9 beta. > > Edit audacity.cfg to just the line "NewPrefsInitialized=1". > plugins.cfg is empty. > Put a Blue Cat VST effect in Audacity's plug-ins folder. > Launch Audacity > - get "language" dialog - wait a few seconds then click "OK" > - second Audacity icon flashes briefly in the Dock > - dialog pops up that Audacity has quit unexpectedly - click "Close" > - Audacity opens OK! - get welcome dialog. > - Audacity does not pick up the VST effect in Audacity's plug-ins > folder > - plugins.cfg remains empty > Check "Rescan VST effects" in Effects Preferences > Quit Audacity > Launch Audacity > - identical behaviour to the above, except no language dialog. > Quit Audacity > - Rescan=0 in audacity.cfg > Launch Audacity > - identical behaviour to the above > > On the PowerBook running 1.3.10 alpha Oct 24 2009, identical > behaviour. > > * As long as the VST effect is in Audacity's plug-ins folder the > "Unexpectedly quit" dialog will appear every time you start Audacity. > > * Behaviour is different for 10.4.11 versus 10.5.8 > > * With 10.4.11, behaviour is the same on PPC and Intel. > -- Bill > > Bill Wharrie wrote: >> I hope this is clear in other mail clients. My original tests are >> quoted two levels deep. My comments on the Nov 9 Mac build are not >> quoted. >> >> The short answer is that this is not fixed. Scanning on startup when >> plugins.cfg does not exist or is empty appears to still be happening >> (although I never see the dialog - is this a symptom?). The hang when >> Audacity finds a VST plug-in still occurs. >> >> However, some things have changed. >> >> In step 5a) it appears that audacity.cfg has not been completely >> initialized, and the [Window] parameters cause Audacity to >> subsequently launch with an invisible window. Quitting and re- >> launching clears this and Audacity launches OK and presents a visible >> empty project window. >> >> In step 5b) Audacity *does* pick up the second VST effect added to >> the >> plug-ins folder, even though it still hangs. >> >>> I've committed a patch from Ed that may fix this issue. >>> >>> Leland >>> >>> Bill Wharrie wrote: >>>> I can reliably reproduce this bug. The hang apparently occurs >>>> only on >>>> Mac, but the scanning on start if plugins.cfg is empty has been >>>> reported >>>> on Windows. >>>> http://forum.audacityteam.org/viewtopic.php?f=16&t=14801 >>>> <http://forum.audacityteam.org/viewtopic.php?f=16&t=14801> >>>> >>>> Audacity 1.3.10 alpha Oct 21 2009 Mac >> >> >> Now Audacity 1.3.10 alpha Nov 9 2009 Mac >> >> >>>> G5 dual 2 GHz, OSX 10.5.8 >>>> Virgin install, with Portable Settings folder >>>> >>>> Note: I used the Portable Settings folder so I could do these tests >>>> without messing up my working installation of 1.3.9. >>>> >>>> Sorry if this is too long. I tried to hit every case. >>>> >>>> 1) -- Effect of "Rescan VST effects" with no VST effects in the >>>> plug-ins >>>> folder >>>> Launch Audacity >>>> Check "Rescan VST effects" >>>> Quit Audacity >>>> Launch Audacity - OK >>>> Check "Rescan VST effects" >>>> Quit Audacity >> >> [The point of step 1 was to demonstrate that launching with "Rescan >> VST Effects" checked does not cause a hang if there are no VST >> effects >> to find.] >> >> No change, which is fine. After the first restart "Rescan VST >> effects" >> is unchecked. >> >> Note that "Rescan VST effects" is active for the next launch. >> >> >>>> 2) -- Effect of "Rescan VST effects" with one VST effect in the >>>> plug-ins >>>> folder >>>> Add a VST effect to the plug-ins folder >>>> Launch Audacity - hangs >>>> Notes: >>>> - a second Audacity icon briefly appears in the Dock on launch >>>> when a >>>> hang occurs. >>>> - you cannot force quit Audacity from the Dock icon, as right- >>>> clicking >>>> on the Dock icon does not show the "Force Quit" choice. >>>> - you can switch to Audacity, and the "Audacity > Quit Audacity" >>>> menu >>>> item is there but it has no effect. The Help menu appears when you >>>> switch to Audacity but is not populated. No other menus appear. >>>> - you must use "Force Quit" from the Apple menu to force quit >>>> Audacity >>>> - the option to rescan for VST effects is now in audacity.cfg and >>>> it is >>>> impossible to launch Audacity without trashing that file or editing >>>> it >>>> so that the relevant line is "Rescan=0" >> >> >> Identical behaviour. >> >> >>>> Start over: trash plugins.cfg, edit audacity.cfg to the single line >>>> "NewPrefsInitialized =1", leave VST effect in the plug-ins folder. >>>> >>>> 3) -- Effect of having one VST effect in the plug-ins folder when >>>> plugins.cfg does not exist -- >>>> Launch Audacity - get "Language" prompt, then Audacity hangs, as >>>> above. >>>> Force Quit Audacity >>>> Notes: >>>> - the "Rescan" option was not active since audacity.cfg had been >>>> cleared >>>> - after force quit, plugins.cfg contains information about the VST >>>> effect >>>> - after force quit, audacity.cfg has not been altered >> >> >> Identical behaviour. >> >> >>>> 4) -- Effect of having one VST effect in the plug-ins folder when >>>> plugins.cfg exists but is empty -- >>>> Edit plugins.cfg, clearing all content, then save >>>> Leave the VST effect in the plug-ins folder >>>> Launch Audacity - hangs, as above >>>> Force quit Audacity. >>>> Notes: >>>> - identical to case when plugins.cfg did not exist. >> >> >> Identical behaviour. >> >> >>>> 5a) -- Effect of adding one VST effect to the plug-ins folder, then >>>> later adding another -- >>>> Start over: trash plugins.cfg, edit audacity.cfg to the single line >>>> "NewPrefsInitialized =1", remove VST effect from the plug-ins >>>> folder. >>>> >>>> Launch Audacity - get "Language" prompt, launches OK >>>> Check "Rescan VST Efffects" >>>> Quit Audacity >>>> Add VST effect to the plug-ins folder >>>> Launch Audacity - hangs as above >>>> Force Quit Audacity >>>> Launch Audacity - hangs, as above - Force Quit >>>> - the option to rescan for VST effects is now in audacity.cfg and >>>> it is >>>> impossible to launch Audacity without trashing that file or editing >>>> it >>>> so that the relevant line is "Rescan=0" >>>> Edit audacity.cfg setting "Rescan=0" and save >>>> Launch Audacity - OK, and the VST effect appears in the Effect menu >> >> >> >>>> 5b)-- Now test if we can add another VST effect -- >>>> Check "Rescan VST Efffects" >>>> Quit Audacity >>>> Add another VST effect to the plug-ins folder >>>> Launch Audacity - hangs >>>> Force Quit Audacity >>>> - the newly-added VST effect is not in plugins.cfg >> >> Different. The info for the two VST effects is now in plugins.cfg, >> even though the hang occurred. >> >> 5c) Edit audacity.cfg setting "Rescan=0" >> Launch Audacity - OK, and both VST effects are in the Effect menu >> Quit Audacity >> >>>> 6) -- Will Audacity pick up two newly-added VST effects? -- >>>> Start over: trash plugins.cfg, edit audacity.cfg to the single line >>>> "NewPrefsInitialized =1", leave both VST effects in the plug-ins >>>> folder. >>>> Launch Audacity - hangs, as above >>>> Force Quit Audacity >>>> - plugins.cfg contains info for only one VST effect, although there >>>> were >>>> two in the plug-ins folder. >> >> Identical behaviour. >> >> -- Bill >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports >> 2008 30-Day >> trial. Simplify your report design, integration and deployment - >> and focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> audacity-devel mailing list >> [hidden email] >> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and > focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Bill Wharrie
|
In reply to this post
by Leland (Audacity Team)
On 11-Nov-09, at 2:16 AM, Leland wrote: > Leland wrote: >> Bill, >> >> Do you ever get any VST effects to actually load? I can (and can't >> reproduce your issues below) on Intel/OSX10.6, but I can't get ANY >> VST >> plugin to load on my G5/OSX10.4 machine. I don't hang and I see >> where >> the plugin actually gets called (some debugging messages), but they >> never appear in the Effects menu. >> >> There is definitely something fishy afoot... >> > The cause of this issue is a case-sensitive file system causing > plugins.cfg to be stored in Library/Application Support/audacity and > Library/Application Support/Audacity. Just gotta track down the > different caps. > > Leland: I never see an "Audacity" folder in ~/Library/Application Support. Also note that all my tests were done using the Portable Settings folder (except Case 6 which I duplicated without the Portable Settings folder). -- Bill > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and > focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Leland (Audacity Team)
|
In reply to this post
by Bill Wharrie
Bill,
When Michael's help, I believe I've tracked down the VST issue and have committed a fix for it. In the process, I found another problem that would cause Audacity to crash at termination if the user closed either a VST or AudioUnits dialog using the window close button. Give it a try and see how it works for you now... Leland ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Bill Wharrie
|
Leland:
Still crashes Audacity ® 1.3.10-alpha-Nov 15 2009 (Unicode) Maybe the fix didn't make it into that build? I'll try again on Monday. -- Bill On 14-Nov-09, at 5:14 AM, Leland wrote: > Bill, > > When Michael's help, I believe I've tracked down the VST issue and > have > committed a fix for it. In the process, I found another problem that > would cause Audacity to crash at termination if the user closed > either a > VST or AudioUnits dialog using the window close button. > > Give it a try and see how it works for you now... > > Leland > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and > focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Bill Wharrie
|
In reply to this post
by Leland (Audacity Team)
Detailed report
Audacity ® 1.3.10-alpha-Nov 15 2009 (Unicode) G5 dual 2 GHz, 10.5.8 Using Portable Settings folder * audacity.cfg contains only the line "NewPrefsInitialized=1" * plugins.cfg does not exist * put AnwidaSoft DX Reverb Light into plug-ins folder * launch Audacity * get language dialog - click OK * second Audacity icon appears briefly in the Dock, then goes away * Audacity has hung * switch to Activity Monitor and click Sample Process on Audacity Sampling process 708 for 3 seconds with 1 millisecond of run time between samples Sampling completed, processing symbols... Analysis of sampling Audacity (pid 708) every 1 millisecond Call graph: 2385 Thread_2503 2385 0x243c 2385 0x2738 2385 0x3800 2385 wxHashTable::~wxHashTable() 2385 0x95f0 2385 EffectLeveller::GetEffectAction() 2385 BlockGenerator::~BlockGenerator() 2385 BlockGenerator::~BlockGenerator() 2385 wxMessageOutputLog::~wxMessageOutputLog() 2385 wxClipboardTextEvent::Clone() const 2381 nanosleep 2381 mach_wait_until 2381 mach_wait_until 4 wxMessageOutputLog::~wxMessageOutputLog() 4 wxwxAccelListNode::~wxwxAccelListNode() 2 ReceiveNextEventCommon 2 RunCurrentEventLoopInMode 1 CFRunLoopRunSpecific 1 mach_msg 1 mach_msg_trap 1 mach_msg_trap 1 CFStringCompare 1 CFStringGetLength 1 CFStringGetLength 1 wxThreadModule::~wxThreadModule() 1 wxThreadModule::~wxThreadModule() 1 wxwxAccelListNode::~wxwxAccelListNode() 2385 Thread_2603 2385 _pthread_start 2385 CAPThread::Entry(CAPThread*) 2385 HALRunLoop::OwnThread(void*) 2385 CFRunLoopRunSpecific 2385 mach_msg 2385 mach_msg_trap 2385 mach_msg_trap 2385 Thread_2703 2379 _pthread_start 2379 AudioThread::callback(void*) 2377 nanosleep 2377 mach_wait_until 2377 mach_wait_until 2 muldiv128 2 saveFP 2 saveFP 6 AudioThread::callback(void*) 6 AudioThread::callback(void*) Total number in stack (recursive counted multiple, when >=5): Sort by top of stack, same collapsed (when >= 5): mach_wait_until 4758 mach_msg_trap 2386 AudioThread::callback(void*) 6 Sample analysis of process 708 written to file /dev/stdout * Apple Menu and Audacity menu exist in the menu bar * click on Audacity menu and Help menu appears * Help menu is not populated * Audacity > Quit Audacity exists but clicking it has no effect * force quit Audacity * audacity.cfg has not been updated * plugins.cfg has been created and contains: [VST] [VST/0] PluginPath=/Applications/Audacity 1.3.10-alpha/plug-ins/DX Reverb Light.vst [VST/0/private] Name=L1V Vendor=ANWIDA Soft Inputs=2 Outputs=2 Note that I never see a "scanning for VST effects" dialog. Try again but with "Excitifier.vst" plug-in. * Same. (did not try Sample Process) Testing on PowerBook G4, 1.4.11 Using Portable Settings folder * audacity.cfg contains only the line "NewPrefsInitialized=1" * plugins.cfg does not exist * put AnwidaSoft DX Reverb Light into plug-ins folder * launch Audacity * get language dialog - click OK * second Audacity icon appears briefly in the Dock, then goes away * get empty project window and splash screen - click OK * everything appears to be OK ** Audacity is functional ** DX Reverb is in Effect menu * quit Audacity * plugins.cfg contains info as above. Note that second Audacity icon still flashes in the Dock. 10.4.11 seems to handle this situation differently, OR there is something very strange going on in my G5. I still don't see the "scanning for VST effects" dialog on either machine. Anything else I can do? - Bill On 14-Nov-09, at 5:14 AM, Leland wrote: > Bill, > > When Michael's help, I believe I've tracked down the VST issue and > have > committed a fix for it. In the process, I found another problem that > would cause Audacity to crash at termination if the user closed > either a > VST or AudioUnits dialog using the window close button. > > Give it a try and see how it works for you now... > > Leland > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and > focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Leland (Audacity Team)
|
I'm sorry Bill, I simply can't get it to fail. I'm not saying the
problem doesn't exist as it apparently does, whether it's specific to your system or not. Let's step back a sec. Do you have anything in: /Library/Audio/Plug-Ins/VST ~/Library/Audio/Plug-Ins/VST ~/Library/Preferences/*audacity* ~/Library/Application Support/audacity Does the problem happen if you don't use Portable Settings? How about if you delete all files within the Portable Settings and let Audacity recreate them (rather than editing them yourself)? The last problem I resolved was a problem where the Blue Cat plugins cause Audacity to crash during startup when running on anything less than Leopard. Bill Wharrie wrote: > Detailed report > > Audacity ® 1.3.10-alpha-Nov 15 2009 (Unicode) > G5 dual 2 GHz, 10.5.8 > Using Portable Settings folder > > * audacity.cfg contains only the line "NewPrefsInitialized=1" > * plugins.cfg does not exist > * put AnwidaSoft DX Reverb Light into plug-ins folder > * launch Audacity > * get language dialog - click OK > * second Audacity icon appears briefly in the Dock, then goes away > * Audacity has hung > > * switch to Activity Monitor and click Sample Process on Audacity > > Sampling process 708 for 3 seconds with 1 millisecond of run time > between samples > Sampling completed, processing symbols... > Analysis of sampling Audacity (pid 708) every 1 millisecond > Call graph: > 2385 Thread_2503 > 2385 0x243c > 2385 0x2738 > 2385 0x3800 > 2385 wxHashTable::~wxHashTable() > 2385 0x95f0 > 2385 EffectLeveller::GetEffectAction() > 2385 BlockGenerator::~BlockGenerator() > 2385 BlockGenerator::~BlockGenerator() > 2385 wxMessageOutputLog::~wxMessageOutputLog() > 2385 wxClipboardTextEvent::Clone() const > 2381 nanosleep > 2381 mach_wait_until > 2381 mach_wait_until > 4 wxMessageOutputLog::~wxMessageOutputLog() > 4 wxwxAccelListNode::~wxwxAccelListNode() > 2 ReceiveNextEventCommon > 2 RunCurrentEventLoopInMode > 1 CFRunLoopRunSpecific > 1 mach_msg > 1 mach_msg_trap > 1 mach_msg_trap > 1 CFStringCompare > 1 CFStringGetLength > 1 CFStringGetLength > 1 wxThreadModule::~wxThreadModule() > 1 wxThreadModule::~wxThreadModule() > 1 wxwxAccelListNode::~wxwxAccelListNode() > 2385 Thread_2603 > 2385 _pthread_start > 2385 CAPThread::Entry(CAPThread*) > 2385 HALRunLoop::OwnThread(void*) > 2385 CFRunLoopRunSpecific > 2385 mach_msg > 2385 mach_msg_trap > 2385 mach_msg_trap > 2385 Thread_2703 > 2379 _pthread_start > 2379 AudioThread::callback(void*) > 2377 nanosleep > 2377 mach_wait_until > 2377 mach_wait_until > 2 muldiv128 > 2 saveFP > 2 saveFP > 6 AudioThread::callback(void*) > 6 AudioThread::callback(void*) > > Total number in stack (recursive counted multiple, when >=5): > > Sort by top of stack, same collapsed (when >= 5): > mach_wait_until 4758 > mach_msg_trap 2386 > AudioThread::callback(void*) 6 > Sample analysis of process 708 written to file /dev/stdout > > * Apple Menu and Audacity menu exist in the menu bar > * click on Audacity menu and Help menu appears > * Help menu is not populated > * Audacity > Quit Audacity exists but clicking it has no effect > > * force quit Audacity > > * audacity.cfg has not been updated > * plugins.cfg has been created and contains: > [VST] > [VST/0] > PluginPath=/Applications/Audacity 1.3.10-alpha/plug-ins/DX Reverb > Light.vst > [VST/0/private] > Name=L1V > Vendor=ANWIDA Soft > Inputs=2 > Outputs=2 > > Note that I never see a "scanning for VST effects" dialog. > > Try again but with "Excitifier.vst" plug-in. > * Same. (did not try Sample Process) > > Testing on PowerBook G4, 1.4.11 > Using Portable Settings folder > > * audacity.cfg contains only the line "NewPrefsInitialized=1" > * plugins.cfg does not exist > * put AnwidaSoft DX Reverb Light into plug-ins folder > * launch Audacity > * get language dialog - click OK > * second Audacity icon appears briefly in the Dock, then goes away > * get empty project window and splash screen - click OK > * everything appears to be OK > ** Audacity is functional > ** DX Reverb is in Effect menu > * quit Audacity > > * plugins.cfg contains info as above. > > Note that second Audacity icon still flashes in the Dock. > 10.4.11 seems to handle this situation differently, OR there is > something very strange going on in my G5. > > I still don't see the "scanning for VST effects" dialog on either > machine. > > Anything else I can do? > > - Bill > > On 14-Nov-09, at 5:14 AM, Leland wrote: > >> Bill, >> >> When Michael's help, I believe I've tracked down the VST issue and >> have >> committed a fix for it. In the process, I found another problem that >> would cause Audacity to crash at termination if the user closed >> either a >> VST or AudioUnits dialog using the window close button. >> >> Give it a try and see how it works for you now... >> >> Leland >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and >> focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> audacity-devel mailing list >> [hidden email] >> https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Bill Wharrie
|
On 15-Nov-09, at 11:35 PM, Leland wrote: > I'm sorry Bill, I simply can't get it to fail. I'm not saying the > problem doesn't exist as it apparently does, whether it's specific to > your system or not. I can get this to fail on 3 machines. On 10.5.8 PPC I get a hang. On 10.4.11 on PPC the problem appears to be fixed except I never see the "scanning" dialog and a second Audacity icon flashes briefly in the Dock. On 10.4.11 Intel Audacity does not hang but the VST effect is not picked up. The flash of the second Audacity icon in the Dock is so fast you might miss it. I tried removing Growl from the PowerBook but that had no effect on the behavrious. > > Let's step back a sec. Do you have anything in: > > /Library/Audio/Plug-Ins/VST nothing there > ~/Library/Audio/Plug-Ins/VST nothing there > ~/Library/Preferences/*audacity* OK, delete that file (I'll let 1.2.6 recreate it if needed) > ~/Library/Application Support/audacity OK, get rid of that folder. > > Does the problem happen if you don't use Portable Settings? OK, get rid of the Portable Settings folder - no change, still hangs > How about > if you delete all files within the Portable Settings and let Audacity > recreate them (rather than editing them yourself)? - no change. scroll down for test on Intel 10.4.11 [snip] >> >> Testing on PowerBook G4, 1.4.11 >> Using Portable Settings folder >> >> * audacity.cfg contains only the line "NewPrefsInitialized=1" >> * plugins.cfg does not exist >> * put AnwidaSoft DX Reverb Light into plug-ins folder >> * launch Audacity >> * get language dialog - click OK >> * second Audacity icon appears briefly in the Dock, then goes away >> * get empty project window and splash screen - click OK >> * everything appears to be OK >> ** Audacity is functional >> ** DX Reverb is in Effect menu >> * quit Audacity >> >> * plugins.cfg contains info as above. >> >> Note that second Audacity icon still flashes in the Dock. >> 10.4.11 seems to handle this situation differently, OR there is >> something very strange going on in my G5. >> >> I still don't see the "scanning for VST effects" dialog on either >> machine. >> Testing on iMac Intel Core 2 Duo 2 GHz, 10.4.11 - same as PowerBook running 10.4.11, EXCEPT - VST effect is NOT in Effect menu - VST effect is NOT in plugins.cfg. Note that the flash of the second Audacity icon in the Dock is so fast that you might miss it. -- Bill ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Leland (Audacity Team)
|
Bill Wharrie wrote:
> On 15-Nov-09, at 11:35 PM, Leland wrote: > >> I'm sorry Bill, I simply can't get it to fail. I'm not saying the >> problem doesn't exist as it apparently does, whether it's specific to >> your system or not. > > I can get this to fail on 3 machines. On 10.5.8 PPC I get a hang. Let's try something crazy. It "may" shed a little more light on the issue. Open a Terminal window Change to the directory where Audacity.app resides Start Audacity with: Audacity.app/Contents/MacOS/Audacity It will produce some output and I'm hoping we'll see something useful. I doubt we will, but it won't hurt to try. > 10.4.11 on PPC the problem appears to be fixed except I never see the > "scanning" dialog and a second Audacity icon flashes briefly in the > Dock. The scanning dialog will only appear if the current progress lasts for more than .5 seconds. With only 1 plugin, chances are it will never be displayed. The icon in the dock is expected. The way Audacity scans for plugins is to start a second copy of itself and that's where the icon comes from. On 10.4.11 Intel Audacity does not hang but the VST effect is > not picked up. The flash of the second Audacity icon in the Dock is so > fast you might miss it. You could check the plugin to see if it is supported on Intel: file <path to plugin.vst>/Contents/MacOS/* Here's what I get: llama:~/Library/Audio/Plug-Ins/VST$ file 'DX Reverb Light.vst/Contents/MacOS/*' DX Reverb Light.vst/Contents/MacOS/DelayEditGUI: Mach-O bundle ppc Which means it won't work on Intel. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Bill Wharrie
|
Leland:
OK, so the "problem" I was seeing on the Intel machine was with the plug-in, not Audacity. On the PowerBook (10.4.11 PPC), I put DX Reverb Light.vst, (Lufonix) LFX1310.vst, Excitifier.vst and BittersweetII.vst. I see the "scanning" dialog, and the second icon comes and goes with each effect that it picks up. All the effects are picked up, even though I get the error message "/Library/Application Support/LUFONIX/LFX-1310/ LFX-1310.fxb file can't be accessed". OK, I didn't install the Lufonix plug-in properly - probably should have used their installer. Despite this all four vst effects show up in the Effect menu and all are in plugins.cfg. Still on the Powerbook, the Bittersweet effect shows up with full graphics. The LFX-1310 complains that it can't find its fxb file but still shows up with full graphics. DX Reverb Light and Excitifier show up in plain mode but still work. OK, problem solved on 10.4.11 PPC. On 16-Nov-09, at 11:34 AM, Leland wrote: > Let's try something crazy. It "may" shed a little more light on the > issue. > > Open a Terminal window > Change to the directory where Audacity.app resides > Start Audacity with: > > Audacity.app/Contents/MacOS/Audacity No output produced. Command does not return until Audacity quits or is terminated, whether it hangs or not. Remove 1.2.6, 1.3.8 and 1.3.9 from the G5 - trash the folders. Trash Portable Settings folder from within the 1.3.10 folder. Trash the audacity folder from within Application Support. Empty the trash. Put two BlueCat vst plugins into the plug-ins folder. Start Audacity. Hangs as before. Remove BlueCat plug-ins from plug-ins folder, try with Excitifier.vst. Same. I quit every other program that was running and tried again - no joy. I removed every custom preference pane (including FlipForMac and Growl) - still no joy. I'm at a loss for what else to try. Note that on the G5 Audacity successfully picks up the first vst effect that it finds and writes the info to plugins.cfg. I'm guessing that something happens when that "mini-Audacity" returns control to the "real" Audacity? And this either has something to do with 10.5.8, or something peculiar to my G5. The only thing that I know I have running other than the standard Mac stuff is Carbon Copy Cloner, and that's just the cron task that schedules the backups (as far as I know) unless a back-up is actually happening. I always do these tests when a backup is not happening. -- Bill ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |
