Cabbage Logo
Back to Cabbage Site

Bidule P64 version and Cabbage

#21

I should add, this is on Renoise (latest 3.2.1) and Bidule (latest 0.9764)

Will try the latest build. Tbh I tested it last night, at the end of a long, hard day!

#22

I can try Renoise myself here when I get a chance. :wink:

#23

I think you mentioned that Bidule for you required a license? In case ur interested - the download of the standalone should be good until June 2020 I think? :wink:

#24

Still no joy with either AU or VSTs exported from this version. I cleared the plugin caches for Bidule to force it to rescan. I then added a new export of Soundwarp File Player, opened Bidule, then it crashed on scan, and I got this:

0   com.cabbageaudio.SoundwarpFilePlayer	0x0000000116a42122 CabbagePluginProcessor::CabbagePluginProcessor(juce::File, juce::AudioChannelSet, juce::AudioChannelSet) + 1666
1   com.cabbageaudio.SoundwarpFilePlayer	0x00000001169e889c (anonymous namespace)::pluginEntryPoint(long long (*)(Vst2::AEffect*, int, int, long long, void*, float)) + 7852
2   com.plogue.bidule             	0x000000010f4f7ef0 0x10f188000 + 3604208
3   com.plogue.bidule             	0x000000010f4f5055 0x10f188000 + 3592277
4   com.plogue.bidule             	0x000000010f4f759e 0x10f188000 + 3601822
5   com.plogue.bidule             	0x000000010f4f14de 0x10f188000 + 3577054
6   com.plogue.bidule             	0x000000010f3ef7a8 0x10f188000 + 2521000
7   com.plogue.bidule             	0x000000010f268fab 0x10f188000 + 921515
8   com.plogue.bidule             	0x000000010f935c21 0x10f188000 + 8051745
9   com.plogue.bidule             	0x000000010f25963d 0x10f188000 + 857661
10  libdyld.dylib                 	0x00007fff6af713d5 start + 1

and this (most relevant to the above I think) is from the bidule_x64.log:

I:4731803072:7020906964:VSTFactory init
I:4731803072:7021152000:Saving VST Cache
I:4731803072:7021153013:Saving VST Cache done
I:4731803072:7021153023:Saving VST Filelist Cache
I:4731803072:7021153562:Saving VST Filelist Cache done
I:4731803072:7021178850:Updating VST cache .. in /Users/boonier/Library/Application Support/Plogue/Bidule/vst_x64.cache with 1 new entries.
I:4731803072:7021178882:dll,longId,uniqueID,vendor,effname,product,numParams,numInputs,numOutputs,isSynth,canReceiveMidi,canSendMidi,canSendVstTimeInfo,canReceiveVstTimeInfo,canReplace
/Users/boonier/Library/Audio/Plug-Ins/VST/SoundwarpFilePlayer.vst is a VST 2.4
#25

same for Renoise, though I don’t think this is particularly helpful (from Renoise.log):

VstPlugs: Plugin is a Mach-O executable...
VstPlugs: Loading bundle: '/Users/boonier/Library/Audio/Plug-Ins/VST/SoundwarpFilePlayer.vst'
VstPlugs: Instantiate FAILED (caught fatal exception)!
VstPlugs: CreateInstance FAILED

Audio Plugins: Failed to open plug VST: SoundwarpFilePlayer

Exception: Failed to initialize the plugin 'VST: CabbageAudio: SoundwarpFilePlayer'.

Error Message: Failed to initialize the plugin 'VST: CabbageAudio: SoundwarpFilePlayer'.
#26

Thanks for looking into this. I should be able to recreate this myself tomorrow morning and go from there.

#27

I just tried here with Renoise 3.1 and the standalone version of bidule, and I can load my newly exported plugins without a problem?

18
181465×713 72.5 KB
46
461245×722 101 KB

#28

is that in the P64 version of Bidule? does the plugin load the audio file too?

I don’t understand. I spent considerable time yesterday deleting cache files and rescanning. Bidule would actually crash when scanning my plugin!

#29

Same result on my laptop :stuck_out_tongue_closed_eyes:

Hangs at this point image

#30

That’s very odd. I always expect some kind of issues with AUdioUnits, but VSTs rarely ever cause problems. Does Bidule just hang at this point? I’m using the 64 bit version…

#31

Yeah, just freezes and I have to force quit it. It was the same on the iMac last nite.

FWIW I’m on Csound 6.14
Mojave 10.14.6

What else am I missing?..

#32

Hmm. I’m using 10.13.6 and Csound 6.13. I doubt the Csound version is an issue, but I worry about the fact you’re using 10.14. I wonder are there any other 10.14 users out there? Out of curiosity, why did you upgrade to 10.14?

#33

Good question. It was a work related reason - I develop apps in React Native and the Xcode and SDK versions had to be updated to latest, which meant upgrading the whole OS. Bloody Apple! I was happy on 10.13 to be honest.

#34

I’m afraid to upgrade. It seems every time I do I get problems. For what it’s worth, have you tried restarting?

#35

I’m afraid to upgrade

on the whole, it’s been absolutely fine. None of my hardware got deprecated thank f***

tried restarting?

after adding the exported plugin? No I haven’t but I will give it a go

#36

just did a search https://forum.cabbageaudio.com/search?q=10.14

seems that there are a few users!

#37

But most seem to be able to load their plugins at least. The problems they reported have all been resolved afaik. Will I update :thinking: it’s a tough one…

#38

Articles like these put me off:
https://cdm.link/?s=10.14

#39

I should add, the plugins created with versions of Cabbage < 2.3.22 or 2.3.21 seem to validate fine. (Just not in the P64 Bidule :slight_smile:)

Oh yeah, staying clear of CAtalina for as long as…

#40

Ok. I’ve updated some processing code, so that might explain the latest problems. Can you try the latest version here.

Let me know. Hopefully, it will work for you as it does here…