When to give up on a plugin (crashing, etc)?

[zvenx]

You mention you've updated OSX. But have you tried doing a clean re-install? That might be a good idea, particularly after changing the motherboard out from under it.

I am curious do you use macs or PC? I assume you must use macs cause your plugins afaik are crossplatform.
But one of the many joys of a mac is I can take any OSX mac, clone hard drive onto an external hard drive and run any other mac (of course providing it isn't too old to run say mountain lion, or you are trying to run a new mac with an OSX version that can't run on it or something like that) with that external hard drive derived from a totally different mac.
By this I mean I can take even a macbookpro hard drive, clone it and run a mac pro with it.... any mac will run any mac.
I have never heard of what you describe above.....it isn't like PC where you can't do this unless you are switching to the same motherboard etc.

Clearly an OS can get corrupted, mac or PC, but motherboard incompatibility requiring a OSX clean install.. I think that's very improbable as an issue for a macintosh.

I don't use Logic, but I have heard and read that it is one finicky DAW.

rsp

[hibidy]

lolz, I don't know about today but clean installs were a constant when I had mac.

Computers puzzle me. It's supposed to be garbage in, garbage out but I still feel they have their own agenda!

[AdmiralQuality]

You mention you've updated OSX. But have you tried doing a clean re-install? That might be a good idea, particularly after changing the motherboard out from under it.

I am curious do you use macs or PC? I assume you must use macs cause your plugins afaik are crossplatform.
But one of the many joys of a mac is I can take any OSX mac, clone hard drive onto an external hard drive and run any other mac (of course providing it isn't too old to run say mountain lion, or you are trying to run a new mac with an OSX version that can't run on it or something like that) with that external hard drive derived from a totally different mac.
By this I mean I can take even a macbookpro hard drive, clone it and run a mac pro with it.... any mac will run any mac.
I have never heard of what you describe above.....it isn't like PC where you can't do this unless you are switching to the same motherboard etc.

Clearly an OS can get corrupted, mac or PC, but motherboard incompatibility requiring a OSX clean install.. I think that's very improbable as an issue for a macintosh.

I don't use Logic, but I have heard and read that it is one finicky DAW.

rsp

I use both, of course.

And I don't see how that can be the case. There's all kinds of kernel extensions (kext) on OS X that are hardware specific and, as far as I know, get set up at install time. And it's unlikely that modern Intel Macs all have exactly the same chipsets on every variety of motherboard.

I could be wrong here, I'm not a big Mac expert. (Ha ha! I said Big Mac!) Anyway, it's one remaining thing the OP hasn't tried. Though yes, if the host works with all other plug-ins then it's unlikely to be the machine's configuration that's at fault. But it's got to be SOMETHING unique about his system. Otherwise everybody would be having the same problem, right?

[masterhiggins]

Thanks for the suggestions, guys. When I switched to my new MacBook Pro I did the archive and install option. Could that have caused an issue? I just dread having to wipe off the OS as it seems to take forever to get my stuff set up the way I like it (dock modifications, email setup, FTP configs, plugins, macros, terminal scripts). Oh well. I might just suck it up. Lately my CPU has been running kind of hot even when the system is idle. I've already tried resetting the SMC. Unfortunately, unlike when resetting the pram, Mac OS doesn't actually provide any indication that it actually worked. I might just have to drop my laptop back off at apple to have their "geniuses" (and I mean that loosely) run another deep diagnostic on it. Want to know what's weird? When I had the logic board switched out last time, it took them 3 times to do it. The first two they received resulted in errors and after getting the third one installed, it finally passed without errors. I still don't know what the f*** that was about. Anyway, I realized how badly I've become addicted to my laptop. Not having it for two weeks resulted in all kinds of withdrawal symptoms.

Anyway...I forgot to ask. Would you recommend that I install the 10.8 update or just stick with 10.7? Thanks!

-sam

[masterhiggins]

