Re: [ecasound] using copp-set with controllers

From: Kai Vehmanen <kvehmanen@email-addr-hidden>
Date: Thu Sep 01 2005 - 03:21:14 EEST


cc'ing back to the list so others can test this, too.

On Thu, 1 Sep 2005, Adam Linson wrote:

>> Hmm, this could be solved by adding an extra parameter to -km which
>> sets the initial value (i.e. value of -km until the first MIDI-CC message
>> is received). Or: -km fetches the initial value from operator... this
>> is a bit tricky to achieve in the current implementation, but might be
>> more elegant.
> With the less elegant implementation, the initial value could be an
> optional parameter in the final position which, when omitted, would
> result in the current behavior (and no existing chains would be
> broken).

I now committed some code to CVS that allows setting an initial controller
value for all sources. Sources like MIDI-CC (-km) can use the initial
value until first valid MIDI-CC bytes are received to the correct
ctrl+channel combination. The initial value is read from the target
operator, which is probably the most intuitive way for the user.

In other words:
ecasound -i foo.wav -o alsa -efl:1500 -km:1,400,4200,1,1 -Md:alsaseq,80:1 -c

The lowpass-freq will be 1500 until we start receiving MIDI-CC messages to
ctrl 1 on channel 1.

Let me know if this works for you.

  links, my public keys, etc at
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement *
Ecasound-list mailing list
Received on Thu Sep 1 04:15:06 2005

This archive was generated by hypermail 2.1.8 : Thu Sep 01 2005 - 04:15:06 EEST