V Collection X is Bugged in Bitwig

Software Instruments V Collection
#1

There appears to be a bug using V Collection in Bitwig (in Analog Lab Pro and all the individual VSTi plugins) that prevents many presets from loading properly. Presets will load and not output any sound; you have to switch to another preset and back to your target preset to fix the issue - and even after that, sometimes the preset will still not output sound properly.

I put up a thread on Reddit asking about this, and several other people are confirming they’re having this same exact issue on Bitwig and Bitwig only (both on Windows and Mac).

I have loaded V Collection on Bitwig (v5.25), Cubase Pro 14, FL Studio, and Reaper… the issue only occurs on Bitwig.

Any advice here is appreciated.

2 Likes
#2

A user on the Reddit thread noted that the Arturia devs are aware of this issue and working on a fix. In the meantime, clicking on the patch multiple times within the preset browser will get every sound to load properly. That’s the workaround for now until an update gets pushed out.

#3

Ditto, Same problem!

#4

Hi,

It reassures me to see that I’m not the only one in this situation. I have a new computer, with just Bitwig, Arturia V Collection and the Arturia AudioFuse 16rig interface installed. No keyboards or controllers. And when I tried my Arturia VSTs, I noticed right away that certain presets no longer had volume and that every time I changed the preset a little asterisk appeared next to the name. I searched and searched and searched for where these changes could come from and I didn’t really find anything. But I understand now that it’s a bug.

All we have to do is wait for a fix!

#5

Yeah, same problem here , they released an update yesterday(ish?) and still not solved it.
I’m going to try a few downgrade to see if it gets better, I think I used it on the laptop which is not up to date by 3 version ago and didn’t have any issue…

#6

Hi @Darouge ,

Who are they?
Who have updated what?

An ASC update is just an update of ASC and nothing else, if that’s what you mean.

Did i read somewhere that Bitwig have tried to do something about this issue? Is that what you mean?

#7

“They” are bitwig guys.
Today I downgraded to bitwig 5.2.3 and playing around for 30 min I didn’t notice any problem.

#8

Thanks for that information @Darouge

#9

I have the same thing, just bought and installed V Collection X a few days ago. It only happens in Bitwig in combination with the Analog Lab V plugin. Running the same plugin in Ableton 12 works flawlessly.

Also noticed that the name of the plugin consistently is named as: ‘Romanmtic e Piano’ (exactly that spelling) in Bitwig for some strange reason. This happened to be my default preset from the DX7 in Analog Lab V(ROM1A 11-E.PIANO).

I have noticed that in my case the individual instrument plugins do load the presets correctly though (DX7 V, Korg MS-20 V, Jun 6 V, MiniFreak V etc.). Also I noticed that sometimes clicking multiple times the preset does indeed provide a sound output, but the preset may still not be loaded properly, since it sounds differently than the preset loaded via the direct instrument plugin. The individual instrument plugins from the bundle do get named correctly in Bitwig when loaded.