all my plugins are 64bit (except sylenth1, which hasn't been updated since the 1800's)...
EVERYTHING works fine in logic...only the z3ta+2 had issues that were never resolved.
i'm running L9 in 10.8.3, and no issues; even the 32bit bridge (which crashes sometimes) is more stable than previously...

Could you please be a doll and install Largo and Lector and twiddle with the parameters for several hours and then let me know if they give you any crashes? They're only about four hundred dollars. Thanks.

-sam

[fisherKing]

or you could send me your serial #s...this way i can also check to see if the serial#s are in fact the problem...

seriously, probably the plugs. i spent six months with cakewalk trying to get their synth to work in logic, and...gave up.

if you do update, def go to 10.8. lion was NOT the best, ML is a much better system (for my money, as good as or better than 10.6.8, a truly-great OS).

good luck...

[masterhiggins]

K I'm not sure if anyone still cares or not, but I thought I'd provide an update on the Waldorf issues.

I did a clean install of OS 10.8.3 and took a couple of days to get stuff where I wanted them. I installed all of my plugins again (including the Waldorf ones) and they still crash my system. Damnit.

Anyway, I did discover something very interesting. They only crash when the actual GUI of the plugin is open/active. If I have it closed and I'm on the mixer page, for example, it doesn't crash. I did an experiment where I drew in VERY heavy automation of the knob twiddling/parameter changes and it plays them back just fine without crashing. However, as soon as I have the GUI open and start tweaking knobs and flipping buttons manually in real time, that's when they crash.

I even tried using MIDI Learn with my Akai MPD32 and tweaked the knobs/automation with no crash. As soon as I started switching them with the mouse.....BLAM! Does anyone have any idea what could be causing it to react to the GUI/Mouse combination and nothing else? Thanks.

-Sam

[hibidy]

How frustrating.

[AdmiralQuality]

K I'm not sure if anyone still cares or not, but I thought I'd provide an update on the Waldorf issues.

I did a clean install of OS 10.8.3 and took a couple of days to get stuff where I wanted them. I installed all of my plugins again (including the Waldorf ones) and they still crash my system. Damnit.

Anyway, I did discover something very interesting. They only crash when the actual GUI of the plugin is open/active. If I have it closed and I'm on the mixer page, for example, it doesn't crash. I did an experiment where I drew in VERY heavy automation of the knob twiddling/parameter changes and it plays them back just fine without crashing. However, as soon as I have the GUI open and start tweaking knobs and flipping buttons manually in real time, that's when they crash.

I even tried using MIDI Learn with my Akai MPD32 and tweaked the knobs/automation with no crash. As soon as I started switching them with the mouse.....BLAM! Does anyone have any idea what could be causing it to react to the GUI/Mouse combination and nothing else? Thanks.

-Sam

Interesting. I'd really think all other users of those plug-ins should be having this same problem.

Your description is a bit unclear as to if you had the effect's GUI open with automation and/or MIDI moving the knobs? Is it ANY knob movement when the GUI is open that causes it to crash? Or only when you click on a GUI knob with the mouse?

Also, are you running Logic in 64 bit or 32 bit mode? And what do the plug-ins claim to be?

[masterhiggins]

K I'm not sure if anyone still cares or not, but I thought I'd provide an update on the Waldorf issues.

I did a clean install of OS 10.8.3 and took a couple of days to get stuff where I wanted them. I installed all of my plugins again (including the Waldorf ones) and they still crash my system. Damnit.

Anyway, I did discover something very interesting. They only crash when the actual GUI of the plugin is open/active. If I have it closed and I'm on the mixer page, for example, it doesn't crash. I did an experiment where I drew in VERY heavy automation of the knob twiddling/parameter changes and it plays them back just fine without crashing. However, as soon as I have the GUI open and start tweaking knobs and flipping buttons manually in real time, that's when they crash.

I even tried using MIDI Learn with my Akai MPD32 and tweaked the knobs/automation with no crash. As soon as I started switching them with the mouse.....BLAM! Does anyone have any idea what could be causing it to react to the GUI/Mouse combination and nothing else? Thanks.

-Sam

