New DTouch for Cubase+Nuendo v1.4.9 BETA

[Home Studio 87]

Another idea for the DTouch toolbar (if possible) : the possibilities to "minimise" the DTouch toolbar without minimizing the other macros folder already open….

This was actually a bug that we already fixed internally.
You will find this solved in the final DTouch v1.5.0, which will be available "tomorrow"

Thank you....

[pablo1980]

v1.5 is a big number...is there any other goodies waiting for us?

[orthogonalrecords]

So, please, remind us of this request in a few months and we'll see what we can do!

Ok, will do. Thanks.

[Support Team]

Ok Silvano! Alt + press is a good idea!
Thanx!
Valerio

Great, let's wait until tomorrow: if nobody has any other idea we'll go ahead this way

Since pressing ALT triggers the Suspend All Channel Linking in Cubase, we chose the CTRL modifier for this function, but that's done right now. You will find it in the final DTouch, v1.5.0

[valario]

Ok Silvano, great!
Did you think also about my idea to add one or two other buttons under the meter on the floating?

Thank you very much,
Valerio

[cpia2002]

cpia2002 wrote: ↑30 Oct 2018 09:47
I tried using DfADER, But as i have a Midi CC X8 Fader device, it is not supported unless in Mackie mode- for the 8 faders ?

so, what is the problem in using it in Mackie-mode?

With the Latest DFader BETA , It works really well now you have done away with the Virtual Midi Routing to make it work (1.2.2) BUT there is one Big problem - An CC Value of 127 reverts to 0 , on every fader, no matter what i assign the midi CC value .

Like i said, i much prefer how much easier it is to use a MCK Controller without virtual routing, but cant find a way to "Reset" the faders - so not sure if it is a problem with DFader or my Icon Platform X sending out the wrong value at 127 only . So Close!

Will try re installing 1.2.1 , using the Virtual midi ports and seeing if the problem is the same or not. If able, can you see if you can reproduce this bug in the 1.2.2 Beta DFader ?

[cpia2002]

With the Latest DFader BETA , It works really well now you have done away with the Virtual Midi Routing to make it work (1.2.2) BUT there is one Big problem - An CC Value of 127 reverts to 0 , on every fader, no matter what i assign the midi CC value .

Aha! I have finally solved it . In Cubase i HAD to tick under Studio, Midi Ports - "Use Device Direct Music " at the bottom, and now it performs as it should.

Now it goes from 0 -127 without going back to 0 at 127, no problem. It might be worth checking that out, and including it in the DFader Manual , if not mentioned before, and if a problem with other Devices other than the Icon Platform X etc

[Home Studio 87]

Thank you Happy user here….
Show you (only DTouch screen) :

Main Workspace :

Main Workspace.png (162.22 KiB) Viewed 12736 times

Record Workspace (UAD Console is multitouch already) :

Record Workspace.png (354.19 KiB) Viewed 12736 times

Mix Workspace (2x Floating Mixer Linked) :

Mix Workspace.png (126.19 KiB) Viewed 12736 times

Black background choice in the setup (like user button floating mixer background) for the macros folder ?

cannot use Cubase without DTouch……

[orthogonalrecords]

What I found with DTouch v1.5 is that the small panner in the channel doesn't work when using my finger - it doesn't react to touches and just stays in its position. It works using the mouse though.
Furthermore the big individual "pop-up" panner seems to be unconnected to the small panner, i.e., when I use the big panner the small one doesn't reflecht the changes of the big one.

Could you please try to replicate that bug? C9.5.41 here on Win 10 Pro.

edit: Just found out that the problem only appears when a Cubase window is lying above the Floating Mixer title bar. I thought that this was not a problem with the latest 1.4.x beta, am I wrong?

[DT_bettinzana]

What I found with DTouch v1.5 is that the small panner in the channel doesn't work when using my finger - it doesn't react to touches and just stays in its position. It works using the mouse though.
Furthermore the big individual "pop-up" panner seems to be unconnected to the small panner, i.e., when I use the big panner the small one doesn't reflecht the changes of the big one.

Could you please try to replicate that bug? C9.5.41 here on Win 10 Pro.

edit: Just found out that the problem only appears when a Cubase window is lying above the Floating Mixer title bar. I thought that this was not a problem with the latest 1.4.x beta, am I wrong?

Hello,
we will check everything on Monday.