Or it could easily be operator error, but either way this one has me stumped. I'm using DP9.01 on OS 10.10.5
First, I do I understand the difference between the "Default Patch" field, and the "Patch" field in the TO window.
What's happening is that anytime I assign a MIDI track to a specific source, it comes up with a patch already inserted in the "Patch" field, but only for that device. If it was on my own machine, I wouldn't care. But it's in a EM lab in a college, so it's being used by students.
We have a half dozen different hardware synths connected through a MIDI express 128, all set up in the Audio MIDI setup. I open a new file (whether from a template, or "empty"), and create a new MIDI track. If I assign the output of the MIDI track to anything in the lab (Fantom G on multiple channels, Triton, Nord, Modular, TR8, etc.), the "patch" field in the tracks window stays blank (nothing filled in). But the moment I assign the MIDI track to the TD10 (which we use on 4 MIDI channels), a patch number suddenly appears in the "patch" (not default patch) field. And just FYI, the MIDI out from the TD10 is not physically routed to anything. The main TD10 channel (for drum sounds) is channel 10, and that always comes up Patch 21 (in the patch field). And the other 3 "parts" (MIDI channels) in the TD10, whenever selected, always cause the "patch" field to go to a certain number (different for each of the 3 channels, but always consistent).
Obviously, it doesn't actually affect the functionality (because unlike the "default patch" field, the PCs in the "patch" field do not automatically send), but it does cause confusion. Is it something I'm doing wrong? Any help is appreciated, thanks, Scott
Patch field in tracks window odd behavior
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.