Your project sounds pretty cool.syncanonymous wrote: ↑20 Oct 2018well, baby steps for me with Ctrlr...lots of them
Lack of documentation leads right into a minefield...gotta be persistent and not get derailed easily.
Every day I think it isn't going to work...and I spend a day on it and find solutions.
Recording SysEx into Reason? I don't have any idea about that yet...Maybe Catblack's "Wall" is looming. I also want to record GSP2101 footcontroller toggles (midi CCs). So might need to make a Cntrlr fer that too.
In standalone mode, the mapped CCs do control my CyberTwins. I turned on TouchOSC just for a look see and that worked controlling my standalone Ctrlr panel doing nothing to Ctrlr...awesome! And got me re-inspired.
When I started (past 2 weeks), I was using the latest version 5.5.2 and "built" (placed modulators and formatted, no Lua) a basic midi cc controller. But that 5.5.2 version doesn't load in a VST host (shows up an empty VST. You need it load in you VST host to save a dll version of a panel). I've been working in standalone only, whoops. I installed Ctrlr version 5.3.201 and thar she blows, I can save my panel as a dll. My dll doesn't work on first load, tho :-/ Likely, I gonna hafta make my panel in 5.3.201 as described here. Not a huge problem....I only have 18 sliders so far. I keep all my settings in a separate doc, so it's a copy and paste fest.
So if you had a say, BCR2000 you'd have a window that showed the layout of it and it'd update the labels to show what device has focus in Reason at the moment. I've been thinking about the problem for a few years now, and I think it'll solve a problem many people have. (I do love the little screen on my Nektar P4, but imagine a configurable window for each of your midi controllers!)