Macro to open floating mixer, channel editor and one macro folder?

[DT_bettinzana]

What do you think about the "MIDI Remote Controller" window? Do you need some improvement? I ask for this because it would be good to document a "stable" version to avoid obsoleting the user guide after 2 days.

Thank you for your support!

I'm really enjoying the MIDI RC window. A suggestion would be to enable transparency on the window. I perform a rough pass of CC1 or CC11 with a foot pedal and then I go back and do a much more detailed "performance pass" with the faders. It's helpful for me to see the notes that are coming up, but they are often obscured by the window. At the moment, I'm having to move the MIDI editor to another screen and then back to the touch screen to do touchups with the draw tool.

This is a pretty minor detail and maybe isn't a concern for enough users to be a worthwhile thing to implement (if it's even possible).

Thanks!

OK, I have no idea at the moment. I will check tomorrow if it is possible.

PS: no more crashes?

Thank you!

[Home Studio 87]

Hello all!
I want to remove the beta status from the last beta version of DTouch for Cubendo and we must update the very outdated User Guide.
What do you think about the "MIDI Remote Controller" window? Do you need some improvement? I ask for this because it would be good to document a "stable" version to avoid obsoleting the user guide after 2 days.

Thank you for your support!

Oups have another Midi Remote Controller window, same as the one that you've done but with button (on/off) in place of fader........

Another one or the same with two faces?
And ... what MIDI messages should this on/off buttons send to the virtual MIDI port?

Another one same layout as the original but with button (on/off) in place of fader with the same midi channel & midi cc layout that the original midi remote controller window. it can be use to communicate with generic remote in cubase to open/close, Power on/off... insert plugins of the selected track... very useful ...

[Havoc911]

PS: no more crashes?

Thank you!

No more crashes, running nice and smoothly now!

[DT_bettinzana]

Oups have another Midi Remote Controller window, same as the one that you've done but with button (on/off) in place of fader........

Another one or the same with two faces?
And ... what MIDI messages should this on/off buttons send to the virtual MIDI port?

Another one same layout as the original but with button (on/off) in place of fader with the same midi channel & midi cc layout that the original midi remote controller window. it can be use to communicate with generic remote in cubase to open/close, Power on/off... insert plugins of the selected track... very useful ...

OK!!
But when you tap on these buttons, what MIDI message should DTouch send? This is what I want to know, not the use that you want to do.

[DT_bettinzana]

PS: no more crashes?

Thank you!

No more crashes, running nice and smoothly now!

GOOD

[Home Studio 87]

Another one or the same with two faces?
And ... what MIDI messages should this on/off buttons send to the virtual MIDI port?

Another one same layout as the original but with button (on/off) in place of fader with the same midi channel & midi cc layout that the original midi remote controller window. it can be use to communicate with generic remote in cubase to open/close, Power on/off... insert plugins of the selected track... very useful ...

OK!!
But when you tap on these buttons, what MIDI message should DTouch send? This is what I want to know, not the use that you want to do.

Midi CC with midi channel like the "original" midi remote controller window one

[DT_bettinzana]

Another one same layout as the original but with button (on/off) in place of fader with the same midi channel & midi cc layout that the original midi remote controller window. it can be use to communicate with generic remote in cubase to open/close, Power on/off... insert plugins of the selected track... very useful ...

OK!!
But when you tap on these buttons, what MIDI message should DTouch send? This is what I want to know, not the use that you want to do.

Midi CC with midi channel like the "original" midi remote controller window one

The original remote controller has faders which send continuous values from 0 to 127.
You want buttons which are not continuos value controllers. So what value should a button send: 0, 1, 2, ... 127? How many buttons per “strip”? 1, 2, ...
And remember that they cannot be “toggle” because the status in Cubendo is unknown.
And ... this should be a general purpose panel useful for all the users. If you like to send a MIDIcc 7 with value = 127, other users could need a C0 Note-Off message.

[DT_bettinzana]

I'm really enjoying the MIDI RC window. A suggestion would be to enable transparency on the window.

We are doing it

[Havoc911]

We are doing it

You are the best!

[pablo1980]

I will begin using the CC soon...will give some feedback, so far I like it very much (would like if it could be snappier, it takes a couple of seconds to appear on screen)

You´ll probably want to kill, me but I would sugest that you divide the manual in standard and legacy versions, it could be a lot more clear and useful moving on from legacy, from now on. Just delete the legacy sections so no confusion arises.