Sorry for jumping right in without having read the complete thread, but
anyway...
On 10/07/2013 11:23 AM, Patrick Shirkey wrote:
On Mon, October 7, 2013 7:41 pm, Tanu Kaskinen wrote:
Ok, so this happens when the native protocol tries to send a block of
audio from the jack source thread to the
On Thu, 2013-10-17 at 14:04 +0200, David Henningsson wrote:
Sorry for jumping right in without having read the complete thread, but
anyway...
On 10/07/2013 11:23 AM, Patrick Shirkey wrote:
On Mon, October 7, 2013 7:41 pm, Tanu Kaskinen wrote:
Ok, so this happens when the native protocol
On Mon, October 14, 2013 11:21 pm, Tanu Kaskinen wrote:
On Mon, 2013-10-07 at 20:23 +1100, Patrick Shirkey wrote:
There are two options that JACK allows for
1) Kick the offender from the graph
2) Allow dropouts in the stream (softmode)
I suppose in this case PA is trying to stop dropouts
On Mon, 2013-10-07 at 20:23 +1100, Patrick Shirkey wrote:
There are two options that JACK allows for
1) Kick the offender from the graph
2) Allow dropouts in the stream (softmode)
I suppose in this case PA is trying to stop dropouts from happening which
is a noble cause because most of
On Fri, 2013-10-04 at 21:49 +1000, Patrick Shirkey wrote:
On Thu, October 3, 2013 11:41 pm, Thomas Martitz wrote:
Am 03.10.2013 10:20, schrieb Patrick Shirkey:
On Thu, October 3, 2013 5:14 pm, Tanu Kaskinen wrote:
That doesn't look healthy. The message is printed when
On Mon, October 7, 2013 7:41 pm, Tanu Kaskinen wrote:
On Fri, 2013-10-04 at 21:49 +1000, Patrick Shirkey wrote:
On Thu, October 3, 2013 11:41 pm, Thomas Martitz wrote:
Am 03.10.2013 10:20, schrieb Patrick Shirkey:
On Thu, October 3, 2013 5:14 pm, Tanu Kaskinen wrote:
That doesn't look
On Thu, October 3, 2013 11:41 pm, Thomas Martitz wrote:
Am 03.10.2013 10:20, schrieb Patrick Shirkey:
On Thu, October 3, 2013 5:14 pm, Tanu Kaskinen wrote:
That doesn't look healthy. The message is printed when
pa_asyncmsgq_post() is called and the message queue is full. The
message
queue
On Thu, 2013-10-03 at 02:33 +1000, Patrick Shirkey wrote:
On Thu, October 3, 2013 12:14 am, Tanu Kaskinen wrote:
On Tue, 2013-10-01 at 00:38 +1000, Patrick Shirkey wrote:
On Sat, September 28, 2013 3:12 am, Patrick Shirkey wrote:
On Sat, September 28, 2013 12:53 am, Tanu Kaskinen wrote:
On Thu, 2013-10-03 at 18:20 +1000, Patrick Shirkey wrote:
On Thu, October 3, 2013 5:14 pm, Tanu Kaskinen wrote:
On Thu, 2013-10-03 at 02:33 +1000, Patrick Shirkey wrote:
I see the following sprinkled in /var/log/messages
Sep 30 12:19:02 xxx pulseaudio[28845]: [pulseaudio] ratelimit.c:
Am 03.10.2013 10:20, schrieb Patrick Shirkey:
On Thu, October 3, 2013 5:14 pm, Tanu Kaskinen wrote:
That doesn't look healthy. The message is printed when
pa_asyncmsgq_post() is called and the message queue is full. The message
queue can store 256 messages before this starts to happen, so some
On Thu, October 3, 2013 12:14 am, Tanu Kaskinen wrote:
On Tue, 2013-10-01 at 00:38 +1000, Patrick Shirkey wrote:
On Sat, September 28, 2013 3:12 am, Patrick Shirkey wrote:
On Sat, September 28, 2013 12:53 am, Tanu Kaskinen wrote:
I don't remember if the alsa compatibility layer forwards
On Sat, September 28, 2013 3:12 am, Patrick Shirkey wrote:
On Sat, September 28, 2013 12:53 am, Tanu Kaskinen wrote:
I don't remember if the alsa compatibility layer forwards the
stream under/overrun notifications to the alsa application - IIRC there
were problems when those were reported
On Thu, September 26, 2013 2:27 am, Tanu Kaskinen wrote:
On Wed, 2013-09-25 at 23:35 +1000, Patrick Shirkey wrote:
On Tue, September 24, 2013 10:33 pm, Patrick Shirkey wrote:
On Mon, September 23, 2013 6:11 pm, Tanu Kaskinen wrote:
The audio is accumulating in some buffer, and the JACK
On Fri, 2013-09-27 at 19:26 +1000, Patrick Shirkey wrote:
On Thu, September 26, 2013 2:27 am, Tanu Kaskinen wrote:
Sorry, forgot to reply earlier. Yes, you can check the stream buffer
with pactl list sink-inputs. The Buffer Latency field shows the
amount of audio in the stream buffer (not
On Fri, 2013-09-27 at 23:31 +1000, Patrick Shirkey wrote:
On Fri, September 27, 2013 10:52 pm, Tanu Kaskinen wrote:
On Fri, 2013-09-27 at 19:26 +1000, Patrick Shirkey wrote:
On Thu, September 26, 2013 2:27 am, Tanu Kaskinen wrote:
Sorry, forgot to reply earlier. Yes, you can check the
On Sat, September 28, 2013 2:58 am, Patrick Shirkey wrote:
On Sat, September 28, 2013 12:53 am, Tanu Kaskinen wrote:
On Fri, 2013-09-27 at 23:31 +1000, Patrick Shirkey wrote:
At the moment I'm trying to pin down the cause of the consistent and
reproducible but fluctuating latency results
On Tue, September 24, 2013 10:33 pm, Patrick Shirkey wrote:
On Mon, September 23, 2013 6:11 pm, Tanu Kaskinen wrote:
On Sun, 2013-09-22 at 20:03 +1000, Patrick Shirkey wrote:
On Sun, September 22, 2013 4:37 pm, Tanu Kaskinen wrote:
If you want to get the minimum latency of this path:
On Wed, 2013-09-25 at 23:35 +1000, Patrick Shirkey wrote:
On Tue, September 24, 2013 10:33 pm, Patrick Shirkey wrote:
On Mon, September 23, 2013 6:11 pm, Tanu Kaskinen wrote:
The audio is accumulating in some buffer, and the JACK sink in
PulseAudio doesn't have any buffer, so it's not the
On Mon, September 23, 2013 6:11 pm, Tanu Kaskinen wrote:
On Sun, 2013-09-22 at 20:03 +1000, Patrick Shirkey wrote:
On Sun, September 22, 2013 4:37 pm, Tanu Kaskinen wrote:
If you want to get the minimum latency of this path:
jack_delay - pulseaudio - application - pulseaudio -
On Sun, 2013-09-22 at 20:03 +1000, Patrick Shirkey wrote:
On Sun, September 22, 2013 4:37 pm, Tanu Kaskinen wrote:
If you want to get the minimum latency of this path:
jack_delay - pulseaudio - application - pulseaudio - jack_delay
then you should use an application that reports
On Sun, 2013-09-22 at 02:30 +1000, Patrick Shirkey wrote:
On Sun, September 22, 2013 1:55 am, Tanu Kaskinen wrote:
PulseAudio doesn't increase the buffering on the fly (well, some small
adjustments are done with ALSA, but you're using JACK, so that's
irrelevant). If the source produces
On Sun, September 22, 2013 4:37 pm, Tanu Kaskinen wrote:
On Sun, 2013-09-22 at 02:30 +1000, Patrick Shirkey wrote:
On Sun, September 22, 2013 1:55 am, Tanu Kaskinen wrote:
PulseAudio doesn't increase the buffering on the fly (well, some small
adjustments are done with ALSA, but you're using
On Thu, 2013-09-19 at 23:54 +1000, Patrick Shirkey wrote:
On Thu, September 19, 2013 6:52 pm, Patrick Shirkey wrote:
On Thu, September 19, 2013 6:42 pm, Tanu Kaskinen wrote:
On Wed, 2013-09-18 at 04:28 +1000, Patrick Shirkey wrote:
Hi,
Can someone shed some light on the best case and
On Sun, September 22, 2013 1:55 am, Tanu Kaskinen wrote:
On Thu, 2013-09-19 at 23:54 +1000, Patrick Shirkey wrote:
On Thu, September 19, 2013 6:52 pm, Patrick Shirkey wrote:
On Thu, September 19, 2013 6:42 pm, Tanu Kaskinen wrote:
On Wed, 2013-09-18 at 04:28 +1000, Patrick Shirkey wrote:
On Wed, 2013-09-18 at 04:28 +1000, Patrick Shirkey wrote:
Hi,
Can someone shed some light on the best case and typical latency that
Pulse provides for standard operations?
What do you mean by standard operations? I'd estimate volume changes
etc. normally (on an ALSA sink) have a few
On Thu, September 19, 2013 6:42 pm, Tanu Kaskinen wrote:
On Wed, 2013-09-18 at 04:28 +1000, Patrick Shirkey wrote:
Hi,
Can someone shed some light on the best case and typical latency that
Pulse provides for standard operations?
What do you mean by standard operations? I'd estimate volume
On Thu, September 19, 2013 6:52 pm, Patrick Shirkey wrote:
On Thu, September 19, 2013 6:42 pm, Tanu Kaskinen wrote:
On Wed, 2013-09-18 at 04:28 +1000, Patrick Shirkey wrote:
Hi,
Can someone shed some light on the best case and typical latency that
Pulse provides for standard operations?
What
Hi,
Can someone shed some light on the best case and typical latency that
Pulse provides for standard operations?
Also how that is affected by using jack-sink assuming jack is set to the
lowest possible latency that a device can handle?
Cheers
--
Patrick Shirkey
Boost Hardware Ltd
28 matches
Mail list logo
