[6.30+] Automations recorded in a track are not sent to VST3i

[m-scozza]

Hi all, I'm going to report a possible bug: starting from Reaper v. 6.30 in the MIDI tracks containing automations, the notes are played regularly while the automation itself is not sent (I tried with the Pitch Bend and Mod Wheel).

I have tried using different plugins (eg Pigments or Zebra2) and the problem always occurs when using VST3i, while all VSTi work fine.

Going back to Reaper v. 6.29 everything works fine.

I'm using:
- Windows 10 21H1,
- Reaper x64,
- AMD Ryzen 3700x,
- RAM 32Gb.,
- SSD Samsung 960 1Tb
- Soundcard RME Digiface USB

[schwa]

What do you mean by automations, exactly? Could you possibly attach a (very small) project that demonstrates the problem using Zebra2, or describe how to create a project?

[m-scozza]

Originally Posted by schwa

What do you mean by automations, exactly? Could you possibly attach a (very small) project that demonstrates the problem using Zebra2, or describe how to create a project?

Yes, of course

What I mean is what you can see in the attached picture :-)

The attached project has 2 IDENTICAL tracks, the first one uses the VSTi while the second one the VST3i version of Zebra2. The first one works and the second one not.

[schwa]

Thanks for posting the project. The playback sounds the (more or less) same to me in REAPER 6.28 and REAPER 6.32 Here are the rendered files:

https://stash.reaper.fm/42425/Funkaf...APER%20628.ogg
https://stash.reaper.fm/42424/Funkaf...APER%20632.ogg

Does it sound different when you play it back? I'm using "REV 10409" of the VST3.

[m-scozza]

Hi, in the attached .rar I've included the audio files so you can listen what happens to me.
If in your system it works, could it be a different setting somewhere that from 6.30 on started to work in a different way?

[schwa]

Do you have the latest version of the plugin?

[m-scozza]

Yes, they are all updated at the newer version.
I've tested also with old versions, the issue is still there.
Please note that I've this issue with *ALL* the VST3s, not only Zebra2 and Pigments.

[schwa]

Could you post your reaper.ini file please?

[m-scozza]

Here it is.

[schwa]

Are you running the plugin bridged by any chance?

Could you attach all of the .ini files in the AppData/.../REAPER folder please?

[m-scozza]

Originally Posted by schwa

Are you running the plugin bridged by any chance?

I don't know what it means :-)

Originally Posted by schwa

Could you attach all of the .ini files in the AppData/.../REAPER folder please?

Here they are.

[Justin]

Originally Posted by m-scozza

I don't know what it means :-)



Here they are.

If you could go to preferences/plug-ins/compatibilty, and change the bridging option there to be "Automatic", it should fix.

[m-scozza]

Now it works, thank you so much for your kind effort!

Only a last question, just for my information: this issue is due to a bug or is a different behaviour of the VST bridging?

[schwa]

Your preferences were set up to always run VSTs bridged, that's something you must have changed at some point, maybe unintentionally.

Prior to 6.30, VST3 bridging was not supported in REAPER, so that preference had no effect for VST3s. As of 6.30, VST3 bridging was introduced, but bridging did not yet support passing MIDI CC data to VST3s.

For the next release, we've removed the option to always run VSTs bridged, because it leads to unintended situations like this. We've also added MIDI CC support to VST3 bridging, so if you do choose to run a specific VST3 synth bridged, it will work as expected.

[m-scozza]

Thank you! :-)