Hi :)

I'm searching for the reason why all my Linux have to extreme
fluctuations in the timing of MIDI events, when using virtual
instruments that aren't plugins.

I often get the message "Cannot allocate memory", e.g. after starting Jack:

    "06:29:16.990 Patchbay deactivated.
    06:29:17.034 Statistics reset.
    06:29:17.052 Startup script...
    06:29:17.052 artsshell -q terminate
    06:29:17.058 ALSA connection graph change.
    06:29:17.472 Startup script terminated with exit status=256.
    06:29:17.473 JACK is starting...
    06:29:17.473 /usr/bin/jackd -R -dalsa -r44100 -p128 -n9 -D -Chw:0
    -Phw:0
    06:29:17.478 JACK was started with PID=5524.
    jackd 0.109.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.
    cannot lock down memory for jackd (Cannot allocate memory)
    loading driver ..
    Enhanced3DNow! detected
    SSE2 detected
    apparent rate = 44100
    creating alsa driver ...
    hw:0|hw:0|128|9|44100|0|0|nomon|swmeter|-|32bit
    control device hw:0
    configuring for 44100Hz, period = 128 frames (2.9 ms), buffer = 9
    periods
    ALSA: final selected sample format for capture: 32bit little-endian
    ALSA: use 9 periods for capture
    ALSA: final selected sample format for playback: 32bit little-endian
    ALSA: use 9 periods for playback
    JACK: unable to mlock() port buffers: Cannot allocate memory
    JACK: unable to mlock() port buffers: Cannot allocate memory
    06:29:17.684 Server configuration saved to "/home/spinymouse/.jackdrc".
    06:29:17.685 Statistics reset.
    06:29:17.686 Client activated.
    06:29:17.689 JACK connection change.
    06:29:17.691 ALSA connection change.
    06:29:17.701 JACK connection graph change.
    Enhanced3DNow! detected
    SSE2 detected
    cannot lock down memory for RT thread (Cannot allocate memory)"

Not only for Jack and not only for my unfavourable upgraded 64 Studio,
also for regular Linux without bold upgrades. If I end such a session
and start a new one for the same user, the memory is fine again. This
error only appears when starting audio RT applications.

What could be the cause for this error message?

Cheers,
Ralf

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
64studio-users mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-users

Reply via email to