Interesting. I'd really think all other users of those plug-ins should be having this same problem.

Your description is a bit unclear as to if you had the effect's GUI open with automation and/or MIDI moving the knobs? Is it ANY knob movement when the GUI is open that causes it to crash? Or only when you click on a GUI knob with the mouse?

Also, are you running Logic in 64 bit or 32 bit mode? And what do the plug-ins claim to be?

Hi Admiral!

Sorry, I'm just a bit sleep-deprived trying to figure this stuff out.

When the GUI itself is open, there's usually no crashing. That's not always the case, though. Sometimes the Logic session crashes just by opening the window for editing (but the plugin is already instantiated/inserted in Logic). So basically, just having it open doesn't necessarily crash it.

The parameters can be automated with no problem, for example, if I draw in the values on the track view. That is how I was able to save the intense amount of automation on the track. I could never tweak that much at once without Logic crashing. So the window can be open and Lector plays back automation just fine. I can also use midi learn in Logic to assign the parameters to my MPD32 and they can be tweaked and modify the automation with no problem, either. It's only when I'm manually touching/modifying the various values (oscillator waveform/sample, filter types, frequency bands, etc) that it crashes.

I know it's super annoying for other readers to post the entire crashlog as it takes up an entire page, so I'll just post snippets, but they're always like this:

PlugIn Path: /Library/Audio/Plug-Ins/Components/Lector.component/Contents/Resources/plugin.vst3/Contents/MacOS/Lector
PlugIn Identifier: de.waldorfmusic.vst3.lector
PlugIn Version: 1.0.1 (1.0.1)

Crashed Thread: 7 com.apple.audio.IOThread.client

Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

VM Regions Near 0:
--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
__TEXT 0000000000001000-0000000000beb000 [ 11.9M] r-x/rwx SM=COW /Applications/Logic Pro.app/Contents/MacOS/Logic Pro

Application Specific Information:
abort() called

Thread 7 Crashed:: com.apple.audio.IOThread.client
0 libsystem_kernel.dylib 0x95adba6a __pthread_kill + 10
1 libsystem_c.dylib 0x99cadb2f pthread_kill + 101
2 libsystem_c.dylib 0x99ce45f3 __abort + 199
3 libsystem_c.dylib 0x99ce452c abort + 232
4 com.apple.logic.pro 0x003e6729 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 3842985
5 libsystem_c.dylib 0x99c988cb _sigtramp + 43
6 de.waldorfmusic.vst3.lector 0x23d46e80 0x23d00000 + 290432
7 de.waldorfmusic.vst3.lector 0x23d4721d 0x23d00000 + 291357
8 de.waldorfmusic.vst3.lector 0x23d2104f 0x23d00000 + 135247
9 de.waldorfmusic.vst3.lector 0x23d21321 0x23d00000 + 135969
10 de.waldorfmusic.vst3.lector 0x23d4bf22 0x23d00000 + 311074
11 de.waldorfmusic.vst.lector 0x2384f266 AUCarbonViewEntry + 13174
12 de.waldorfmusic.vst.lector 0x2385b38c AUWrapperEntry + 38044
13 de.waldorfmusic.vst.lector 0x2385cde3 AUWrapperEntry + 44787
14 de.waldorfmusic.vst.lector 0x23851f1e AUWrapperEntry + 46
15 com.apple.CoreServices.CarbonCore 0x9153aade CallComponent + 151
16 com.apple.CoreServices.CarbonCore 0x9153ab38 CallComponentDispatch + 29
17 com.apple.audio.toolbox.AudioToolbox 0x978cc7fe _AT_AudioUnitRender + 202
18 com.apple.logic.pro 0x005931bc std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 5598780
19 com.apple.music.apps.MAAudioEngine 0x02b151f7 MD::PluginProcess(MDProcInfo*, MDPlug*, float const*, long, long, long, eProcessLevel) + 4135
20 com.apple.music.apps.MAAudioEngine 0x02b16384 MD::StreamProcessing(eProcessLevel, long, long, long) + 2036
21 com.apple.music.apps.MAAudioEngine 0x02b19354 MD::Process(eProcessLevel) + 1044
22 com.apple.music.apps.MAAudioEngine 0x02b2205f MD::DriverCallback(IODriverAudioPB*) + 8735
23 com.apple.music.apps.MAAudioEngine 0x02b35c32 GetCurrentCoreAudioDeviceNameFromUserDefaults(signed char) + 5474
24 com.apple.audio.CoreAudio 0x9943ec4e HALC_ProxyIOContext::IOWorkLoop() + 2878
25 com.apple.audio.CoreAudio 0x9943e061 HALC_ProxyIOContext::IOThreadEntry(void*) + 145
26 com.apple.audio.CoreAudio 0x9944804a ___ZN19HALC_ProxyIOContextC2Emj_block_invoke_0 + 20
27 com.apple.audio.CoreAudio 0x9943df85 HALB_IOThread::Entry(void*) + 69
28 libsystem_c.dylib 0x99cac5b7 _pthread_start + 344
29 libsystem_c.dylib 0x99c96d4e thread_start + 34

