On Dec 11, 2009, at 11:33 AM, Martin Schied wrote:

Hi,

The delay setting only affects alsa, oss, asio and so on. Jack brings its own buffer size (periods * frames) and pd depends on that. The -audiobuf command line option, or delay setting in the 'media' menu doesn't affect your latency when using jack (you can verify that by setting it to 500ms for example).

Maybe there's a way to indicate that. It would be cool if the delay input box in the Audio settings dialog would not be editable when using Jack.

Dan Wilcox danomatika.com robotcowboy.com

michael noble wrote:

Martin,

Thanks for the clarification. Is this actually documented anywhere, or is it one of those learning from experience situations?

Hi Michael

I think I read about that in the list once and also found things out by experimenting with it.

I tried to get some official Information to this on puredata.info, flossmanuals and through google - I only found this thread giving the information (didn't search in the mail archives). I now made a change to http://en.flossmanuals.net/PureData/ConfiguringPD, it was the first google match for "puredata delay jack" and also has additional informations related to this. I hope this is ok for all authors of the manual.

Changing the audio dialog itself for jack would be far more intuitive - so you wouldn't have to read a manual at all. For command line users a small note on jack would also be nice.

until now it's:

-audiobuf <n> -- specify size of audio buffer in msec

it could be

-audiobuf <n> -- specify size of audio buffer in msec (overriden by jack)

or if there are more audi APIs which override this setting

-audiobuf <n> -- specify size of audio buffer in msec (overriden for some audio API)

cheers Martin