<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
<br>> ><br>> > So anyway, if a new port does get defined I would personally not like <br>> > to see it called<br>> > a CV port. Automation (CA) maybe, but not CV, that confuses the issue.<br>> <br>> Hm? And how do we use the automation? By mouse or by hardware MIDI <br>> controllers ;)?<br>> If the hardware MIDI controller would define the start and end point and <br>> cv uses a movement curve it isn't really manually control, but having a <br>> resolution of 14 bit for MIDI might be smooth enough and manually <br>> movements could be recorded by the sequencer.<br><br>I would imagine the movements of the controls in the GUI would have to<br>be recorded then potentially interpolated/smoothed. Isn't this how the <br>automated decks handle fade/mixes? If you say you want to record the<br>settings of a controller during playing the song then any movement of <br>that control is saved somewhere - then it shouldn't matter whether that<br>was moving the control with the mouse or having it move from a surface<br>control linked to the GUI device. Actually scrub that - it would just be <br>recording a MIDI track next to the audio track that drives the mixing<br>desk itself. I take it Ardour can do that anyway for any of its controls as<br>they can all be linked to MIDI surfaces.<br><br>Must have missed the point again.<br><br>Regards, nick.<br> <br /><hr />Hotmail: Powerful Free email with security by Microsoft. <a href='https://signup.live.com/signup.aspx?id=60969' target='_new'>Get it now.</a></body>
</html>