<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">I have experienced similar things with the Hydrogen Humanize option.<br>I guess it's only natural it might have a slight delay in output depending on system/jack latency issues.<br>It hasn't hampered me much tho-<br><br>dav=-0<br><br><br><br><br>I
think
Arnold
has
the
key
to
it
actually
-
it
might
well
be
the <br>Humanize
controls
in
Hydrogen
that
are
the
problem.
I've
done
quite
a <br>few
experiments
now,
it's
still
not
entirely
clear
to
me
what's
going
on <br>but
if
I
create
completely
new
projects
in
Hydrogen
and
Ardour
and
don't <br>use
Humanize,
the
phasing
effect
seems
to
go
away.
I'm
not
100% <br>convinced
yet
though
and
I'd
be
interested
Paul
if
you
know
of <br>version(s)
of
Jack
which
exhibit
the
problem
you
describe.<br><br>Thanks
all,<br><br>Mark.<br><br>Dominic
Sacré
wrote:<br>>
On
Jan
28,
2008
3:39
PM,
Paul
Davis
<<a ymailto="mailto:paul@linuxaudiosystems.com" href="mailto:paul@linuxaudiosystems.com">paul@linuxaudiosystems.com</a>>
wrote:<br>>
<br>>>
On
Mon,
2008-01-28
at
13:56
+0100,
Arnold
Krille
wrote:<br>>>
<br>>>>
Which
means
its
constant
(in
your
session
of
jack)
and
simply
because
of<br>>>>
latency
compensation
happening
/
not
happening.
Nothing
to
really
worry<br>>>>
about,
ardour
just
can't
tell
wether
the
sound
its
playing/monitoring
is
from<br>>>>
inside
or
outside
the
computer...<br>>>>
<br>>>
actually
it
can,
and
it
does.
ardour
will
trace
the
signal
path
back
to<br>>>
a
physical
port
(if
one
exists).<br>>><br>>>
however,
the
version
of
JACK
is
important.
although
the
basic<br>>>
information
required
for
latency
compensation
has
always
been
available,<br>>>
there
are
some
little
details
about
how
and
when
its
computed
that<br>>>
affect
the
results.<br>>>
<br>><br>>
Is
this
really
a
problem
with
latency
compensation?
Or
could
it
just
be
the<br>>
old
jack-transport-off-by-one-period
issue,
which
is
still
present
in
the<br>>
latest
JACK
version,
and,
to
my
knowledge,
always
has
been?<br>><br>><br>>
Dominic<br>>
_______________________________________________<br>>
Ardour-Users
mailing
list<br>>
<a ymailto="mailto:ardour-users@lists.ardour.org" href="mailto:ardour-users@lists.ardour.org">ardour-users@lists.ardour.org</a><br>>
<a href="http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org" target="_blank">http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org</a><br>><br>>
<br>_______________________________________________<br>Ardour-Users
mailing
list<br><a ymailto="mailto:ardour-users@lists.ardour.org" href="mailto:ardour-users@lists.ardour.org">ardour-users@lists.ardour.org</a><br><a href="http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org" target="_blank">http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org</a><br></div><br></div></div><br>
<hr size=1> Sent from <a href="http://us.rd.yahoo.com/mailuk/taglines/isp/control/*http://us.rd.yahoo.com/evt=51949/*http://uk.docs.yahoo.com/mail/winter07.html">Yahoo!</a> - a smarter inbox.</body></html>