[wildthing]

Anyone?

[wildthing]

Thanks a lot Dnaldoog, I’ll take a look!

[wildthing]

Thanks jasefos! I’m glad that you like it. Unfortunately, “under the hood” parameters are not pubblic so it needs a bit of reverse engineering to bring them out. I’m trying to understand more on how to do that but it needs time.

[wildthing]

Hi Synthman, i’m still on Cubase 9.5.41. I’ve noticed that is possible to avoid that issue turning on monitor and/or recording on CTRLR track but this way your synth track will sound each time you play another track by the keyboard. Any idea?

• This reply was modified 5 years, 2 months ago by wildthing.

[wildthing]

Hi Possemo, finally i’ve extended the code to all controllers and everything seems to work perfectly with my moog.Thanks again!
Now i would like to do the same thing with my Roland SE-02.I started from the Maniek’s panel and I’ve tried to create the same “send” button adapting your code to it but somehow it doesn’t work.
Maybe Roland Boutique use e different standard?
Any idea on how can i fix it?

[wildthing]

Ok i will extend it on all other controllers. I think i can do it. Thanks again Possemo!

[wildthing]

Yeah, the easier way is what i was thinking about. Can you gimme a short example on how You would write the method?

[wildthing]

Great! Possemo you are the one! The method looks easier and it work really well. Thanks a lot!

[wildthing]

Thanks for your help Possemo! My first idea was to use Sysex and build up 2 “send/receive panel” buttons, but i didn’t find Voyager Sysex structure. Or better, surfing the web i’ve found the syxex table that i’m attaching, but it reports mainly bytes compositions. As you will see many bytes enclose bits from different parameters and i have no idea on how code them. It’s something too difficult to me (maybe someone here is gonna take the challenge 😉 ).
That’s why i’ve decided to go for a simple button to transmit snapshot parameters at least.
I’m also attaching my panel…..it’s a raw version, i’m still working on some graphics.

Attachments:

You must be logged in to view attached files.

[wildthing]

Thnaks Possemo! Actually i’m experimenting the XY surface out of my panel because i don’t want to create a mess on it. I’m definitely new on code.

This is the spinoff panel about the xy panel i’m working on.

Attachments:

You must be logged in to view attached files.

[wildthing]

Hi! I’ve read this post because i’m trying to insert an X/Y surface in my editor and i followed your advice on the matter. I’ve also took a look to the great Access-Virus-TI5 panel to understand how to settle the x/y surface. In my mind i would like to set variables for x and Y axes using 2 combo boxes privided with the names of all main modulators of the panel. So i’ve adapted what i’ve learnt, to my panel ending up with this method duplicated on both combo boxes (changing X & Y):
—
— Called when a modulator value changes
—

GLOBAL_PadY = function(modulator, newValue)

global_pad = panel:getModulatorByName(“GLOBAL Pad XY”)
if xypad_mod ~= nil then
c = global_pad:getComponent()
c:setPropertyString (“uiXYSurfaceDestinationY”, xypad_mod[newValue+1])
end
c = global_pad:getComponent()
c:setPropertyString (“uiXYSurfaceMaxY”, xypad_value[newValue+1])
pos = 1
text = string.format(“%s %s”,”Y-Axis Pad assigned to”,xypad_mod[newValue+1])
end

Unfortunately it doesn’t work and i get the attached error. Line 13 starts at “c = global_pad:getComponent()”
Could you please help me to fix the problem?

Thanks in advance…

Attachments:

You must be logged in to view attached files.

[wildthing]

It works! Thanks a lot!!!

[Author]

Posts