PT Logic

Logic Pro Saving LogicX files as midi ...some questions

LogicChallenged

LogicChallenged

Logician
Having trouble with saving files (tunes ) as midi.
Using export> Save selection as midi file.
I want to end up with a saved midi file, with individual tracks, ie format 1
I highlight all, the do the save.
Works ok with "normal" tracks, ie, if I record tracks .
But when I copy and drag a track, for doubling purposed, it seems the region is not recognized as a new midi track. I read on an Apple info sheet (may be old, pertain to Logic 9) that you have to prepare midi regions for export, and go to MIDI>Normalize Region Parameters. But that does not seem to do anything.

Also , issue with loops. I try Apple drum loops (green/midi) , expanded to cover entire tune.
Also have tried some Groove Monkee loops.
Both work fine on Logic, but won't export as midi with the export process.
Once again, my Apple info sheet says to convert any loops into regions, ,( Convert>Convert loops to regions, ) but when I hiighlight the loop track, and go to Convert, the choices are greyed out.

Basically I'd like to make my 2 track tune, + loop drum track, into a 5 track (or channel) midi file,
with the first two tracks doubled, to fatten up sound, and a drum track on channel 5.

Also, not sure whether to check off or not: : Prefs>general>project handling> "Export midi file....saves single midi regions as format 0 ". That's a bit confusing.

Almost there, but something isn't working.
Any suggestions very much appreciated.

Bud
 
Sort by date Sort by votes
Thx for answer.
But...there is no obvious choice in prefs between format 1 and format 0
All I can find is: Prefs>general>project handling> "Export midi file."...saves single midi regions as format 0 ".
Seems to only address saving one track at a time.
What about multiple tracks??
B
 
Upvote 0
See if this helps....
Type 1 files contain separate information for each track. For a Type 0 file, however, all the tracks are merged into a single track, although MIDI channel information is still retained. When a Type 0 file is loaded into Logic, it will take each channel’s information and put it on a separate track. So for a typical sequence with one track per MIDI channel, it will normally not matter if the sequence is saved as Type 0 or Type 1. But if your source sequence has several tracks assigned to the same MIDI channel (for example several drum tracks playing the same program on the same channel, but with an individual drum sound on each track), then it is best to export it as a Type 1 file. If exported as Type 0, all tracks assigned to the same channel will be merged into a single track when the .MID file is loaded.
To export as a Type 1 Midi file - the option in preferences should not be checked ( correction to my thread above after I looked at the wording once in front of Logic).
 
Upvote 0
Hey , thx for answer. Cleared up a couple of things I did not know.
Actually solved my issue, thru the suggestion of a friend.
Went into event list of each track, and manually changed the midi channels, ie, 1.2.3.4.5.
Then saved as midi file.
Now my tunes (midi files) transfer correctly to outside sequencer... a yamaha cvp clavinova.

Somehow I had assumed that Logic would assign a midi channel sequentially to each track automatically,,,,,,but now realize that after 16 tracks, this idea would fall apart. My bad.
Looks like all tracks start out as midi #1, then you have to change like above for a multi track file.

Question: what is the function of the midi channel choice in the drop down menu in the tracks area of inspector?

thx.
Bud
 
Upvote 0
Great Question.....
In the context for which you are asking..... The midi channel in the track inspector specifies the output channel (for any event on the track ) that is being played back. All data is channelized to whatever midi channel is specified in that parameter.
so if a region has one or more midi channels and is played when the midi channel track parameter is set - then everything is being directed to that channel on output.

Let take a specific example.
If you have events in regions on track xyz and you have the track midi inspector parameter set to channel 10 - all data on track xyz will play on channel 10 regardless of what the individual events are set for. ( if that's sound the way you want it great, )... however if you then export the midi regions - they will export based on the event channels in the regions which is not channel 10 - hence you get undesirable results.

The solution is that when everything is playing correctly. Highlight the tracks and press Control N, or from the midi menu apply parameters permanently. This will change all regions events to the channel currently assigned in the track inspector - hence ensuring when exporting and played back externally - if will send midi data to the same channel you had in your track inspector.

So to get this all to work you only missed one key stroke.....
1/ Make is sound correct in Logic on your computer.
2/ highlight the tracks and press control N
3/ export your tracks.

So that parameter is the final stage in determining what channel the midi events are reassigned, associated or channelized through prior to sound generation. Making those channelization permanent by the control N option - ensures that is the case only at the individual note event level required for a midi export to work properly on an external device, DAW etc.

Also note that when you have the midi channel set to "all" you are effectively turning channelizing off, meaning all midi notes/channel assignments passed unaltered from the midi region to the external destination as specified by the individual event in the region

Whooo !!! How was that?
 
Upvote 0
Whooo....that was great. Lots of good info.
So, I followed it all , and basically discovered that the control N command described is the shortcut for the
Function> Midi Region Perameters> Apply all Perameters Permanently" .
It does a quicker job of changing all midi #'s in the event list. My version is cumbersome.

But now I'm hung by the "Insert Midi Instrument settings as Events, command.
It seems that would put a MSB and LSB event at the top of list, describing the chosen patch, and make that part of the midi data stream, ie, make the remote sequencer jump to a patch ( tho, maybe not the correct one)
But the command does not seem to do this. Am I missing another key stoke.?
I kinow the MSB etc insert idea works, because I've done it manually (cumbersome) with some earlier projects.

I have two books, Logic Pro X for dummies, and the Edgar Rothermich Logic Pro X book....both excelent. But neither seem to get down too far into the Midi weeds, and describe procedures like above. Maybe Rothermich's book, but I can't find it.
My friends who are into Logic are mostly audio dudes, and only scratch the midi surface a little bit.
Seems like an entire book addendum for deep midi-freaks would be valuable

Thanks for help,
Bud
 
Upvote 0
Back
Top