Re: [LAU] jack-stdio 1.1 - was [ANN] jack-stdout 1.0

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Kjetil S. Matheussen <k.s.matheussen@...>
Cc: <linux-audio-user@...>
Date: Sunday, April 3, 2011 - 5:04 pm

On 04/03/2011 11:20 AM, Kjetil S. Matheussen wrote:

> Ouch, there's a bug there! 'tobuffer' must change position

In my case (1<=bytes_to_write<=4*no_of_channels): very very unlikely.

The Linux pipe is 64k by default and IO_BUFSIZ is 8K bytes (on my 32bit
debian/squeeze - The C standard only specifies the minimum for BUFSIZ).

Since you're writing whole periods worth of samples: It's more likely to
happen with odd bytes/sample and/or odd number of channels. But unless
one is piping directly into some network-socket or is doing similarly
crazy things, I don't think it'll ever happen.

It's different for reading, because the app producing the stream could
fflush() anytime. Anyways, jack-stdio is intended as
instrumentation-tool. Although I'm confident that it works, I do not
recommend using it in a pro-studio or on-stage. It's easy enough to
write a proper JACK client.

Cheers!
robin
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [LAU] jack-stdio 1.1 - was [ANN] jack-stdout 1.0, Kjetil S. Matheussen, (Fri Apr 1, 12:13 pm)
Re: [LAU] jack-stdio 1.1 - was [ANN] jack-stdout 1.0, Robin Gareus, (Fri Apr 1, 1:14 pm)
Re: [LAU] jack-stdio 1.1 - was [ANN] jack-stdout 1.0, Kjetil S. Matheussen, (Sun Apr 3, 9:14 am)
Re: [LAU] jack-stdio 1.1 - was [ANN] jack-stdout 1.0, Kjetil S. Matheussen, (Sun Apr 3, 9:20 am)
Re: [LAU] jack-stdio 1.1 - was [ANN] jack-stdout 1.0, Robin Gareus, (Sun Apr 3, 5:04 pm)