Virtual Instrument Wonkiness With MIDI Tracks(Solved)

[Luke]

I have several virtual instruments that change the preset I've chosen every time I hit stop and return back to the beginning of the song when working with MIDI. For instance, let's say I have Arturia's Minimoog assigned to a specific MIDI track and I have selected "preset x." Upon starting playback again it changes on it's own to "preset z."

Anyone know how to stop this from happening? And please forgive my ignorance as I am just a "pup" with all this and this may be "MIDI 101."

And I suspect I may get my first

[terrybritton]

And please forgive my ignorance as I am just a "pup" with all this and this may be "MIDI 101."

Actually, that is a MIDI 102 question. I'll go get the MIDI 102 person - I'm the MIDI 101 guy.

There are no stupid questions - only stupid answers.

I'll pull up my copy of that plugin and see. First, are you getting the correct preset number position-wise but in the wrong bank?

Second, have you set the preset at the top by renaming it? That sometimes helps. But that might be a perfect example of a stupid answer, so I'd wait for the MIDI 102 person.

Terry

[buzzsmith]

I'm not the "MIDI 102" guy but I'll jump in.

By any chance, do you have a "Default Patch" showing on the Minimoog MIDI track? It could be the actual name of the patch or something like "Patch 008". If so, then whenever you hit Play the default patch is sent to the instrument.

You can clear the Default Patch or replace it with the patch that you actually want.

Buzzy

Sent from my iPad using Tapatalk

[stubbsonic]

The only time you would want or need a default patch or any patch change at all is if you plan to change the patch at some point during the chunk (sequence).

As Buzzsmith mentioned, clearing the PATCH and DEFAULT PATCH is important. Here's the trick though. Once something is selected, can't get rid of it directly. It's a MOTU oversight. The only way I've found to clear the default patch is to momentarily change the output assignment, then change it right back. That should clear it.

The next thing to look at is whether your track actually has a program change in it. You can select the track in question, and type SHIFT-E (to open the event list), scroll through and see if there are any patch change messages in there and delete them. A view filter might be "hiding" the program change messages-- so you can go to the SETUP MENU/VIEW FILTER... and make sure that box is ticked.

Finally, you can look at whether something in your controller or COMMANDS is transmitting a program/patch change when you do something on your controller. I won't go into details about that right now, but you can try the above things first to see if any of those sort it.

Let us know how it goes.

[Luke]

Thank you gentlemen. I am going to try your suggestions later tonight and will report back what I find. Could be pretty late though. I am a Night Owl.

[cuttime]

The next thing to look at is whether your track actually has a program change in it.

This. I've found Public Domain and Internet MIDI files rife with extraneous patch changes that usually need to be scrubbed before the file is usable. Check this out:
viewtopic.php?f=26&t=62462

[HCMarkus]

The only way I've found to clear the default patch is to momentarily change the output assignment, then change it right back. That should clear it.

There is a "Clear Default Patch" command in the Tracks Overview Mini Menu. Works on the selected MIDI Track

[stubbsonic]

Ah! Thanks! I always was looking for "none" in the list which would be more intuitive, IMHO.

[Tonio]

yup, I always forget that menu too

[Luke]

Just a check in as I feel I've been somewhat remiss after receiving everyone's suggestions. I haven't got an opportunity to try anything out yet and that's why I haven't reported back. As soon as I do, I will let everyone know what transpired. You took the time to offer assistance and I will do the same. Until then, thank you again.

[MIDI Life Crisis]

If the default patch isn't the issue that check your event list for a patch change. Also, there a preference somewhere (I'm away from the studio but will check later) where you can check "send patch changes" or something like that.

Whatever you do DO NOT but do open it and search for patch change and you should find an answer or two.

[Luke]

Mystery solved thanks to the great folks here! The fix was going to the "Event List" and sure enough in the very beginning is a ton of convolution. And on the 8th line of 1/1/1000 (forgive my ignorance if that's not how you say it ) was a line that read "Patch 28." So I counted the actual Patch I wanted (67) and replaced 28 with 67. Problem go away

Thanks again gentleman and sorry for taking so long to let you know what transpired. Been juggling kittens (thank you Steve Martin!) lately and just got a chance to investigate.

[terrybritton]

Good to hear! These little things could make one's hair turn gray, eh?

(I have different excuses - my grey (UK version) hairs pre-date my involvement with DP...)

Terry

[stubbsonic]

The only time I ever use Patch Change messages these days is when I'm controlling my external K2500R. Seems like the DAW is more than capable of storing all the VI settings and presets without my having to bother with PCs.