[nama] Re: Preliminary debugging info for "silence" problem

On Fri, Jul 15, 2011 at 10:36:40AM -1000, Joel Roth wrote:
> On Fri, Jul 15, 2011 at 03:29:56PM -0400, S. Massy wrote:
> > On Wed, Jul 13, 2011 at 01:55:47AM -1000, Joel Roth wrote:
> > > Other tests:
> > > 
> > > In Nama, run your same setup:
> > > 
> > > nama> eval eval_iam("forward 10")   # sends "forward 10" to ecasound
> > > 
> > > Load the Nama setup directly into Ecasound and try 'forward 10' there.
> > > 
> > > Either: 'ecasound -c -s Setup.ecs' or starting in Nama:
> > > 
> > > nama> cs-save-as fullsetup.ecs
> > > 
> > > Then 'ecasound -c -s fullsetup.ecs'
> > Okay! Doing this, I can reproduce the issue, which means nama is
> > likely blameless. Will poke around some more and take it to the ecasound
> > list.
> 
> Well, this is a known problem when seeking with JACK. Nama's solution is to do
I didn't realise this was a known issue. It sadly makes life rather
impossible when trying to use ecasound as DAW backend. 

> the following (from a command-line viewpoint).
> 
> nama> eval eval_iam("stop"); eval_iam("forward 10"); sleeper(0.1); 
> eval_iam("start")
> 
> You can try changing the 'sleeper' interval to see if that
> helps.
I read your post refering to $seek_delay, but I didn't realise at the
time that it was added specifically to try to mitigate this problem. As
I said previously, though, the problem occurs in nama even when
muting/unmuting/soloing/nosoloing, which I wouldn't think involved any
seeking. In fact, now that I think of it, the problem mostly occurs in
nama when muting/soloing/etc., and far less frequently when seeking,
while it occurs very predictibly in ecasound even with a simple forward
seek; so $seek_delay must be helping there.

One question: is it correct, when trying to use an in-tree version of
nama, that running ./src/ui will run the right version of the code?

Cheers,
S.M.

Other related posts: