Cubase 8/8.5/9/9.5 Issue For Mac

• Cubase 8/8.5/9/9.5 Issue For Mac Free

In Cubase 8.5 and 9.5 (both Windows and Mac) I’m seeing the following strange behavior with my VST2 plugin:. put the plugin on an audio track: - OK, plugin starts up with 1st program named “Default” and corresponding settings. change the program of the plugin to the 2nd one in the list of plugin programs, using the Cubase plugin program list in the Cubase interface: - OK, settings are changed to the ones for that program, and the program name in the Cubase interface is updated correctly. set back the plugin program to the first one (“Default”): - NOT OK! Settings are not being set to the “Default” program (they remain the same as the ones set in 2.), but the program name does change to “Default” in the Cubase GUI My plugin is built with Juce 5.3.1 (master), but this also happens with a much older version from several years ago.

Buy Cubase Pro 10 now Steinberg Online Shop. All in a sleek, expandable Thunderbolt 3 package for Mac and PC. جديد لأصحاب MG2 EDITION. Cubase 9.5.40 Activation Code is designed by keeping in touch with all the professional requirements of producers, engineers as well as composers. Also, it offers features for limitless creativity, high technology as well as very best productivity. If you need any type of composing or mixing you can perform these operations as much.

I’m using 127 programs, represented internally by a 2D array of floats, a 1D array of strings for the program names and an int member variable for the current program. I’m implementing getNumPrograms, getCurrentProgram, setCurrentProgram, getProgramName, changeProgramName, getStateInformation, getCurrentProgramStateInformation, setStateInformation, setCurrentProgramStateInformation. Plugin state is saving and restoring correctly. I don’t see this problem in about 4 other VST2 hosts (Bidule, Live, Reaper, FLStudio).

I also tested with older versions of Cubase (5.5.3, 7.0.7, 8.0.34) and there, I am NOT seeing this behavior. Has any of you experienced this issue in the latest Cubase versions (and are you also using “programs”)?

I’ve also inserted some tracing with the DBG macro, and this is what I’m seeing: action: changing to 2nd program in list: getCurrentProgram - current program = 0 setCurrentProgram - index = 1 ApplyProgram - programNum = 1, notifyHostOfParameterChanges = true getCurrentProgram - current program = 1 getProgramName - index = 0 getProgramName - index = 1. GetProgramName - index = 125 getProgramName - index = 126 getCurrentProgram - current program = 1 getCurrentProgram - current program = 1 action: changing back to 1st program in list: getCurrentProgram - current program = 1 (and then setCurrentProgram is NOT being called with number 0?) Question for Juce team: is there a plugin example in the repository that uses programs (that way I could test this with code you also have)? I took the AudioPluginDemo though and implemented the program-related methods (3 programs, 2 params).

Cubase 8/8.5/9/9.5 Issue For Mac Free

See attached code. This exhibits the issue:. load the plugin (shows 1st program “first” with settings of that program). switch to 2nd program (“second”) - settings are changed as expected.

switch back to 1st program - nothing changes This issue occurs with Cubase 9.5 (and probably 8.5 again as well, but didn’t test that), but it does not occur with Live, Reaper or Bidule. I also tested again in (older) Cubase 8.0.35, and there the issue also doesn’t occur. (26.7 KB) Do you have any ideas? Do you have contacts with the Steinberg devs?

I remember this bug being in Cubase since pretty much forever (at least 5 years). I’ve been trying to get to the bottom of this all morning but I think there is no real fix for this - it’s completely messed up. For example, try changing your program names to end with a consecutive numbers (“prog 1”, “prog 2”, “prog 3”).

You will see that this simple name change will actually fix the bug (program switch from the 2nd to the 1st program works), but now you won’t get any program switches from the 1st to the 2nd. So Cubase’s behaviour actually seems to depend on the program names itself?!? Seems like a big bodge of compatibility workarounds in Cubase to get some popular plug-ins to work. I’d be really interested in how some of the more established plug-in devs deal with this. Just not use programs?