[Ardour-Users] Hydrogen/Ardour sync problem
fatgerman at ntlworld.com
Mon Jan 28 08:41:16 PST 2008
I think Arnold has the key to it actually - it might well be the
Humanize controls in Hydrogen that are the problem. I've done quite a
few experiments now, it's still not entirely clear to me what's going on
but if I create completely new projects in Hydrogen and Ardour and don't
use Humanize, the phasing effect seems to go away. I'm not 100%
convinced yet though and I'd be interested Paul if you know of
version(s) of Jack which exhibit the problem you describe.
Dominic Sacré wrote:
> On Jan 28, 2008 3:39 PM, Paul Davis <paul at linuxaudiosystems.com> wrote:
>> On Mon, 2008-01-28 at 13:56 +0100, Arnold Krille wrote:
>>> Which means its constant (in your session of jack) and simply because of
>>> latency compensation happening / not happening. Nothing to really worry
>>> about, ardour just can't tell wether the sound its playing/monitoring is from
>>> inside or outside the computer...
>> actually it can, and it does. ardour will trace the signal path back to
>> a physical port (if one exists).
>> however, the version of JACK is important. although the basic
>> information required for latency compensation has always been available,
>> there are some little details about how and when its computed that
>> affect the results.
> Is this really a problem with latency compensation? Or could it just be the
> old jack-transport-off-by-one-period issue, which is still present in the
> latest JACK version, and, to my knowledge, always has been?
> Ardour-Users mailing list
> ardour-users at lists.ardour.org
More information about the Ardour-Users