MU.LAB 2 Test F

[robenestobenz]

Thanks for such a thorough response: I'll get back to you with mine tomorrow. I realise there was a was quite a bit I could have picked up from the manual. Sorry for that - I did skim through it. I'll look more thoroughly before putting out the questions next time.

[MuTools]

The program's quite talkative

In your opinion: Are there any places where MU.LAB should shut up instead of talk?

[Oxygenee]

Well, the export in this musession also fails to produce a valid MIDI file if I unmute a track containing MIDI data.

I unmuted the second track of the session you sent me, exported that as a midi file, and re-imported that in mulab. Looked fine to me.

Could you please give me more details where it goes wrong?

I have unmuted the 5th track and exported a MIDI file, but I also tried the 2nd track as you did, however the results are similar:

In Quicktime the file plays.

In other sequencers, the file either doesn't load or only loads the very first note(s).

If imported into a new session, the MIDI files created from the session I sent you show that behaviour:
The track that was unmuted is correctly shown as MIDI data, but additional tracks are being created so as to match the number of tracks in the Musession the MIDI file was exported from and the tracks that were muted there are filled with short sequence parts. - This should not happen.


See you!

[MuTools]

I have unmuted the 5th track and exported a MIDI file, but I also tried the 2nd track as you did, however the results are similar:

In Quicktime the file plays.

In other sequencers, the file either doesn't load or only loads the very first note(s).

1) Also note that if parts are selected, only the selected parts are written to the MIDI file. So make sure there are no selected parts if you want to export all (unmuted) parts.

2) I've rechecked exporting a midi file, and loaded that into EXT, FLStudio, Live and Reaper. All went fine, except for reaper which said 'offline', but don't know what that means.

If imported into a new session, the MIDI files created from the session I sent you show that behaviour:
The track that was unmuted is correctly shown as MIDI data, but additional tracks are being created so as to match the number of tracks in the Musession the MIDI file was exported from and the tracks that were muted there are filled with short sequence parts. - This should not happen.

Next version has finetuned behaviour regarding importing/exporting empty tracks.

[Oxygenee]

I have unmuted the 5th track and exported a MIDI file, but I also tried the 2nd track as you did, however the results are similar:

In Quicktime the file plays.

In other sequencers, the file either doesn't load or only loads the very first note(s).

I've rechecked exporting a midi file, and loaded that into EXT, FLStudio, Live and Reaper. All went fine, except for reaper which said 'offline', but don't know what that means.

Thanks for checking: I tested it in Reaper and Aria Maestosa (a simple MIDI-only sequencer) and as it didn't work well there, I assumed it wouldn't work elsewhere. - So, you found out that it works in some sequencers - I am curious if it will work in Reaper and Aria Maestosa when you have told MuLab only to export tracks into MIDI-files that are not muted!


See you!

[MuTools]

I already tested that here, and still 'OFFLINE' in reaper. Strange. Does anyone knows what that 'OFFLINE' thing means in reaper?

[Oxygenee]

I don't really know about OFFLINE in Reaper, but I couldn't set a MIDI file exported from MuLab as previously reported and then imported into Reaper to ONLINE. OFFLINE maybe means that reaper somehow does not (in this case maybe cannot) access the file on the hard drive, but that's just a guess.