Rob Papen Blue 3 up

[Echoes in the Attic]

Anyway, for people who have installed the full version, check your VST 3 folder. On both systems here the installer dropped an extra VST 2 .dll in the VST 3 folder. I couldn't figure out why the VST 2 version was showing up twice after scans.

Sometimes developers make VST3s in a way that it points to a VST2 version and without the VST2, the VST3 doesn't work. For example Tone2 VST3 - I removed the VST2 version from the VST2 directory and the VST3 no longer worked. Perhaps RP thought it best to include a needed VST2 in the VST3 folder in case people deleted the VST2 from the VST2 folder thinking it was unneeded.

Yep - Just tested. Removed the dll from the VST3 folder and the interface wouldn't load.

That might be a problem though as VST2 becomes more deprecated such as on Apple Silicon. Also it’s interesting that none of these wrapped plugins from Tone2 or Rob Papen support VST2 to VST3 migration because you would think it would make that easier

I'm not sure if deprecation on an OS would mean that the dll could no longer be used as a reference for a VST3, but either way, I tend to prefer a self-contained VST3.

[Teksonik]

Sometimes developers make VST3s in a way that it points to a VST2 version and without the VST2, the VST3 doesn't work. For example Tone2 VST3 - I removed the VST2 version from the VST2 directory and the VST3 no longer worked. Perhaps RP thought it best to include a needed VST2 in the VST3 folder in case people deleted the VST2 from the VST2 folder thinking it was unneeded.

Yep - Just tested. Removed the dll from the VST3 folder and the interface wouldn't load.

That's news to me. I just checked and the only other developer in my VST 3 folder who does it that way is iZotope and their plugins don't show up as duplicate entries in Bitwig but then I often don't even bother installing the VST 3 version of a plugin so don't have all that many compared to VST2.

Even Rob's Predator 3 doesn't do it that way, at least there's not a 2 .dll in the 3 folder here.

The problem is if I select one of the VST 2 files and send it to Favorites in Bitwig, then Blue 3 shows up twice on the list. Certainly not a big deal but I do like to keep my favorite list clean. Since I primarily use VST 2 version of plugins I can just move the second VST .dll out for now and rescan.

I have a feeling that the VST2 version in the VST 3 folder is not supposed to show up in plugin scans alongside the VST2.dll installed in whatever location we chose.

Anyway I haven't got a crash yet today while working in Bitwig but that might just be a testament to it's stability rather than the performance of Blue 3. .

[Echoes in the Attic]

Sometimes developers make VST3s in a way that it points to a VST2 version and without the VST2, the VST3 doesn't work. For example Tone2 VST3 - I removed the VST2 version from the VST2 directory and the VST3 no longer worked. Perhaps RP thought it best to include a needed VST2 in the VST3 folder in case people deleted the VST2 from the VST2 folder thinking it was unneeded.

Yep - Just tested. Removed the dll from the VST3 folder and the interface wouldn't load.

That's news to me. I just checked and the only other developer in my VST 3 folder who does it that way is iZotope and their plugins don't show up as duplicate entries in Bitwig but then I often don't even bother installing the VST 3 version of a plugin so don't have all that many compared to VST2.

Even Rob's Predator 3 doesn't do it that way, at least there's not a 2 .dll in the 3 folder here.

The problem is if I select one of the VST 2 files and send it to Favorites in Bitwig, then Blue 3 shows up twice on the list. Certainly not a big deal but I do like to keep my favorite list clean. Since I primarily use VST 2 version of plugins I can just move the second VST .dll out for now and rescan.

I have a feeling that the VST2 version in the VST 3 folder is not supposed to show up in plugin scans alongside the VST2.dll installed in whatever location we chose.

Anyway I haven't got a crash yet today while working in Bitwig but that might just be a testament to it's stability rather than the performance of Blue 3. .

