CtrlrX v5.6.31 Release - GUI & Maintenance Update [2025.02.01]

[damiensellier]

Dear Ctrlr Users,

I just released a new version for the CtrlrX Fork : v5.6.31b
It's already available on the CtrlrX Master and on the CtrlrX 5.6.31 Branch.

Panel data encryption :
I added a security update for macOS that allows encryption of the exported panel code & resources for the developers providing exported instances. Previously, you could just copy the resources from the mac bundle and paste it to a blank CTRLR app and it would work, now the embedded panel and resources are encrypted with your passkey located in Source/Native/CtrlrMac.cpp ... :

Encryption stage :
https://github.com/damiensellier/CtrlrX/blob/e8f5cffc10d2bd8fa3c682370ad975b421111589/Source/Native/CtrlrMac.cpp#L89

// Define the BlowFish encryption key as string
String keyString = "yourkey"; // Replace with your actual key (security!) Added v5.6.31

Decryption stage :
https://github.com/damiensellier/CtrlrX/blob/e8f5cffc10d2bd8fa3c682370ad975b421111589/Source/Native/CtrlrMac.cpp#L141

// Define the BlowFish encryption key as string
String keyString = "yourkey"; // Replace with your actual key (security!). Added v5.6.31

If you don't care and use it as it was in the previous version, just leave it as it is when compiling. If you use registration keys or pace ilok, please customize your passkey to encrypt your panels and resources to keep everything safe.

Audio layout update :
I also updated the CtrlrProcessor.cpp with the up-to-date in/out layout class BusesProperties(). It was using deprecated JUCE v4 definitions in previous versions and caused problems with Logic and Live.

Sysex Roland checksum macro :
Sysex Roland checksum macro have been updated thanks to John @dnaldoog

LUA Method Editor update :
LUA Method Editor has been updated as well with a few more design options to make code more legible thanks to Dominique @dobo365

I fixed almost all bug reported from the Ctrlr issues section like sliders not providing the correct max values when set with negative values, which was a big bummer. thanks to @mtarenskeen for the report.

Ableton Live update :
I also fixed the most requested issue : CtrlrX not showing up in Ableton Live. (tested on macOS Ableton Live Lite 11).

To get exported instances working in Live, you either need to un-codesign your instance OR re-codesign it. BUT since the exported binary won't get the same size as CtrlrX vst/vst3 it's going to be blacklisted by Ableton Live on scan. AudioUnit version will work in Live for macOS though.

AudioUnit validation update :
Another request was : CtrlrX not validating the AudioUnit test in Apple Logic Pro. It should now work from what I got on my setup. (tested with Ableton Live, Apple AU Validation tool command, Presonus Studio One).

AU Validation Tool
    Version: 1.6.1a1 
    Copyright 2003-2013, Apple Inc. All Rights Reserved.
    Specify -h (-help) for command options

--------------------------------------------------
VALIDATING AUDIO UNIT: 'aumu' - 'cTrl' - 'cTrX'
--------------------------------------------------
Manufacturer String: CtrlrX
AudioUnit Name: CtrlrX
Component Version: 5.6.31 (0x5061F)


--------------------------------------------------
AU VALIDATION SUCCEEDED.
--------------------------------------------------

Exported instance crashing DAWs if panelIsDirty = 0 update :
For me the biggest annoyance was VST crashing Cubase when loading projects with a panel having the property panelIsDirty = 0.
I fixed it yesterday so it should be good to go with a panel with either panelIsDirty=0, panelIsDirty=1 or without this property (legacy panels).

Default LookAndFeel update :
I also improved the default Look and feel management. The previous version was a bit messy.
Depending on your tastes, you just need to select the default LnF version and colourScheme in the general preferences menu :

You need to restart Ctrlr as requested on the popup.
Upon restart CtrlrX will always have the selected default LnF version & colourScheme.
When you create a new panel, it's going to have the LnF version and colourScheme you set up from the general preferences by default. Easy!

NOTE : The colourScheme from the general preferences of CtrlrX is only your default starting point for new panels.
But you can have a default colourScheme set to Light for exemple, and you can still design a panel in "Jet Black" if you want, and also assign another LnF/colourScheme to each modulator.
Exported panels will always get the panel's colourScheme, not the one from your preferences.

