Forum Replies Created
-
Posts
-
Hi
IMO the ability to link nodes is a “nice to have” (if I am understanding the requirement), whereas a workable envelope widget seems essential for a synth editor.
Well, with my approach I was trying to provide a generic solution, as intended by atom. IIRC he wanted to either provide a generic control that is simple to use, or eventually integrate proprietary envelope controls like ADSR. The problem with my code is, that it being an entirely scripted solution all customization must be done in code. If it was a proper control, you as the user wouldn´t have to worry about the linking of the nodes. You´d rather have a button that appends a node to the last node and you could checkbox it as dependant or something like that.
wow this D20 panel is really great, any release plan, macrodx?
Thanks, but no, I´m sorry. If so then I will announce that in a seperate topic.
Hmmm.. somehow I´m getting the feeling this relates to the problem I´ve posted here.
Atom, I know you´ve got alot on your hands, but am I mistaken that there might be a general issue with cubase?BUMP UP 🙂
Any news on this? Haven´t checked the latest nightly yet though…all seems to be working in C7
Which version of Ctrlr did you use and how did you set it up in C7?
i don[‘t own it and i really don’t want to install any pirated stuff.
And I wouldn´t want you to… Thanks for looking into that though.
Maybe you wanna give this a try and see if the plugin behaves differently than in other hosts:
http://www.hermannseib.com/vsthost.htm
It may be quite close to the cubase spec…Bump… No input to this, anyone?
Seems to me that Cubase is the least used VST host 🙂I couldn´t open it either… If you need any help with the envelope components then tell me.
Without seeing it I assume the controls are still children of the group but are positioned outside its bounds. Most times the only way to get them back in place is by the modulator list, where you can then edit the bounds by hand. Also, when you copy a group then only the group modulator is copied, not the contained modulators. When you paste a modulator that you´ve copied from a group, it is pasted as child of the panel itself. you then have to drag-drop them onto the group and reposition them. If you do that for a multiselection of modulators, always make sure to hold down shift before left-click for dragging. Otherwise your multiselection will be lost and some of the modulators become invisible as they are positioned outside of the group bounds…
Another remark: I did not see much sense in implementing controls for the lower partial, because I don´t think one will have the need to control the upper and lower partial in realtime. As a sound editor, I would use my panel to edit the upper partial, save it and then assign it als lower partial if I want to. But that´s a matter of taste…
Hi,
well I never tested it as an AU plugin. I´m aCubase user and as far as rendering goes never had a problem with a panel. Things do get messed up sometimes during design time though, when you copy-paste UI elements around, especially between tabs. I do like the tabs because you can keep things compact, but that´s a matter of taste. You could also use layers instead. Ctrl comes with a demo panel that shows you how to handle them…Actually,
after having close and opened the panel again, everything’s up side down now, and i get a Lua error on line 18…Well, the D-20 panel contains more than 20 scripts, so which line 18 are talking about 🙂 ?
Hi,
just as I wrote in an earlier post:
VAL = xx
CHK = z4Hi,
your SysEx messages are missing the value and checksum parameters. Instead, in their place you only have a 00 value…
Try this for lower partial 1 frequ:
F0 41 00 14 12 00 01 4D xx z4 F7
xx will be replaced by Ctrlr with the current modulator value
z4 will be replaced by Ctrlr with the calculated Roland checksumAnother question at this point: Have you ever successfully sent ANY MIDI message from Ctrlr to the D-50?
For example, place a uiMidiKeyboard on the panel and hit a note. Does the D-50 play?
I am still convinced that your message setup is correct (F0 41 00 14 12 00 01 4D xx z4 F7), but there´s a general communication prblem…Hi,
I took a look at the D-50 manual and according to that your settings should enable your device to receive SysEx. The only thing I can´t tell is whether the internal write protection migth prevent this. I have a D-20 and successfully control it using Ctrlr, but it is not comparable to the D-50 SysEx and settings wise (but that´s where my DeviceID question came from. The D-20 has a device ID parameter that let´s it receive SysEx disregarding the MIDI channel)…
Have you tried sending other messages from Ctrlr to the D-50? Like Pitch Bend, Program Change or any of the supported CC´s?The Bitstream settings say “Control value position 1 (V1) = 8”. This is the 00 byte before F7 in the Message. Also it says “Insert sysex checksum = yes”. So Bitstream will do that for you right between the value byte (00) and eox (F7). So the message I´ve suggested for Ctrlr should be correct.
I suspect I might be missing something on the D50, but after re-reading the manual and more, everything is setup how it should be to receive Sysex.
I think it has something to do with your settings. Could you post in detail how you´ve set up your D-50? Relevant params like RxChannel, DeviceID…
Hi,
your SysEx messages are missing the value and checksum parameters. Instead, in their place you only have a 00 value…
Try this for lower partial 1 frequ:
F0 41 00 14 12 00 01 4D xx z4 F7
xx will be replaced by Ctrlr with the current modulator value
z4 will be replaced by Ctrlr with the calculated Roland checksumWell, if you´re talking about the DW template I´ve provided then in fact there are no modulators for that. The sliders are only connected to the D-20 Envelope. But here´s how that works:
The class CEnvelopeList is initialized in panelLoaded(), collects all modulators with modulatorCustomNameGroup == “DXDynamicEnvelope” and stores them in a table as CEnvelope objects with their modulator name as the key. Sliders or other modulators are connected in two ways: Each modulator that has modulatorCustomNameGroup == [modulatorName of the envelope] will be regarded as linked to that envelope. (Check the sliders in the demo, they are all linked to the D-20 env). Now each of these modulators is assigned distinctively to a point axis in the respective envelope template file by setting pt:setLinkedModulatorX/Y. You will see that in the DW template file all seLinkedMod lines are commented out…
And one more link thingy: If you connect two points using setLinkedPointY() then both will follow each other. That way you control e.g. the sustain point with the decay point and vice versae.Hello again,
I´ve investigated a little further and here are the results:
– Cubase6 has problems with the 32bit plugin version. But this is the case with many plugins running on the 64bit version. Crappy vst bridge app…
– I could not get my panel to work with any MIDI path inside the host. It´s only working when I select input and output devices not occupied by the host. That in fact completely bypasses all plugin functionality and except the panel runnning inside the plugin it just as running controller standalone.
What did work though was recording controller movements into cubase. But then again during playback they are not reflected back to the panel.Thanks, feedback is appreciated.
Please use the version attached to this post where I fixed a bug I iscovered with linked modulators.Hello again all,
finally I´ve got a demo panel to present. Actually it´s more than a demo. I wanted to have envelope control for my panels so this turned into a fully useable control and therefore took a while longer…
Maybe you want to give it a shot.
About the demo panel:
i´ve included a button that lets you switch between two envelope templates. One is a Roland D20 pitch envelope, which also connects to the slider modulators.
The other one is a Korg DW style envelope with ADBSSR.
Take a look at the template code files (via the lua editor, in group Envelope Templates). The envelope is based on a basic set of properties for each point.
The entire framework is such that you can put as many envelopes on your panel as you like. They all use the same set of codefiles. If anyone finds it useful I can write some documentation on how to integrate it into panels and set up envelope points.Edit: The first file version had a bug. Forgot the isRestoring check on the template switch button…
