Windows/Mac VST issues

[stoo]

Hello all, new to the forum.

I'm using Bidule for testing some multi-channel (16in - 16out) VST plugins that I've developed, they're working fine on Windows but the time has come to make some Mac versions. So I've recompiled a VST on the Mac and opened it in Bidule, but there are some really strange problems: the GUI shows fine but most of the components don't update (most noticeably the VU meters), and from listening to the output the audio seems to be bypassing most of the processing stages of the algorithm. I have tried manual methods of automating the GUI and it updates just fine, so it seems to be purely an audio routing issue. Interestingly the Mac VST works perfectly on Cubase, so it seems to have compiled correctly, but clearly there's some kind of compatibility problem between it and Bidule OSX.

So basically, before I spend hours debugging the problem line by line, has anybody got any suggestions as to differences between the PC and Mac versions of Bidule relating to VSTs? I used Juce to create the plugins, supposedly totally cross-platform compatible and I wasn't expecting any problems!

Thanks very much.

[seb@plogue]

If it sounds like the signal goes through dry, did you check if Bidule automatically set your plug-in to bypass?

From which thread are you updating your controls? Are you installing your own timer on the UI thread or are you relying on effEditIdle calls?

[stoo]

Thanks for the quick reply.

Yeah the plugin definitely stays in processing mode. For the GUI update, I'm not too confident with specific VST calls as I haven't delved too far beneath Juce's architecture, but there's a manual 50ms timer and a call back function from which the controls update. For instance, within the callback function I have calls such as:

Code: Select all

slider49->setValue   (ourProcessor->K_GUI[0]);


Which doesn't update, but if I replace the K_GUI[0] variable with, for example, an incrementing integer separate from the processor, that will update fine. But the audio isn't completely bypassing my processing part, I have a master LR fader updated from within the same callback which monitors the output and adapts to prevent clipping, and that will adjust fine if I boost the input signals. Strange.

[stoo]

Getting closer, Bidule doesn't seem to like the way arrays are used in the processing code. If I allocate each VU meter its own variable, rather than an index in an array, then I can get the levels to show. I'll try a few things and report back.

[seb@plogue]

I would be surprised using arrays vs not makes a difference. Are you sure you're no doing reading/writing overflow which would give quite different results from host to host.