Thanks for your suggestions to everyone involved BTW.

Here is all the list of fixed issues for CtrlrX v5.6.31b :

Version 5.6.31b | 2025.01.29

Security update : Encryption of the panel file in the macOS bundle for restricted instances. CtrlrMac.cpp, CtrlrEditorApplicationCommandsMenu.cpp, CtrlrManager.cpp

NEW JUCE Class MouseInputSource added to LUA. LCore.cpp,LCore.h, LJuce.cpp, LJuce.h, LMouseInputSource.h
NEW algorithm for Roland checksums. CtrlrSysexProcessor.cpp & CtrlrUtilities.cpp
NEW settings for LUA Method Editor. CtrlrValueTreeEditor.h CtrlrLuaMethodCodeEditorSettings.cpp & .h CtrlrLuaMethodCodeEditor.cpp CtrlrLuaMethodEditor.cpp CtrlrIDs.h & CtrlrIDs.xml

FIXED MSB 14 bit numbers sending 0xFF instead of 0x7F. CtrlrSysexProcessor.cpp & CtrlrUtilities.cpp
FIXED missing File Management bottom notification bar. CtrlrPanelFileOperations.cpp, CtrlrPanelEditor.cpp, CtrlrPanelEditor.h, CtrlrPanel.cpp, CtrlrPanel.h
FIXED missing menuBar on export for log and MIDI monitor windows. CtrlrChildWindowContainer.cpp
FIXED uiSlider value not reaching maxValue when using negative values for minValue. CtrlrSlider.cpp
FIXED uiImageSlider value not reaching maxValue when using negative values for minValue. CtrlrImageSlider.cpp
FIXED black text on black background for Modulator List window. CtrlrPanelModulatorList.cpp
FIXED typo in alert when closing dirty panel. CtrlrPanelFileOperations.cpp
FIXED parameters count passed to VST host is set from the highest vstindex when a panel is an exported VST/VST3 instance, not (64). CtrlrProcessor.cpp
FIXED LnF panel close button colour on mouseover follows the panel colourScheme. CtrlrDocumentPanel.cpp
FIXED CtrlrModulator Value statement precised to help avoid feedback loops between LUA and (delayed) UI. Commit 6e5a0b2 by midibox. CtrlrLuaManager.cpp
FIXED exported VST crashing DAW if panelIsDirty = 0 on export. CtrlPanelFileOperations.cpp
FIXED Ctrlr not showing up in Ableton Live. CtrlrX.jucer, CtrlrProcessor.cpp & CtrlrProcessor.h, CtrlrProcessorEditorForLive.cpp & CtrlrProcessorEditorForLive.h
FIXED MIDI Monitor IN/OUT turned ON by default. CtrlrManager.cpp
FIXED Console window & Midi Monitor crashing Cubase if closed from the Menu File>Close. CtrlrLuaConsole.cpp & CtrlrMIDIMonitor.cpp
FIXED LUA mod:getMidiMessage():getProperty("propertyName") CtrlrMidiMessage.cpp & CtrlrMidiMessage.h
FIXED exported instances not getting the proper LnF version or colourScheme (popup, child windows etc). CtrlrManagerInstance.cpp, CtrlrEditor.cpp
FIXED property pane tabs not showing up on exported instances. CtrlrManagerInstance.cpp
FIXED Property Pane tabs not following panel LnF. CtrlrPanelProperties.cpp & CtrlrPanelProperties.h
FIXED Child Windows (LUA Editor, console etc) not getting the proper menuBar background. CtrlrChildWindowContainer.cpp
FIXED LUA Editor Method Tree selected item not getting the proper colour. CtrlrLuaMethodEditor.cpp
FIXED AU AudioUnit version of CtrlX was failing the Apple/Logic Validation Test. CtrlrX.jucer, CtrlrProcessor.cpp & CtrlrProcessor.h
FIXED Panel Tabs showing up on exported instances. CtrlrDocumentPanel.cpp
FIXED messy preferences window and settings. CtrlrSettings.cpp & CtrlrSettings.cpp ctrlrIDs.h & CtrlrIDs.xml
FIXED default New Panel LnF not following global LnF from Global Preferences. ctrlrPanel.cpp ctrlrIDs.h & CtrlrIDs.xml
FIXED FileChooser hanging when exporting instance on OSX Catalina & macOS BigSur. CtrlrManager.cpp
FIXED About popup design refurbished with new CtrlrX logo. CtrlrAbout.cpp & CtrlrAbout.h
FIXED About popup not getting current build date, fixed with C++ Macro timestamp. CtrlrRevision.h
FIXED CtrlrX icons for macOS and WIN. ctrlrx_logo.svg, CtrlrX.jucer
FIXED VST crashing DAW when loading a project with panelIsDirty = 0. CtrlPanelFileOperations.cpp

