Replies: 2 comments 1 reply
-
Verrrry good question. Unless you want to process audio, I would prefer focusing on optimizing Ctrlr by adding JUCE classes and enhancing the workflow to focus on beautiful working panels. Ctrlr can really be improved, having all jUCE color schemes would be great for exemple, some JUCE class are not bound to LUA and so on... The pros of all JUCE The Cons of all JUCE For midi only interfaces I will forever stick to Ctrlr. Someday, if I have extra freetime I'll try to fix and add extra JUCE features to Ctrlr, but I am not a developper and definitely prefer doing music instead of coding :) So Ctrlr is the right way to make midi plugins to me. |
Beta Was this translation helpful? Give feedback.
-
Have to agree with both of you about the pros and cons. It's the GUI-editor of Ctrlr that smashes Juce out of the ballpark. But in my humble opinion, as soon as there is LUA involved to go beyond what's capable with the GUI-editor, Ctrlr has a steep learning curve as well. I think the (old) forum proves my point here despite its helpful members. In the meantime, I've been doing my research about JUCE. Found some tutorials that might help one another. Here's a small list: http://scowlingowlsound.com/blog/2019/blog-1 https://www.youtube.com/channel/UCpKb02FsH4WH4X_2xhIoJ1A https://suzuki-kengo.dev/ |
Beta Was this translation helpful? Give feedback.
-
Perhaps it's like swearing/ cursing in a church but how many of you guys tried to make a panel in Juce instead of CTRLR?
I started a few weeks ago and didn't get much further than a few sliders with some L&F applied to it. The fact that I'm a noob concerning C++ doesn't help either. C++ is an instant headache. Take into account the whole structure of Juce with its overrides/ namespaces, do this here and that over there in another file without any explanation why (and do not dare to ask simple questions on the forum) and it might be clear that Ctrlr is a breeze to work with. Although it has its limitations.
All tutorials seem to cover just the basics or are copying the tutorials of Juce itself which in itself are very confusing to me. I found some books on Juce/ C++ but the books about Juce are getting too old and I haven't found a book about C++ without a lot of foo bar or a/ b which confuses the hell out of me.
Then why do I start with Juce and C++? Well, I thought if I could get a better understanding of Juce/ C++ I could help improve the CTRLR project. I'm not reluctant to put some effort into it but it's like hitting a brick wall every 10 minutes. So the question is, do you guys have any recommendations where to start to learn C++ or Juce? Or do you have good tips on how to take this hurdle?
Beta Was this translation helpful? Give feedback.
All reactions