Forum Replies Created
-
Posts
-
Hi dasfaker,
sure, no problem
https://sdk.steinberg.net/
you need to download the SDK and in the VST2 folder there is the PDF to fill and send back to SB.
Cheers!Hi guys,
I hope I can clear few things about this situation.
Steinberg came with the VST2 format in 1999, in 2008 they have introduced VST3 and already then they said that VST2 will be ditched in a near future. Ten years later developers are still developing mainly for VST2.4 and the VST3 standard has hard time establishing on the market (for various reasons). During the last 2017 Juce DevCon the head of developement at Steinberg Yvan Grabit already explained that VST2.4 will is longer supported and that the whole manpower goes into VST3 dev anyways since years already.
Few weeks ago the VST3.6.10 came out and they also announced that VST2.4 licenses will no longer be granted after October 1st 2018. This simply means that if you are a developer that still want to develop/sell/distribute plugins using the VST2.4 technology you can do this until 01.10.19 without any extra paperwork IF you need/want to do this after the 01.10.18 though, you need to apply for a VST2 license BEFORE 01.10.18 so once this date comes you are still allowed to use the VST2.4 in your products (for VST3 there is another separate license to obtain).
As for the VST2SDK the license always said: “This Software Development Kit may not be distributed in parts or its entirety without prior written agreement by Steinberg Media Technologies GmbH”. They just never cared too much for all the Github repos that distributed the SDK in full or partially. Now they care thou because they want the VST2 development to finally stop and they want to push the VST3 on the market. I think we all understand this move. They have invested a lot time and money to develop the VST3 and it is clear to me that they will push to use it.
It is worth to mention that we are talking about the VST2SDK here (the only reason Ctrlr Git is down) and about the possible development of VST2 plugins.
Steinberg never said that the DAWs will stop the VST2 compatibility and that all the zillions VST2 plugins will suddenly stop working after the 01.10.18, on the contrary, they assured many times on different occasions that VST2.4 will still be there and the developers will migrate to VST3 over time anyway (or some will not) but the VST2 will still work although will not be supported anymore in any way (this is the case already since few long years).
So, I hope that short explanation will help some of you. If you develop panels with VST2.4 fill out the paperwork, wait for the written approval from SB and keep developing until the sun freezes.
I think Atom should do this too if he is planning to develop Ctrlr and its VST2 connectivity. Including VST3 might be also a good thing but as we all know this is another can of worms so he might not be so quick to jump on that wagon.
Cheers people and have a nice day!Hi human fly,
take a closer look at your findvoice(), fetchVoiceTable() and fetchKeyTable() methods. Those get triggered multiple times whenever you use the Kit button or the Pad button (in kitSelect() and padSelect() methods).
Also in the Library() where you placed all those functions there are weird dependencies and triggering one of them triggers the other. I just glanced over quickly and did not test any further since I got a project to finish but I think you should start there. Also the way you create tables using the _G metamethods might have something to do with it. Dunno. Just few ideas to think about.
Cheers!+1
yes, goodweather, is there the last version available to download (even in french)?
Cheers!Hi desfaker,
nope, no memoryBlocks in any of the panels in question. Just reading values, passing them to labels, sending some Sysex when a particular track is being selected etc. I use Lua to recognize what midi note was played on the midi keyboard and harmonize the incoming pitches using some harmonic rules I wrote for that purpose. I use a lot of tables thou to store the currently selected settings and to recall them later, kinda basic “preset” storing and recalling. The panel uses around 700 modulators altogether and most of them send values to tables when there is a need for a “preset” storing. Might this be the issue?
Cheers!Hi lfo2vco,
the problem might be the Ctrlr version you are using, if you use the latest build you shouldn’t. Atom said few times already that it is full of bugs and the Lua implementation might be broken there. I use a Ctrlr version from March 2016 and all works as intended. Cheers!
Hmmm, interesting point Puppeteer!
Is there a way we can test it or dig in some documentation to get to the bottom of it? My initial search didn’t gave me much back about this issue.
Cheers!Hi zmix,
if I recall correctly Atom once said that they are all “undefined_x” in the VST /AU instance of Ctrlr because as the plugin Ctrlr instance loads first in your host there it has to declare some parameters but the names are not available by then, next you load/open your panel that might have named parameters but they will not show. After you export your AU/VST version of your panel and open it your DAW the names should be visible as intended.
Cheers!Hi Puppeteer,
yes in theory this is what I thought but it looks like XYpad is not even changing its own “Current Modulator Value”. This is why I think it is able to control the assigned Modulators for X and Y axis but it is not able to receive any feedback and that makes it kinda useless really if you ask me and creates even more confusion when user “think” the values are represented by the position of the “ball” on the XY canvas but they are not.
Any ideas on the ev. Lua method that could somehow make it respond to changing values? This will be my last try or I will have to give up on XYpads completely.
Cheers!Hi Puppeteer,
thanks for chiming in. Can you please elaborate on what do you mean by isMidiCLock? Couldn’t find anything on this.
My DAW is sending MIDI clock (0x78 value) but nothing is recieving and interpreting it in Ctrlr.
Cheers!hi humanfly,
I can’t think of any method that will be resposible for the feedback on my XY pad. When I use the pad the associated Knobs are moving only the other way around it is not working. When I move knobs I should see XY pad mirroring the changes but nothing seems to happen.
If your XYpad works properly I would of course appreciate the Lua method that is associated.
Cheers!hi,
try maybe thisfor i=1,4 do
local dec= panel:getComponent(“pcmDec_pt1p”..i)
console(String(“selected is: “..dec))
end
endnot in front of my workstation now so can’t check it ATM.
Why don’t you create a table with all the ASCII characters you need in it and just randomize thru the tables elements? I am pretty sure guys on the forum here posted this kind of ASCII characters tables many times already.
Cheers!hi,
for now you randomize before you go into looping so the rnd value isn’t changing anymore while you are in the looping part. Try to put the randomization bit inside the loop so it will be randomized each time your loop iterate.
Cheers!Hi dnaldoog,
I did tested your code and what I’ve found out is that the Sysex that comes from OX indeed changes the numbers on all the modulators BUT the actual value of the modulator is not affected at all. Can you please explain why this might be happening? I was under the impression that Sysex will cause the value to change and not only the values display. I hope this make sense to you. For testing purposes send Sysex to a modulator that had a value of 0 for example and after you see the new value displayed go to edit mode and see that the value is still 0 and there was no change in value caused by the incoming Sysex data. Weird right?
Cheers!