Compiling :
For the people looking to compile CtrlrX v5.6.31b, 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

Version :
I decided to keep CtrlrX v5.6.31 as beta ,hence v5.6.31b, to receive all your suggestion for nightly fixes, and also because the next step would be to provide codesigned binaries to prevent CtrlrX from being denied by the windows gatekeeper and the macOS app blacklist. We're almost there ;)

If everything is confirmed and mostly fine, I'll update a few things here and there and release CtrlrX v6.0 a major release in Q2 2025 with codesigned binaries. v6.0 will finally follow the JUCE number version (v6.0.8) for more coherence.

I also designed the CtrlrX logo from the Ctrlr one with an extra X obviously, CtrlrX is alive. how cool is that :)

Enjoy!

Damien

CtrlrX v5.6.31b Windows Intel
CtrlrX-5.6.31b-EXE-WIN-x64
CtrlrX-5.6.31b-VST3-WIN-x64
CtrlrX-5.6.31b-VST-WIN-x64

CtrlrX v5.6.31b macOS Intel
CtrlrX-5.6.31b-APP-macOS-INTEL
CtrlrX-5.6.31b-AudioUnit-macOS-INTEL
CtrlrX-5.6.31b-VST3-macOS-INTEL
CtrlrX-5.6.31b-VST-macOS-INTEL
CtrlrX-5.6.31b-VST-macOS-INTEL NoCodesignForLive.zip

CtrlrX v5.6.31b macOS Silicon (compiled thanks to @bijlevel)
CtrlrX-5.6.31b-APP-macOS-Silicon
CtrlrX-5.6.31b-AudioUnit-macOS-Silicon
CtrlrX-5.6.31b-VST3-macOS-Silicon
CtrlrX-5.6.31b-VST-macOS-Silicon

CtrlrX v5.6.31b LINUX Fedora 41 Intel
CtrlrX-5.6.31b-LINUX-FEDORA-INTEL

PS: I need someone to provide me with the macOS silicon binaries, that would be very appreciated. Please upload in the comment below. Thanks

PS 2: It's required to delete ctrlr.settings to refresh your global preferences since I removed and updated CtlrlrX default global settings.

WINDOWS : C:\Users_username_\AppData\RoamingCtrlr\Ctrlr.settings
MAC : Users/your_username/Library/Preferences/Ctrlr/Ctrlr.settings

[damiensellier]

CtrlrX v5.6.31b Windows Intel
CtrlrX-5.6.31b-EXE-WIN-x64
CtrlrX-5.6.31b-VST3-WIN-x64
CtrlrX-5.6.31b-VST-WIN-x64

CtrlrX v5.6.31b macOS Intel
CtrlrX-5.6.31b-APP-macOS-INTEL
CtrlrX-5.6.31b-AudioUnit-macOS-INTEL
CtrlrX-5.6.31b-VST3-macOS-INTEL
CtrlrX-5.6.31b-VST-macOS-INTEL
CtrlrX-5.6.31b-VST-macOS-INTEL NoCodesignForLive.zip

CtrlrX v5.6.31b LINUX Fedora 41 Intel
CtrlrX-5.6.31b-LINUX-FEDORA-INTEL

CtrlrX v5.6.31b macOS Silicon (compiled thanks to @bijlevel)
CtrlrX-5.6.31b-APP-macOS-Silicon
CtrlrX-5.6.31b-AudioUnit-macOS-Silicon
CtrlrX-5.6.31b-VST3-macOS-Silicon
CtrlrX-5.6.31b-VST-macOS-Silicon

