usb, firewire and latency

[autostatic]

Try 48 frames and a sample rate of 48Khz.

http://old.nabble.com/usb-and-jack-td26046087.html

[Capoeira]

Try 48 frames and a sample rate of 48Khz.

http://old.nabble.com/usb-and-jack-td26046087.html

will test it, never used framerate wich isn't period of 16 (because of qjackctl)
only for testing though with 48Khz, as downsample for 48k to 44.100 afterwards gives a loss in quality

[horo]

...will test it, never used framerate wich isn't period of 16 (because of qjackctl)...

Besides chosing from pull down menu you can edit the values in the boxes.

Ciao Martin

[Capoeira]

...will test it, never used framerate wich isn't period of 16 (because of qjackctl)...

Besides chosing from pull down menu you can edit the values in the boxes.

Ciao Martin

damn, never realized that lol

(ach, nen Belina hia? Ick bin in Belin uffjewachsen )

Try 48 frames and a sample rate of 48Khz.

http://old.nabble.com/usb-and-jack-td26046087.html

It starts up with x-runs using 48 frames 48kHz and 2 periods
It starts up without x-runs using 48 frames 44.1kHz and 2 periods (sure they will apear)
Don't know why they recomend 48KHz - I know my card is 44.1 nativley (alias it has jumpers below it for that)
Don't know why they recomend 3 periods - never experienced a diference between 2 and 3

[autostatic]

Don't know why they recomend 48KHz - I know my card is 44.1 nativley (alias it has jumpers below it for that)
Don't know why they recomend 3 periods - never experienced a diference between 2 and 3

To quote Clemens Ladisch from his reply to this thread:

For most USB audio devices, using period sizes that are an integer
multiple to the USB packet size (1 ms) will definitely help. Some
devices like the SB Audigy 2 NX or UA-101 do not synchronize their
sample clock to the USB clock (and this has nothing to do with USB
2.0), and in those cases, the period size does not matter.

It starts up with x-runs using 48 frames 48kHz and 2 periods

Try 3 periods. This will set the latency to 2ms, which is an integer multiple to the USB packet size (1 ms).

[Capoeira]

It starts up with x-runs using 48 frames 48kHz and 2 periods

Try 3 periods. This will set the latency to 2ms, which is an integer multiple to the USB packet size (1 ms).

this sets latency to 3ms (48frames = 1ms x 3 periods)
it works without xruns running an ardour-project with lots of effects.

I tested again 48frames 48kHz and 2 periods: gives me an x-run at startup but running ardour afterwards works without xruns

If I could only set 44.1 frames to work with 44.1 Hz....

[autostatic]

You're absolutely right, I'm so bad at maths 48Khz and 48 periods should yield 2ms and that should work, at least it does with my card. But no, you can't set your periods to 44.1, only whole numbers.

[Capoeira]

But no, you can't set your periods to 44.1, only whole numbers.

yea, I tried it from comand-line, no way
but 88frames works without any x-run, too at 44.1kHz wich gives 4ms of latancy. 64 or 66 frames give me some xruns wich doesn't seam to be audible BUT now that I have my studio-monitors I heard some recordings again and I could identifie some (not verry obvious though)
So, I can work with 2ms of latancy with 48KHz and with 4ms latancy with 44.1KHz.
Though I don't think there is a difference between 2 and 4 ms I learned a lot from this about jack-settings:
Thank you verry much.
And in fact, this can help me find a better setting for running VSTis with fst, wich I will try out now

So, firewire doesn't care about those odd numbers? That surely gives firewire more flexibilitie