Rob Papen Blue 3 up

[hurricaneaudiolab]

He needs to have someone else do his GUIs. They’re not the worst I’ve seen, but they’re not good.

OMG yes please.

I don't believe he will though because when Predator RE was released and I emailed him about the simplistic and bland RE gui he said something to the effect of "no one cares about the way it looks, it's all about the sound".

[zerocrossing]

Being able to load up your own samples is huge, considering you can use them for FM. Fun.

[abducted]

Is there a way to assign velocity (or a midi controller) to sample start ?

[LoveEnigma18]

He needs to have someone else do his GUIs. They’re not the worst I’ve seen, but they’re not good.

I was afraid of this being a possible case for Blue 3, which it is, so I skipped on the awesome ~$52 deal on Blue 2 (with free upgrade to Blue 3) on Best Service up until 15th November.

I have owned and used Albino 3 a lot in the past and sold it some time ago. Kicking myself a little bit for skipping the deal as Blue is something I always wished to own, but at the moment I am not digging the new Blue 3 GUI and I haven't even downloaded the demo yet. Maybe I will give it a try in the future, but there's a lot of other plugins already on the table for now.

Sound wise, no complains at all. It is amazing.

[Echoes in the Attic]

Yeah other than the pain panel knobs being more high res, which is good, the rest of the GUI is worse than V2 (at least contrast/readability). It's too bad. But it's not terrible.

[Teksonik]

Judging just on the early screenshots I didn't think I would like the Blue 3 gui either but after using it for hours yesterday I've warmed up to it quite a bit.

Still not a fan of the new knobs but tabs like Samples, Arp/Seq, Browser etc are all so easy on my eyes I could work with them for hours with no strain. I find the workflow intuitive and fast considering the depth of the instrument and the colors just suite my eyes perfectly.

Of course "good gui" is as subjective as "good sound" so I think everyone should really try the demo while the deal is on.

To me Blue 3 is such a great sounding synth that I can live with a GUI that's not 100% to my liking.

Unfortunately I had stability issues yesterday so I'm going to work with Blue 3 today in other DAWs to see if I have the same issues.

[Boy Wonder]

I'm sure, somewhere along the way, somebody will make a new skin for Blue III.

[Satch1]

Is there a way to assign velocity (or a midi controller) to sample start ?

Yes… you have to assign it using the mod matrix. It’s in each of the Osc menus.

EDIT: It’s named ‘Osc Sample Offset’

[Echoes in the Attic]

Any MPE users? Anyuone know how to modulate with Y axis (timbre)?

[Teksonik]

I'm sure, somewhere along the way, somebody will make a new skin for Blue III.

I don't believe Blue 3 can be skinned unless you hack the .dll and I don't advise that.

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.

[Teksonik]

Any MPE users? Anyuone know how to modulate with Y axis (timbre)?

Sorry, I am not an MPE user.

[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.

[tremolounge]

Well, here's a little problem.... Upgraded and installed Blue 3 yesterday; today I opened a Studio One session where I used GG Audio's B-3 emulation called... Blue 3... and get a plugin not found message. Looks like RP Blue 3 overwrites GG Blue 3 in the Components folder.

Workaround: Install GG Audio Blue 3 as AU, and RP Blue 3 as VST3. Tested, and (so far) they can coexist in a session (just have to remember which is which).

[aMUSEd]

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

[teilo]

Their String model needs work. Something weird going on with the impulse engine where some notes just don't fire correctly.