when trying midi export, I encountered some problems:
1) after midi export and immediate re-import (merge mode, to check export file),
some tracks are empty.
2) when merging all parts of a track then export seems to be ok, no empty tracks afte re-import.
3) when trying to load exported midi file in other application, it is not possible, "improper midi file" errors (e.g. mixcraft or melody assistant).
Any explanation or hints ?
Must I add some midi standard events using list editor prior to export ?
(e.g. inserting a program change to choose an GM instrument? )
Only prep I've done is assigning each track a separate #channel.
questions regarding midi export
-
- KVRist
- Topic Starter
- 152 posts since 15 May, 2009 from Germany
further information:
error message when trying to import midi reads:
"can't find Mtrk".
Might be that size information of predecessor chunk is wrong, so that next Mtrk label not at position as computed ?
error message when trying to import midi reads:
"can't find Mtrk".
Might be that size information of predecessor chunk is wrong, so that next Mtrk label not at position as computed ?
Everything should be made as simple as possible, but not simpler!
-
- KVRist
- Topic Starter
- 152 posts since 15 May, 2009 from Germany
further analysis of a midi file I've created as example
(based on a correct midi file imported and modified):
In the MThd chunk it says "6 tracks", but then in the remaining file there are 2 MTrk chunks only. When correcting it with an hex editor to "2", then the file can be opened by an other daw (showing one track, but when creating the midi export out of Mulab it should be 6 tracks)
I'll stop here, might be there is some bug in midi export code.
(based on a correct midi file imported and modified):
In the MThd chunk it says "6 tracks", but then in the remaining file there are 2 MTrk chunks only. When correcting it with an hex editor to "2", then the file can be opened by an other daw (showing one track, but when creating the midi export out of Mulab it should be 6 tracks)
I'll stop here, might be there is some bug in midi export code.
Everything should be made as simple as possible, but not simpler!
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
I've exported the Demo.Musession to a MIDI file.
Now when i import this MIDI file in Mixcraft, all seems fine, i don't see a problem.
FYI: MU.LAB does not 'skip' tracks that only contain audio parts or that are fully muted. Such tracks will appear as empty tracks in the MIDI file. Which is ok imho because it more accurately represents what you have exported than when we would skip such tracks. It's a detail.
When i re-import that same exported MIDI file in MU.LAB, there is a little issue:
MU.LAB saves the Start-Loop-End info as markers in the MIDI file, which is ok.
But when importing this MIDI file, MU.LAB also uses this info to set the Start-Loop-End of the imported MIDI part which is less ok because the MIDI file contains all events for the full track, not only of a single part.
So in fact the Start-Loop-End markers should be ignored on import, i think.
So how to bypass this problem: When you export a MIDI file from MU.LAB and re-import the same MIDI file in MU.LAB (not sure why one would do so), then edit the imported sequence parts, right-click the End locator and do "Remove End".
This will make the parts play all events.
Now when i import this MIDI file in Mixcraft, all seems fine, i don't see a problem.
FYI: MU.LAB does not 'skip' tracks that only contain audio parts or that are fully muted. Such tracks will appear as empty tracks in the MIDI file. Which is ok imho because it more accurately represents what you have exported than when we would skip such tracks. It's a detail.
When i re-import that same exported MIDI file in MU.LAB, there is a little issue:
MU.LAB saves the Start-Loop-End info as markers in the MIDI file, which is ok.
But when importing this MIDI file, MU.LAB also uses this info to set the Start-Loop-End of the imported MIDI part which is less ok because the MIDI file contains all events for the full track, not only of a single part.
So in fact the Start-Loop-End markers should be ignored on import, i think.
So how to bypass this problem: When you export a MIDI file from MU.LAB and re-import the same MIDI file in MU.LAB (not sure why one would do so), then edit the imported sequence parts, right-click the End locator and do "Remove End".
This will make the parts play all events.
-
- KVRist
- Topic Starter
- 152 posts since 15 May, 2009 from Germany
Jo,
I'll send you an eMail with an example Mulab File where midi export results in wrong midi format.
When re-importing the file Mulab seems to be more tolerant than other daws.
I'll send you an eMail with an example Mulab File where midi export results in wrong midi format.
When re-importing the file Mulab seems to be more tolerant than other daws.
Everything should be made as simple as possible, but not simpler!
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
IMO, if MU.LAB is going to export events that only have meaning to MU.LAB (i.e. not General MIDI / standard MIDI File spec), on import, those events should recreate exactly what was exported -- otherwise there is no point exporting them and potentially confusing other MIDI File processors. 
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
MU.LAB uses SMF markers for that, so it's all 100% compatible.pljones wrote:IMO, if MU.LAB is going to export events that only have meaning to MU.LAB (i.e. not General MIDI / standard MIDI File spec), on import, those events should recreate exactly what was exported -- otherwise there is no point exporting them and potentially confusing other MIDI File processors.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Eggu and i emailed about a possible issue with exporting MIDI files, but we have different results, so it might be a system dependent issue.mutools wrote:Thanks for the mail, well received.
I'll reply per email, going into technical details.
So i would like to ask: Is there anyone else who's having problems with importing/exporting MIDI files in/from MU.LAB 2.6.x?
-
TheGuysanIdiot TheGuysanIdiot https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=213066
- KVRist
- 308 posts since 10 Aug, 2009 from United Kingdom
Jo
Not really a problem more of an observation about MIDI import/exports. As you know I was mainly a Cubase SX2 user before MU.LAB, but now I am a fully converted MU.LAB chap. I have exported all my songs out of Cubase SX2 via MIDI and imported them to MU.LAB and all is well.
Generally speaking when importing MIDI files to any DAW the only problem I have experienced over the years between DAWs of many kinds is this:
Just say I had a number of notes on C3 each following each other, when imported to another DAW the "gap" between each consecutive note may or may not be recognised so only the first C3 note would play and the rest of the C3 notes would be silent.
Cubase had a setting to put a couple of "ticks" between two notes of the same value as in this case C3 note followed by another C3 note. My general understanding of MIDI is that a tiny "gap" between notes is needed so that a sequencer can trigger each note separately.
I was wondering how MU.LAB was configured to handle this tiny "gap" between notes.
What I have also noticed in MU.LAB is this:
Set grid to 1/16 and then add notes with pencil tool then use the list editor you can see all notes are "299" long.
If I then select all these notes and quantize lengths using 1/16 the notes are now "300" long.
This is just a general question of how MU.LAB is configured. Hopefully you can understand what I am trying to explain.
OZ
Not really a problem more of an observation about MIDI import/exports. As you know I was mainly a Cubase SX2 user before MU.LAB, but now I am a fully converted MU.LAB chap. I have exported all my songs out of Cubase SX2 via MIDI and imported them to MU.LAB and all is well.
Generally speaking when importing MIDI files to any DAW the only problem I have experienced over the years between DAWs of many kinds is this:
Just say I had a number of notes on C3 each following each other, when imported to another DAW the "gap" between each consecutive note may or may not be recognised so only the first C3 note would play and the rest of the C3 notes would be silent.
Cubase had a setting to put a couple of "ticks" between two notes of the same value as in this case C3 note followed by another C3 note. My general understanding of MIDI is that a tiny "gap" between notes is needed so that a sequencer can trigger each note separately.
I was wondering how MU.LAB was configured to handle this tiny "gap" between notes.
What I have also noticed in MU.LAB is this:
Set grid to 1/16 and then add notes with pencil tool then use the list editor you can see all notes are "299" long.
If I then select all these notes and quantize lengths using 1/16 the notes are now "300" long.
This is just a general question of how MU.LAB is configured. Hopefully you can understand what I am trying to explain.
OZ