[bijlevel]

OK, here are the silicon binaries. As I wrote earlier they are compiled for running on Ventura (macOS 13) and up. Beware of the fact that macOS will tell you, when downloading these binaries, that they are damaged and tells you to put them in the bin. This is because of the more severe protection scheme of macOS. They are quarantined. To get it out of quarantine you have to start the Terminal app and paste this command: xattr -d com.apple.quarantine /path/to/app.app It is the easiest to drag and drop your file into the terminal window to get the right path. This only applies for software downloaded from the internet!
BTW I did a quick test of AU and VST3 in my DAW (Digital Performer) and they seem to work OK.

CtrlrX v5.6.31b-APP-MacOS-Silicon .zip
CtrlrX v5.6.31b-AU-MacOS-Silicon.zip
CtrlrX v5.6.31b-VST3-MacOS-Silicon.zip
CtrlrX v5.6.31b-VST-MacOS-Silicon.zip

[damiensellier]

Thanks mate ! That really helps.

[damiensellier]

NOTE : If you want to report bugs in details, please do it in the following section of CtrlrX github :

https://github.com/damiensellier/CtrlrX/issues

Thank you ;)

[iuliancazan]

Reporting on the new build after a bit of smoke testing ...
Apple M2 Max / Sequoia 15.2 / Ableton 12

[CtrlrX-5.6.31b-APP-macOS-INTEL] -> works
[CtrlrX-5.6.31b-VST3-macOS-INTEL] -> works (forgot i have to start Ableton with Rosetta enabled, i thought at first it's not working :D)

One thing to mention - i exported a panel as VST3 (JOX'3P), but it's not showing up in the Plugins list (not even after a hard reload)

[damiensellier]

@iuliancazan Here is CtrlrX VST2.4 for macOS Intel :
CtrlrX 5.6.31b macOS Intel VST.zip

Your exports should be ok as VST.

NOTE : Some DAWs shows only VST3 version over VST when both are present so , remove the vst3 if you don't see the VST2.4 version.

Enjoy!

[damiensellier]

Hi @iuliancazan , I tried exporting an instance in Ableton Live from CtrlrX.vst (VST2.4 not VST3) and the exported instance is not seen by Live.
Every DAW has its own way to identify old VST2.4 plugins, it also depends on the OS. It seems Live Ableton on mac doesn't see the exported instance differenty than CtrlrX.vst so I'll check and test later to make it work.

For the moment I recommand you use AudioUnit version to export your instance in Live, I just tried it and it worked well.
After the export, I just had to refresh the list of AU in the Live>plugins>preference menu to make it visible.

Hope it helps.

Damien

[unityconstruct]

@damiensellier outstanding work brother! Thanks for maintaining this wonderfully unique & useful project.

[damiensellier]

@unityconstruct thanks! let me know if you find any issue, I know you're really good for that :)

[damiensellier]

@iuliancazan I found the problem, it's coming from the codesigning of the VST. Since you export an instance which is a copy of the original CtrlrX and it has changed obviously with the extra panel size, info.plist etc, Ableton see that as a file corruption.

The solution is there : damiensellier#59
It requires to add a custom flag in Xcode : CODE_SIGNING_ALLOWED set to NO.

CtrlrX 5.6.31 macOS Intel VST NoCodesignForLive.zip

With this build you'll see your exported instances. I just tried. I never use Ableton Live and discovered an offset margin on top in the exported instance plugin window. I'll fix that later.

Enjoy ;)

Damien

[mtarenskeen]

Any chance someone can build/publish/maintain a Linux version?
I can see a Linux Makefile but I can't make it work yet - my developer skills are very limited. Maybe someone can give me a hint.
I am on Linux Fedora 41.

In general: I have a website where I have published several Ctrlr panels ( https://ctrlr.martintarenskeen.nl Where should I point users today who ask me where they can download a recent and stable build of Ctrlr or CtrlrX for their platform (Windows/Apple/Linux) so that they can use my panels?

[unityconstruct]

@damiensellier that's the one I saw, but almost certain someone posted a comment re:linux <60d. Considering the audience partitioning, would hate to burden you further on it. My AV hosts are all Win7/10 so I'm cruising fine.

That said, if 1) its beneficial to the community-at-large and 2) now is a good time in the roadmapto merge & test so all OS's are possible ( even if Linux requires build script changes you won't support ) - I'd be glad to conduct any testing/triage to assist & if successful produce documentation in full or to hand off for final.

