Export MIDI file with notes & CC data
-
- KVRist
- 219 posts since 3 May, 2016
I have a MIDI track with notes & CC data (please see attachment). When I use Project-->Export MIDI file, I only see the note data when I import into Ableton Live or back into MuLab. This happens even if I specifically select all the tracks and subtracks I want before exporting from Mulab. Please advise.
Thank you,
d. vyd
Thank you,
d. vyd
You do not have the required permissions to view the files attached to this post.
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
File->New project
Add instrument, Factory, Bass, Aliasing
Add subtrack, automation, LFO Freq
Add subtrack (to the automation)
Draw in parts on all three tracks
Edit the Aliasing bass sequence and add a C3 note
Edit the LFO Freq automation and draw a simple curve
Edit the third sequence; in the controller lane, select a MIDI CC (e.g. 8 - Balance) and draw in some data
Export to a new MIDI file.
Quit MuLab (important), reload and start a new project and create the three tracks as before but this time don't draw in the parts.
Now import the MIDI file.
Hm. No, the note data is not reliably imported if it's actually there in the export.
Without quitting MuLab, sometimes I was getting the VST automation "imported" where I think it was simply copying the existing sequence data -- possibly the same for the note data... I checked in Reaper, too. It sees the VST automation track header but only sees MIDI CC data, no MIDI note data.
Add instrument, Factory, Bass, Aliasing
Add subtrack, automation, LFO Freq
Add subtrack (to the automation)
Draw in parts on all three tracks
Edit the Aliasing bass sequence and add a C3 note
Edit the LFO Freq automation and draw a simple curve
Edit the third sequence; in the controller lane, select a MIDI CC (e.g. 8 - Balance) and draw in some data
Export to a new MIDI file.
Quit MuLab (important), reload and start a new project and create the three tracks as before but this time don't draw in the parts.
Now import the MIDI file.
Hm. No, the note data is not reliably imported if it's actually there in the export.
Without quitting MuLab, sometimes I was getting the VST automation "imported" where I think it was simply copying the existing sequence data -- possibly the same for the note data... I checked in Reaper, too. It sees the VST automation track header but only sees MIDI CC data, no MIDI note data.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Ok i had a look. Currently only the selected and non-muted parts are exported. Does that explain what you encountered? Anyway, maybe it's a bit confusing that only the selected non-muted parts are exported. I guess that if the user wants to exclude certain tracks/parts from the export to MIDI file, he can (temporary) mute these tracks/parts as muted tracks/parts are not exported. So i'll change this so that simply all non-muted parts are exported, independent from the selection, that will be more straightforward functionality.
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Yes, it gives no indication that anything is being excluded. I think it should also pop up a message if it finds anything is muted (that had anything useful to export), either before or after, to alert the user.
