CTRLR Workflows vs Versions ( and URLS to various Versions ) #601
-
|
Version Table that's possibly deprecated/incorrect at time of reading
Old-Old Official Builds_(ctrlr.org)_New-Old Official Releases (github)Current Tip Revisions [as of 2024-01-29] :
Ctrlr Versionstable under dev
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 19 replies
-
|
RE: CTRLR DEV I imagine there are at least 2 'active' tips various peeps are on:
|
Beta Was this translation helpful? Give feedback.
-
|
@Godlike-Productions ... lol... if you knew how lost I am looking at the noodlefest they call C BUT.. looking at those zipped blog archives.. there's a shittone of awesome stuff, from both UI design and programming principles... I'm somewhat weary at jumping into the code too much - I don't konw how many languages I know enough of to get the damn job done & God has a sense of humor I haven't figured out yet b/c seems like every other contract bounces between Java & C# so I'm nimble but NEVER get the luxury of getting mystical with either. |
Beta Was this translation helpful? Give feedback.
-
|
@damiensellier ... yeah I've moved on from that idea :-P
Can't say enough about your recent facelift of CtrlrX brother!!!!! Didn't look too trivial.. & I hope that mapping some of all this out might help your or one of the other gurus. The shear volume of information seems to lend itself to forgetting kool stuff as soon as new kool stuff hits the desktop. |
Beta Was this translation helpful? Give feedback.
-
|
Oh I wish SYSEX was so structured. Its designed specifically for model specific support. I think the only universal command is the model ID request, and even among manufacturers their SYSEX model varies wildly. Many are not even publicly available, especially sysex dump formats. By way of example, we've been reverse engineering the Kurzweil patch dump format for over 20 years, and finally have most of it mapped, but it's been a monumental effort. A patch has thousands parameters, most of which are optional, and even with the support of Kurzweil it has been difficult, as it isn't documented there either. So many companies simply no longer exist, so when developing a panel it's really a matter of researching the synth in question and mapping control to a message the synth understands. Sometimes we've had to hack functionality that was never intended (such as my Jupiter 8 Morph Panel) as the synth never supported MIDI. Heck, even a library of links to MIDI specs of synths would be amazing, let alone full blown support within the programming interfaces. Companies like Soundtower, SoundQuest and the old SoundDiver only really provide a veneer of control over the synths they support, often implemented in a very inefficient manner, and often with serious bugs that they won't fix. |
Beta Was this translation helpful? Give feedback.
-
|
haha.. going to assume they do that 'bit packing' absurdity that makes the trivial, monumental
|
Beta Was this translation helpful? Give feedback.
-
|
Don't get me started on bit packing. Everyone does it differently. And then there are checksums that evaluate to negative numbers without disclosing their algorithms (side eye at Eventide) Don't get me wrong. Kurzweil's are amazing and I'm grateful at their long term support. They synths internally are bulletproof, and flexible. It's us trying to do stuff they were never designed for that is the cause, and the turnover of engineers and lack of code comments. EMU do have some nice filters though. I have an ESI32 in my studio, and an Orbit, but honestly rarely use them. We are really spoilt for choice though and Kurzweil's just work from power on without having to load any samples. |
Beta Was this translation helpful? Give feedback.
-
Old Official Builds: https://ctrlr.org/nightly/?C=M;O=DCtrlr-5.3.191.exe 07-Apr-2017 11:31 12418210
Ctrlr-5.3.199.exe 07-Apr-2017 11:34 12446672
Ctrlr-5.4.11.exe 07-Apr-2017 11:37 12950017
Ctrlr-6.0.4.exe 16-Jan-2019 17:33 26294401
Ctrlr-x86_64-5.4.11.sh 07-Apr-2017 11:36 16680052 |
Beta Was this translation helpful? Give feedback.
-
|
Hi @unityconstruct , you're spot on. For anyone releasing VST3 the only way to go is with 5.6.23 and above. VST3 builds require at least the Ctrlr version moddified by @jmechnich to work properly with xcode. My version CtrlrX base on @jmechnich 5.6.23 is currently at v5.6.28 and has new features and bug fixes. The changelog is on the fork home page. Enjoy! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @damiensellier I stole your notes & added above, but failed to pass on THANKS!... Haven't built your latest Hatz off. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your different version Logs, it helps understanding where we are at. Everyone here on this github are all versed into synths, external hardware FX and it seems we are more into doing music... but for our own need we had to keep the project (almost) up to date to be able to design panels for our beloved MIDI controlled gears. My fork called CtrlrX is relying on Jorg's @jmechnich Ctrlr spin. If your project is working with 5.6.23, 99.99% chance it will work with CtrlrX. There's no major updates in there and I will keep JUCE 6.0.8 as long as it's possible. You can export VST3 "intermediates" as I call them to build properly named and identified plugins with CtrlrX. It works for both mac Intel and M1 M2 and PC. I'm not into Linux so I can't tell if it's working on this particular platform. I started working on the AAX version of CtrlrX for pro tools, but Avid's partner prohibitive requirements ($$$) prevented me from going further. I had a dev account but it needs to be renewed every year. It's far from being enticing and hated that "exclusive" approach. Most people using ProTools have VST wrappers anyway. CtrlrX will stay at version 5.6.xx until we have every bug/issue fixed, especially the VST3 naming issue. It has to export instances properly to deliver VST3 plugins with juce one click. It's unfortunately not the case right now. I always post version updates on the Ctrlr discussion section to let people know about the new features, and the changelog is always updated on the .md of my fork. Thanks for your work. Welcome to the community, hope you'll design nice panels with those tools! |
Beta Was this translation helpful? Give feedback.
-
lol... that makes 2 of us....!Anyway your recent UI update is SLLLLIIIIICKKK sir! |
Beta Was this translation helpful? Give feedback.
-
|
last year's stab at the Prodatum UI port.. with a new UI mockup attempt built while traversing that HELPFUL StepByStep doc |
Beta Was this translation helpful? Give feedback.
-
|
One other consideration that's important to me is the iLok linker code for OSX to support PACE copy protection. One other thing I have noticed with VST3's built from the original 5.6.23 is there is an issue with the canvas and panel size in Windows. Has this been sorted in your latest CtrlrX version? I'm looking at doing some Windows VST3 builds again, and looking at the best current version to compile? I applaud all the development going on, I'm just struggling with which version is the best for VST3's right now. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, the xlinker to give the extra space required for ilok is always added to my jucer file in the xcode mac settings :
The canvas and panel size (showing scrollers) have been fixed in my version 5.6.28. #588. We talked together last year about being able to design responsive/scalable panels, instead of forcing different size settings... it's now available with v5.5.28+ (More details here : #588). Please Confirm this is what you're talking about. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
@unityconstruct Great overview, must have cost you an awful lot of time! I have some additions to your overview. I have 5.6.23 to 5.6.29 compiled for Silicon Mac succesfully using Juce 6.1.4. On this Silicon Mac also the AU and VST3 do load OK in my DAW's (Digital Performer 11 and Mixbus 9 for Silicon Mac). I also compiled succesfully these CTRLR (Standalone, VST3) versions for Win 10 and Win 11, but both Windows systems are running within VMWare Fusion, because I don't have a PC. But I'm confident these CTRLR-version will also run on a "real" PC. I did look at the differences between Juce 6.0.8 and 6.1.4. and it seems mainly being about better VST3 support. So I propose to everyone to try and build CTRLR with Juce 6.1.4, because it may fix VST3 issues? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @bijlevel , thanks for your feedback, can you please post individual zip files of your Apple silicon of 5.6.29, standalone, VST3 and AU builds on the discussion #604 ? We would get all the available versions over there that would be awesome! Thanks! Damien PS: I'll upgrade to Juce 6.1.4 for the next release, it'sa nice suggestion. |
Beta Was this translation helpful? Give feedback.
Old Official Builds: https://ctrlr.org/nightly/?C=M;O=D
Ctrlr-5.3.191.exe 07-Apr-2017 11:31 12418210
Ctrlr-5.3.193.exe 07-Apr-2017 11:31 12415654
Ctrlr-5.3.196.exe 07-Apr-2017 11:31 12417540
Ctrlr-5.3.199.exe 07-Apr-2017 11:34 12446672