Development Thread About CTRLR 5.6 for Apple Silicon M1/M2 [ARM64]

[damiensellier]

ARM64 being the new standard architecture for the latest Apple computers with their Apple Silicon M1 & M2 CPUs, we decided to open a thread about the current status of CTRLR for Apple M1/M2 setups.
More to come soon.

Damien

[damiensellier]

NOTE : version deprecated v5.6.31b is now available :

#700 (comment)

---

There's a macOS M1 version for Ctrlr 5.6 (commit f452347) build available, I downloaded it when I saw it but I don't have a M1 or M2. Here are the files :

Ctrlr 5.6 Mac ARM Standalone:
Ctrlr-5.6-f452347-App.zip

Ctrlr 5.6 Mac ARM Appex:
Ctrlr-5.6-f452347-appex.zip

Ctrlr 5.6 Mac ARM AU:
Ctrlr-5.6-f452347-component.zip

Ctrlr 5.6 Mac ARM VST2:
Ctrlr-5.6-f452347-vst.zip

Ctrlr 5.6 Mac ARM VST3:
Ctrlr-5.6-f452347-vst3.zip

It seems that the midi I/O are not working properly on this version.
The latest intel version of CTRLR is 5.6.1 based on JUCE 6.0.7.
The first thing to do would be to update CTRLR to work with the latest JUCE version 7 which is fully compatible with Apple Silicon computers.

[bijlevel]

I started with implementing a mouseUp event for a slider. I did copy all the mouseDown code I could find and copied it into to the various files and changed every mouseDown text with mouseUp text. Sometimes Xcode gave an error after pasting, so that code I did remove. After I had copied/pasted many, many code from many places in the source and Xcode didn't show errors, I did a build. It build without errors, but the interface showed this:

So it seems it needs some more work in the UI... I'm on my way, but not yet reached the finishline! 😉 If someone has tips about how to proceed, I would be grateful. In the meantime I will keep on trying.

[damiensellier]

Did you copy paste everything from both the .cpp and the headers .h ?

You should also take a look at CtrlrComponent.cpp on line 103 it refers to the different panel properties for the generic components :

ctrlr/Source/UIComponents/CtrlrComponents/CtrlrComponent.cpp

Line 103 in 8aa00d8

setProperty (Ids::componentLuaMouseDoubleClick, COMBO_ITEM_NONE);

A new line defining the mouseUp event must be added :

setProperty (Ids::componentLuaMouseUp, COMBO_ITEM_NONE);

then define the MouseUp function on line 186, always in CtrlrComponent.cpp :

void CtrlrComponent::mouseUp(const MouseEvent &e)
{
    if (mouseUpCbk && !mouseUpCbk.wasObjectDeleted())
	{
		if (mouseUpCbk->isValid())
		{
			owner.getOwnerPanel().getCtrlrLuaManager().getMethodManager().call (mouseUpCbk, this, e);
		}
	}
}

then on line 448 must be added the related callback function on this particular event (after the double click definition) :

ctrlr/Source/UIComponents/CtrlrComponents/CtrlrComponent.cpp

Line 441 in 8aa00d8

else if (property == Ids::componentLuaMouseDoubleClick)

	else if (property == Ids::componentLuaMouseUp)
	{
		if (isInvalidMethodName (getProperty(property)))
			return;

		mouseUpCbk = owner.getOwnerPanel().getCtrlrLuaManager().getMethodManager().getMethod(getProperty(property));
	}

And also on the related header CtrlrComponent.h , you should add on line 92 :
virtual void mouseUp(const MouseEvent &e);

Then on line 132 you should add the mouseUpCbk variable :

WeakReference <CtrlrLuaMethod> mouseMoveCbk, mouseDownCbk, mouseDragCbk, mouseDoubleClickCbk, mouseUpCbk ;

I think this would work with all that. This should add the mouseUp event callback dropdown for every "generic component" like sliders and buttons.

Hope it helps ;)

Edit: I added the mouseUp function. The different sliders cpp require the mouseUp function to be modified too.

[bijlevel]

