29 Apr
2010
29 Apr
'10
4:32 p.m.
Rui Nuno Capela wrote:
On Thu, 29 Apr 2010 17:36:43 +0400, Louigi Verona
wrote:
This is exactly how I thought it can be done! Great Paul, really nice
job
As I've written before, unfortunately negative values aren't possible,
neither for the start-time nor for the offset-time.
OT: I guess today I'll upgrade Qtractor ;) and in coming days I should
go on testing, resp. using Qtractor, sorry for the rest ;D. For testing
purpose I'll switch to 64 Studio 3.3 alpha (Ubuntu Karmic), assumed that
I'm able to get ALSA seq repaired, it's written that it should be broken
... won't become too OT.
On Thu, Apr 29, 2010 at 5:21 PM, Paul Davis
wrote:
> On Thu, Apr 29, 2010 at 6:45 AM, Louigi Verona wrote:
>
>
>> "you can swap qtractor for ardour, or anything else for that matter
>>
and
>> the latency will be exactly the same
systematic. a client can only
>>
process
the results of its own outputs or sends in the _next_
process cycle."
Ha! Rui, that makes sense. Now I think I get it. Indeed.
I wonder if there is an easy way to compensate for this after the
recording took place.
Ardour specifically has a "nudge by period size" (since that is
the
offset that results) for precisely this purpose.
you did!
I think Rui is planning to implement something of that sort as well.
do i? :)
anyway, while on the clip properties dialog you can always alter the clip
start-time manually, in frames
cheers