5 Sep
2009
5 Sep
'09
9:55 a.m.
I can't quite figure it out, can anyone tell me the circumstances that would
lead to jack reporting a change to samplerate/buffersize on the fly?
cheers, Cal
5 Sep
5 Sep
10:07 a.m.
On Sat, 05 Sep 2009 21:55:15 +1000
cal <cal(a)graggrag.com> wrote:
I can't quite figure it out, can anyone tell me
the circumstances
that would lead to jack reporting a change to samplerate/buffersize
on the fly?
cheers, Cal
Afaik only on-the-fly samplerate changes are possible. Usually this
only happens on user action. Some applications that provide this
possibility are: Ardour and patchage
Philipp
6 Sep
6 Sep
4:55 p.m.
On Sat, 5 Sep 2009 14:07:30 +0200
<hollunder(a)gmx.at> wrote:
On Sat, 05 Sep 2009 21:55:15 +1000
cal <cal(a)graggrag.com> wrote:
Sorry for the miss-information, seems like I was really confused and
probably in a hurry when I wrote that.
Philipp
I can't quite figure it out, can anyone tell
me the circumstances
that would lead to jack reporting a change to samplerate/buffersize
on the fly?
cheers, Cal
Afaik only on-the-fly samplerate changes are possible. Usually this
only happens on user action. Some applications that provide this
possibility are: Ardour and patchage
Philipp 
5 Sep
5 Sep
10:16 a.m.
Hi Cal,
On Sat, 5 Sep 2009, cal wrote:
I can't quite figure it out, can anyone tell me
the circumstances that would
lead to jack reporting a change to samplerate/buffersize on the fly?
cheers, Cal
It's part of the API of JACK... so any application can cause it to happen
for any reason. It usually doesn't happen automatically, but as the
result of a user's interaction.
For example, the attached C++ program gives you a command-line tool to
change the buffersize on the fly. Compile & run it like this:
$ g++ -o jack_set_buffer_size jack_set_buffer_size.cpp -ljack
$ ./jack_set_buffer_size 1024
It's pretty simple to write a similar app. for samplerate.
HTH,
Gabriel
10:23 a.m.
guitarix allows this too from its main menu, so that the user can modify the latency
during a session.
J.
--- On Sat, 9/5/09, Gabriel M. Beddingfield <gabriel(a)teuton.org> wrote:
From: Gabriel M. Beddingfield
<gabriel(a)teuton.org>
Subject: Re: [LAD] jack samplerate/buffersize callbacks
To: "cal" <cal(a)graggrag.com>
Cc: Linux-audio-dev(a)lists.linuxaudio.org
Date: Saturday, September 5, 2009, 8:16 AM
Hi Cal,
On Sat, 5 Sep 2009, cal wrote:
I can't quite figure it out, can anyone tell
me the
circumstances that would
lead to jack reporting a change to
samplerate/buffersize on the fly?
cheers, Cal
It's part of the API of JACK... so any application can
cause it to happen for any reason. It usually doesn't
happen automatically, but as the result of a user's
interaction.
For example, the attached C++ program gives you a
command-line tool to change the buffersize on the fly.
Compile & run it like this:
$ g++ -o jack_set_buffer_size
jack_set_buffer_size.cpp -ljack
$ ./jack_set_buffer_size 1024
It's pretty simple to write a similar app. for samplerate.
HTH,
Gabriel
-----Inline Attachment Follows-----
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
10:53 a.m.
On Sat, Sep 5, 2009 at 7:55 AM, cal<cal(a)graggrag.com> wrote:
I can't quite figure it out, can anyone tell me
the circumstances that would
lead to jack reporting a change to samplerate/buffersize on the fly?
changing the SR is not implemented and we have no plans at present to
implement it. it was added to the API at the outset, and over time is
has become clear that it causes a lot of pain for many apps if we were
to implement it. neither jack2 nor jack1 actually does anything when a
client makes this request. however we have still not definitively
decided whether or not it should be a functioning part of the API,
hence the misleading situation you see at present.
5352
days inactive
5353
days old
linux-audio-dev@lists.linuxaudio.org
5 comments
5 participants
participants (5)
-
cal -
Gabriel M. Beddingfield -
hollunder＠gmx.at -
James Warden -
Paul Davis