I use hydrogen with ardour as Jack Master, and i program tempo changes in ardour (right on the bar). When playing the tempo changes well (which was a great surprise cause i thought that didn't work with H2) but sound problem occur
It's like the sound of the first note of the new bar is cut.

Has this happen to anyone ?
Or could someone do a quick check ?

I would like to disable jack sync in H2 for tests.
Maybe i could use it only as a sample player with seq24
But in 0.9.4, no more "jack transport" button.
Where did it go ?

open properties and change driver to jack.
the jack transport buttons only available if you activate the jack driver.

ok so as i thought :
using H2 as a simple sample player, no glitch is heard at tempo change.
seems logical, no jack transport, so H2 could even know there is a tempo change but still it means that the problem is not in jack transport

So we're back to :
Has this happen to anyone ?
Or could someone do a quick check on their machine ?

What do you think of this problem wolke ?

Ok so i've narrowed the field :
It seems that it makes the nose when the tempo change is right on the end of the song in H2
When starting back the song, the tempo change must be disturbing for H2 -> glitch
Should i file a bug ? Or could so with an account do so ?

>Should i file a bug ?
tempo change is a bit groggy. there are many effects which happens but are unsolicited. so yes, you can file a ticket for this.
but please give a detailed step by step description what you do in both applications.

just now, to work fairly smooth with tempo changes between |ardour<--> hydrogen | using the jack transport you have to make some song settings totally synchronous.
that means:
*all pattern length for each bar must be exactly the same
example:
hydrogen pattern in song arrangement | ardour time-line-bar settings
pattern 1 = 12 beats length |bar 1 = 6 beats long (6/8)
pattern 2 = 8 beats length |bar 2 = 4 beats long (4/4)
pattern 3 = 14 beats length | bar 3 = 7 beats long (7/4)
and so on. | and so on.

*no time-line offset in ardour.
that means the song must start exact in position zero.
--but--
*let the first bar empty (insert an empty pattern e.g. 4 bats long in both apps). start the song in bar two.
*smaller buffer size around 256 - 512 buffers
this you can test if some double hits occur.
*don't use loops!!!! arrange your complete song in only one-piece.