9 Feb
2013
9 Feb
'13
12:24 p.m.
Hi James,
On 02/09/2013 01:11 PM, James Stone wrote:
Hi Flo, I am also running Ubuntu 12.10 and using
jackdbus. It is
really nice for things like playing along to youtube videos.. On my
computer, I noticed that jack does have a tendency to lockup after a
while when jackdbus is running. I had the feeling that it might be
something to do with latency, as I found it is impossible to start
jack at very low latencies with jackdbus running. I was using 128
samples which seemed to be OK, but at that latency, the lockups
occurred after some time. I tried increasing latency to 256
samples/44.1k. Following this, it seems to operate fine (at least I
have had no more dropouts), but it is all a bit fiddly to get it to
work properly, and I would probably disable pulse if I wanted to do
serious recording etc without the mixing capabilities that jackdbus
adds.. James
I use very large period sizes, 1024 or even 2048. The problem of jackd
starting to eat 100% cpu occurs usually when I'm done with my current
work (recording something or fiddling around) and just leave it running
idly. Then when I return to my computer after a few hours jackd sits
there happily eating cpu. It has the side effect of heating my room, but
heating with electricity is expensive and thus I'd rather avoid it ;D
Have fun,
Flo
--
Florian Paul Schmidt
http://fps.io
9 Feb
9 Feb
12:36 p.m.
New subject: [LAU] jackdbus eating 100% cpu after a while
On Sat, Feb 09, 2013 at 01:24:22PM +0100, Florian Paul Schmidt wrote:
I use very large period sizes, 1024 or even 2048. The
problem of
jackd starting to eat 100% cpu occurs usually when I'm done with my
current work (recording something or fiddling around) and just leave
it running idly.
This sounds a bit like denormals.
Which CPU? Just to be sure.
Cheers
--
mail: adi(a)thur.de http://adi.thur.de PGP/GPG: key via keyserver
12:37 p.m.
New subject: [LAU] jackdbus eating 100% cpu after a while
On 02/09/2013 01:36 PM, Adrian Knoth wrote:
On Sat, Feb 09, 2013 at 01:24:22PM +0100, Florian Paul
Schmidt wrote:
Yeah, I thought about denormals, too. But it takes a few hours to kick
in. Never happened with jack1.
processor : 3
vendor_id : AuthenticAMD
cpu family : 16
model : 10
model name : AMD Phenom(tm) II X4 960T Processor
stepping : 0
microcode : 0x10000bf
cpu MHz : 800.000
cache size : 512 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 6
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl
nonstop_tsc extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm
cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch
osvw ibs skinit wdt nodeid_msr cpb hw_pstate npt lbrv svm_lock nrip_save
pausefilter
bogomips : 6000.24
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate cpb
Flo
--
Florian Paul Schmidt
http://fps.io
I use very large period sizes, 1024 or even 2048.
The problem of
jackd starting to eat 100% cpu occurs usually when I'm done with my
current work (recording something or fiddling around) and just leave
it running idly.
This sounds a bit like denormals.
Which CPU? Just to be sure.
Cheers
4186
days inactive
4186
days old
linux-audio-dev@lists.linuxaudio.org
2 comments
2 participants
participants (2)
-
Adrian Knoth -
Florian Paul Schmidt