CtrlrX v5.6.32J Release | VST3 Exports & Maintenance Update [2025.04.14] #716
Replies: 26 comments 185 replies
-
Beta Was this translation helpful? Give feedback.
-
|
Hi, sorry I don't have a mac silicon yet. If you can compile the binaries that would be great. Don't forget to clear your /builds/MacOSX/ folder before and start with projucer from CtrlrX 5.6.32.jucer . Compilation is in Release mode ;) Damien |
Beta Was this translation helpful? Give feedback.
-
|
OK, I will have a go tomorrow, but if @dobo365 has already started, let me know! |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, no. |
Beta Was this translation helpful? Give feedback.
-
|
Report from the front...
So, I'm blocked as I cannot export to Xcode... |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I just replied to your email with screencaps. In projucer, check your modules path, they should be pointing to the JUCE/Modules/ of your CtrlrX directory.
You then need to update the Architecture from x64 to ARM (maybe it's set to default) And also C++ standard should be C++14 (or other minimum version).
If you want "universal binaries" containing both Intel and apple silicon compatible architechures just select both In Xcode you just need to follow the guide in PDF, things did not change that much.
And "Play" button for building... |
Beta Was this translation helpful? Give feedback.
-
|
Just fantastic. Thx to all! |
Beta Was this translation helpful? Give feedback.
-
|
Hi Goodweather, It's great to finally get VST3 working and also having it not crash when there's a lua coding error during development. That was a big one for me. Regarding compilation on Windows. If you use VS 2022 there is no need to do all those configurations anymore found in the excellent guide by @bijlevel. That was for Visual Studio 2019 I believe. After setting the global paths in Projucer to JUCE and JUCE/modules and opening Visual Studio from Projucer, you just move the zipped boost file up a folder and unzip. Set the output to Release (or keep as Debug) at the top of Visual Studio and that's it. You will probably get a prompt to upgrade the SDK kit as well. So just three steps; that's on Windows 11. Edit: see here |
Beta Was this translation helpful? Give feedback.
-
|
Salut Dominique @dobo365, je t'ai répondu en email ;) Bonne journée à tous les deux! |
Beta Was this translation helpful? Give feedback.
-
|
Here is a Windows installer for Standalone, VST2 and VST3 with optional install of each candidate. CtrlrX_Installer_x64.zipCtrlrX_Installer_Win32.zip |
Beta Was this translation helpful? Give feedback.
-
Note: On a fresh install of Windows 11, whether using the installer or just the executable standalone, CtrlrX did not load. Neither were there any error messages. Just totally unresponsive. To fix this I needed to install: Now it loads fine. |
Beta Was this translation helpful? Give feedback.
-
|
Suspect this might be resolvable by the SLN setup in VS (like in proj properties > C/C++ targets) |
Beta Was this translation helpful? Give feedback.
-
|
I fixed it by adding a silent install of the latest Microsoft VC++ redistributable if it doesn't exist on machine to the new installer versions. But I can't post them here as they exceed 25MB. |
Beta Was this translation helpful? Give feedback.
-
|
NOTE : The export of VST3 requires a "search and replace" method to re-identify properly your exported instances. If you want to compile your own VST3 intermediates with your custom projucer infos like we used to do prior to this 5.6.32 version, you can just disable the re-identification process from the property "Replace with panel IDs". It won't overwrite the VST3 source identifiers. |
Beta Was this translation helpful? Give feedback.
-
|
Win32 builds for CtrlrX 5.6.32: |
Beta Was this translation helpful? Give feedback.
-
|
Hi to all. I have a MAC M2 with Sequoia 15.3.2 and I can try to built the needed instances. Which Xcode Version should I use? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, You probably need to use the latest version of Xcode available.
|
Beta Was this translation helpful? Give feedback.
-
|
Today I was able to try building the files, but had no success. Xcode gives me this error message after building the VST3. The Standalone Version works, but all panels I´ve built crashes after closing. The known issue I described a few month ago. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @synthmania67 , the mac silicon binaries are now available thanks to @bijlevel . Let me know if it's working on macOS Sequoia. CtrlrX v5.6.32 macOS Silicon (thanks to @bijlevel ) |
Beta Was this translation helpful? Give feedback.
-
|
You can build a Standalone Version with the MAC Intel files and it works without any issue with Sequoia. Only the VST3 and AU needs the arm64 architecture. |
Beta Was this translation helpful? Give feedback.
-
|
Here are the macOS Silicon files. I did compile for Sequoia with Xcode v16.3 and did only test the Standalone, which worked OK on my computer, a Mac Studio M2. I don't know if some more work needs to be done (like code signing). Let me know. |
Beta Was this translation helpful? Give feedback.
-
|
But why do I get this error message with that cycle issue? |
Beta Was this translation helpful? Give feedback.
-
|
It seems that xcode 15 is having this problem but xcode 14 does not. https://developer.apple.com/forums/thread/730974 You could try updating the target to macOS 15 and follow xcode update code suggestions, but it can open a huge rabbit hole to reprogramming CtrlrX entirely with C++ 20 etc :) |
Beta Was this translation helpful? Give feedback.
-
|
Ok, none of the versions works with my M2. At the moment you export the instance CtrlrX crashes. The instances are created, but they also crash when Cubase or Ableton is closed. You cannot simply delete the midi track because the entire DAW will also crash. It's a real pain in the neck with the new Macs. |
Beta Was this translation helpful? Give feedback.
-
|
Concerning the cycling problem when compiling, here is the trick, at least on Sonoma :
You maybe need to re-codesign your binary after that to be whitelisted from Ableton.
|
Beta Was this translation helpful? Give feedback.
-
|
Ok, if I set “Deployment Location” to "No" in Xcode 16, then the creation is successful...when using the new instances, they are recognized by Logic and Cubase without problems, but the settings for “Panel ID” are ignored. They are always Tools and not Instruments as specified. Also the name of the plugin is ignored in VST3 and it is always “CtrlrX”. The validation of the newly created plugin with CtrlrX.components, which has successfully passed the validation, also fails. |
Beta Was this translation helpful? Give feedback.
-
|
CtrlrX_Silicon.component.zip Maybe someone can check these versions. |
Beta Was this translation helpful? Give feedback.
-
|
To check what's wrong with the VST3 crashing cubase, I would need to run it in debug mode and add breakpoints to follow where the problem really happens. I'll get a M4 soon. I'll dive into that. For the AU, I have an idea, I updated all values to double type instead of float or integer and, contrary to VST3 which can handle big numbers, Logic and AU probably don't. I'll add a cast to float or int if only the plugin runs as AU. It should be OK. It's always hard to deliver a program compatible with systems we don't have at hand. I try to do my best. That's super cool if we already know what to fix for a robust solution with Apple Silicon. |
Beta Was this translation helpful? Give feedback.
-
|
OK, so I checked the AU validation and I have some logs from the previous versions and the warning was already there : It should be ok then. ENjoy! |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I'm at a loss right now. What do I have to do? :-) |
Beta Was this translation helpful? Give feedback.
-
|
Forget about the warnings from the AU validator. It should be ok. Just try your panel as AU and see if logic stores your modultor values etc as it should. Concerning the VST3 crashing the host when closing, I can't really help for now since I don't have a new Apple computer running sequoia. For the fixes I proposed so that you get your VST3 exports with the right plugin name and category I'll push an update this weekend. you're the beta tester ;) I'll do it differently though, I'll add a statement to return the type of CPU and if the cpu is not "genuineIntel" which means apple silicon, you'll get the mods I proposed above. It will then run properly on both architectures. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I'm looking forward to it :-) |
Beta Was this translation helpful? Give feedback.
-
|
FWIW I did check the AU, VST3 and VST2 for Silicon Mac in my DAW's (Digital Performer, DSP Quattro and Mixbus) and all plugins loaded fine and showed the familiar CTRLR interface. I noticed that now the plugins are called "CTRLRX Project". I'm on macOS Sequoia v15.3.2 and my Mac is a Mac Studio M2 Ultra. |
Beta Was this translation helpful? Give feedback.
-
|
is it crashing youe host as vst3 when closing ? |
Beta Was this translation helpful? Give feedback.
-
|
BTW it seems that you exported as universal binary not ar64 only. Get ready ;) |
Beta Was this translation helpful? Give feedback.
-
I don't know what you mean. I confirmed on my system all plugins work as expected, also the vst3. No crashing...
I did check in Projucer the box for arm64 architecture only, but I did not double check this in Xcode. I'll have a look. Can we expect then a new version to compile? |
Beta Was this translation helpful? Give feedback.
-
|
What else I noticed: The size of the files provided here for the MAC Silicon is 75 MB and the ones I created are only 35 MB. How can that be? |
Beta Was this translation helpful? Give feedback.
-
|
Hi Damien, sorry for my late reply. I moved on with the modification of my Roland SH-101. The VST3 crashes Cubase when closing Cubase itself and it doesn´t matter if a panel is loaded or not. All new Builds crashes also Cubase. The same thing happens with an AU and Logic. It´s always the same...it crashes after closing the app. Tomorrow I will check the modified line of "CtrlrProcessor.cpp". The day will come when everything works. I am quite sure of that. |
Beta Was this translation helpful? Give feedback.
-
|
I have already tested it. I was too curious. Maybe the problem is the panel itself which was created with older CTRLR versions. If so, this is not as good because I must recreate all my panels. This is not worth it. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
There's not a lot of things that changed concerning the panel coding, the major thing would be the function to cast the send MIDI message with memoryblock. There's a few other things but nothing that will force you to give on that. You can create another discussion about your panel and the crash situation. I'll help with others. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe you could try just creating a simple panel with only one slider and save it (for later recall). |
Beta Was this translation helpful? Give feedback.
-
|
2025.04.10 It's now available on the CtrlrX Master and on the CtrlrX 5.6.32 Branch. @bijlevel & @synthmania67 you can fetch the repository and try compiling and testing to see if you have properly exported vst3 instances ;) You're lucky I'm on my day off ;) |
Beta Was this translation helpful? Give feedback.
-
|
OK... Approaching the issue... Now experienced a bit further... |
Beta Was this translation helpful? Give feedback.
-
|
Found answer on StackOverflow! Build succeeded! With a lot of yellow issues but that's another story ;-) |
Beta Was this translation helpful? Give feedback.
-
|
This is how I formulated my question for Chatgpt: what could be the cause Juce not being able to read a certain .mm file while compiling with Xcode? To use Chatgpt go to https://chatgpt.com/ and get an account. You can make free use for a limited amount of questions, but in practice it's in most cases enough. (Sorry I made you feel old, but keep on working with CtrlrX, Juce and Xcode! It will keep you forever young 😋) |
Beta Was this translation helpful? Give feedback.
-
|
FYI: I've been beating up chatGPT while developing AI prompts for comfyui pipelines without need for an account. Just click |
Beta Was this translation helpful? Give feedback.
-
|
Wow this file access permission is strange, usually you get a warning the first time you open the app, you allow for it and it's ok. |
Beta Was this translation helpful? Give feedback.
-
|
I found some issues:
You can try yourself. The archive contains the panel and the VST3. |
Beta Was this translation helpful? Give feedback.
-
|
Can you try : It will give more room to each element |
Beta Was this translation helpful? Give feedback.
-
Ok! Actually, I just tried this and it's working! void CtrlrPanelResourceEditor::paintRowBackground (Graphics& g, int rowNumber, int width, int height, bool rowIsSelected)
{
if (rowIsSelected)
{
gui::drawSelectionRectangle (g, width-28, height-28);
}
}
|
Beta Was this translation helpful? Give feedback.
-
|
Except when you click on a resource it the text disappears under the mouse. But definitely suggests some kind of overlap. Should probably be |
Beta Was this translation helpful? Give feedback.
-
|
You did it! Well done!
|
Beta Was this translation helpful? Give feedback.
-
|
You've been fast on this one! |
Beta Was this translation helpful? Give feedback.
-
|
One thing I forgot. There is an error message after building the AU.
|
Beta Was this translation helpful? Give feedback.
-
|
https://developer.apple.com/forums/thread/731138 It's a warning though, it probably still handles that issue to make it work, or you would get a red error and compilation failure. |
Beta Was this translation helpful? Give feedback.
-
|
Good Morning. When I work in my panel, the midi automation also works. The controllers move as the curve for this parameter was drawn. The midi monitor of the plugin also shows nothing. In both cases. There is definitely something wrong with the processing of the midi data within the application. I have provided the two panels. Could someone please test this? This is not a problem of Cubase :-) |
Beta Was this translation helpful? Give feedback.
-
|
I have another question: Is the VST index limited to 63?
|
Beta Was this translation helpful? Give feedback.
-
In windows on 5.3.201 a panel loaded into the VST2 instigator has that 64 index limit, but with the standalone VST2 it is pretty much unlimited. I’m guessing it’s no different with VST3. |
Beta Was this translation helpful? Give feedback.
-
|
I set to 64 as default and hide the parameter because it uses JUCE jmax which returns the biggest number. if you have 200000000000 parameter you'll get them in cubase. you can update this following function to your taste if you just want it to adjust to the number of parameters. |
Beta Was this translation helpful? Give feedback.
-
|
I see, thank you. |
Beta Was this translation helpful? Give feedback.
-
|
I’ve noticed a few other things that are directly related to the MIDI controllers. By the way, all of these knobs are copies of the first knob “Cutoff”, with just the modulator name and the CC number adjusted for each. Bildschirmaufnahme.2025-04-12.um.09.23.23.mov |
Beta Was this translation helpful? Give feedback.
-
|
II think I found the error. Automation works up to VST index 9, so the first 10 values are interpreted correctly. Anything after that no longer works. As soon as a knob is assigned VST index 10, it gets the wrong label and doesn't respond to MIDI data. |
Beta Was this translation helpful? Give feedback.
-
|
WOw this is insane. I just spent an hour testing this and it makes no sense. I tried with Cubase as well, here is my results : Ctrlr 5.3.198 VST2 : All mods reacts to automation and send MIDI CC There's definitely something wrong with the VST3 interface Host<>CtrlrX I'll take a look at it, because with VST2 it's working great... I never had more than 8 mods to control from the host to CtrlrX that's why I never noticed the problem. Thanks for reporting. I suggest you use a VST2 instance for the moment and I'll try to fix this crazy VST3 bug. I thought I was done with that because I'm fed up with this project. I spent way to much time on it. I never thought there was a bug like this on the line. |
Beta Was this translation helpful? Give feedback.
-
|
I think I have a clue about what is happening. With CtrlrX 5.6.32 VST3 : With an exported VST3 instance from the CtrlrX 5.6.32 VST3 : With CtrlrX 5.6.32 VST2 : Same with an exported VST3 instance from the CtrlrX 5.6.32 VST2:
That's weird, the problem is coming from that particular value range discrepancy. |
Beta Was this translation helpful? Give feedback.
-
|
I opened an issue on CtrlrX not to flood this discussion : damiensellier#83 |
Beta Was this translation helpful? Give feedback.
-
|
It's really strange how many issues the VST3 format causes. The main problem is that most DAWs no longer support VST2 versions. Apple in particular is very strict when it comes to VST3 plugins. I believe this issue also occurs with AU versions compiled from 5.6.32, which is why they fail the validation process. They can be re-enabled manually, but then they appear in the plugin list as "incompatible," and Logic or MainStage also displays a warning about it on startup. The validation process in Logic’s Plugin Manager shows a warning about the parameter values after the scan, although everything is marked as "passed" during validation. Still, I’m confident that this issue will be resolved as well. We’ll get through this together. Thanks to everyone who is actively helping out! |
Beta Was this translation helpful? Give feedback.
-
2025.04.14NOTE : I Fixed the modulators not sending MIDI messages from Host automations with VST3 and AU. Thanks @synthmania67 for reporting the bug and testing this FIX. It's now available on the CtrlrX Master and on the CtrlrX 5.6.32 Branch. |
Beta Was this translation helpful? Give feedback.
-
|
@bijlevel or @synthmania67, could you please upload the new binaries for Apple Silicon below ARM64 only from the updated branch (VST2, VST3, AU, APP)? Thank you so much Damien |
Beta Was this translation helpful? Give feedback.
-
|
CtrlrX v5.6.32J Windows Intel x64 ( thanks to @dnaldoog ) (UPDATED 2025.04.14 : REV.J) CtrlrX-5.6.32J-x64.WIN.x64.INTEL.STANDALONE CtrlrX v5.6.32J Windows Intel 32Bits ( thanks to @dnaldoog ) (UPDATED 2025.04.14 : REV.J) CtrlrX-5.6.32J-Win_32.INTEL.STANDALONE.zip CtrlrX v5.6.32J macOS Intel (UPDATED 2025.04.14 : REV.J) |
Beta Was this translation helpful? Give feedback.
-
|
CtrlrX 6.6.32 for Intel and Silicon Mac (Universal): |
Beta Was this translation helpful? Give feedback.
-
|
What is good for to have installers? |
Beta Was this translation helpful? Give feedback.
-
|
@bijlevel I'm not doing installers because I would need a mac silicon to produce univerdal binary Installers. There's no point to distribute intel installers requiring rosetta to set up arm plugins :) |
Beta Was this translation helpful? Give feedback.
-
|
That's exactly how I see it, too. Installers, at least on Apple systems, absolutely require a developer certificate — and that costs money... a lot of money maybe. |
Beta Was this translation helpful? Give feedback.
-
|
it's 100$ a year for a single Apple dev ID. You also need a PFX certificate for windows apps, they are different, it's another 100$. |
Beta Was this translation helpful? Give feedback.
-
|
Just too much hassle and cost for personal use. |
Beta Was this translation helpful? Give feedback.
-
|
Here is code for fixing the unresponsive Add,Remove,Move...,Reload Buttons in the resources editor.
Thanks to @damiensellier for the code which will no doubt be included in version 5.6.33. In the meantime you can compile using this attached file (
//void CtrlrPanelResourceEditor::resized()
//{
// resourceList->setBounds (0, 0, getWidth() - 0, getHeight() - 32);
// add->setBounds (0, getHeight() - 28, 64, 24);
// remove->setBounds (72, getHeight() - 28, 64, 24);
// move->setBounds(144, getHeight() - 28, 64, 24);
// reload->setBounds (getWidth() - 64, getHeight() - 28, 64, 24);
//}
void CtrlrPanelResourceEditor::resized() // updated Damien 4/24/2025 fixe unresponsive Buttons
{
resourceList->setBounds(0, 0, getWidth() - 0, getHeight() - 64);
add->setBounds(0, getHeight() - 48, 72, 32);
remove->setBounds(72, getHeight() - 48, 72, 32);
move->setBounds(144, getHeight() - 48, 72, 32);
reload->setBounds(getWidth() - 64, getHeight() - 48, 64, 32);
}
|
Beta Was this translation helpful? Give feedback.
-
|
Honestly, I can understand the displeasure of some users here. Especially on the Apple Mac, Ctrlr only causes problems. The program is as bad and unstable as it can be. I'm now so annoyed by it that I've decided to stop using it. Sorry, Damien, you have improved a lot, but unfortunately the program needs to be completely rewritten. The old JUCE versions have too much problems with the actual OS. There are also new problems with the current version, e.g. with “uiImageSlider”, these can often only be moved with a delay when the file is exported. And if you don't click exactly on a certain part of the slider, it doesn't move at all. And the worst thing about it is that it happens randomly. The validation process of Logic fails in some cases and I can´t find out the reason. In any case, I've had enough and will no longer develop even one panel with Ctrlr. It's exhausting and it gets on my nerves.... |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I understand your frustrations but I disagree about CtrlrX being "as bad and unstable as it can be". I exported a panel I did with 5.3.198 yesterday with the latest version and just had to update the Lua method to send midi messages. It has more than 100 uiImageSliders fixed and lineae, and I did not experienced what you said about required delay etc. If you could expand more about this particular problem on the issue page of ctrlrx I'll help. Don't give up on your projects mate, I know it can be frustrating but I honestly don't see any equivalent software that could create MIDI panels such as ctrlr right now. It's worth doing the little improvements here and there. And after all it's just midi control softwares, in my case it's almost always a set and forget tool. I use it to control presets of my external hardware fx and recall patches automatically from the cubase sessions. Take a break, but don't give up. Good luck with your midi panels and again thanks for your help with debugging those last few weeks. |
Beta Was this translation helpful? Give feedback.
-
|
Hello Damien, please don't get me wrong. It's not a criticism of you. I appreciate all your work with the project and I am very happy that someone with your knowledge has taken on the further development. At least the biggest VST3 problem has finally been solved. The frustrating thing about developing panels is also LUA. Some things have changed there too and you have to be very careful what you do. Cheers, |
Beta Was this translation helpful? Give feedback.
-
|
I'd like to echo synthmania & express my uber-appreciation for all you do for this project @damiensellier . If the job markets ever get better in the US to where its not so 'contract driven' to where I'm constantly scrambling to pick up new langs/tech to get my loot, I'm all over C/C++ so I can jump in to render aid sir. This project means a lot to many people & I'd like to return something more tangible to the community that's seriously changed the dynamics with my music with this gear I have. You are a one-of-a-kiind. Hugz n Kisses n TonsOLove to you Brother! |
Beta Was this translation helpful? Give feedback.
-
|
Hello, thanks for your support, don't worry I don't take it personally at all. I know ctrlr has a lot of flaws and especially with the new Mac CPUs. I don't even have one yet but it's in my plans. If ever I come across any issue, I'll go the Rosetta way. |
Beta Was this translation helpful? Give feedback.
-
|
To be honest, I'm still only using 5.3.201 on Windows for my panel development and I'm very satisfied with it. |
Beta Was this translation helpful? Give feedback.
-
2025.04.29NOTE : I just fixed a problem I added in 5.6.32 rev J, the mac standalone intel was not exporting panels properly. It's now available on the CtrlrX Master and on the CtrlrX 5.6.32 Branch. |
Beta Was this translation helpful? Give feedback.
-
NOTE : From now on (2025.04.29)All the updates will be pushed to the CtrlrX 5.6.33 branch before I merge it to the Master on release date ;) Thanks Damien |
Beta Was this translation helpful? Give feedback.
-
|
@bijlevel sounds awesome! It's not the final release of 5.6.33, I'd like to fix a bug @dobo365 reported about sliders not all reacting if they are assigned to the same cc number. |
Beta Was this translation helpful? Give feedback.
-
|
Here are the binaries for v5.6.33B CtrlrX v5.6.33B-macOS Silicon.AU.component.zip |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much! |
Beta Was this translation helpful? Give feedback.
-
|
M2 Max / Ableton 12 I have tried these, but with no success:
Interpreting the
|
Beta Was this translation helpful? Give feedback.
-
|
In case this will help, i have ran the same commands on Ctrlr_Matrix1000_1_260.vst3 (which is an older CtrlrX build i'm using for the Oberhem Matrix1000 - got this from the creator of the panel directly built)
|
Beta Was this translation helpful? Give feedback.
-
|
Hi, I can't get Ableton to load the VSTs. I have tried these: CtrlrX v5.6.32J-macOS Silicon.APP CtrlrX v5.6.32J-macOS Silicon.VST2 Am i doing something wrong? |
Beta Was this translation helpful? Give feedback.
-
|
I know but we're talking about synthmania universal binaries and I redirected you to bijlevel's which are arm only. The problem with your case is that I don't have a Mac m silicon neither your macOS neither live 12. So I can't help any more even if I 'd be glad to. It's an open source project and I can't spend to much time to debug support all users. I try to do my best for the community but I can't do the impossible, it would take me 1K for a new Mac, 500 for live pro , and I just can't. From your log, the problem is coming from either the code signing signature or the fact the info.olist is different from the 1st time you opened CtrlrX. Export is a glorified name for duplicate+panel resource add-ons, + binary hacking. So if ever another user happen to have a solution I would be really happy that it could sort things out for your kind of setup. Worst case scenario you can fallback to Intel version and Rosetta. Damien |
Beta Was this translation helpful? Give feedback.
-
|
Would you mind uploading the exported instance of your plugin? You should have something like this : nothing else. The "unsealed contents" error typically refers to files directly in the root of the bundle, not within its standard subdirectories. Let me know if you found any unexpected files in the root of the plugin bundle when you examine its contents. Is it the same thing for all exports or just this particular one? You can also run |
Beta Was this translation helpful? Give feedback.
-
|
I̶t̶'̶s̶ ̶a̶l̶s̶o̶ ̶v̶e̶r̶y̶ ̶s̶t̶r̶a̶n̶g̶e̶ ̶y̶o̶u̶ ̶d̶o̶n̶'̶t̶ ̶h̶a̶v̶e̶ ̶I̶n̶f̶o̶.̶p̶l̶i̶s̶t̶ ̶i̶n̶ ̶y̶o̶u̶r̶ ̶b̶u̶n̶d̶l̶e̶.̶ ̶ EDIT : NOT BOUND (not NOT FOUND) Here is bijlevel's ARM only CtrlrX v5.6.33b vst3 content : 
It has the info.plist and the info.plist shows it's been compiled on macosx15.4 for arm: Please open an issue on CtrlrX issue section, we'll get deeper into that issue there : https://github.com/damiensellier/CtrlrX/issues |
Beta Was this translation helpful? Give feedback.
-
|
Can you please try the install with codesigned binaries @spiffo-smith just uploaded? Let us know |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
For anyone on Apple Silicon, I've compiled App, AU and VST3 versions using the 5.6.33 Code and put them into a Package Installer. I had to Sign and Notarise using my own Apple Developer Account, if that's overstepping the mark just let me know and I'll stop and get rid of it. But it's the only way I could ensure no one has to mess around in Terminal. There are scripts that will wipe out any previous CtrlrX Versions so you may want to save them somewhere else first. I've tested in Logic, Ableton and Reaper and all appears good! |
Beta Was this translation helpful? Give feedback.
-
|
That's really cool, there's so many users struggling with this quarantine and codesigning issue that will really help. Is it ARM64 only or universal binaries? Is it from latest 5.6.33 commit I pushed yesterday with the missing sliders type add-ons? I'll stop the dev of 5.6.33 and will publish the release early next week with your package if you're ok with that. Next updates will then be for 5.6.34 Thanks for everything |
Beta Was this translation helpful? Give feedback.
-
|
Cubase blocks the VST3 because it´s not an ARM64 architecture. |
Beta Was this translation helpful? Give feedback.
-
|
All versions are INTEL... |
Beta Was this translation helpful? Give feedback.
-
|
Yep, ok, my bad, I am using Producer v8.0.4 and Xcode v16.3 because I don't want to run old versions of stuff, consequently the Build Settings in Xcode are all over the place and lot's of things have to be manually changed, I missed the Build Settings - User Defined - VALID_ARCHS change to arm64 only! Anyway, try this one: |
Beta Was this translation helpful? Give feedback.
-
I've installed this (the first revision that you posted), and everything worked fine! Phew ... (M2 MAx / Ableton 12) |
Beta Was this translation helpful? Give feedback.
-
|
2025.05.28 UPDATE: CtrlrX 5.6.33 has been released, please visit #725 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Dear Ctrlr Users,
A new version for the CtrlrX Fork has been released: CtrlrX v5.6.32
It's now available on the CtrlrX Master and on the CtrlrX 5.6.32 Branch.
VST3 exports :
This new version is a huge update with THE feature everybody was waiting for : exporting VST3 instances. It works for both macOS and Windows.
You can select the plugin category from the "pluginType" property, it works both as Instrument or FX.
Panel to control synths will sit well in the instrument| category and will be seen by your DAW as a VSTi. If your panel controls Multi-FX you can select the FX| category. You'll be able to insert your panel on the path of your external hardware as if you were using a regular plugin processor, handy!
On macOS, you will also be able to select a developer signature from your keychain to codesign your export.
Codesigning is also available on Windows with a PFX file in order to prevent those pesky warnings from the Windows Defender SmartScreen.
If you don't have a developer certificate either on macOS or Windows, the plugin will be signed Ad-Hoc anyway.
Thanks to John @dnaldoog and @synthmania67 for their help with the debugging.
uiSlider with decimals :
uiSliders and their variants (image & fixed) can finally use decimals for values, Min Values Max values and also you can set the interval to decimals as well. - 2.5468|5.16457 with 0.00001 is now possible. You can also add a suffix to your value such as dB, ms, % etc. It's also possible to set the decimal place for your current value. You will need to use the expression fields to send/receive MIDI messages as integer accordingly.
Windows crashing when loading a panel with faulty LUA :
Prior versions of CtrlrX and Ctrlr 5.6 crashed on Windows when loading a panel containing a modulator associated to a faulty LUA script (when modulator value changes). This problem is now fixed thanks to @dnaldoog who updated the luabind call function.
A new preference "Run modulator valueChange LUA callback in Bootstrap state" was added to select if you want to display the LUA error warning window when loading a panel (as in 5.3), or if you want to mute it (as in 5.6+).
Thanks to John @dnaldoog and @unityconstruct.
VST3 Host>CtrlrX interface : ( 2025.04.14 Rev.J FIX )
Previously, the conversion from VST2 to VST3 SDK was missing some calls to the modulators (parameters to Host). Automations were not working on exported instances and had only the 10 first modulators sending MIDI messages on CtrlrX.vst3.
From now on sliders react 100% to Host automations of parameter values. Related Modulators send MIDI output messages.
Thanks @synthmania67 for helping with the debugging.
Here is the list of all fixed issues for CtrlrX v5.6.32 :
Compiling :
For the people looking to compile CtrlrX v5.6.32, it's required to clear all your IDE (Visual Studio & Xcode) temp files from the folder CtrlrX/Build and restart from scratch with CtrlrX.jucer with projucer because many settings have been updated in the project file.
To compile, please follow the guides available to download there :
https://github.com/damiensellier/CtrlrX/wiki/Guides-to-Building-Ctrlr
Enjoy!
Full Changelog: damiensellier/CtrlrX@5.6.31b...5.6.32J
CtrlrX v5.6.32J Windows Intel x64 ( thanks to @dnaldoog ) (UPDATED 2025.04.14 : REV.J)
CtrlrX_Installer_x64.zip
CtrlrX-5.6.32J-x64.WIN.x64.INTEL.STANDALONE
CtrlrX-5.6.32J-x64.WIN.x64.INTEL.VST2
CtrlrX-5.6.32J-x64.WIN.x64.INTEL.VST3
CtrlrX v5.6.32J Windows Intel 32Bits ( thanks to @dnaldoog ) (UPDATED 2025.04.14 : REV.J)
CtrlrX_Installer_Win32.zip
CtrlrX-5.6.32J-Win_32.INTEL.STANDALONE.zip
CtrlrX-5.6.32J-Win_32.INTEL.VST2.zip
CtrlrX-5.6.32J-Win_32.INTEL.VST3.zip
CtrlrX v5.6.32J macOS Intel (UPDATED 2025.04.14 : REV.J)
CtrlrX.5.6.32H-macOS.Intel.APP
CtrlrX.5.6.32J-macOS.Intel.VST2
CtrlrX.5.6.32J-macOS.Intel.VST3
CtrlrX.5.6.32J-macOS.Intel.AU.component
CtrlrX v5.6.33B macOS Silicon (UPDATED 2025.05.02 : REV.B) (thanks to @bijlevel )
CtrlrX v5.6.33B-macOS Silicon.AU.component.zip
CtrlrX v5.6.33B-macOS Silicon.VST2.zip
CtrlrX v5.6.33B-macOS Silicon.VST3.zip
CtrlrX v5.6.33B-macOS Silicon.APP.zip
CtrlrX v5.6.33 macOS Intel Signed Installer (APP, VST3, AU) (UPDATED 2025.05.24) ( thanks to @spiffo-smith )
https://www.icloud.com/iclouddrive/0e4xJ5lbMiJg6ANYx_2yrTzqQ#CtrlrX_Distribution_Installer_v5.6.33.pkg
CtrlrX v5.6.33 macOS Silicon Signed Installer (APP, VST3, AU) (UPDATED 2025.05.24) ( thanks to @spiffo-smith )
https://github.com/user-attachments/files/20422024/CtrlrX.Distribution.Installer.v5.6.33.-.Apple.Silicon.pkg.zip
PS 1: It's required to delete ctrlr.settings to refresh your global preferences since I removed and updated CtlrlrX default global settings.
PS 2: In CtrlrX 5.6.32.jucer Projucer project, don't modify the Plugin Name, Version, Plugin Manufacturer, Plugin Code and Manufacturer code. The export of VST3 requires a "search and replace" method to re-identify properly your exported instances.
If you modify those Projucer fields, the VST3 will fail to be re-identified from your panel informations.
PS 3: If you want to compile your own VST3 intermediates with your custom projucer infos like we used to do prior to this 5.6.32 version, you can just disable the re-identification process from the property "Replace with panel IDs". It won't overwrite the VST3 source identifiers.
Beta Was this translation helpful? Give feedback.
All reactions