I have no idea what any of that crap is. Holger from Waldorf support told me that it looks like I was missing a Library file in OSX and that a clean install should fix it. Wrong. I sent them an example session file that was causing the crashing, but I'm guessing it won't show them anything useful unless they can recreate the crashing themselves. This really blows. I really want to use these plugins (especially Lector) as the sounds are nuts. Oh well. Thanks!

-Sam

[AdmiralQuality]

K I'm not sure if anyone still cares or not, but I thought I'd provide an update on the Waldorf issues.

I did a clean install of OS 10.8.3 and took a couple of days to get stuff where I wanted them. I installed all of my plugins again (including the Waldorf ones) and they still crash my system. Damnit.

Anyway, I did discover something very interesting. They only crash when the actual GUI of the plugin is open/active. If I have it closed and I'm on the mixer page, for example, it doesn't crash. I did an experiment where I drew in VERY heavy automation of the knob twiddling/parameter changes and it plays them back just fine without crashing. However, as soon as I have the GUI open and start tweaking knobs and flipping buttons manually in real time, that's when they crash.

I even tried using MIDI Learn with my Akai MPD32 and tweaked the knobs/automation with no crash. As soon as I started switching them with the mouse.....BLAM! Does anyone have any idea what could be causing it to react to the GUI/Mouse combination and nothing else? Thanks.

-Sam

Interesting. I'd really think all other users of those plug-ins should be having this same problem.

Your description is a bit unclear as to if you had the effect's GUI open with automation and/or MIDI moving the knobs? Is it ANY knob movement when the GUI is open that causes it to crash? Or only when you click on a GUI knob with the mouse?

Also, are you running Logic in 64 bit or 32 bit mode? And what do the plug-ins claim to be?

Hi Admiral!

Sorry, I'm just a bit sleep-deprived trying to figure this stuff out.

When the GUI itself is open, there's usually no crashing. That's not always the case, though. Sometimes the Logic session crashes just by opening the window for editing (but the plugin is already instantiated/inserted in Logic). So basically, just having it open doesn't necessarily crash it.

These statements are contradictory. GUI open doesn't crash it/Opening the GUI crashes it.

Again, you seemed to be making some distinction between using the mouse to move knobs vs. automation or MIDI knob movement. But then if it crashes when the GUI is open (sometimes?) then obviously it crashes when the GUI is open and automation/MIDI are moving the knobs.

The parameters can be automated with no problem, for example, if I draw in the values on the track view. That is how I was able to save the intense amount of automation on the track. I could never tweak that much at once without Logic crashing.

Again, you're being imprecise. Was the plugin's GUI open when the automation was playing back? And by "tweak" I assume you mean control the plugin's GUI with the mouse instead of just by played back automation. Obviously the plugin's GUI needs to be open for that. But you don't specify if it's open when playing back massive automation successfully.

So the window can be open and Lector plays back automation just fine.

