Re: [ecasound] reset "over" counters in ecasignalview?

From: Kai Vehmanen <kvehmanen@email-addr-hidden>
Date: Sun Aug 07 2005 - 20:29:08 EEST


a follow-up to an older issue.

On Fri, 20 May 2005, Kai Vehmanen wrote:

> On Fri, 20 May 2005, Peter Lutek wrote:
>> shouldn't the ecasound-iam "start" be the trigger for file-writing, rather
>> than the start of a separate ecasignalview process?
> All these problems are caused by the fact that both ecasound and
> ecasignalview are JACK-transport aware. So when you issue "start" in
> ecasound, also ecasignalview will start, and when issue "stop", also
> Now when JACK-transport support was introduced initially, there was some
> discussion on what the default behaviour should be. It was decided that full
> support ("-G:jack,ecasound,sendrecv") is the best default. But, but,
> I guess for ecasignalview this really doesn't make that much sense. I'll add
> this for my 2.4.2 todo-list.

I just committed a change to CVS (will be in 2.4.2), that causes
ecasignalview to disable sending/receiving JACK-transport events. This
should be the best solution from "least-surprises" design perspective.

  Audio software for Linux!
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 Mon Aug 8 00:15:04 2005

This archive was generated by hypermail 2.1.8 : Mon Aug 08 2005 - 00:15:04 EEST