Automatically Inserting MIDI Controllers While Recording

[ggm1960]

Perhaps the best way to try and find a solution for this particular thing is to seek out an answer in reverse. Let's say you wanted to add a couple controller on/off messages and a patch change automatically every time you hit record on a MIDI track would there be a way to do it?

The actual problem I'm having is exactly this: Every time I click record on a MIDI track I get a controller 80 and/or 81 plus a patch change message! I can't figure out where the hell this is coming from?! It only happens in one particular project file. In fact, simply record enabling an external MIDI track and hitting play causes the external device's patch to change. It's a file I started clear back with version 5.13 and has many chunks. I used to use this file during live performances for backing tracks and controlling some external gear. I've gone into Commands and tried to disable anything that may be influencing the transport section and turned off any switching functions that could be occurring with my MTP AV via ClockWorks. This problem never occurs with any new project I've created recently which indicates the problem is definitely specific to this particular project file.
Currently I'm running DP8.0.1 on a 17" MBP (MC024LL/A) running OS 10.6.8.

[MIDI Life Crisis]

It sounds like it might be a MIDI message from one of your synths, especially your controllers.

Disconnect all your external controllers and hit record. Still get the message?

[b.g.]

I don't know about the cc's, but the patch change might be because a default patch is in effect for that track/device. See here:
http://www.motunation.com/forum/viewtop ... 26&t=46142
"Top right hand corner of Tracks Overview window. Drop down menu, Clear Default Patch."

[Buzzy]

Further to what has been suggested also try opening the file, delete all chunks, create a new one, create and record enable a MIDI track and hit play. If your problem doesn't occur then you know the issue exists in one (or more) of your chunks. Delete half of them at a time until you find out which one it is. Good luck.

PS: Obviously don't Save anything here while you are troubleshooting. I'm sure you knew that, I just don't want to be considered the devil if things went South this way.

[ggm1960]

It sounds like it might be a MIDI message from one of your synths, especially your controllers.

Disconnect all your external controllers and hit record. Still get the message?

I thought the same thing at first but I've confirmed the problem only occurs within this particular project.

[MIDI Life Crisis]

Don't use that project! Seriously, start a new one, and LOAD the chunk(s) and that should cure you - well, I don't know about should, but it might.

[ggm1960]

Further to what has been suggested also try opening the file, delete all chunks, create a new one, create and record enable a MIDI track and hit play. If your problem doesn't occur then you know the issue exists in one (or more) of your chunks. Delete half of them at a time until you find out which one it is. Good luck.

PS: Obviously don't Save anything here while you are troubleshooting. I'm sure you knew that, I just don't want to be considered the devil if things went South this way.

Adding a new chunk was something I'd wanted to try and did that tonight. Without removing any of the current sequences, I created a new one and added several MIDI tracks for my external devices and the patch change problem was not occurring. Next I'll continue with your suggestion in hopes of finding the bad chunk(s).
I also want to investigate that Remove Default Patch command as also suggested.

I think I'll be able to get to the bottom of it and I appreciate the great suggestions!

[MIDI Life Crisis]

If it is coming from a track, then check every track in the EVENT LIST and if there's a patch change, you'll find it.

[ggm1960]

Don't use that project! Seriously, start a new one, and LOAD the chunk(s) and that should cure you - well, I don't know about should, but it might.

This is basically the same thing MOTU tech support is recommending and I'll be giving it a try real soon. Thanks!

[FMiguelez]

I don't know about the cc's, but the patch change might be because a default patch is in effect for that track/device. See here:
http://www.motunation.com/forum/viewtop ... 26&t=46142
"Top right hand corner of Tracks Overview window. Drop down menu, Clear Default Patch."

+1

I'd definitely try that. As long as you don't clear that one, DP will insist on reverting to it.

If that doesn't work, you can use the View Filter and hide everything but Patch Changes. This should make it awfully clear to see where the culprit is hiding.

[ggm1960]

Well I've finally figured this out it seems and yeah, it's weird. In this live projects sequences there are always at least six MIDI tracks, three for processors (Lexicon MX400, Antares AVP-1, Digitech GSP1101) that just get default patches and sometimes patch changes during songs and then there are three MIDI instruments (Korg TR88, Roland XP30, Roland Fantom XR) which can have 0, 1 or more tracks playing.

All the MIDI devices are connected through a MTP AV unit, each on it's own port and each unit is set to respond on a different MIDI channel yet somehow the default patches of the processors are affecting the instruments!

So to correct the problem I've been having I can disable the processor tracks but for a more permanent fix it looks like I can clear the default patches on those tracks and sorta restart with them.

It's not a huge deal since I don't use this project for live performances anymore and the patches have been changed/rearranged in the time since but this is still a handy project to sequence songs I'm learning to play for bands and, of course, there's always the chance that I may use this setup again in the future for live performance again.

I appreciate all the helpful suggestions, this is a great forum!

[Buzzy]

Yup, lots of knowledge here. And a mature crowd.

Glad it all worked out.