HI Damien, I did double check, but I did add indeed the needed mouseUp code to all those places you indicate, and I think even to some other places. The fact that the build succeeds without errors means (I hope) this part is OK. Still the mouseUp callback has to appear in the panel interface...

[nutsynick]

i have an m4 mac and the standalown works but none of the others show in ableton 12

[bijlevel]

Did you have to move the standalone out of quarantine? If so then you should do the same with the plugins.

[dobo365]

Also interested in that one and in the same situation as you; no M1/2 computer ;-)
Thx for creating this summary thread!

[damiensellier]

I know John @goodweather worked on the PC version of CTRLR with JUCE 7.3 in April but not sure if he succeeded with that.
If all the files are working well together with the latest LUA, LUA Bind, JUCE etc that would be a good start to upgrade both PC, Intel Mac and M1/M2 Ctrlr versions. I'll ask him via email so that we can use his github fork as a starter.

[nutsynick]

Tried that nothing happened with vst2 and vst3--Sent with mail.com Mail appOn 13/02/2025, 19:23 bijlevel ***@***.***> wrote: Did you have to move the standalone out of quarantine? If so then you should do the same with the plugins. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[bijlevel]

What about the AU plugin?

[damiensellier]

Hi, we covered the problem with Ableton Live. There's a problem with codesigning.
This is a link I posted in the ctrlrx 5.6.31b release discussion:

https://github.com/user-attachments/files/18652941/CtrlrX.5.6.31.macOS.Intel.VST.NoCodesignForLive.zip

This build does not have the local signature so it's not blacklisted by live when scanning for new vst plugins.

Hope it helps. I'll post the link to this specific issue below 👇

Damien

[damiensellier]

Ctrlrx v5.6.31b fixed the vst not showing up in live ableton
#700 (comment)

But, vst2 has codesign issue so here is the fix :
damiensellier#59

There's a command line to uncodesign the binary :
damiensellier#47 (comment)

codesign -f -s - your_path_to_CtrlrX.vst_or _your exported_instances

It's going to be required for all exported instances.

Damien

[nutsynick]

That's in there now but still not seen by Ableton --Sent with mail.com Mail appOn 13/02/2025, 19:31 bijlevel ***@***.***> wrote: What about the AU plugin? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[bijlevel]

I will look into it. On my side it is no problem, because I did build the app and plugins ;-), so it is trusted by my Mac. I will download the builds, which forces my Mac to put them in quaratine, and will see what happens. But not tonight, maybe tomorrow...

[nutsynick]

Awesome...IAM a beginner at this code stuff.....but used ctrl for years on an intel Mac, I luv it--Sent with mail.com Mail appOn 13/02/2025, 19:37 bijlevel ***@***.***> wrote: I will look into it. On my side it is no problem, because I did build the app and plugins ;-), so it is trusted by my Mac. I will download the builds, which forces my Mac to put them in quaratine, and will see what happens. But not tonight, maybe tomorrow... —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[bijlevel]

You should know that the Intel version works like a charm on a Silicon Mac, but of course the Mac uses Rosetta to accomplish this. Speed is not an issue, I noticed. BTW I never found it a problem to use (old) Intel stuff this way on my Silicon Mac. Maybe you can try that (also).

[bijlevel]

I noticed you're probably using not the latest downloads. These can be found here: #700 So maybe you try them first. Also you should be aware of the problems with Ableton as indicated by @damiensellier. I'm not sure if the issue is already solved. AFAIK he is working on a CTRLR update (5.6.32)

[nutsynick]

Many many thanks guys, I'll keep u posted --Sent with mail.com Mail appOn 13/02/2025, 21:20 Damien Sellier ***@***.***> wrote: Hi, we covered the problem with Ableton Live. There's a problem with codesigning. This is a link I posted in the ctrlrx 5.6.31b release discussion: https://github.com/user-attachments/files/18652941/CtrlrX.5.6.31.macOS.Intel.VST.NoCodesignForLive.zip This build does not have the local signature so it's not blacklisted by live when scanning for new vst3 plugins. Hope it helps. I'll post the link to this specific issue below 👇 Damien —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[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