Yeah it definitely is not ideal to have two VST2s. My guess is that they did this so that you could chose not to install the VST2 in the normal VST2 directory. I don't have my VST2 folder turned on anymore in Bitwig, but Bitwig doesn't see the VST2 in the VST3 folder (Not sure why turning off the VST2 directory would mean it doesn't see a VST2 in the VST3 folder but for me it doesn't). I don't remember now if the installer had a VST3 only option. That's the only reason I could think why it's included along with the VST3. Maybe a question for support.

[Dencheg]

I've got Blue 3 via Sweetwater... Initially I paid for Blue II, then there was some delay cause at that very moment they were switching to Blue 3, so they sent me a Blue 3 license.
Long story short - I can use Blue 3, but not Blue 2, which says "Invalid Serial, Please re-install Blue 2"

[matamoris]

I'm disappointed that the GUI still isn't fully hi-def ready. On my 5k iMac, some text is blurry and/or pixelated.

[Teksonik]

My guess is that they did this so that you could chose not to install the VST2 in the normal VST2 directory.

I wonder if in this case the .vst3 file acts more like a wrapper if the VST2 .dll is required for it to function? Would that make it not really a native .vst3 version? (I don't really care just wondering out loud)

I'm disappointed that the GUI still isn't fully hi-def ready. On my 5k iMac, some text is blurry and/or pixelated.

Even at 200% GUI size ?

Oh and I got another crash today, this time in Bitwig which thanks to its sand boxing didn't crash but Blue 3 did go down again.

[Echoes in the Attic]

My guess is that they did this so that you could chose not to install the VST2 in the normal VST2 directory.

I wonder if in this case the .vst3 file acts more like a wrapper if the VST2 .dll is required for it to function? Would that make it not really a native .vst3 version? (I don't really care just wondering out loud)

Yes often times VST3s are wrapped VST2. But sometimes devs don't even bother to wrap it up in a single file. I don't know why.

[Boy Wonder]

Interesting. I just checked the Papen's RP-Pan Vst3 folder and there's a RP-Pan dll there as well. I removed it and RP-Pan stopped working, so I put it back. Bidule and Cubase ignored the dll but I guess Bitwig didn't.

[Teksonik]

Yes often times VST3s are wrapped VST2. But sometimes devs don't even bother to wrap it up in a single file. I don't know why.

Just easier that way? It seems like a VT2 with a VST3 wrapper would be the least efficient form to use.

Interesting. I just checked the Papen's RP-Pan Vst3 folder and there's a RP-Pan dll there as well. I removed it and RP-Pan stopped working, so I put it back. Bidule and Cubase ignored the dll but I guess Bitwig didn't.

Same with RP Pan here. Maybe it's something Rob Papen just started doing because like I said it's not that way with Predator 3.

Oh well not a big deal just an annoyance.

Has anyone done any sound design with the full version of Blue 3 yet? That's when I've been getting the crashes I've been experiencing, right in the middle of making a patch. There doesn't seem to be any issues with just browsing presets.

[Gribs]

This is strange: I cross-graded Blue 2 + Blade I to the Sound Design-X package a while ago and now there is no place to click to get a coupon for a Blue 3 upgrade at the reduced price. Hmm...

[cryophonik]

Nicely surprised to see that my 4 RP products (including Blue2 and a few cheap effects) qualified me for a $74 upgrade to Explorer 8.

[Gribs]

Nicely surprised to see that my 4 RP products (including Blue2 and a few cheap effects) qualified me for a $74 upgrade to Explorer 8.

Yeah, that is probably the thing to do from the Sound Design X bundle.

[bite_me]

These novembers are exhausting ...

[ramseysounds]

Nicely surprised to see that my 4 RP products (including Blue2 and a few cheap effects) qualified me for a $74 upgrade to Explorer 8.

Theres some great synths in the full explorer pack. Well worth the upgrade bundle price. Enjoy

[ralfrobert]

Nicely surprised to see that my 4 RP products (including Blue2 and a few cheap effects) qualified me for a $74 upgrade to Explorer 8.

Yeah, that is probably the thing to do from the Sound Design X bundle.

Just drop them a message and see what they have to offer. RP support is very responsive and helpful.