13 Nov
2011
13 Nov
'11
7:23 p.m.
Hi,
just discovered this strange behaviour:
USB audio interfaces (Lexicon Omega and UCA202 with BB2902) with JACK
framesize of 48 or 96 work well with jaaa but segfault with japa, while
japa with framesize 64, 128, 256... is ok.
I use 48/96 framesize because of this info:
http://old.nabble.com/usb-and-jack-ts26046087.html
Any idea or suggestions?
Ciao, Martin
14 Nov
14 Nov
1:42 p.m.
On 11/13/2011 07:23 PM, Martin Homuth-Rosemann wrote:
Hi,
just discovered this strange behaviour:
USB audio interfaces (Lexicon Omega and UCA202 with BB2902) with JACK
framesize of 48 or 96 work well with jaaa but segfault with japa,
while japa with framesize 64, 128, 256... is ok.
I use 48/96 framesize because of this info:
http://old.nabble.com/usb-and-jack-ts26046087.html
Any idea or suggestions?
Ciao, Martin
Doesn't the jack API guarantee that nframes is 2^n where n is an integer?
http://jackaudio.org/files/docs/html/types_8h.html#a4923142208a8e7dacf00ca7…
So if your jack implementation allows you to change that, then it might
be a bug..
Flo
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
7:52 p.m.
On Sun, Nov 13, 2011 at 07:23:23PM +0100, Martin Homuth-Rosemann wrote:
just discovered this strange behaviour:
USB audio interfaces (Lexicon Omega and UCA202 with BB2902) with JACK
framesize of 48 or 96 work well with jaaa but segfault with japa, while
japa with framesize 64, 128, 256... is ok.
Both japa and jaaa work OK here with -p 48 or 96, and there is no
reason why they shouldn't. Also both use the same method to transfer
data from Jack's callback to the analyser, and don't depend on any
particular period size.
--
FA
Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
4550
days inactive
4551
days old
linux-audio-user@lists.linuxaudio.org
2 comments
3 participants
participants (3)
-
Florian Paul Schmidt -
Fons Adriaensen -
Martin Homuth-Rosemann