It seems when you quit from the system tray icon (right-click->Quit),
qjackctl fails to execute script that is supposed to run after shutdown
(set on the options tab in the settings). Perhaps some timeout is
missing in there?
BTW, quitting from the regular GUI seems to work fine.
Best wishes,
Ico
This isn't a critical bug but for the sake of "correctness" it'd be
nice to have it fixed eventually:
Yoshimi writes a semaphore (sem.yoshimi) in /dev/shm during start but
doesn't remove it when closing. If another user on the same system
tries to start the program it won't work without a reboot or root
removing the file.
Howdy gentlebeings,
I have this USB card made by emagic before they were bought by Apple
lock, stock and barrel (the replacement MIDI cable that they send you
free of charge already has Apple Computer Germany written on the
package,, and the emagic site simply forwards you to apple.com) - is
anybody here familiar with such devices? They come in two flavours -
6|2 m with 6 RCA inputs and 2 outputs (or a single stereo output -
MIDI and SP/DIF functionality is also implemented as a single RCA
input and output, which can be switched between these modes - an
uncanny construction. The MIDI cable they sent me is in fact some
proprietary DIN to RCA adapter. Yeah. RCA jacks for MIDI - weird
innit? Anyway, a 2|6 m has two inputs and 6 outputs, and is identical
to the 6|2 m in all the other respects. The Linux kernel contains
dedicated modules as of version 2.6.31.4 (there used to be a single
driver for both cards IIRC); they are supposed to load firmware into
the card, which subsequently becomes controlled by snd-usb-audio. In
reality, the only time this card worked under GNU/Linux was back in
the epoch of dual booting - the Windows driver would load the firmware
into the card, and it remained functional after rebooting into
Kubuntu. This is no longer the case - I have banished the Redmond
demon, but everybody's favourite OS has apparently decided to surprise
me with an extra challenge. I don't mind as long as I get to see those
green LEDs again - the ones that succeed the single red LED that would
usually light for a second or two, and then give way to the green
messengers of success. Is anybody familiar with the card in question?
Did anybody ever manage to make this soundcard a fully functional
component of their penguin-friendly audio setup, with full support and
an infinitesimal latency? I certainly haven't as to yet - if there are
any insights , I'll be much obliged if you share them. Or should I
pester the kernel team instead?
Cheerio,
Mick
Well, perhaps I spoke too soon about LinuxSampler. I don't know why it
crashes on me at quit, and I don't know how to find out what to do. On
2009-10-12 I posted here:
http://bb.linuxsampler.org/viewtopic.php?f=6&t=402&sid=9eef1ca3cf9a983a65fc…
and although 36 views of the post have occurred, no suggestions are
available. I am going to try a little general cleanup, make one more
strong effort at JSampler, then try to compile LS+QS from source. I am
strongly thinking that the problem has something to do with the fact
that AVLinux is based on Debian Testing, whereas the LS debs are from
Lenny (Stable), which is in some ways quite legacy.
J.E.B.
OK. I got JSampler to mostly work (no preferences yet) by removing the
other two standard Debian Java environments, keeping Sun's version 6,
and setting up the path variables in /etc/profile. It has reported an
interesting anomaly: "Updating database directory: Cannot open
instruments database: /var/lib/linuxsampler/instruments.db". The
directory "/var/lib/linuxsampler" does not exist. Will be trying a few
things now, both Q and J.
J.E.B.
>> I hear you, and you're right, I use Linux live and have had exactly the
>> same thought. Behavior such as you're reporting, is why I won't use
>> Ubuntu and several other distros, including updated 64 Studio; I have
>> been where you are and won't go back :-).
> J.E.B, it's rather reassuring that I'm not the only guy on the planet
> using linux live. I was beginning to question my sanity lately....
I questioned mine for quite a while :-) I am going to also suggest that
we both try posting at the LinuxSampler forums. Many LS folks seem to be
very results-oriented.
>> If I were you, I would try
>> AVLinux, use its highly tweaked default kernel, and see how it works
for
>> you.
> Thanks! I'm now quite excited about AVlinux, downloading right away...
I will be eager to hear results. I also encourage you to set ALSA up
according to two patterns I recently learned right here; I have summarized
them here:
http://linuxaudio.joshuacorps.org/index.php?entry=entry091019-191706 [1]
I have found that better general stability is a result. I am beginning
to be convinced, that relying on ALSA device numbers, is a very bad idea on
many levels. And yet this is what every distro does right now.
Hopefully a change can be motivated.
> :)
> The sample IS a Bosendorfer sample. I also have a Steinway SF2 (the
same
> sample, perhaps?), which used to sound good to my ears.... UNTIL I
> discovered the sound of the Bosendorfer. Compromising on the sound is
> something I am NOT willing to do. I'm a pro musician first, linux
> afficianado next.
Well said, Guru. Given your words, I will probably just have to blow
the $ on the Bosendorfer (unless you found a free one?), because my
priorities are identical.
> So if I can't get linuxsampler to be stable, then I'm
> switching to OSX and Logic Pro.
> I'm looking forward to further suggestions on making jack (relatively)
> crash-proof. Meanwhile, I'm pinning my hopes on AVLinux... (and then
> Sabayon/UbuntuStudio-RT kernel... but I pray I never have to).
> Cheers,
> Guru
We will see. I will hopefully find myself motivated enough to go to the
LS forums in the next day or two :-)
J.E.B.
Links:
------
[1] http://linuxaudio.joshuacorps.org/index.php?entry=entry091019-191706
Greetings,
After reading the latest fanboy anti-Linux tirades on another site I
decided to relate a little story here on LAU.
One of my students has a 12-year old boy who wanted to build his own
computer. Even cooler, he wanted to install Linux on it. I gave him some
installation discs and spare parts, he ordered the rest of what he
needed, he assembled the machine himself after referencing various
articles on the net, and he just sent me a message to announce that he
had completed the work and was happily running Kubuntu Jaunty. He even
updated the mobo BIOS on his own, just to get the soundchip working
correctly. He's also installed and configured the nVidia proprietary
binary driver and is very happy with Compiz on his desktop.
So I have to ask, when I read comments from soi-disant "Linux-savvy"
folks who somehow can't seem to get their audio working (or even install
the system without aches & pains) and thus declare Linux dead in the
water re: audio work, are these people simply too impressed with what's
really just a little knowledge ? Is it possible that they're really not
so smart after all, and they just like to think they are ? I ask,
because a 12-year old boy with no special background in computers just
kicked their whingeing asses all the way from alpha to omega.
Adding to his achievement he has convinced his parents to switch the
family machines to Linux. He's now the only 12-year old I know whose
chores include Linux system administration. :)
Okay, that's all, and I feel better now. Sorry for the OT noise. EOF.
Best,
dp
Jörn Nettingsmeier wrote:
> that doesn't mean the system is within its limits. if you have, say, a
> background task running that will cause very short load spikes to 100%
> (which you won't necessarily see in any monitoring tool, as most do some
> averaging over time), and you don't have taken precautions to give your
> audio priority over those (by running jack in realtime mode and possibly
> by running an rt kernel), your audio will glitch, or worse, the audio
> will get stuck in the way you described.
>
> but for now, you will have to ensure that nothing
> ever stalls your audio processes.
>
> so:
> * run jackd as realtime
> * maybe increase the period size a bit (what are you using atm?)
> * kill background tasks (networkmanager, cron, ...)
> * try an rt kernel (31.4-rt14 gives me very good results)
>
Thanks Jörn, for the reply!
Sorry, I forgot to mention the following:
- I'm running the Ubuntu realtime kernel: 2.6.28-3-rt
- The 'realtime' option in qjackctl is checked
- I've also tried using icewm, and using 'free -m', I find that upto
500MB of memory is freed.
So I have the following questions:
- How do I check whether the realtime stuff is doing it's job properly?
- Which are the processes that I should manually kill?
- Apart from staring at the system monitor as I bang the keyboard, is
there a more scientific manner of logging a time-series of system
resource usage (of course, the time resolution would necessarily need to
be quite high), which will conclusively show that cpu usage actually
spiked just before the instant that jack crashed?
Jörn Nettingsmeier wrote:
maybe there is a way to make jack and applications more robust (just have a dropout, then continue as normal)
Now this sounds ideal! What do I do to make this happen? Is there some
way I can provide constructive feedback to the good folks behind jack
and applications? It would be next to tragic if, despite all those
wonderful applications, totalling thousands of man-hours of effort, nice
GUIs, so many thoughtful features, none of them are stage-worthy, from a
professional musician's perspective...
I eagerly look forward to your suggestions... I need help with this, and
would sincerely appreciate any pointers.
Cheers!
Guru
Hi all,
Thanks to off-list advice by Peter Plessas, I was able to resolve the
issue by running
sudo ldconfig
before running Aliki - this time successfully.
Thanks Peter, thanks list.
best,
flo.H
Florian Hollerweger <flo(a)mur.at> wrote:
I had my first go at compiling Aliki today. [...] However, I get an
libclxclient-related error message when running aliki:
aliki: error while loading shared libraries: libclxclient.so.3: cannot
open shared object file: No such file or directory
Hi all,
I had my first go at compiling Aliki today. I *did* compile the required
libraries by Fons (libclthreads, libclalsadrv, libclxclient) and decided
to stick with the default libsndfile and lifftw3f. The libraries as well
as Aliki itself seemed to compile without any problems.
However, I get an libclxclient-related error message when running aliki:
aliki: error while loading shared libraries: libclxclient.so.3: cannot
open shared object file: No such file or directory
The object file *is* actually present in /usr/local/lib - here is an
excerpt of an ls -lh on that directory:
lrwxrwxrwx 1 root root 21 2009-10-20 12:39 libclthreads.so ->
libclthreads.so.2.4.0
lrwxrwxrwx 1 root root 21 2009-10-20 12:39 libclthreads.so.2 ->
libclthreads.so.2.4.0
-rwxr-xr-x 1 root root 32K 2009-10-20 12:39 libclthreads.so.2.4.0
lrwxrwxrwx 1 root root 21 2009-10-20 12:39 libclxclient.so ->
libclxclient.so.3.6.1
lrwxrwxrwx 1 root root 21 2009-10-20 12:39 libclxclient.so.3 ->
libclxclient.so.3.6.1
-rwxr-xr-x 1 root root 134K 2009-10-20 12:39 libclxclient.so.3.6.1
The error appears no matter whether I install Aliki to /usr/bin or to
/usr/local/bin and no matter whether I run it as root or non-root.
Any ideas?
Thanks,
flo.H