Multiple initialization of vst reported in console log
I’m trying to debug crashes that I’m still seeing in Max 6.0.7 related to handling vst objects
I have noticed that if I have a trivial patcher that just sends a plug message to a vst, the console log tells me that it loaded the plugin twice. See below. I don’t know if this is just a logging mistake or if in fact the VST is being loaded and then reloaded immediately.
10/6/12 9:00:01.143 AM [0x0-0x5a05a].com.cycling74.Max: Attempting to load VST: /Library/Audio/Plug-Ins/VST/Crystal.vst
10/6/12 9:00:01.147 AM [0x0-0x5a05a].com.cycling74.Max: Creating VST instance: Crystal
10/6/12 9:00:01.192 AM [0x0-0x5a05a].com.cycling74.Max: Initialising VST: Crystal
10/6/12 9:00:01.237 AM [0x0-0x5a05a].com.cycling74.Max: Attempting to load VST: /Library/Audio/Plug-Ins/VST/Crystal.vst
10/6/12 9:00:01.237 AM [0x0-0x5a05a].com.cycling74.Max: Creating VST instance: Crystal
10/6/12 9:00:01.264 AM [0x0-0x5a05a].com.cycling74.Max: Initialising VST: Crystal
You could verify this with some big sampler plug like eg. Kontakt.
Loading twice may then be visible by consecutive loading process windows.
Not sure what you mean? Are you talking about the dialog that pops up when you load a library preset? I’m earlier than that, just loading the synth itself.
My bad, I misunderstood the problem. But have you looked at the Max window? I think it reports some information whenever a synth is loaded.
Other than stuff explicitly sent to the [print] object, the Max window typically displays only errors.
Max 6 seems to generate all sorts of stuff in the system logs (accessible easily via Console application) including the apparent double initialization of VSTs.
At this point, I’m again having trouble using Max 6 reliably and my problems seem mostly related to JUCE and VSTs so I’m trying to understand what’s going on under the covers. So I’d like to know whether it’s just a log error or whether in fact VSTs are being instantiated twice (and if so, what happens to them)?