KVR Audio

blof_eld · Post by **blof_eld** » Sat Aug 20, 2022 12:07 pm

Using Ableton 11.0.11 and BlueARP does not pass through Modwheel (or any midi cc's actually).

I have Scaler 2 -> BlueARP -> a VST synth on separate channels.

I've added MIDIMonitor m4l device before BlueARP and I can see the modwheel messages, but I can't see any modwheel messages on the MIDIMonitor before my Synth.

So BlueARP isn't passing through the Modwheel messages.

Edit: I discovered that it works with the VST2 version but not the VST3 version. Both are v2.3.8.

chk071 · Post by **chk071** » Sat Aug 20, 2022 12:22 pm

Sounds familiar... I think we just had a similar thread not long ago. Like you said, the VST3 is the issue. Use the VST2 instead.

phreaque · Post by **phreaque** » Sat Aug 20, 2022 12:23 pm

blof_eld wrote: Sat Aug 20, 2022 12:07 pm Edit: I discovered that it works with the VST2 version but not the VST3 version. Both are v2.3.8.

Good you discovered that quickly. VST3 sucks in handling MIDI CC's

blof_eld · Post by **blof_eld** » Sat Aug 20, 2022 1:43 pm

phreaque wrote: Sat Aug 20, 2022 12:23 pm
blof_eld wrote: Sat Aug 20, 2022 12:07 pm Edit: I discovered that it works with the VST2 version but not the VST3 version. Both are v2.3.8.
Good you discovered that quickly. VST3 sucks in handling MIDI CC's

Who said I discovered it quickly??

Took me half an hour of mucking around, then I wrote that message, and while I was writing it I thought of trying the VST2 because I've had trouble with different versions of a plugin before. Decided to post the message anyway because my googling didn't come up with anything, maybe my post can save someone the time.

phreaque · Post by **phreaque** » Sun Aug 28, 2022 6:21 pm

New video, very useful:

chk071 · Post by **chk071** » Sun Aug 28, 2022 6:28 pm

Yeah, I watched that earlier.

Well, would have been a surprise if BlueARP couldn't do what the ANA arp can.

Maximo Asensio · Post by **Maximo Asensio** » Wed Aug 31, 2022 9:35 pm

Hello.

A few days ago I downloaded the latest version (.8 VST3) of your BlueARP VST plugin. I installed it and it worked out of the box in my Daw; Ableton 11. I was pleasantly surprised by its versatility.
But when I got to the functionalities of the chain program box, the problem arose. If we understand BlueARP as an arpeguiator/sequencer, the arpeguiator is ok, but the sequencer just doesn't work, at least in Ableton.
In the latest version of vst3, and in the previous 3 (versions .5,. 6 and .7 ), which I downloaded and installed.
The digits that appear in the current chain boxes do not correspond to what was initially selected.
So if there is a change to the next chain (if it occurs) these jumps are totally unpredictable, although most of the time they do not occur while staying in the same chain.
Has any other user reported such a malfunction?
Is this a compatibility issue with my software?
Greetings, thank you and congratulations for your work.

phreaque · Post by **phreaque** » Thu Sep 01, 2022 6:14 am

Hi

Maximo Asensio wrote: Wed Aug 31, 2022 9:35 pm In the latest version of vst3, and in the previous 3 (versions .5,. 6 and .7 ), which I downloaded and installed.

Before diving deeper, try using VST 2.4 instead & see how it goes.

The digits that appear in the current chain boxes do not correspond to what was initially selected.
So if there is a change to the next chain (if it occurs) these jumps are totally unpredictable, although most of the time they do not occur while staying in the same chain.
Has any other user reported such a malfunction?
Is this a compatibility issue with my software?

Visual explanation (a video) or sharing a simplified project would be very helpful since it is really difficult to explain & to understand music production in texts

graywolf2004 · Post by **graywolf2004** » Sat Sep 03, 2022 4:46 pm

Hi, I postponed this for a while but this is a minor Windows only fix for VST3 v2.3.9, which should solve loud output noise in Cubase (and probably some other DAWs).
https://www.omg-instruments.com/bluearp ... v2.3.9.zip

The reason was is that BlueARP plugin has 'fake' audio outputs which do nothing, but is has to have them, otherwise some DAW's won't recognize it (they don't like midi-only VST plugins, as well as $teinberg). But what it didn't do in VST3 - it didn't clear output buffers, so in some DAWs where those weren't pre-cleaned, random garbage came to the audio output. If you still have this issue, let me know.

Any bugs/critical issues I need to look into? I was idle for a few months for obvious reasons, but now hopefully slowly getting back.

rasmusklump · Post by **rasmusklump** » Sat Sep 03, 2022 5:11 pm

Welcome back.
Nice to hear from you again. I hope you are doing well.

mabian · Post by **mabian** » Sat Sep 03, 2022 5:44 pm

I think I posted a report about weird stuff in the vst3 version with cc automation. I posted also in your new forum, maybe the wrong place... I'll find the link later...

mabian · Post by **mabian** » Sat Sep 03, 2022 9:21 pm

Here it is: viewtopic.php?t=585202

Thanks,
Mario

phreaque · Post by **phreaque** » Sat Sep 03, 2022 10:09 pm

mabian wrote: Sat Sep 03, 2022 9:21 pm Here it is: viewtopic.php?t=585202

Because VST3 format is known of mishandling MIDI CC.

mabian · Post by **mabian** » Sun Sep 04, 2022 8:13 am

phreaque wrote: Sat Sep 03, 2022 10:09 pm
mabian wrote: Sat Sep 03, 2022 9:21 pm Here it is: viewtopic.php?t=585202
Because VST3 format is known of mishandling MIDI CC.

Not sure this is the real reason (not sure all other VST3 plugins I have have the same misbehavior), but I hope nevertheless that this VST3 sh*t is going away . VST2 works so well, maybe it's a less modern and more lousy documented (grey zones) framework but it doesn't get in the way of so many things...

Fingers crossed for CLAP... I know I know if it happens it'll take a lot...

- Mario

francoisphil · Post by **francoisphil** » Tue Sep 06, 2022 2:36 am

Hi , i am using bluearp in linux , with yabridge and Reaper 6 linux , and the latest version crash Reaper , when removing bluearp from a track , removing a track containing bluearp , or even trying to close Reaper if there is a track containing bluearp in the project.So i went back to the 2.3.2 version which works perfectly.

BlueARP VST Arpeggiator development - let's discuss! (Apple M1 ready, 4K)