Forum Replies Created
-
Posts
-
Yes, same here. Only the zipFile method is what I am using for now but wish for an easy SVG implementation like we alrady have with the PNGs. But at least there is a way at all 😉
Cheers!Hi All,
About the licenses.
I was talking to Atom about that the other day and his creation – Ctrlr – is free for all to use and experiment with. You can even compile it for your needs adding stuff you need (if you have the knowledge). The code is on Github and ready to download. He has no problem with people creating panels and making money by selling them
BUT, since Atom is using external libraries anyone who want to use Ctrlr commercially should also make sure he is not breaking any laws.
This is what I’ve asked Jules (the creator of Juce) this January at the NAMM. His response was “If you are selling plugins or programs using Juce you should purchase the “Indie” license”. So this is what I did. He means also that if Ctrlr would display the splashscreen “Made with JUCE” only the personal, free license would be needed.
Anyone creating VST plugins with Ctrlr should also be a registered VST developer, it is a free and quick process through the Steinberg website.
Having this bases covered you can feel safe and free to use Ctrlr for commercial projects.One of Atoms bold ideas was that Ctrlr will be developed for Win,OSX and Linux. The fast development of new OSes on all of those platforms plus lack of suitable hardware for the OSX development is a problem for Atom. He has a regular job and Ctrlr was always a hobby of his but I think he just realized how time consuming it is to keep developing a multiplatform software. On the way Juce changed too and some libraries needed an update.
Last year he tried to work on the new GUI and few other things along the way but the ver.6 is not usable at the moment.
We all love what Atom did gave us so far and we should think about a way to keep the project going.
Maybe a Kickstarter? Maybe a separate teams developing or testing for a particular platform? I dunno. Many of us here are using Ctrlr as a hobby project so it will be hard to delegate tasks and push for results. Any ideas?
Cheers!W10 1909 here and so far all runs OK!
More and more users with newer OSes have problems with the VST versions of Ctrlr.
On Catalina it is impossible to use Ctrlr at all. Some newer versions of Cubase and Nuendo are blacklisting the plugin and not allow to open, some like Vienna Ensemble Pro can’t even find the .dll anymore.
Let’s face it – Ctrlr is getting old and need an overhaul but this will not happen too soon considering the trends from last few years and Atoms lack of interest in supporting it. This will be a very sad day but it will eventually come. Sorry for the pessimism but in 2020 we’ve seen worse, so I will not be shocked if one day Ctrlr will not open at all or the builds will be useless.
Just reading the room.
I hope Roman will find some time to give Ctrlr a bit more love. Roman – are you listening? 🙂
Again, sorry for not helping too much but I had to vent on that occasion.
Cheers!Hi spiffo!
1. What value “1y” suppose to represent? It is not a valid hex number.
2.
declare your variable ex. “yourVariable”:
yourVariable = …(some value coming from somewhere, could be as Hex could be Integer)
in your Lua code you need to concatenate that variable with the rest of the SysEx:
“F0 43 11 13 “..yourVariable..” 7F F7”Cheers!
Nice dnaldoog!
I myself am diving into the whole uiCustomComponent universe right now but the Graphics Class, although very powerful, is a bitch to be honest 😉
Have a great weekend guys!
M.I did asked Roman about that some time ago and he explained to me that no audio classes are implemented to safe him some headache 😉
Hi dnaldoog!
Thanks for the reply!!! This is exactly what I was worried about. Too bad those are not included, it would be so much easier to create panels smaller in size without the need to use PNGs but SVGs instead.
The good news is it still can be done using the ZipFile but I personally wish for a simpler way so maybe in some future build Roman will do something about it.
BTW: Any word on what is the current state of the Cntrlr updates? Ver.6 was around the corner but since over a year nothing happened really. I know Roman has a lot on his plate right now so I am not even gonna bother him about my little SVGs issues 😉
Cheers people and stay safe in this turbulent times!
M.Simple LUA script where you check for those parameters in question, create 2 variables and assing the resulting values to them like so:
outDevice = panel:getProperty(“panelMidiOutputDevice”)
outChannel = panel:getProperty(“panelMidiOutputChannelDevice”)console(“currentOutDevice = “..outDevice)
console(“currentOutChannel = “..outChannel)if you use console to see what the results are you should see something like this:
LUA>> currentOutDevice = YAMAHA-CS80-OUT
LUA>> currentOutChannel = 1Cheers!
Hi atom,
just realized you have uploaded the 6.0.25 installer the other day.
Downloaded and tested ASAP and all the issues described here (http://ctrlr.org/forums/topic/6-0-1-release/) are still there.
So, no VST3 exported plugins for now. Bummer.Any idea how we could help bringing the VST3 version to life?
Cheers.
Great idea!
I am interested in this too so i will be following.
No idea what build is the stable one for Linux so can’t help, sorry.
Roman???Hi Roman,
yes, I can load Ctrlr as a VST2 plugin but with the graphics issue above and VST3 Ctrlr without any issues.
Also i can open my Panels from the VST3 version of Ctrlr and they work fine. The exporting as you mentioned above is not working for now.
I hope that help.
A helpful tip: You can test any version of Cubase or Nuendo for 30 days fully functional. Just an idea 😉
Cheers!Hi Roman,
short feedback regarding ver 6.0.4.
Great to finally see the included VST3 format of Ctrlr!Issues:
When both plugins are installed – VST2 and VST3 – only VST3 is visible from inside Cubase and Nuendo (newest and older versions) and it is in the “Synth” category but this is no biggie.
When VST3 version is not installed/copied, the VST2 version finally pops up in Cubase/Nuendo but it has the same issues as described already above in this thread, tested on Cubase 8, 9, 10 and Nuendo 7, 8.
A VST3 plugin version of a panel (that is working already as VST2 just to be sure that the panel isn’t the issue here) does not pops up in Cubase or Nuendo at all. Nada. Like it isn’t there (but it is), the VST3 version of a panel made with the VST3 version of Ctrlr isn’t also blacklisted in Cubase/Nuendo (this happen sometimes with plugins from other vendors).
So considering issues above the new build is not usable at the moment: VST2 panels can’t be created due to the CtrlrVST2 version issue and VST3 panels can be created but are invisible for the DAWs so no luck here either.Any ideas what might be the cause?
I was so pumped seeing the VST3 format added and knowing that Steinberg is ditching the VST2.4 for good very soon and allowing only VST3 plugins to be used in a near future.
Always happy to help/test newest builds!
Thank You again for your commitment to this awesome project and let’s hope for a working, bugles version of Ctrlr soon!Cheers mate!
Hi Roman,
it is Cubase 10.0.10 (the newest version with the actual newest update).
The ver. 5.3.201 of Ctrlr worked flawless though.
Cheers!Hi Roman!
Happy New Year 2019 and Thank You for the newest build.
So far so good, except, the VST version on Windows is showing like this (see attachment) and the plugin window can’t be resized in any way. Ideas what could be wrong? I will test some more and report any weird findings!
Cheers!@daimondamps – no I don’t, sorry, but don’t worry, all will be back again soon. They have dmca’d Stanford and Cycle74 among many others 😉
Roman will sort this out for sure.
Cheers!Hi guys,
– the Github repo is down because it contains parts of the VST2SDK and this was never allowed without a written permit from SB. They just never cared too much but now they do since they are getting rid of this VST version and I suppose now even after asking them they will not give the permission cause this is not in their interest to spread the VST2 format any longer.
– from what I understood once the VST2SDK is not present in the repo anymore Github will unblock it.“As a panel developer you don’t distribute the vst sdk therefore it shouldn’t be necessary to ask Steinberg for permission.” – true if you distribute a panel only or a stand alone version, not true if a VST plugin – for that you need to register as an official developer and obtain a VST2 license from Steinberg (free and fairly simple task, SB just need you to sign the license so you play by the rules).
“To me another question is: what happens when you sell panels? You will sell the free Ctrlr framework, the Juce libraries which are not allowed to sell unless you buy it, and proprietary Steinberg vst code. In other words, you make money with the work done by other people / companies. I would be surprised if this would be legal.” – Ctrlr is using Juce code and Atom is distributing his creation for free under the GNU license, this is all OK and by the rules made by Juce/Roli. As soon as you use Ctrlr to create a panel that you sell commercially you as the creator/developer need to get a proper Juce license: Personal, Indie or Pro. Personal is free up to 50k cash flow and you need to put the “Made with Juce” disclaimer on your product. Indie and Pro are paid licenses without the “Made with Juce” branding and much higher budgets. When you sell VST plugin made with Ctrlr all of the above apply plus you need the free VST2 license from Steinberg which can still be obtained until October 1st 2018.
Have a great evening guys!
Possemo, please read my first post in this thread, I think all is there. Please don’t mix the terminology, VST SDK is something different then plugins/panels using VST2 format.
Cheers!… or directly from the ftp:
https://download.steinberg.net/sdk_downloads/vstsdk3610_11_06_2018_build_37.zip
