Hi there, I’m testing out a new cc controller, and I’ve got something very odd going on please see the video, the controller is sending Midi cc1 and Cc11 , I can hear the plug-in and see it responding to the controller. I can also see in the lanes that. Cubase is seeing the data , but when I record a pass the Cc data is not recording , if I switch back to my monogram everything is working fine , I have check midi in put filters they are fine
One thing I can spot which is odd on midi Monitor is this new controller is not sending any position data, I don’t know what this is but all of my other controller sent position data
I have just test with clean prefs int fix it
and also Logic Pro which work as expected
Hi,
Are there any Remote Devices or Quick Controls involved in your setup?
Just Eucon and metagrid , not used Quick Controls
There are several different ways to deal with controller data.
To make this happen, go in the main Cubase menu to:
Set the Record Destination on conflict to:
Notice how the Global settings for each CC in this MIDI Controller Automation Setup can also be adjusted independently.
In this scenario, the sequencer sends the actual CC to the connected end point, and it’s up to the VSTi or external instrument to know what to do with the events. Many VST3 instruments these days ignore CCs unless specifically ‘learned’ or otherwise activated in the plugin.
In this scenario, for CCs to pass through to the instrument as they are being played by a controller, a track must be armed (monitor or record).
While you can set up Cubase to record CCs directly into automation lanes instead of MIDI parts, I personally I recommend recording and keeping them in the MIDI parts initially, because your MIDI Key and MIDI Logic Editors are quite powerful and make batch manipulation of CC events a breeze. In contrast, these powerful editors can’t get at the automation lanes.
There is an option in the MIDI menu to extract all selected CCs in the Key or List Editors from MIDI Parts to automation lanes. I.E. Open a MIDI part (or several of them) in the MIDI Key Editor, select all events, then extract them.
You can also get events kept in automation lanes back into a MIDI part by using the MIDI/Merge MIDI in Loop feature.
The primary advantage to this system regardless of your VSTi or external instrument, is that CC Events get bound to notes rather than floating freely on the timeline like traditional channel events. Double click a note, and if it has Note Expression events applied, you get a event display/graph/editor to draw/edit with. This means you can move notes around and the attached CC (and other note expression data) data moves with it. You can quantize, stretch or shrink phrases, and the controller data attached to the notes will slide and scale along with your changes. As you can imagine, this can be quite a valuable thing if you’re scoring for video/film/games and need to hit precise cue points and such.
For instruments that do not support VST3 note expression, it still works (CCs attach to notes), but events will control anything sounding on that MIDI channel. If more than one note on the same channel sounds at the same time and more than one note has CC data attached to them, it’s easy to mute/unmute events and ultimately pick the one you prefer.
For tools that do support Note Expression, such as some of the instruments that are included in HALion/Sonic, it’s possible to do all sorts of expressive manipulation on a note by note basis. I.E. A chord sounding on the same MIDI channel with all four notes doing different things with volume/vibrato/timber/tuning/etc.
You do get tools to quickly convert your CCs back and forth between Note Expression and traditional channel CC lanes.
I.E. Keep everything in MIDI Parts as independent channel CCs while recording/editing. Convert to Note Expression if you want to quantize/move notes around. Convert back to CC lanes if you want to easily do batch edits and such and find it easier to see/use.
There are also a variety of newer methods to quickly make your own MIDI Remote control panels on the fly and bind a controller CC to virtual knobs/faders/buttons/ect in them to any VST parameter in the DAW.
This a great help for anyone look into this , my problem is with the new controller im testing , as you can see in my video , cubase is receiving the CC data and also passing it onto the VSTi , but does not record as CC data .
I understand. How you have things set up can make a difference.
Double check the MIDI channels…you might give it a try with both channel in and out set to ANY.
If you have it set up to record the CC Events on automation lanes, then you’ll need to open the lane(s) and tick the ‘write’ button.
If you have it set to record CC events straight to the MIDI part, I’m currently at a loss as to what the problem might be.
You might double check the note expression tab in the track inspector and make sure it’s not intercepting the events and changing them into note expression on the fly…perhaps those don’t take if no ‘notes are sounding’?
Make sure the Globals are NOT ticked…
You might also check preferences to make sure nothing is being ‘filtered’.
Check the rest of your Track Inspector options…make sure no MIDI Modifers or transformers are in place and filtering them out.
Finally, if none of the previous suggestions got it sorted…
If you have any Remote Controls running in the MIDI Remote Manager, disable them temporarily and try it then.
I’ve built myself a loopback controller that allows me to control a bunch of things in the DAW via MIDI track that don’t have special automation/control tracks of their own yet. I can bind these 12 knobs on the fly as needed to tweak various parameters throughout Cubase. I’m actually running several different MIDI remotes right now…just throwing this one up here as an example of where to look to disable Remote scripts.
It’s ‘possible’ that a remote script might be stealing events somehow? I dunno, but it’s worth a shot in the ‘trouble shooting’ phase.
Hi,
Double-check the settings, I mentioned, please.
Thanks for everyone’s support, it’s been confirmed. It’s a bug Mac only with this new controller, I am testing, It’s very exciting when they fix it I can’t say now what it is but it’ll be out very soon
Thx Andy
Since it is moving the faders in the plugin…can you not locate that parameter and record the automation there?
Something odd is happing with the new controller I’m testing , it’s not sending position data
Hi,
Where does the MIDI Monitor come from?
Is any Quick Control or Remote Device involved?
I think, this is a duplicate of other forum.
I can now show you what I was testing. It’s released yesterday. It’s brilliant and working really well now. Eucon can now set midi Ccs
You’ve already created a separate Cubase thread for this too. Maybe just keep that in The Lounge and not fork the thread? Thanks.
This was the clarity this thread , incase some one else has the none record of midi (just in cubase)
I thought the other thread would be good for other Eucon user to join in 
