search

RomanKubiak / ctrlr

Ctrlr
BSD 3-Clause "New" or "Revised" License
497 stars 58 forks source link

VST3 export not recognized by Cubase (CtrlrX 5.6.30) #653

Open dervur opened 2 weeks ago

dervur commented 2 weeks ago

Hello there,

I am trying to export a vst3 in version CtrlrX 5.6.30 within Cubase Elements 12 on Windows 11 version 22H2. When I export the .exe it is fine and it works fine (didn't try to connect it MIDI but at least it opens). Meanwhile, when I export as restricted instance while using CtrlrX vst3 I can see that a file is exported (in the correct folder). Nevertheless, when I scan for VST plugins or close and reopen Cubase the VST is not scanned at all. It is like it is not exported correctly or not identified as a vst3 maybe, I don't know.

I have just been learning CtrlrX for about 2 days, and I'm only now understanding the export options. Do I need to click something to make it work and export correctly to VST3? Or do I have to modify that exported VST3 file somehow to make it work?

If you need any extra information let me know. Cheers!

EDIT: I also tried the VST2 version and it works. So it seems to be a VST3 issue only.

dervur commented 1 week ago

Ok I think I found out the problem... It seems that the exported version is read by Cubase and other DAWs as an iteration of CtrlrX, so if there is an instance of CtrlrX that has been read before the one that I exported is ignored... Does anybody have any idea of why this happens?

damiensellier commented 1 week ago

Currently VST3 instances of CTRLR panels are not working properly because CTRLR is not able to generate different VST3 compliant plugin identifiers. Unfortunately, exported VST3 instances of your panel will always be named after CTRLR | Instigator. The only way to get the correct identifiers for a panel project is to force them at the core during the building step of the VST3 in Xcode/VS/IDE. To export properly identified VST3 plugins it is then required to build a different stock CTRLR VST3 plugin with JUCE Projucer and Xcode/VS/IDE. However, this alternative version of CTRLR VST3 will have the desired panel/plugin identifiers predefined in the Projucer settings. (Plugin Name, Manufacturer Name, Plugin ID, Manufacturer ID etc). This intermediate VST3 plugin will then be able to export a final VST3 version of the panel with the proper identifiers.

Please check : https://github.com/RomanKubiak/ctrlr/discussions/394

FIX: export as VST2 or create your own custom VST3 CtrlrX instance with the appropriate identification properties

dervur commented 1 week ago

Hi Damien, thank you very much! Yeah I read about that earlier today... I was having issues compiling though (around 2000 errors), I will take a look at that another day, I'm just tired after the all day trying lol I also noticed another issue, with VST2, basically I am able to generate only one plugin instance, if I export another one with different name, device, id and so on it seems to be read still as the same plugin (basically I can only do 1 VST and that's it), is this a known issue? Is this solvable in the same way compiling my own VST2 instance in Visual Studio?

damiensellier commented 1 week ago

Yes exactly, VST3 will always have the same same name for different exported panels. This is a JUCE library issue. I'm trying to find a way to circumvent that issue for months. If you use a VST2 instance to export your panels that should be OK, exported VST2 should get the right name and be recognised in Cubase as a different plugin. I never tried but from the way the code works it should be ok.

All CtrlrX versions are here :

CtrlrX v5.6.30.1 macOS Intel CtrlrX-5.6.30.1-APP-macOS-Intel.zip CtrlrX-5.6.30.1-VST3-macOS-Intel.zip CtrlrX-5.6.30.1-AU-macOS-Intel.zip

CtrlrX v5.6.30.2 macOS Silicon CtrlrX v5.6.30.2-APP-MacOS-Silicon.zip CtrlrX v5.6.30.2-AU-MacOS-Silicon.zip CtrlrX v5.6.30.2-VST3-MacOS-Silicon.zip

CtrlrX v5.6.30.1 Windows Intel CtrlrX 5.6.30.1- EXE-Windows-x64.zip CtrlrX-5.6.30.1-VST3-Windows-x64.zip CtrlrX-5.6.30.1-VST-Windows-x64.zip

EDIT: The above builds are not working properly and need to be updated because source files were not the right one.

CtrlrX 5.6.29 Windows 10 CtrlrX-x64-5.6.29.zip CtrlrX-x64.vst3-5.6.29.zip

dervur commented 1 week ago

Hi Damien,

I noticed it didn't today, I began working on a new instrument and Cubase was not reading it until I took away the one from the other instrument I was working on... Maybe I can fix this by building VST2 as well.

I have those files, as per issue #658 they do not work anymore for some reason, I worked the all day on making it work again, but since I want to be able to build it I will try to fix the building, I think the issue might be that I'm using VS2022 instead of VS2019 and/or maybe something is not installed correctly.

damiensellier commented 1 week ago

29 JUNE 2024 EDIT: The above CtrlrX v5.6.30.1 builds are not working properly and need to be updated because source files were not the right one.

CtrlrX 5.6.29 Windows 10 CtrlrX-x64-5.6.29.zip CtrlrX-x64.vst3-5.6.29.zip

dervur commented 1 week ago

Hi Damien, I don't know why these .exe you submitted do not open anymore... I don't know what happened to be honest, I'll keep trying to build it, maybe I will have more success then...