Re: [Jamin] ardour export + jamin

[Kees v. V. <kee...@gm...>]

Jack,

Just a thought: since it only happens with low frames/period and 
freewheeling, it would also be possible to issue a warning when the 
condition fails (and maybe to slow down Jack a bit in freewheeling mode, 
if no harm is done (still the wrong solution, I know, but it would 
complete the export)), and ask Jack for the current frames/period 
setting, so the user will know why Jamin is aborted (or Jack is slowed 
down).

That way this issue would not get in the way of a new release, and still 
give the user a clue as to what is happening. Might also generate more 
specific posts of the problem. It took me a while before I knew why 
Jamin 'disappeared' all of a sudden. If you're new to using Ardour, 
Jack, Jamin, you often look in the wrong places, thinking you did 
something wrong with the insert or something.

If I can be of any help, let me know.

Regards,
Kees

-------- Original Message --------
Subject: Re: [Jamin] ardour export + jamin
From: Jack O'Quin <jac...@gm...>
To: Kees van Veen <kee...@gm...>
Date: Mon Jan 18 2010 16:38:28 GMT+0100 (CET)
> On Mon, Jan 18, 2010 at 6:51 AM, Kees van Veen <kee...@gm...> wrote:
>   
>> Hi Jack,
>>
>> Thanks for your help, so far. At least I have a work-around, so that gives
>> me some air, and it's good we found the cause of the trouble.
>>
>> Looks like you still do development on Jamin, but no new version has been
>> released for some time. Are you guys planning one?
>>     
>
> Yes, I think we will.  There are a couple of small but useful
> enhancements in CVS already.  Once we can come up with a solid fix to
> this "low-latency freewheeling" bug, it needs to be released.  I'm
> still not sure exactly what a good solution will look like; I am not
> eager to do a major rewrite of those DSP queuing states.  Meanwhile, I
> think the recommended work-around is to use a period size of a least
> 256 samples.
>
> Jamin has been in maintenance mode for quite some time.  It seems to
> work well for most purposes and sounds good, so there's been no
> pressure to make new releases.  (If it ain't broke, don't fix it.)
>
> I wish we'd known about the freewheeling problem sooner, but I don't
> recall it being reported here, and don't follow the Ardour forums
> myself.  Thanks for letting us know about the problem.
>