<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;" dir="ltr">
<p>Hi,</p>
<p><br>
</p>
<p>I (respectfully !) disagree with using a separate context for MIDI editing for numerous reasons :</p>
<p>- it disrupts the workflow and decontextualizes the editing (i.e. how to align with an audio segment ?)</p>
<p>- the space has to be found in Ardour's window, replacing something (obviously) probably useful</p>
<p><br>
</p>
<p><br>
</p>
<p>As is, the midi system is a sequencer that can turn into an editor at the click of a button, which is particularly powerfull. I agree there are some oddities, but a disruptive modification would (imho, again) simply dumb down the system to achieve an uncertain
result, based on what's done in other editors.</p>
<p><br>
</p>
<p>I think the main oddity is the constant switch between the editor and sequencer modes with the edit tool. Maybe that could be solved as:</p>
<p>- clicking on an empty zone of the canvas creates a region</p>
<p>- double clicking on a region allows to edit it (instead of showing the region properties)</p>
<p>- clicking anywhere outside the region (be it on the same track or not) switches back to grab mode.</p>
<p><br>
</p>
<p>This workflow is close to what's used in e.g. graphic design programs (vector or raster), see text in Inkscape as an exemple. It would retain what we love in Ardour (linked regions) but make inputung MIDI feel more natural.
<br>
</p>
<p><br>
</p>
<p>As a side note, maybe each region in a track could have a different color if they are not linked, so that we could immediately see which regions are linked and which are not. Or if it's too much color, maybe a floating "chain" icon in the top left near the
name of the region, that could be clicked to unlink it ? </p>
<p><br>
</p>
<p>Regards,</p>
<p>Ed<br>
</p>
<br>
<div style="color: rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>De :</b> Ardour-Dev <ardour-dev-bounces@lists.ardour.org> de la part de Lorenzo Sutton <lorenzofsutton@gmail.com><br>
<b>Envoyé :</b> dimanche 5 mars 2017 21:45<br>
<b>À :</b> ardour-dev@lists.ardour.org<br>
<b>Objet :</b> Re: [Ardour-Dev] let's talk about MIDI regions</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi all,<br>
<br>
My take. Disclaimer: while I use Ardour quite a lot for audio-only, I <br>
hardly use MIDI for various reasons; so my point of view might be <br>
strongly biased by using other software.<br>
<br>
On 03/03/17 16:03, Brett McCoy wrote:<br>
> On Fri, Mar 3, 2017 at 5:02 AM, Paul Davis <paul@linuxaudiosystems.com<br>
> <<a href="mailto:paul@linuxaudiosystems.com">mailto:paul@linuxaudiosystems.com</a>>> wrote:<br>
><br>
><br>
> one idea that is in the air for Ardour 6.0 is to move away from the<br>
> idea of MIDI regions entirely.<br>
<br>
I think one of the problems with current *MIDI* regions in Ardour is <br>
that they are a bit confusing from an UI point of view when the MIDI <br>
notes grid is also visible (i.e. vertical zoom is enough to trigger the <br>
notes grid with the 'piano roll' like view).<br>
With the default theme and the Draw tool it is very confusing if you are <br>
going to input a note or create a new region by clicking on an empty <br>
note space. When I tried *composing* (i.e. not recording from a MIDI <br>
instrument) in Ardour I easily found myself accidentally creating <br>
multiple empty MIDI regions ending up with not knowing where I could <br>
actually input notes in.<br>
The fact is that audio regions as much as you can split them and <br>
theoretically arrive at sample granularity are unique events containing <br>
materials, while midi regions contain other discrete events which are <br>
essentially notes and other MIDI events (controllers, wheel, ..).<br>
<br>
One idea would be to have the main window as an "arranger" only for <br>
MIDI, where regions become big 'blobs' which one just arranges like <br>
audio ones. Then actual editing of the events happens in a separate <br>
context (different window or space, e.g. down below on the bottom of the <br>
screen).<br>
<br>
I am aware that Ardour developers have strong feelings *against* a <br>
separate MIDI editing window (piano roll, aka matrix), but the fact is <br>
that midi is completely different from audio, and there is a very good <br>
reason for having the option for several midi editing windows for a <br>
region, potentially many in parallel.<br>
<br>
Now, personally I think that if Ardour stands still in not wanting to <br>
provide a dedicated MIDI editing environment like many sequencers do, <br>
and stick to only 'inline' editing, it *shouòd* indeed remove MIDI <br>
regions, just for the sake of making MIDI editing a bit more sane.<br>
<br>
Overall I think it all depends on what the aimed target (use case) for <br>
supporting MIDI in Ardour is:<br>
- quick adding of a bass-line or drum track in a still strongly <br>
audio-centric software?<br>
- full blown midi sequencer support enabling composition?<br>
- MIDI 'recording' with some editing and arranging feature?<br>
- mix of the above?<br>
<br>
My longish two cents :)<br>
Lorenzo.<br>
<br>
<br>
_______________________________________________<br>
ardour-dev mailing list<br>
ardour-dev@lists.ardour.org<br>
<a href="http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org">http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org</a><br>
</div>
</span></font></div>
</div>
</body>
</html>