Question about Real Time Controllers

[RhythmRmixd]

Hey Everyone,

Ok here's the deal. I have a couple E-MU sound modules running through a MOTU MIDI Express XT Interface into Digital Performer 3. I've finally figured out almost everything possible as far as interfacing the modules and DP3 to give me the results I want for recording MIDI tracks. I keep running into a problem with getting my modules realtime controller knobs (4 of them on the front panel of each module) to remember the settings I just set them at whenever I rewind the MIDI sequence back to the start using DP3's transport controls. I understand how to save the presets on the modules once I've altered the real time controller settings to my liking, but to bring these settings back I have to recall them from the module save menus (on the modules themselves) after everytime I rewind (with the transport controls) to the beginning. This problem does not occur when I set the sequence to loop continously. Does anyone know how to prevent DP3 to stop sending whatever message its sending causing the real time controllers to reset when I rewind?

Thanks for your help

 

[ssscientist]

I've never used DP, but in general it sounds like you have the 'chase controllers' mode enabled. Look around in the software and the manual --- what you are looking for is a menu or manual page devoted to CC's. It should be a simple matter of unchecking a box that's now checked...

 

[RhythmRmixd]

I messed around with some settings on the master menu on each of the modules last night, and found one of the submenus called "recieve program change" for each of the 16 MIDI channels on the modules (the Proteus 2000 actually has 32 MIDI channel capability). Once I set the real time controllers and preset settings to my liking on a particular MIDI channel, and then turned the "recieve program change" for that channel off, this corrected the problem. I'll have to look more into DP3 to see if there is a quick fix for this problem in that program as well, like you suggested.

Thanks

 

[tedluk]

That sounds like Cubase is sending out a "Program Change" or possibly a "Zero Continuous Controller" message at the start of the sequence. I don't use Cubase so I don't know exactly how it works. Lots of sequencers send a message at the beginning before the sequence begins to make sure everything is zeroed so you don't get any strange results. Somewhere in Cubase will be settings to control this. Look in the manual for information on sending "Program Change" or "Continuous Controller" messages.

When you turn off the "Receive Program Change" parameter, it stops the Proteus from acting on that message so everything stays as you've set it. What you want to do is fix it so that at the start of the sequence, Cubase sends a message to the Proteus (and every other device connected to it) telling it exactly what programs and settings you want to use. That way, every time you start the sequence, it will sound the way you want it to. And then you can learn to automate your continuous controllers!

Good luck!

Ted

 

[RhythmRmixd]

There is a sub-menu in DP3 (under the Basics Menu) called "Set Event Chasing", and it has radio buttons to toggle note on-velocity, off-velocity, patch changes, etc., and controller information. I'm guessing this is what I'll want to use, and it looks like I have to punch in each of the realtime controller #'s that I want to be unaffected (or affected) by the change. I'll mess with it some more when I get off work today. Ted, your right though about me not wanting to use the "recieve program changes" because I don't need to turn off DP3's instructions to the modules indefinatly, just at the beginning so I can maintain whatever preset edits I've made on each rewind. Although it is useful to temporarily "freeze" the preset if needed. I think if I automate the preset parameters with DP3's automation features, I can set "reference points" at the beginning of the song for each preset parameter I intend to automate, and that should correct the problem as well.

Peace