View Issue Details
|ID||Category||Date Submitted||Last Update|
|0003490||features||2010-10-05 07:22||2012-05-28 00:21|
|Fixed in Version|
|Summary||0003490: Advanced MIDI Export|
|Description||This is a turning point posting for me as it genuinely feels like this will be my final feature request for Ardour 3.0. We essentially need two options for MIDI import I think- export selected regions as SMF and export all MIDI regions as SMF. Menu placement such as whether or not these two get bundled under one Session -> Export -> Export to MIDI files menu or not I'll leave you to decide.|
|Additional Information||As stated- I see this as likely my final feature request for 3.0- sorry its late. If Carl has fixed the display of MIDI tracks when recording (potentially fixing http://tracker.ardour.org/view.php?id=3229 ) now then as far as MIDI bugs go there only a few I know of now, all listed on Mantis already 'cept for maybe not the one about the playback of MIDI regions that have been moved/ are being moved after pushing play but las knows about that one.|
The boy who cried beta (soon)
|Tags||No tags attached.|
||implementers note: this should be easy to do, since its identical to the "clone" operation but with a user-specified path for the file.|
||basic single-region export implemented in svn.|
Single region export is a bit of a non-feature as all the MIDI region smfs are readily available in the session folder anyway.
What I was requesting here and I'm sure what many people have expected/ will expect to see in 3.0 inc. most likely the person who flagged its absence in the b4 release comments is the ability to export either all the MIDI regions in the session or just the currently selected regions into one .mid
To be honest its not a feature I'll be using that often but you would expect this as a given in any (semi)pro level MIDI sequencer worthy of the title, even if it is a first stable release.
the export feature allows you to export a region that is a subset of an SMF file.
3.0 will absolutely not have any feature that represents consolidation/bounce of existing MIDI into a single region/file.
the person who pushed me to do this by asking about it on the forums reported that single region export is enough for their needs.
|2010-10-05 07:22||danboid||New Issue|
|2010-10-05 11:18||cth103||cost||=> 0.00|
|2010-10-05 11:18||cth103||Target Version||=> 3.0-beta1|
|2010-10-19 17:08||paul||Note Added: 0009281|
|2010-10-20 01:40||cth103||Status||new => assigned|
|2010-10-20 01:40||cth103||Assigned To||=> cth103|
|2011-03-01 02:43||cth103||Assigned To||cth103 =>|
|2011-03-01 02:43||cth103||Status||assigned => acknowledged|
|2011-10-24 23:33||cth103||Target Version||3.0-beta1 => 3.0|
|2012-05-24 17:10||paul||Note Added: 0013291|
|2012-05-24 17:10||paul||Status||acknowledged => feedback|
|2012-05-25 17:00||danboid||Note Added: 0013296|
|2012-05-25 18:11||paul||Note Added: 0013297|
|2012-05-28 00:21||cth103||Target Version||3.0 => 3.X|
|2012-05-28 00:21||cth103||Summary||MIDI Export => Advanced MIDI Export|