Currently switching from my old audio PC to a new Mac ... unfortunately cannot make the MIDI program change work in Repro-5.
I have installed Repro-5 (latest version) and copied my presets to the MIDI Programs folder at:
/Library/Audio/Presets/u-he/Repro-5/MIDI Programs
The presets are shown in Repro-5 as expected and I can switch them manually. But when I send a program change event (and I can see that it is being sent correctly - I see it in the MIDI monitor of my daw and I see a brief flash of Repro-5's MIDI-In led) nothing happens.
This is the VST3 version, I use VST Live 2 and/or Cubase as my hosts.
Any ideas?
Thanks, Chris
Problem with program changes in Repro-5 ...
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 2170 posts since 22 Mar, 2005 from a planet called u-he
After you made changes to the presets in the MIDI programs folder, you first need to restart your host.
And it can not work in Ableton Live, because Ableton does not support MIDI program changes when using the VST3 format.
You'd have to use either VST2 or AU in Live to use this feature.
And it can not work in Ableton Live, because Ableton does not support MIDI program changes when using the VST3 format.
You'd have to use either VST2 or AU in Live to use this feature.
That QA guy from planet u-he.
-
- KVRAF
- 2245 posts since 10 Apr, 2002 from Saint Germain en Laye, France
What a shame from Ableton 
-
- KVRer
- Topic Starter
- 11 posts since 6 Sep, 2010
Thanks for the info, I‘ll give it a try.
BTW my hosts are VST Live 2 (from Steinberg) and Cubase not Ableton Live. Unfortunately the Apple-silicon native version on Cubase 14 no longer supports VST 2 so hoping for a fix from U-He …
BTW my hosts are VST Live 2 (from Steinberg) and Cubase not Ableton Live. Unfortunately the Apple-silicon native version on Cubase 14 no longer supports VST 2 so hoping for a fix from U-He …
-
- KVRAF
- 2245 posts since 10 Apr, 2002 from Saint Germain en Laye, France
No, we need a fix from Steinberg and Ableton
-
- KVRer
- Topic Starter
- 11 posts since 6 Sep, 2010
According to my (brief) research, VST3s can support patch changes in reaction to MIDI program changes, there’s just some additional abstract wrapper around the program change which needs to be handled in the VST3. The respective event is forwarded from hosts like Cubase or VST Live to the plugins and there are VST3 plugins where the program change works nicely.
Any chance to see this implemented for U-He plugins?
Any chance to see this implemented for U-He plugins?
-
- u-he
- 30180 posts since 8 Aug, 2002 from Berlin
We have implemented it. It works in Cubase etc.
If it does not work in VST3 Live then we have no means to investigate how it differs from Cubase - all we see in such cases is "it does not send the event". Therefore I'd suggest to raise the issue with them. If they think we do something wrong, they are welcome to let us know.
If it does not work in VST3 Live then we have no means to investigate how it differs from Cubase - all we see in such cases is "it does not send the event". Therefore I'd suggest to raise the issue with them. If they think we do something wrong, they are welcome to let us know.
-
- KVRAF
- 24404 posts since 7 Jan, 2009 from Croatia
No Live for sure doesn't support Program Changes with VST3. It's on their end.
-
- KVRAF
- 2245 posts since 10 Apr, 2002 from Saint Germain en Laye, France
-
- u-he
- 30180 posts since 8 Aug, 2002 from Berlin
This was wrong, I stand corrected - from Cubase 13 or so, Program Changes do not work in our VST3 plug-ins anymore. We have no idea what went wrong or what has changed, if anything.
Maybe a new mechanism was added. If that's the case we'll support the new mechanism as soon as we have the resources to look in to it.
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 2170 posts since 22 Mar, 2005 from a planet called u-he
Sorry for the confusion, guys.
Naming your host Live is an awkward decision, when there's already Ableton Live.
That's what got me confused.
Just searched through our bug tracking database.
We deliberately deactivated VST3 program changes if the host is a Steinberg host.
This was done some years ago, after we discovered a serious bug in Steinberg's VST3 program change implementation.
We kept this function deactivated ever since, so users of old Cubase versions would not run into this issue when using our plugins.
Naming your host Live is an awkward decision, when there's already Ableton Live.
That's what got me confused.
Just searched through our bug tracking database.
We deliberately deactivated VST3 program changes if the host is a Steinberg host.
This was done some years ago, after we discovered a serious bug in Steinberg's VST3 program change implementation.
We kept this function deactivated ever since, so users of old Cubase versions would not run into this issue when using our plugins.
That QA guy from planet u-he.
-
- KVRer
- Topic Starter
- 11 posts since 6 Sep, 2010
Retested VST3 program changes with a couple of other manufacturer's plugins in Steinberg VST Live 2:tasmaniandevil wrote: Mon Nov 18, 2024 10:59 am Just searched through our bug tracking database.
We deliberately deactivated VST3 program changes if the host is a Steinberg host.
This was done some years ago, after we discovered a serious bug in Steinberg's VST3 program change implementation.
We kept this function deactivated ever since, so users of old Cubase versions would not run into this issue when using our plugins.
- Some Steinberg VST3s
- Arturia V-Collection X
- Some Cherry Audio Instruments (Blue3, PS-3300)
- Some Native Instruments stuff (FM8, Massive)
So *maybe* you could consider to re-enable this feature (at least optionally by a switch in the UI or a config file change).
The problem is that Cubase 14 (and probably VST Live 2 as well in the foreseeable future as they share some core code) do no longer support VST2 plugins on Apple-silicon Macs unless the DAW is running in Rosetta Intel emulation mode.
And on my laptop used for playing live, I cannot use a parallel dedicated plugin instance for each song for performance reasons.