On Thu, Nov 12, 2009 at 1:24 PM, cal
<cal@graggrag.com> wrote:
You've had quite a little tragedy unfolding there, and I felt guilty for ignoring
it. Hopefully things have improved, but ...
No problem, I just compiled your stuff to test it, hoping to learn something.
> ADsynth Oscilsize: 2048
> Sample Rate: 44100
> Sound Buffer Size: 32
Are you really running jack with period size 32? Wow!
Yes, with 3 periods, but I didn't use it for recording a large piece yet. It's a setting I changed one day, but forgot about.
I'll try again after increasing the period size ...
Here's a
screenshot of qjackctl's settings now.
> [ 81%] Building CXX object CMakeFiles/yoshimi.dir/MusicIO/WavRecord.cpp.o
> [ 82%] Building CXX object CMakeFiles/yoshimi.dir/main.cpp.o
> In file included from /mnt/Data/src/yoshimi-0.037/src/main.cpp:315:
> /usr/lib/gcc/i486-linux-gnu/4.3.3/include/xmmintrin.h:35:3: error:
> #error "SSE instruction set not enabled"
What cpu is this?
[ ...]
AMD Phenom X3:
peter@FreqHost:~$ lscpu
Architecture: i686
CPU(s): 3
Thread(s) per core: 1
Core(s) per socket: 3
CPU socket(s): 1
Vendor ID: AuthenticAMD
CPU family: 16
Model: 2
Stepping: 3
CPU MHz: 1050.000
Virtualization: AMD-V
L1d cache: 64K
L1i cache: 64K
L2 cache: 512K
L3 cache: 2048K
peter@FreqHost:~$ cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to
cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0
hardware limits: 1.05 GHz - 2.10 GHz
available frequency steps: 2.10 GHz, 1.05 GHz
available cpufreq governors: userspace, conservative, powersave, ondemand, performance
current policy: frequency should be within 1.05 GHz and 2.10 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 1.05 GHz.
cpufreq stats: 2.10 GHz:13.89%, 1.05 GHz:86.11% (251)
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 1
hardware limits: 1.05 GHz - 2.10 GHz
available frequency steps: 2.10 GHz, 1.05 GHz
available cpufreq governors: userspace, conservative, powersave, ondemand, performance
current policy: frequency should be within 1.05 GHz and 2.10 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.05 GHz.
cpufreq stats: 2.10 GHz:1.67%, 1.05 GHz:98.33% (6665)
11:01:56.676 Patchbay deactivated.
11:01:56.682 Statistics reset.
11:01:56.808 Startup script...
11:01:56.809 artsshell -q terminate
11:01:56.816 ALSA connection graph change.
11:01:57.966 Startup script terminated with exit status=256.
11:01:57.966 JACK is starting...
11:01:57.967 /usr/bin/jackd -R -p128 -u -dalsa -r44100 -p32 -n3 -D -Chw:M1010 -Phw:M1010 -Xseq -H -M
11:01:57.968 JACK was started with PID=3721.
Memory locking is unlimited - this is dangerous. Please alter the line @audio - memlock unlimitedin your /etc/limits.conf to @audio - memlock 2335929
no message buffer overruns
jackd 0.116.2
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:M1010|hw:M1010|32|3|44100|0|0|hwmon|hwmeter|-|32bit
configuring for 44100Hz, period = 32 frames (0.7 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 3 periods for playback
There actually is no /etc/limits.conf here.
Maybe I'll have to make one, or is AVLinux using a different setup?