[Ardour-Dev] let's talk about MIDI regions
edwsaintesprit at hotmail.com
Fri Mar 3 16:48:37 PST 2017
One idea would be that every "empty" midi track gets a default, undeletable background region that is infinite in length (or at least, spans the whole session, time-wise,and resizes itself when the start/end markers are moved).
1) make midi editing less disturbing for new users (no need to create a region first)
2) keep all the good aspects of region editing (linked regions, etc...) as new regions could still be overlaid over the "background" region
Recording while on "edit" mode could rewrite the content of the active region, and create a new region outside edit mode. Or, the MIDI tracks could have (like audio ones) their record mode set to Normal/Tape/Non layered. Or simply (but disruptively) create a switch in the track header "destroy/overlay". Or create a secondary rec-arm that is a "rec destructively".
It may solve the cons you mentionned, but not the illegal overlapping notes... But we keep the consistency between audio and midi AND full compatibility with previous Ardour versions.
De : Ardour-Dev <ardour-dev-bounces at lists.ardour.org> de la part de Robin Gareus <robin at gareus.org>
Envoyé : vendredi 3 mars 2017 16:31
À : ardour-dev mailing list
Objet : Re: [Ardour-Dev] let's talk about MIDI regions
[re-arranged to avoid top-posting]
On 03/03/2017 04:17 PM, nick mainsbridge wrote:
> On 3 March 2017 at 21:02, Paul Davis <paul at linuxaudiosystems.com> wrote:
>> one idea that is in the air for Ardour 6.0 is to move away from the idea
>> of MIDI regions entirely. in the simplest terms:
>> makes editing MIDI more like editing audio
>> allows easy copying of motifs, themes, drum fills etc. without having
>> to select stuff
>> greatly complicates the basic nature of MIDI tracks
>> hard to overdub MIDI - does this create a new region, or edit an
>> existing one
>> MIDI CC data ("automation") always needs a region, somewhat
>> MIDI data is much more discrete than audio, and can be easily
>> selected, then
>> copied, moved, pasted etc.
>> without regions, a MIDI track would just be a single context for MIDI
>> data. each new overdub would add more MIDI data to that context (possibly
>> replacing or altering existing notes in the case of MIDI-illegal note
>> overlaps). edits would be done via cut-n-paste. MIDI CC data ("automation")
>> could be added to a track at any point.
Making this even more destructive strikes me as backwards. Now it's not
only regions that are edited destructively but whole tracks.
It would really be nice if midi editing would be non-destructive. One
possible way: write a new .mid for every change-set (or on every
> i would like to add:
> - the audio/midi similarity extends to recording also
> e.g. ad hoc take management is simple (mute the last take of
> audio + midi recording and go again)
> - lock to audio / music is al least partially possible
> - regions may be positioned at sample resolution
> - most anti-region arguments look like decisions that are yet to be made.
> - solving 'MIDI CC data ("automation") always needs a region' seems
> than removing complexity (are we overwhelmed by this?).
> - regions are difficult to get right.
select 2 linked regions. one starting at 1|0|0, one at 3|2|123. quantize
to grid. It's ambiguous what should happen and it gets worse if there's
a tempo/meter change in between.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ardour-Dev