Page 1 of 1

CC midifeedback on selected channel (Cubase)

Posted: 02 May 2012 22:20
by pablo1980
Hi, new user here, I am making a cubase template. It includes some CC faders (to control virtual instruments)

Is there some way in cubase to get feedback from the selected channel so I can punch in and see CC data?
The problem seems to be that the output of the midi channel is routed to the vsti, so lemur canĀ“t get any data...

I have searched the forums and this seems to be an issue with midi control surface in general, but maybe I am lucky and somebody here has found a solution.

Thanks!!!

Re: CC midifeedback on selected channel (Cubase)

Posted: 03 May 2012 00:15
by Phil999
it's an old story with bidirectional MIDI controllers. You'll have to create a Generic Remote Device inside Cubase. You can also create a second MIDI channel with output to Lemur, but I recommend the former method, in the end it's easier I think. There's a template for Cubase including xml already posted on this forum, maybe you can have a look at it.

Re: CC midifeedback on selected channel (Cubase)

Posted: 08 May 2012 04:07
by pablo1980
Thanks phil, I have used generic remote to control cubase functions, but I don' t know how to apply this approach to midi cc messages within each track

The solution would be to have cubase send midi data (via midi sends maybe?) only of the selected channel.

How can a generic remote can be used to achieve this?

Thanks again

Re: CC midifeedback on selected channel (Cubase)

Posted: 08 May 2012 18:25
by bxsj
Have you looked at this template? http://liine.net/en/community/user-library/view/151/
B-

Re: CC midifeedback on selected channel (Cubase)

Posted: 08 May 2012 18:56
by Phil999
pablo1980 wrote:Thanks phil, I have used generic remote to control cubase functions, but I don' t know how to apply this approach to midi cc messages within each track
in the Generic Remote Device you can choose 'selected' as destination. You also may need to tick 'Transmit' for each entry for parameter feedback. You can control VSTi's, sends, inserts, whatever you like. You can find a more detailed description of how it works here:

http://liine.net/forum/viewtopic.php?f=26&t=1013

A different approach is with the Mackie Control protocol, like the one bxsj suggested. It is not that flexible, but has the advantage of track/parameter name feedback.