Forum Replies Created
-
Posts
-
I’m setting the compatibility flag for 10.7 (OSX Deployment Target) and the Base SDK is 10.10.
I have no idea how this will impact Ctrlr on any version of OSX so any feedback is welcome.
I can’t get the Ctrlr AU plugin to compile from the latest git download. I’m using Xcode 6.3.2 on El Cap 10.11.6, with a 10.7 deployment target and 10.10 base SDK (previously tried Xcode 8.0 (base SDK 10.12), but that caused even more compilation problems).
I managed to get the Wrapper.jucer project to compile and copy the libau_wrapper.a static library to /usr/local/lib; had to create and fix permission problems on that folder (is the wrapper still required now that JUCE includes the CoreAudioUtilityClasses?)
Then I had to fix the path in the ‘post-commit’ script in the ./Scripts folder, from this:
[OSNAME=”OSX”]
CTRLR_ROOT=”$HOME/devel/ctrlr”To my personal ‘ctrlr-master’ root folder:
CTRLR_ROOT=”$HOME/Documents/Programming/Ctrlr”
Running the edited post-commit script then successfully generated the CtrlrRevision.h file.
——
So, after spending 4 frustrating days getting to that stage, the AU plugin won’t compile in Xcode. I get a missing file error for this file:
‘/Users/dan/Documents/Programming/Ctrlr/Source/Misc/lua.c‘
These files are also missing from the ./Lua/luabind/luabind folder:
luaxlib.h
lua.h
lua.hpp
luaconf.h
lualib.hHope someone can help. Wouldn’t want to waste the last 4 days trying to compile Ctrlr 🙂
Thanks..
It’s just the template hooks that get created in the editor on a blank new panel. I haven’t added any code to the hooks at all, or code in the panel at all.
The “Called to calculate the MIDI value to send” isn’t crashing, it just isn’t being called. “Called to calculate new modulator value from a MIDI value” is the one that’s crashing since. Neither hook works after version 262f on El Capitan, although they worked on Lion (I think).
The modValChanged() hook is working as normal, otherwise my panels wouldn’t work.
Quick update. It seems the “Called to calculate the MIDI value to send” hook/callback? just isn’t being called in any version after 262f2710 (Apr 2014), but I can’t go back that far. And the “Called to calculate new modulator value from a MIDI value” hook is crashing all version of Ctrlr that I’ve used – so the crash problem looks El Capitan related because it wasn’t crashing in 262f where most of my Lua code was written. Luckily I’m not really using the hooks anyway, so I’ve gone back to 5.3.85 which seems to have the most stable plugin/GUI editor.
One thing that would help is being able to determine why the modValChanged() hook has been called i.e. was the mod val change coming from the GUI, MIDI input or controller input. That way I could bypass using these hooks and do all my processing in the modValChanged() hook. Is there any way to do that in Lua?
Anything on OSX right now i beyond anything i can fix. And yes there are bugs in previous versions i try to fix one at a time when they get reported.
No problem, I’m aware of the OS X situation. Just view some of my posts as a “for future reference”.
In case of LUA it’s not that easy, very often people crash Ctrlr using Lua
How very dare you. My Lua code is solid as a rock! :):):)
I’ve had 3 stable plugins running on 5.1.2
I meant 5.3.57. I think? At least, a version prior to 5.3.85.
OK, it seems it’s just uiButton’s so far that aren’t triggering the modValChanged() callback. The buttons aren’t doing anything in 5.3.163 on El Cap.
I don’t even think the mouse click is triggering a mod val change.
So that’s the newModValFromMidiVal() that’s crashing completely, and so far the buttons aren’t even switching between 0 and 1.
I’ve had 3 stable plugins running on 5.1.2 for over a year and half, and they make heavy use of Lua.
It’s just 5.3.85, and 5.3.163 in particular that I’m having problems with. I don’t think any of my Lua code is running at all in 5.3.163, or none of my modValChanged() callbacks are being called?
I need DAW recall too. Non-negotiable.
