CtrlrX v5.6.30 Release - GUI & Maintenance Update #619
Replies: 18 comments 180 replies
-
|
// Reserved For Posting Links To Binaries // CtrlrX 5.6.30.1 | macOS Intel versions : CtrlrX v5.6.30.2 macOS Silicon CtrlrX v5.6.30.1 Windows Intel CtrlrX v5.6.29 Windows Intel CtrlrX v5.6.30 Windows ARM64 |
Beta Was this translation helpful? Give feedback.
-
|
Hey 'compiler guy'... and goodweather, which version are we talking about? Any chance of getting the direct link to the repository or release version that I need to check Dobo's problem on windows? |
Beta Was this translation helpful? Give feedback.
-
|
I just tried and macOS versions are OK but the PC has been compiled with a old VS cache or project files, so the ctrlrIDs.xml are out of date and doesn't pass the new properties like colourSchemes and viewPort properties. @Ted-juh We are talking about CtrlrX v5.6.30.1 here. Source files are there : https://github.com/damiensellier/CtrlrX I cannot compile the WIN binaries because I just have a VM version of my PC available currently on my Mac and it's slow as hell. |
Beta Was this translation helpful? Give feedback.
-
|
I did run the EXE on Win 11 and indeed the same issues as John describes. But OTOH no "Hello-Kitty"... When I compile, I always first use 'Clean Solution' assuming this will clean an old VS cache(?). The build is definitely based on version 5.6.30.1, I did check the CtrlrDMS.xml file for that. VS also offers a 'Clean CtrlrX_SharedCode', 'Clean CtrlrX_StandlonePlugin' etc. Maybe I should try that, but for now I leave it to @Ted-juh, because I think he is our 'Window guy' 😉. 
|
Beta Was this translation helpful? Give feedback.
-
|
I'll try to make a EXE of 5.6.30.1. I'm also on Windows |
Beta Was this translation helpful? Give feedback.
-
|
I checked again with the downloaded WIN10 version of v5.6.30.1 and I have the version name hello kitty as default for a new panel. This thing is becoming a mystery to me: |
Beta Was this translation helpful? Give feedback.
-
I'll check that directly. I'm on Win10... |
Beta Was this translation helpful? Give feedback.
-
|
@damiensellier I have no clue how to put them in Ctrlr but I do know that the L&F implementation in Ctrlr itself is not completely there yet. Not that I could do better, no way. You are probably getting tired of hearing this, but I'm still busy with my Ctrlr project. I'm about 80% done. So, when the time is there and I don't feel comfortable yet to see how to replace Luabind/ Boost, which I probably will feel like, I'll have a look at the L&F in Ctrlr itself. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks ;) I found a way to implement them in the ctrlr files. I would just need to add the getScheme() functions and schemes enum in the different ctrlr files where they are called or even put them in a common file like CtrlrInlineUtilitiesGUI.h |
Beta Was this translation helpful? Give feedback.
-
|
Ok, need to boost my ego here. How does this look so far?
A couple of minor GUI/ paint mistakes but besides that: |
Beta Was this translation helpful? Give feedback.
-
|
It looks good but what is it for? |
Beta Was this translation helpful? Give feedback.
-
|
Its primary goal is to simplify how to build the Ctrlr VST3 with CMake with a IDE of choice. Just select the IDE, set the source folder and you're good to go. Only thing required is that you install CMake and a IDE of course. All processes run in the background. Every choice you make in the VST3 options section gets "injected" in the CMakeLists.txt file. That way it should build a ctrlr.vst3 in a folder format that you need to open in a DAW and save the file again with the panel of choice to get the right VST3 file. It's separate from the panel, for now. But it should be possible to get all this inside the panel editor. But I ran in so many problems that I decided to test it this way first before I added it to the panel properties. There is an option to save/ open all the chosen options. So you can differentiate version numbers or ID's to your likings with different configurations. And because I was busy anyway, I made it possible to build a release yourself. Download the "newer" repository, point to the source folder and IDE and off you go. Oh, and in case you wondered, no more Projucer. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
@damiensellier I deleted some/many of my comments (mainly the ones about the 'Internal function' and the uploads) to avoid cluttering this thread. Maybe you can do the same, because otherwise your answers to my posts are hanging in the air, so to speak ;-). Later this day I will build the Silicon and Windows ARM versions. |
Beta Was this translation helpful? Give feedback.
-
on my Mac with virtual Win11 (ARM) shared code took 9:48 and standalone 8:09 |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure if it's useful to compile shared code, I only compile standalone, AU and VST3 even if my project is started from scratch. Each instance probably compile the shared code anyway and use it later for the other types. |
Beta Was this translation helpful? Give feedback.
-
|
Damien is right. The SharedCode is a sort of container for all the source files, every format as in standalone/vst3 are basically just links to the SharedCode needed to build said format. That means the SharedCode is being built everytime you build a format and thus no need to build the SharedCode separately. Apart from the SharedCode: Debug however, just compiles the files that the IDE thinks are changed, adds them back in the IDE blob. See it as a fragmented compiled file the IDE can take fragments out of it, which have changed code, compiles the new code and adds it back. Thus much faster than recompiling a release everytime. That builds the whole project just in case or to make sure anything that's changed gets compiled. Compiling a release takes around 3:30 mins for me while debug usually around 3 to 5 seconds. While a clean/ rebuild takes around 15 seconds. |
Beta Was this translation helpful? Give feedback.
-
|
From the beginning of my compile journey I always compiled first the shared code. I didn't realise that compiling for the other instances it always includes compiling also the shared code in the process. Thanks for the tip! When developing I will take @Ted-juh 's advice at heart to use first debug and then, when ready, release. |
Beta Was this translation helpful? Give feedback.
-
Is this 5.6.30 or 5.6.31 because that
|
Beta Was this translation helpful? Give feedback.
-
|
Dnaldoog posted a test panel in this thread, somewhere. I think it's this one: It won't work in that panel because the mouseInputSource has been added to 5.6.32. It will work if you are on 5.6.32 and open the panel in that version. If I'm right. |
Beta Was this translation helpful? Give feedback.
-
|
I don't know how this panel is supposed to work. With "my" v5.6.30.2 on Mac the mouse jumps to various locations when I alter the sliders. I'm not sure this his the normal behaviour I did inspect the source files and did find Lua>JuceClasses>LMouseInputSource.h. So is it fair to assume that this file is included when compiling? BTW can we be consistent about the version numbering (5.6.30.2 versus 5.6.32)? I think we have to leave it to @damiensellier to alter the version to a higher number. |
Beta Was this translation helpful? Give feedback.
-
|
If it jumps to various place it should be working then. |
Beta Was this translation helpful? Give feedback.
-
|
Ah, thank you! So then my previous upload for Silicon Mac stands with the agreed version number. Happy Eastern! |
Beta Was this translation helpful? Give feedback.
-
|
On my side, I also succeeded to build 5.6.30.1 on Windows. If 5.6.30.2 is useless, can we just scrap it to not confuse people? Happy Eastern to all of you! |
Beta Was this translation helpful? Give feedback.
-
So I have just built this. Is this the correct 'about' notice? It is still showing 5.6.30 but the build time is showing as WED 27 March 2024 14:00.
|
Beta Was this translation helpful? Give feedback.
-
|
This happens a lot to be true. Sometimes you get a stack trace, sometimes the Ctrlr window just vanishes into oblivion. No alert window or anything. Especially when there seems to be a wrong luabind. |
Beta Was this translation helpful? Give feedback.
-
|
So it's not just me - phew |
Beta Was this translation helpful? Give feedback.
-
|
I'll check if there's a statement checking if a method is valid in the ctrlr source code. If not we should add one and a fallback with an alert box. EDIT: LUA methods poorly checked from the callbacks combobox with "isInvalidMethodName", we need something more elaborated :) I'll add it to the to-do-list. |
Beta Was this translation helpful? Give feedback.
-
|
To add to the problem: A def or whole class added to the Juceclasses as Luabind might look and compile fine without a problem. Then you write a Lua method in Ctrlr. Then even the Lua method compiles fine and passes through without a hiccup. It's then when you want to test the code at runtime that you run into three options:
I had this at my end multiple times. Nothing to worry about. But adding defs and classes to Luabind became an extremely infuriating experience. You never know what the problem is. Somewhat related to this topic: Let me take a moment to explain an infuriating case of Luabind: Why on earth, does getEventRelativeTo get accepted while it's wrong in so many places (No call to the component class) but the second, withNewPosition results in an error? I know.. It will show the error and all that, but then again, that kind of moment makes me want to pull my hair out. And God knows I have a lot of hair to pull. |
Beta Was this translation helpful? Give feedback.
-
|
I'm working on a Lua Test Framework and some design patterns that seem to alleviate much of the pain by allowing the bulk of the logic/features to be developed without the need of Ctrlr. This allowed me to develop all the Sysex Dump and State-Management logic, create Tests that I can run again & again, and let the IDE do most of the work. One of the main tenets I'm striving for is to have a
As the test Library grows, I can make rather large changes & let the tests find where I screwed up and give me all the data needed to debug. Critical for one who isn't blessed with tons of hair 😎 |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
I have trouble compiling v5.6.30.2 for Silicon Mac. I don't know what's the problem, because v5.6.30.1 did compile OK for Silicon Mac. I did confirm this by downloading this version and checking with activity monitor, which says it is an 'Apple" application. I tried many variants of build architecture settings in Xcode and even copying the settings from the CtrlrX.jucer file, but none works, it still compiles for Mac Intel... |
Beta Was this translation helpful? Give feedback.
-
|
Digital Performer accepts the exported VST3 instance, but I had to put it in the system library, and also my second DAW, Mixbus10, does load the exported restricted instance of a panel as VST3 plugin OK. I will look into building a VST. I think I did not build it, because VST's are deprecated AFAIK. |
Beta Was this translation helpful? Give feedback.
-
|
Oh no hang on, the Steinberg VST3PluginTestHost does actually recognise and run the Exported Instance it was just hiding it from me, probably because it thinks they are the same Plugin. I think then that there is a particular problem with Ableton recognising the VST3? I looked at Digital Performer but it's too rich for me, I'll probably pickup a copy of Reaper for some further testing as that's more in my budget :-) |
Beta Was this translation helpful? Give feedback.
-
|
On another note about Code Signing, I assume that you are building and signing to run locally only?
I tried to sign it myself with my own Developer Account, and a new Provisioning Profile:
You have to do this for everything, Standalone, VST, etc.. And the Standalone built successfully and it runs!
I'm obviously not doing something correctly. The situation of having to do a Terminal hack to get an App out of quarantine whenever you move it to another machine is not ideal, but I guess we are stuck with it? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for diving into this code signing. I never bothered with it, because on older MacOS's it wasn't realy a issue. And I think if it gives, as you indicated, still problems with restricted instances, it is better to stick with the "unquaratine" option, which is relative easy to apply. The real problem is still that the restricted instances (VST3 and AU) of a panel are getting the same name as the generator CTRLR VST3/AU. Some DAW's have a problem with this, but for example Mixbus shows both plugins with the same name, but when activated shows the right UI for each instance. Digital Performer has definitely a problem with these "same name" plugins. I believe (or rather hope ;-)) @damiensellier is (still) working on solving this issue. I'm aware of the solutions already at hand on this github given by @damiensellier and also by @Ted-juh, but a more automatic route would be highly preferable! |
Beta Was this translation helpful? Give feedback.
-
|
@spiffo-smith You can code sign your exported apps/plugins outside xcode with terminal command "codesign". |
Beta Was this translation helpful? Give feedback.
-
|
Hi @damiensellier, I noticed this sendCC = function(--[[ CtrlrModulator --]] mod --[[ number --]], value --[[ number --]], source)
if panel:getBootstrapState() then
return
end
local myNumber = mod:getMidiMessage():getProperty("midiMessageCtrlrNumber") -- CRASHES
-- myNumber=15 -- WORKS
panel:sendMidiMessageNow(CtrlrMidiMessage(string.format("B0 %.2x %.2x", myNumber, value)))
end
Regards, John |
Beta Was this translation helpful? Give feedback.
-
|
It does not crash on mac 5.6.30 but I get the following error : it doesn't work for the other midi properties as well. midiMessageCtrlrNumber sits in the follwing part of the code : We need to fix that for sure ! PS: I tried with 5.6.23 and the bug is there too. So it has something to do with the migration to the newer juce and the modified code that's been done. I'll dig deeper into that. |
Beta Was this translation helpful? Give feedback.
-
|
Excellent - thanks for that! |
Beta Was this translation helpful? Give feedback.
-
|
@dnaldoog I found the problem, I don't how it was working on 5.3.198 but with the update it should be ok with 5.6.x You can now either use |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @damiensellier ! |
Beta Was this translation helpful? Give feedback.
-
|
I can't seem to be able to build it... I would say writing a whole list is impossible to put here... I can't seem to understand what I'm doing wrong |
Beta Was this translation helpful? Give feedback.
-
|
Also, I managed to build it fine today with no errors, I didn't even change any file or folder, I just set the names back to how they originally were... So I think I must've changed a "CtrlrX" I didn't have to in projucer... |
Beta Was this translation helpful? Give feedback.
-
|
I saw you posted about getting empty red properties in another post. This is because you came across the common problem with CtrlrIDs.xml not being updated automatically in your visual studio temp folder. You had the old one from 5.6.23 and 5.629+ have new properties so they get flagged as unknown hence the red. You have everything working properly now? |
Beta Was this translation helpful? Give feedback.
-
|
Hi Damien, yeah I deleted it cause I solved it for that panel. I think the issue was that I was still using the old executable you already said to not use. By building CtrlrX successfully I managed to have the resizing options and everything else correctly. |
Beta Was this translation helpful? Give feedback.
-
|
It's all good, congrats! |
Beta Was this translation helpful? Give feedback.
-
|
Cool! Finally hahaha Now I'll get into learning new things in lua to build my panels properly hahaha |
Beta Was this translation helpful? Give feedback.
-
|
NOTE : on Saturday June 29th 2024. The Windows files posted previously are not working as it should. LookAndFeel is not working as it should and panels are not exported with the menuBar. https://github.com/damiensellier/CtrlrX/archive/refs/heads/master.zip Damien PS: We are working on v5.6.31 with Dominique @dobo365 . It's going to be available around september. |
Beta Was this translation helpful? Give feedback.
-
|
I also fixed some reported bugs in the Ctrlr issue section. |
Beta Was this translation helpful? Give feedback.
-
|
Quite a big list, again, I take off my hat for all the work you (and Dominique) put into it. One question though, maybe it deserves its own topic, but do you happen to know about juce's Valuetree? |
Beta Was this translation helpful? Give feedback.
-
|
I hope this version will help people doing the transition to Ctrlr with JUCE 6. I used 5.2.198 last week to do a comparison and it was not a pleasing experience for me, especially because the colour picker is not there so you have to find the hex codes for colours with another app. Big bummer for me. Btw, what do you want to know about valueTree? Maybe you could open a new discussion, is it ok for you? |
Beta Was this translation helpful? Give feedback.
-
|
Great. Will the VST3 identifier Win issue be fixed by September? |
Beta Was this translation helpful? Give feedback.
-
|
@alfonso73 probably not. Not even sure it's going to be fixed someday. VST2 are exporting fine though. |
Beta Was this translation helpful? Give feedback.
-
|
I did (re)compile a Windows 10 version and to me the L&F and the menubar export seems to work. I can post it tomorrow, but maybe @damiensellier you will test if first. If so I need to send it to you. How? |
Beta Was this translation helpful? Give feedback.
-
|
I think Dominique was going to post it here soon with an intermediate version 5.6.30.3 including a few features from the 5.6.31. |
Beta Was this translation helpful? Give feedback.
-
|
OK, here is the exe for Windows 10 Intel. |
Beta Was this translation helpful? Give feedback.
-
|
I'll test it later this week, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Is Ctrlr a dead project? Should I move over to CtrlrX? |
Beta Was this translation helpful? Give feedback.
-
|
Ok got it, thank you very much! |
Beta Was this translation helpful? Give feedback.
-
|
If I'm not mistaken I did already compile for Mac Silicon some time ago... |
Beta Was this translation helpful? Give feedback.
-
|
@bijlevel yes you did. It's in the list above #619 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
Yes I know 😉, but I wrote it because of @dervur planned to compile for Silicon Mac, I believe, and that would be a kind of waist of energy. Of course it is always good to try as a good excercise😉. |
Beta Was this translation helpful? Give feedback.
-
|
No I was mainly asking to see if there would be a way to export my panels for Silicon Mac as well. But unfortunately I will not be able to... I saw a little bit online and Intel AU can be opened even on Silicon DAWs, but that is not true for VST3... I was just trying to think of a way for me to export an instance of my plugin for all case scenarios/every user. |
Beta Was this translation helpful? Give feedback.
-
|
Hey, is anyone here familiar with building ctrlrX on Linux? I tried running the build.sh in the ./Build/LinuxMakefile but I get the following error: The readme seems to be out of date for building on Linux. Thanks :) |
Beta Was this translation helpful? Give feedback.
-
|
Okay, I've downloaded juce for Linux and I'm trying to build it through that, but the Linux icon is greyed out when I select 'Linux Makefile' and I can't export. Maybe I'm an eejit and using projucer incorrectly, or am I missing a configuration specific to ctrlrlx? |
Beta Was this translation helpful? Give feedback.
-
|
Wait, CtrlrX? What's that? |
Beta Was this translation helpful? Give feedback.
-
|
@esrevinue But to my knowledge you only need the projucer to open the project with your favorite editor. If it's visual studio (probably blasphemy for you Linux users) then there is the sln file. Or a codeblocks Linux build file. You can find it in the build folder of CtrlrX. That's all I can tell. @milnak |
Beta Was this translation helpful? Give feedback.
-
|
I don't know how to use cmake I always run projucer to set up the build with xcode or VStudio. There's a pull requests from @keinstein I did not add yet to CtrlrX for Linux. It's right here #400 If you ever happen to merge the pull request 400 and be able to compile for Linux and a particular distribution, let us know ;) Good luck! Damien EDIT : the pull request to update files for LINUX is from this fork : https://github.com/keinstein/ctrlr/tree/fix_linux_build_and_startup it requires to cherry pick the updated lines and merge to CtrlrX which is a lot of work and compare. I suggest you try to build Keinstein fork first to see if you succeed then merge to CtrlrX. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks damien. I'll give that fork a shot later on today :) |
Beta Was this translation helpful? Give feedback.
-
|
I´m trying to build individual VST3 on a MAC M1 with Sonoma, but it fails every time. All builds crashes by closing the DAW. |
Beta Was this translation helpful? Give feedback.
-
|
Does probably not help you with your particular whishes for building CTRL, but I had a version (CTRLX 5.6.28) running in Monterey on a Intel Mac, compiled for as early as macOS 10. I copied the standalone to Sonoma on a Silicon Mac and it runs OK, be it under Rosetta of course. |
Beta Was this translation helpful? Give feedback.
-
|
That's very kind of you, but it doesn't do me much good at the moment. |
Beta Was this translation helpful? Give feedback.
-
@synthmania67 What is wrong with it? Can you precise the problem please, I'll check that tomorrow. There's a thread on the JUCE forum about Sonoma and it seems that its compatibility is problematic even with JUCE 8. |
Beta Was this translation helpful? Give feedback.
-
|
Validation with AU is not ok probably because of 3 things I have in mind:
I will export an AU of 5.6.31 and you'll tell me if it validates Have a nice day ! |
Beta Was this translation helpful? Give feedback.
-
|
@synthmania67 if you could post your Logic AU validation report on this page that would be very helpful : |
Beta Was this translation helpful? Give feedback.
-
|
Hi Damien, thanks. About the issue: I don't know how to formulate it in English. Even in German it is difficult to describe. Compare the screenshots of version 5.6.31a and 5.6.30. |
Beta Was this translation helpful? Give feedback.
-
|
Lokk at the difference at the top left. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the report, I opened an issue on CtrlrX, it's an easy fix, I know why the panel tab is showing up : |
Beta Was this translation helpful? Give feedback.
-
|
The validation report: VALIDATING AUDIO UNIT: 'aumu' - 'sYmA' - 'cTvs'Manufacturer String: Synthman
TESTING OPEN TIMES: validation result: Öffnen fehlgeschlagen |
Beta Was this translation helpful? Give feedback.
-
|
I got it passed right away on my side with the updated plugin see : damiensellier#45 (comment) I put a link to the modified .component file in the discussion : https://github.com/user-attachments/files/18222698/CtrlrX.5.6.31.02a.component.zip |
Beta Was this translation helpful? Give feedback.
-
Hi everyone,
I just released a new version for the CtrlrX Fork : v5.6.30 it's available on the CtrlrX Master and on the CtrlrX 5.6.30 Branch.
I fixed all the reported bugs by everyone here (white on white issue, crashes etc). Thanks for your suggestions to everyone involved BTW.
The main updates are the addition of new colourScheme as global and for different components. They are inspired by famous synth and hardware colour schemes like Lexicon, Arturia, Kurzweil K Series, Roland Aira, Akai, Korg Volca and more, so that you'll be able to match your Panel to the hardware design.
!!! IMPORTANT NOTE !!!
JUCE colourSchemes are added straight to the LookAndFeel_V4 file of the GUI module in JUCE. You have to use the JUCE version (v6.0.8) bundled in the CtrlrX release or modify your own files as followed :
https://github.com/damiensellier/CtrlrX/blob/aca65f688996fbc98925b6bbf620a1c99214dc85/JUCE/modules/juce_gui_basics/lookandfeel/juce_LookAndFeel_V4.cpp#L108
https://github.com/damiensellier/CtrlrX/blob/aca65f688996fbc98925b6bbf620a1c99214dc85/JUCE/modules/juce_gui_basics/lookandfeel/juce_LookAndFeel_V4.h#L107
I also brought back the close buttons to the Panel Editor tabs, as well as on the LUA Method Editor.
And as suggested by Dominique @dobo365, buttons now can show the MIDI Monitor window on mouse click by selecting the option from their componentInternalFunction property.
It's not a major update but follows the 5.6.29 with bug fixes and overall improvements.
I'll post Binaries later as usual.
Enjoy!
Damien
Version 5.6.30
Micro Revisions
5.6.30.2 LUA mouseInputSource Addon
5.6.30.1 MidiSettings Panel Colours now follow the global LookAndFeel ColourScheme
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-EXE-WINDOWS-Intel (Fixed build provided by @bijlevel on July 2, 2024. Needs to be tested)
CtrlrX-5.6.30-Windows.zip (Fixed build provided by @dervur on Oct 14, 2024. Needs to be tested)
CtrlrX-5.6.30-VST2.zip ((Fixed build provided by @dervur on Oct 14, 2024. Needs to be tested)
CtrlrX-5.6.30-VST3.zip (Fixed build provided by @dervur on Oct 14, 2024. Needs to be tested)
CtrlrX v5.6.29 Windows Intel
CtrlrX-x64-5.6.29.zip
CtrlrX-x64.vst3-5.6.29.zip
CtrlrX v5.6.30 Windows ARM64
NOTE: Need to be updated because builds are not working properly...
CtrlrX-5.6.30-EXE-WINDOWS-ARM64.zip
CtrlrX-5.6.30-VST3-WINDOWS-ARM64.zip
CtrlrX-5.6.30-VST-WINDOWS-ARM64.zip
Beta Was this translation helpful? Give feedback.
All reactions