[mtarenskeen]

Today I had some success building CtrlrX on my Linux Fedora 41 system!
This is what I did:

1. I cloned latest CtrlrX from GIT
2. I cloned latest ctrlr from GIT
3. I copied CMakeLists.txt from the old ctrlr source directory to the new CtrlX directory
4. I edited the path to my vst2sdk in CMakeLists.txt to match my local paths
5. I run: cmake ./ ---> a Makefile is created
6. I run: make ctrlr_Standalone ---> ctrlr_artefacts/Standalone/ctrlr binary is build
7. I run: make ctrlr_VST ---> ctrlr_artefacts/VST/libctrlr.so is build
8. I run: make ctrlr_VST3 ---> ctrlr_artefacts/VST3/ctrlr.vst3 directory and content is build

A short test running the standalone ctrlr binary was succesful.
I will do more testing later.

I also tried building CtrlrX using Producer and the Ctrlx.jucer file to give me (another) Makefile. Building using this Makefile look fine at first, but the building process at a certain point stops with a bunch of error messages. I will attach the output of my terminal here.
ProjucerLinuxMakeFile-build.log

[damiensellier]

That's really cool! thanks for checking that.

If everything is working fine, would you mind posting zip files of the different builds (Standalone, VST, VST3) as a comment, I'll put them in the list in the first post for other users to try.

Thanks

Damien

[damiensellier]

I had issues building Ctrlr at first because I did not unzip the boost file to the right folder :
The correct boost directory should be CtrlrX/Source/Misc/boost/boost/(boost_subfolders_like_accumulators_here)

I don't know if the those errors from the cmake log are related.

[damiensellier]

Also, luabind requires compiling with the older C++11 or C++ v14 not above, that's probably why some luabind and boost are seen as deprecated.

I used an old mojave computer to compile the macOS intel binaries so c++ 14 is default on mine, but default in more recent computers will be c++ 17

You would need to select "C++ Language Standard : C++14" in the Projucer project settings :

I'll set to c++ 14 not (default) in the next release.

[mtarenskeen]

Hi, I downloaded installed latest version of Projucer/JUCE, a whole bunch of libraries and the Steinberg VST_SDK and the simply tried to load CtrlrX.jucer in Projucer. Then it created a Linux Makefile for me and I tried how far it would succeed in compiling. I cd to CtrlrX/Builds/LinuxMakeFile/ The build process started, and proceeded succesfully for quite some time, stopped after a series of errors. If we are able to identify and fix these errors, wouldn't that be the way to go? Isn't that CtrlrX.jucer project file meant to give a multi-platform solution? I would not prefer different build scripts, and different GIT forks for every different platform... I have attached the text output from my terminal when I did "make -f Makefile" using the Makefile I got from Projucer. Op dinsdag 4 februari 2025 om 00:21:38 -08:00:00 schreef UnityConstruct ***@***.***>:

…

@damiensellier <https://github.com/damiensellier> that's the one I saw, but almost certain someone posted a comment re:linux <60d. Considering the audience partitioning, would hate to burden you further on it. My AV hosts are all Win7/10 so I'm cruising fine. That said, if 1) its beneficial to the community-at-large and 2) now is a good time in the roadmapto merge & test so all OS's are possible ( even if Linux requires build script changes you won't support ) - I'd be glad to conduct any testing/triage to assist & if successful produce documentation in full or to hand off for final. — Reply to this email directly, view it on GitHub <#700 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2YYODBEOEDA5G3TBEIJK32OB2BFAVCNFSM6AAAAABWJVZ6G2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBVGIYDSNI>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[damiensellier]

projucer is supposed to set a compiler file for the different platforms but Ctrlr has other libraries included so it may contain errors or incompatibilities.
You replied via email and the attached file vanished so if you could post here the error log maybe it could help.

