Page 1 of 1

Posted: Fri Aug 30, 2002 10:14 am
by december
This is probably very simple, but I can't figure out how to do it yet. I'm playing guitar live through the mixer, then blending that signal with nuendo. I have "Sequencer Midi Source" connected to the mixer, but I don't know what to do from nuendo. I tried automating Main Volume, and I can see the mixer receiving a midi signal, but nothing happens to any faders. Can I automate Mute?

Posted: Fri Aug 30, 2002 10:57 am
by at0m
You have to assign midi CC# to each DSP control yourself. Then save the Midi remote Preset in the SFP device Preset list.

Or download my Pc1600x remote control set in the PResets & Tools Forum. I've made Remote presets for some mixers already. You could load those and send CC# accordingly form Nuendo. The remote control set also contains screenshots of the editor I made the Pc1600x presets in, as a means of Midi implementation guide.

Posted: Fri Aug 30, 2002 11:00 am
by at0m
Oh, and there's still some bug in Midi Remote Presets. Sometimes the mixer just mutes everything and I have to reload the device in order to hear something from it.

Ingo said these Midi Remote Preset issues will be corrected in 3.1c, which can be expected one of the following weeks.

Posted: Fri Aug 30, 2002 11:25 am
by december
Thanks for your help. I did re-read the manual, and found the procedure for assignments, unfortunately I can't find a mute command in nuendo. I tried "bank select 0" and let pulsar learn it, and it does mute the mixer, but I can't get it to learn un-mute.
Maybe I should try muting the mixer manually and letting nuendo record the info. How do I connect and record that?

Posted: Fri Aug 30, 2002 11:49 am
by at0m
Connect midi out from assigned device to Seq Dest

Bank select, among others, is not really appropriate for this job. Here's more. I copied it form a previous post I think.


When I created the Pc1600x midi remote control presets for CW devices, I noticed that some CC# are not useable for fader control.

For example:
CC# 0,32: bank select & program change,
CC# 1: modulation, is reset (read set to 0) on midi Stop
CC# 6: MSB (it's LSB will be in CC# 32-63 but 33-63 is perfectly useable for fader remote)
CC# 98-99: Non-Registered Parameter Number (NRPN) LSB-MSB
CC# 100-101: Registered Parameter Number (NRPN) LSB-MSB
CC# 121-127: Reserved for Channel Mode messages.

I don't know exactly from which of these CC# are filtered/abused where. Ie. CC#1 is reset by Cubase on Stop and is on opening of a project or sequencer.
CC#0 is already assigned to bank select in the DSP device.

It may be very boring info, but it's quite important to know if you want decent midi remote. It's not very funny to make mistakes, when you had it all written down on paper and finally made it all look very logical. I want every possible knob controlled, so I need to make these presets. I hear of people assigning CC# per CC# as they go thru the song, but that's ehm impossible time eating work if you want everything to work remotely. I mean, I don't know which knob I'm going to tweak and once I'm doing music I don't want to think about assignments no more. I want it there all ready.

Related:
http://www.midi.org/about-midi/abtmidi.htm
http://www.planetz.com/forums/viewtopic ... 41&forum=1
http://www.planetz.com/forums/viewtopic ... 6&forum=13
http://www.planetz.com/forums/viewtopic ... forum=16&6
http://www.defectiverecords.com/pc1600/pc1600.html

Posted: Fri Aug 30, 2002 1:41 pm
by december
I'll read up on those links. Thanks.
It would be so easy to just stay in Nuendo. I automated my live inputs (direct monitoring)but the problem there is that every time I open a song, the stereo signal defaults to mono, and the fader to unity. If I move the fader, the stereo sigal returns, but that's a pain in a performance situation. Maybe Steinberg will improve midi capabilities with 2.0.
I know what you mean about not having to worry with assignments when you're working.
By the time you problem solve, it's hard to switch back to being creative.

Posted: Fri Aug 30, 2002 2:46 pm
by december
Just to let you know, I got it to work now.
I recorded the changes, then looked to see how it appeared in the browser window.
BankSel 0(mute off) BankSel 127(mute on).
I don't know why it chose Bank Select, but at least the values make sense.
Thanks again for your help!

Posted: Fri Aug 30, 2002 8:14 pm
by at0m
bank select is CC#0, the first in the list.