Re: [LAD] automation on Linux (modular approach)

Nick Copeland wrote:
>
> Perhaps it is just me that is confused but I still see a dichotomy
> where on one
> side there are parameters that can be automated/quantised and on the
> other side
> there is modulation that needs to be exact and smooth. This is the
> difference
> between CV and control automation but the thread seems to me to be
> discussing
> both at the same time. Automation can be used for MIDI parameters but
> I still feel
> that CV should be used for modulation. The Tuxfamily crosses that
> barrier by the
> way it can apply CV to any control which is a very interesting
> approach and
> possibly a good reason to have a look at their apps for some musical
> styles.
>
> So anyway, if a new port does get defined I would personally not like
> to see it called
> a CV port. Automation (CA) maybe, but not CV, that confuses the issue.

Hm? And how do we use the automation? By mouse or by hardware MIDI
controllers ;)?
If the hardware MIDI controller would define the start and end point and
cv uses a movement curve it isn't really manually control, but having a
resolution of 14 bit for MIDI might be smooth enough and manually
movements could be recorded by the sequencer.

-- 
Has anybody information about defects known for Roland HiHat 
controllers? The drummer who ask me to repair it seems to have a FD-8. 
It should be fine when it's opened and perhaps half opened, but the 
sound should be to silent when it's closed. He fumble around at the 
female jack and for a moment it should have been ok, in his opinion this 
should be the reason why the sound module should be ok. I'm sceptic 
because of his description. Perhaps he is at home now, then I will take 
a look. Any hints are welcome! Maybe it's a well known defect.
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-dev