The best would be to take the latest CtrltX version and merge the different linux mods available in the keinstein pull request.
That's a lot to compare and never done this kind of thing before.
I'm going to try to use the cherry pick/compare" function in github desktop to see if the software can help me with that.
If someone else confident with linux and github could do it and do a pull request to ctrlrx that would be even more appreciated.
Damien

damiensellier/CtrlrX@master...keinstein:ctrlr:fix_linux_build_and_startup

[ekwipt]

Would love to see a version for Apple Silicone, as i don't run anything Rosetta anymore. only Component and VST3.

Thanks for keeping the project running

[damiensellier]

it's coming ;)

Usually @bijlevel works on them and provides them soon after the release.

[bijlevel]

I will have a look one of these days. Still I think running CtlrlX with Rosetta is a good alternative.

[mtarenskeen]

CtrlrX-5.6.31b-LinuxBuild.zip

This is a Standalone/VST/VST3 Linux version that I succesfully built on Linux Fedora 41. I copied https://github.com/RomanKubiak/ctrlr/blob/master/CMakeLists.txt to my CtrlrX directory, I edited some lines to match my local VST_SDK path and then did

cmake .
make all

And I had to manually put the version number and date in a file named "CtrlrRevison.h" to show up in the About dialog in CtrlrX.
In the zip you will find a Linux VST, VST3, and Standalone version. It seems to be working on my Linux Fedora 41 system, but I do see a lot of warnings and error (?) messages, mostly JUCE related, in my terminal if I start CtrlrX from there but seems to be giving no fatal problems (yet). Fingers crossed...

Feel free to try my builds, or try to build yourself. You might need to install a bunch of libraries and the Steinberg VST_SDK in that case.

[damiensellier]

Thanks for the files!
I changed the CtrlrRevison.h so that it gets the build time from a c++ macro.
The build version is taken from the projucer project plugin version field so , since you get your cmakelists file from an old ctrlr version I guess this is why yyou had to do it manually.

the most important is to use the JUCE directory included with ctrlrX it's version 6.0.8 and I modded some modules to have more lookandfeel colourSchemes.

The builds should be set to Release mode, not debug.

Thanks for your help!
Damien

[mtarenskeen]

I never succeeded comipling the keinstein fork, so no no surprise that this CMakeLists.txt doesn't work for me (yet).
First I had to change project version from 5.6.31b to 5.6.31 because the "b" wasn't accepted.

Then I was getting an error about lua-5.1 not found.

P.S. The CMakeLists.txt that I copied from the "old" ctrlr tree in fact had a higher version number "5.7.1". I also have an old ctrlr-5.7.1 installed on my system that I compiled from the original ctrlr tree.

Someone suggested to bump CtrlX version numbering to 7.x. I think that's not a bad idea.

[damiensellier]

oh okay I remember the versioning went totally wrong at one point.
Next official release of ctrlrx will be 6.0 because JUCE v is 6. If ever one day we update juce to 7 ctrlrx will follow.

Projucer is supposed ro generate a cmakelist, I wonder if we could find a way to have it working with the right projucer settings.

[keinstein]

I never succeeded comipling the keinstein fork, so no no surprise that this CMakeLists.txt doesn't work for me (yet). First I had to change project version from 5.6.31b to 5.6.31 because the "b" wasn't accepted.

Then I was getting an error about lua-5.1 not found.

The reason may be that there is no lua-5.1 development package installed in your system. The build instructions https://github.com/keinstein/ctrlr/tree/master clearly say that the package must be installed on your Linux machine. The way Ctrlr was provided was completely nonstandard, hard to upgrade and even broken (wrongly included incompatible system headers, conflicting libusb, etc.) when I started to play with it. Whenever I change something I try to use the standard ways provided by CMake and PkgConfig and the system wide packages. This allows to benefit from bugfixes that are added to the Linux distribution while Ctrlr is unable to detect them.

On the other hand the included Lua package was a mixture of a long outdated original lua-5.1 version, mixed with source files of additional lua libraries and patched to load these. I reverted and sorted these things in such a way, that the additional libraries are loaded within the Ctrlr code, so that a standard Lua package can be used, e.g. the latest lua-5.1 package. The libraries are all loaded in Source/Lua/CtrlrLuaManager.cpp, now.