Okay... so it can be open. (Except you just said above that sometimes it crashes when you open the GUI.)

I can also use midi learn in Logic to assign the parameters to my MPD32 and they can be tweaked and modify the automation with no problem, either. It's only when I'm manually touching/modifying the various values (oscillator waveform/sample, filter types, frequency bands, etc) that it crashes.

Consistently? Like the very instant you click on a control?

I know it's super annoying for other readers to post the entire crashlog as it takes up an entire page, so I'll just post snippets, but they're always like this:

PlugIn Path: /Library/Audio/Plug-Ins/Components/Lector.component/Contents/Resources/plugin.vst3/Contents/MacOS/Lector
PlugIn Identifier: de.waldorfmusic.vst3.lector
PlugIn Version: 1.0.1 (1.0.1)

Crashed Thread: 7 com.apple.audio.IOThread.client

Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

VM Regions Near 0:
--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
__TEXT 0000000000001000-0000000000beb000 [ 11.9M] r-x/rwx SM=COW /Applications/Logic Pro.app/Contents/MacOS/Logic Pro

Application Specific Information:
abort() called

Thread 7 Crashed:: com.apple.audio.IOThread.client
0 libsystem_kernel.dylib 0x95adba6a __pthread_kill + 10
1 libsystem_c.dylib 0x99cadb2f pthread_kill + 101
2 libsystem_c.dylib 0x99ce45f3 __abort + 199
3 libsystem_c.dylib 0x99ce452c abort + 232
4 com.apple.logic.pro 0x003e6729 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 3842985
5 libsystem_c.dylib 0x99c988cb _sigtramp + 43
6 de.waldorfmusic.vst3.lector 0x23d46e80 0x23d00000 + 290432
7 de.waldorfmusic.vst3.lector 0x23d4721d 0x23d00000 + 291357
8 de.waldorfmusic.vst3.lector 0x23d2104f 0x23d00000 + 135247
9 de.waldorfmusic.vst3.lector 0x23d21321 0x23d00000 + 135969
10 de.waldorfmusic.vst3.lector 0x23d4bf22 0x23d00000 + 311074
11 de.waldorfmusic.vst.lector 0x2384f266 AUCarbonViewEntry + 13174
12 de.waldorfmusic.vst.lector 0x2385b38c AUWrapperEntry + 38044
13 de.waldorfmusic.vst.lector 0x2385cde3 AUWrapperEntry + 44787
14 de.waldorfmusic.vst.lector 0x23851f1e AUWrapperEntry + 46
15 com.apple.CoreServices.CarbonCore 0x9153aade CallComponent + 151
16 com.apple.CoreServices.CarbonCore 0x9153ab38 CallComponentDispatch + 29
17 com.apple.audio.toolbox.AudioToolbox 0x978cc7fe _AT_AudioUnitRender + 202
18 com.apple.logic.pro 0x005931bc std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 5598780
19 com.apple.music.apps.MAAudioEngine 0x02b151f7 MD::PluginProcess(MDProcInfo*, MDPlug*, float const*, long, long, long, eProcessLevel) + 4135
20 com.apple.music.apps.MAAudioEngine 0x02b16384 MD::StreamProcessing(eProcessLevel, long, long, long) + 2036
21 com.apple.music.apps.MAAudioEngine 0x02b19354 MD::Process(eProcessLevel) + 1044
22 com.apple.music.apps.MAAudioEngine 0x02b2205f MD::DriverCallback(IODriverAudioPB*) + 8735
23 com.apple.music.apps.MAAudioEngine 0x02b35c32 GetCurrentCoreAudioDeviceNameFromUserDefaults(signed char) + 5474
24 com.apple.audio.CoreAudio 0x9943ec4e HALC_ProxyIOContext::IOWorkLoop() + 2878
25 com.apple.audio.CoreAudio 0x9943e061 HALC_ProxyIOContext::IOThreadEntry(void*) + 145
26 com.apple.audio.CoreAudio 0x9944804a ___ZN19HALC_ProxyIOContextC2Emj_block_invoke_0 + 20
27 com.apple.audio.CoreAudio 0x9943df85 HALB_IOThread::Entry(void*) + 69
28 libsystem_c.dylib 0x99cac5b7 _pthread_start + 344
29 libsystem_c.dylib 0x99c96d4e thread_start + 34

