Metro Outputs, ports, and program changes

[clord]

Am teaching group of college students using Metro. Can't seem to get consistent results in having their bank select/program change messages take effect, even when the info is visible in the Events/Graphic displays.

Can you offer a safe way to make sure all MIDI information affects the final output? We're trying a mix of Change Ports, setting outputs in the Tracks window (using the popup port menu with that), and applying the Options..Channel command, resetting everything on a given track to the same channel.


I probably need a clearer explanation of ports vs. Metro Outputs too - I thought I got it from the online manual until I read that the Edit Port... popup option doesn't apply to Metro Outputs...

For example, when the Output in the Tracks window is set to, say, Port 1 (no channel number attached), can/will the MIDI signal go to the channel(s) assigned in the MIDI messages (Event window)? I'm assuming setting that track to Port 1-3 will override the MIDI messages and send that track to channel 3, right?

So how does the Change Port option interact with all this? When is it necessary to set all the channel info on a track to the same channel?

We're confused, as I'm sure this message reveals! The simplest safe method for getting everything on a track to work on a specific channel is what we need.

Thx, chuck

[Jerm]

I probably need a clearer explanation of ports vs. Metro Outputs too - I thought I got it from the online manual until I read that the Edit Port... popup option doesn't apply to Metro Outputs...

Okay it does sound like your a little confused between ports and MIDI channels. A port is an output destination such as a device. MIDI devices accept up to 16 different MIDI channels. When a track in metro in the tracks window reads something like Port:DEVICEA then the channel information is specified by the data in the track. If you use MetroOutputs, which I recommend, then the channel information in the track data is overridden by the MetroOutput's channel. In this case the MetroOutput would be something like DEVICEA-1. This means that all MIDI data on the track will be destined for DEVICEA with a MIDI channel of 1.

For example, when the Output in the Tracks window is set to, say, Port 1 (no channel number attached), can/will the MIDI signal go to the channel(s) assigned in the MIDI messages (Event window)?

Yes. This is what happens.

I'm assuming setting that track to Port 1-3 will override the MIDI messages and send that track to channel 3, right?

Yes. Assuming that you mean Port-1, through Port-3, which are 3 distinct and unique MetroOutputs.

So how does the Change Port option interact with all this?

If you would like to change the output of a document from DEVICEA to DEVICEB you would use change ports. This is most likely used when tranfering documents between two different studios. So I don't think this is what you are looking for.

When is it necessary to set all the channel info on a track to the same channel?

Never. If this is what you want then it is a lot easier to simply assign a MetroOutput to the track. MetroOutputs are created using the 'Modify outputs and busses' command.

The simplest safe method for getting everything on a track to work on a specific channel is what we need.

To recap, the best way to do this is to (if necessary) go to 'Special-Modify outputs and busses', create the MetroOutputs you need (save preferences to make it the default), then assign the specific output to the track.

Hope that helps!

[Scoot]

Say you had ports for quicktime sounds (internal), audio and an external synth as standard.
If you were to remove the synth from the setup you may get a dialog on startup to change ports basically saying - I can't find what these ports belong to.......what do you want to connect them to in the meantime?
It pays to have your setup consistant on startup to avoid such things.

Like Jerm said - decide which ports you need and save it to the prefs and it will open that way next time.

What exactly are you doing?
Are you having problems with drums?
(drums need to be allocated to port 10 othewise you may hear a piano instead of a drumkit).

As far as program changes consistancy:

- go into the graphic editor
- go to the 'notes' popup and select program change
- select all
- delete
- choose the instrument you want to use in the graphic editor.
(I think changing it in the tracks window only gives you a temporary change......or something).

This removes any program changes that may have previously been in the document and lets you use the pgm. you want.


See if someone has placed in pgm changes and you have 'chasing' on program changes in the setup menu, as you play the file, metro will switch instruments depending on where you are in the music.

As an example open a piece of midi and with the pencil tool click on a different program change at bar 5, 10, 15
Play the whole piece and notice the instrument changes.
Then play an area in 1-4 , 6-9, 11-14, 16-... with pgm change chasing off and then on and see what's different.

[almapercus]

May I suggest to put some graphic explanation in the manual to figure it out?

Maybe it could help, IMO. I've yet to understand all the possibilities.

[Scoot]

There are several graphical walk thrus on site here....and one old one recently commented in which talks about outputs and covers mostly everything about adding a new device and giving it outputs.

http://sagantech.com/metroforum/viewtop ... 33&start=0


One sticking point is the word PORT in the graphic editor popup and the tracks window........unless this could become OUTPUT....or does PORT have a different meaning here?

[Jerm]

the word PORT in the graphic editor popup and the tracks window........unless this could become OUTPUT....or does PORT have a different meaning here?

Yes it means output. Even though a port can be thought of as input or output , in this case you are dealing with the output column of the tracks window and edit-original, so it means output.

Think of the 'original-port' destination as a multi-output because it enables the capability of having one track output to multiple MIDI channels!

[cornutt]

One other thing to remember: Bank select isn't very well standardized, particularly with older devices. Some devices use only the Bank Select LSB (controller 32); some use only the USB (controller 0); some require both to be sent even though the USB is always 0. I've got a Lexicon MPX-500 which requires some amount of time (I usually leave it about 100 clocks) after a Bank Select before it will accept any other MIDI data. And, then there are some older devices whose bank select messages are totally non-standard (usually a sysex of some sort).