P.S. The CMakeLists.txt that I copied from the "old" ctrlr tree in fact had a higher version number "5.7.1". I also have an old ctrlr-5.7.1 installed on my system that I compiled from the original ctrlr tree.

Someone suggested to bump CtrlX version numbering to 7.x. I think that's not a bad idea.

[dervur]

Thanks so much for the amazing work! I built it in Windows and I works just fine. The only weird thing is that I created a modulator, and its value does not seem to change, I don't know if it me that I forgot to do something when creating operator, or it is an actual issue... If I copy paste operators from old projects they work, but the newly created ones it doesn't seem so and they don't give an output to MIDI either.
Maybe it is just me as it has been plenty months since I did a panel and for now I can just copy-paste modulators from other ones.

For reference:

[damiensellier]

@bijlevel you can just post them here as 3 different zip files I'll put them in the 1st post. I'll run a virus scan before as I always did.
I use avast on my mac computer and do scan with https://www.virustotal.com/gui/home/url for online files. It's working great.

Thanks!

[dervur]

Yeah daminen that was weird, tbh said modulator was not sending MIDI but it was an isolated case all new modulators were fine.

A weird bug (if it is a bug) is that after I change the look and feel once I cannot change it again until I close Ctrlr and reopen it again. Rarely it happens to the button of the resources too (they become unclickable).

[damiensellier]

@bijlevel "after I change the look and feel once I cannot change it again"

Which look and feel? the general one from the preferences ?

the one from the panel?

or the one from the modulator?

[dervur]

I mean the general one (I didn't even know there was one for the modulators lol). If you want I can make a video later

[damiensellier]

The one in the Preferences is actually setting your default LookAndFeel for the entire CtrlrX app. It's going to tell what colourScheme you prefer when you open the app, and what default colourScheme/LnFversion your new panel will get.

For exemple, some people like to work with the old Ctrlr 5.3.x style by default which is V3. So for them it would be a great idea to select in the CtrlrX preferences "Default Look And Feel Version" to "V3". Don't panic on restart if CtrlrX is still V4 light, but when you create a panel it will be V3 indeed and everything will follow.

It requires to restart CtrlrX to apply this setting. close everything, restart, you'll get V3 and when you create a new panel just go for New panel and the default panel LookAndFeel will be V3 and the default LookAndFeel of the new component will follow as "V3".

But if you want to work in a V4 environement and still design a V3 panel, keep the preferences to V4 BUT change the panel LookAndFeel to V3. you'll get a V3 panel anyway.

CtrlrX preferences "Default Look And Feel Version" is stored on your computer in preferences Ctrlr/Ctrlr.settings
panel & modulators lookandfeel are stored in the panel file.

If you load a V3 lookandfeel panel, CtrlrX will follow the style.

If you design a V4 jetBlack panel, and you export it as a restricted instance, the exportedInstance.app or exportedinstance.vst3 etc will get V4 jetblack by default so that everyone using your plugin are seeing the same thing and Preferences/exportedinstance/exportedinstance.settings will get the default lookandfeel set to V4 jetblack.

You can also design a panel with V4 jetblack lookandfeel BUT want your sliders or just one slider green, you can select "KurzGreen" in the slider settings et voilà. If you want a custom colour slider click "LookAndFeel is customized" and select your own colours, this will lock the colours' settings.

So if you mostly design V4 white/blue panels, just go with:
Preferences / Default Look And Feel Version" "V4"
Preferences / Default Look And Feel ColourScheme" "Light"

If you like the old design of Ctrlr and want those ugly blue sliders :
Preferences / Default Look And Feel Version" "V3" or even "V2"
Preferences / Default Look And Feel ColourScheme" "_" (does not matter)
(don't panic on restart if CtrlrX is still V4 light, when you create a panel it will be V3|V2 and everything will follow)

Preference LookAndFeel requires restarting as the popup notifies to apply new default.

Hope it helps to understand the logic.

[damiensellier]

For information, I'll soon release v5.6.32 which fixes a few issues mentioned here.
Probably early March.

If you have any issues, don't hesitate to report your bug with details.

Thanks

Damien