I have no idea what any of that crap is. Holger from Waldorf support told me that it looks like I was missing a Library file in OSX and that a clean install should fix it. Wrong. I sent them an example session file that was causing the crashing, but I'm guessing it won't show them anything useful unless they can recreate the crashing themselves. This really blows. I really want to use these plugins (especially Lector) as the sounds are nuts. Oh well. Thanks!

-Sam

And not being the developer of the plugin, it doesn't mean much to me either. Except I see it's a VST3 that's been wrapped as an AU and as far as I know developers are still finding bugs in Steinberg's VST3->AU wrapper. (Part of why I refuse to "up"grade to VST3. It offers nothing you couldn't do in VST2.4 and more often than not causes a lot of problems.)

Incidentally, how does it perform as a VST? (If you don't have a VST host, try it in Reaper http://reaper.fm You can also try the AU in Reaper and see if you get the same crash, for what it's worth.)

Another thing to verify. You're starting a fresh project in Logic, right? (If not you could have a "poison project".) Nothing else loaded, you just drop in a Lector, touch a control on its GUI, and boom?

It is VERY strange though that all AU users of this plug-in aren't experiencing the same thing. It can be very difficult for developers to debug something that only happens on a small percentage of users' systems, that they can't replicate themselves. I feel for them, but I also can't help the suspicion that this is brought on by VST3's still relatively new and untested status. (Yes, it's been years since VST3 came out, but adoption is VERY low. For all these reasons I've mentioned.)

[masterhiggins]

Again, you're being imprecise. Was the plugin's GUI open when the automation was playing back? And by "tweak" I assume you mean control the plugin's GUI with the mouse instead of just by played back automation. Obviously the plugin's GUI needs to be open for that. But you don't specify if it's open when playing back massive automation successfully.

Oh I'm sorry. I meant if I save the session with Lector open and then close it and then come back to it later, it opens without crashing. However, if I close Lector and later on I'm moving between different plugin windows and then go back to open it up...it SOMETIMES crashes immediately. Not always. I've just noticed that sometimes when I click the Lector instrument box in the mixer to open the GUI, it crashes as soon as the Lector window opens, but not consistently enough for me to reproduce every time.

When I say tweak I mean control the plugin GUI with a mouse. If the Lector window is already open when playing back automation, it doesn't seem to impact the frequency of the crashes. If it's closed and I open it up, it CAN crash Lector, but not always. I know that doesn't help. Sorry.

Okay... so it can be open. (Except you just said above that sometimes it crashes when you open the GUI.)

Correct. It sometimes crashes just by opening the GUI.

Consistently? Like the very instant you click on a control?

Yeah I guess that was a bad choice of words. It's not instant. I usually have to click on and adjust various parameters for about 15-30 seconds before Logic gives up and dies. My impatience tends to distort time for me.

And not being the developer of the plugin, it doesn't mean much to me either. Except I see it's a VST3 that's been wrapped as an AU and as far as I know developers are still finding bugs in Steinberg's VST3->AU wrapper. (Part of why I refuse to "up"grade to VST3. It offers nothing you couldn't do in VST2.4 and more often than not causes a lot of problems.)

Incidentally, how does it perform as a VST? (If you don't have a VST host, try it in Reaper http://reaper.fm You can also try the AU in Reaper and see if you get the same crash, for what it's worth.)

Another thing to verify. You're starting a fresh project in Logic, right? (If not you could have a "poison project".) Nothing else loaded, you just drop in a Lector, touch a control on its GUI, and boom?

It is VERY strange though that all AU users of this plug-in aren't experiencing the same thing. It can be very difficult for developers to debug something that only happens on a small percentage of users' systems, that they can't replicate themselves. I feel for them, but I also can't help the suspicion that this is brought on by VST3's still relatively new and untested status. (Yes, it's been years since VST3 came out, but adoption is VERY low. For all these reasons I've mentioned.)

I haven't used it as a VST. However, I did use it as an AU in Ableton Live Lite 8 and it didn't crash for the entire hour I was using it. Maybe I was just lucky in that respect. It's annoying that it crashes Logic as an AU but doesn't crash Live as an AU, though. AS I didn't experience any crashes in Live I just assumed it was a matter of Logic and OS 10.7, hence the clean install.

Yes, this project I'm working in brand-new. I created from scratch in Logic without any templates. All I did was add a few instruments tracks, loaded Logic's ES1 as a sidechain signal to feed into Logic via a Bus track and put a Logic limiter on the Lector track to keep it from blowing my speakers out with the parameter changes.

If it is a matter of VST3 to AU wrapper gone bad, I suppose there's nothing I can do. Yeah I've heard that other developers have been having issues with VST3, but at least they acknowledge it and communicate it with users. I know it sounds bad, but I think the reason why it may not be that common of an issue with Lector is that there just aren't many Lector users out there. On this forum, I'm probably one of 10 users that consistently uses this plugin. I think I've only heard about 5 people actually using it though. I'm just hoping that the other users are just being silent rather than simply nonexistent. Maybe I should just jump on the XILS V bandwagon. It does sound very good. I just love the crazy stuff that Lector does. It's modulation capabilities are pretty awesome, it has 100 frequency bands, HUGE-sounding chorus, a separate vocoder band modulation section (in addition to the LFO for the oscillators/filter). If there's another vocoder that does all that I could just start using a different one, I suppose. I'm guessing Reaktor has some pretty crazy ones. The vocoding in Razor seems pretty bland feature-wise though.

The past 3 times I've submitted a support request for Waldorf, I seem to always get the same person. I hope this isn't indicative of a bigger problem. I think the company has a lot of potential, but not if their support continues to wane.

Anyway, thank you for trying to help. I know it's not your plugin. It's just nice to get some input from a developer.

-Sam

[AdmiralQuality]

I'd recommend being a bit more scientific in your tests. Like, does a new project that ONLY has Lector in it and nothing else exhibit that same crashing behavior? Try to reduce the complexity as much as you can, and then add the other plug-ins one by one. You may find it's an interaction with some other plug-in (which can greatly reduce your chances of other users having it happen to them too).

I'd trust Waldorf that they can't replicate it if that's what they say. And it's virtually impossible to debug a bug you can't replicate. But if you can come up with a methodology that reliably crashes it, then that can help them a lot. (Particularly if it happens when no other plug-ins are loaded.)

[mcnoone]

Try this.
http://www.machelpmate.com/index.php?op ... &Itemid=33
Run all the maintenance tasks.
Then repair the permissions.
See if it helps.
The cache cleaning, and "deep cleaning on reboot" are the important ones.

Also try to manually repair permissions on the vst, and au folders.

[masterhiggins]

Try this.
http://www.machelpmate.com/index.php?op ... &Itemid=33
Run all the maintenance tasks.
Then repair the permissions.
See if it helps.
The cache cleaning, and "deep cleaning on reboot" are the important ones.

Also try to manually repair permissions on the vst, and au folders.

Hi there. Thanks for the info. I've performed the cleanup scrips with Onyx. MacHelpMate appears to be for an older version of OS X (10.6). I ran all of the maintenance tasks, repaired the permissions, and manually repaired the permissions on the AU and VST folders. I wasn't able to see an option for deep cleaning on reboot, but I'll try to look more tomorrow.

AdmiralQuality,

Why do you suppose some developers choose to use a VST3>AU wrapper instead of just porting to AU directly? Do most developers do it or is it just a "lazy" way to package an AU plugin? I'm not a developer, of course, but I'd imagine that wrapping a plugin in another format would only increase the odds that the plugin would inherit vulnerabilities from the weakest point (in this case VST3). Is this not true? Thanks!

-Sam