Thad E Ginathom
Well-Known Member
Warning: unless you have a very specific interest in the subject, you will find that this is one of the most boring things I've ever posted on the net. And that's saying something!
We touched on Linux issues in another interesting thread on PCs as an alternative to CD players.
I tried installing Ubuntu 11.04 in a separate partition. It doesn't even recognise that I have a firewire card :sad:. I also found adjustments to the desktop unstable, and it was a general pain, not only in the neck. This could be because I started off with an early-version image and updated from there. Some other day, I'll download a new image. Several hours, and several hundred Mb of bandwidth wasted.
Reverting to my usual 10.04 (with Ubuntu Studio additions) I thought I'd give it a try, fired up Jack, started VLC, plugged in the headphones (having failed to find the right cables for the speakers) and ... hey, it sounded nice. Nicer than my beloved RME, but jack is not stable.
Today, I dug deep for the TRS<--->TRS balanced cables that I must have bought just for this device, and confirmed that it sounded good on the speakers too, but still problematic with occasional drop outs, and, even if that were to happen even once an hour or so, it would still be unacceptable. The cheapest, nastiest kit at least plays a CD from beginning to end!
Taking time off from trying to improve matters with the jack parameters (one can vary it between silence and complete distortion!) I applied the question, "What's the point, if I can't, for example, listen to flash audio on the internet? It is one thing to get it working with programmes that can be told to output to it, but what about Firefox, Youtube, BBC, etc, etc, etc."
That took a bit of googling, and a bit of trial and error. Anyone with similar needs should start at the Jackaudio FAQs. I tried a couple of different approaches, but settled on the one described here: Jack and Loopback device as Alsa-to-Jack bridge. Yes, it is techie to the point of adding a load-at-boot-time module to the kernel, but, for the most part, the command-line and scripting stuff can be copied or cut&pasted from the instructions in that link. I don't pretend to understand just what I was doing!
I found the answers to some technical how-to questions (but hey, it was a world away from plugging something in and installing the drivers in Windows) and that was satisfying, but the result is still unusable. Even when it is playing nicely, any video output screws it up. Even scrolling up and down a web page.
1. I did turn off all the Compiz 3-d effects and stuff, but it may still be clashing with the proprietary video drivers.
2. The next step would be to start on the ladder of low-latency and then realtime kernels. This is much scarier than loading modules.
3. It might be my hardware.
4. It might be my face!
The next chapter... one day maybe...
We touched on Linux issues in another interesting thread on PCs as an alternative to CD players.
I unboxed it again yesterday, and have spent about a day in total messing around with it. I've had a silent house to myself for a couple of days. Just right for the task!I can understand a professional getting it together with Jack. There is some great music studio software for Linux, and, for a pro, it could be well worth while to spend the time tweaking those settings and getting it set up right. Honestly, I can't be bothered. My boxed Audiofire is a monument to that.
I tried installing Ubuntu 11.04 in a separate partition. It doesn't even recognise that I have a firewire card :sad:. I also found adjustments to the desktop unstable, and it was a general pain, not only in the neck. This could be because I started off with an early-version image and updated from there. Some other day, I'll download a new image. Several hours, and several hundred Mb of bandwidth wasted.
Reverting to my usual 10.04 (with Ubuntu Studio additions) I thought I'd give it a try, fired up Jack, started VLC, plugged in the headphones (having failed to find the right cables for the speakers) and ... hey, it sounded nice. Nicer than my beloved RME, but jack is not stable.
Today, I dug deep for the TRS<--->TRS balanced cables that I must have bought just for this device, and confirmed that it sounded good on the speakers too, but still problematic with occasional drop outs, and, even if that were to happen even once an hour or so, it would still be unacceptable. The cheapest, nastiest kit at least plays a CD from beginning to end!
Taking time off from trying to improve matters with the jack parameters (one can vary it between silence and complete distortion!) I applied the question, "What's the point, if I can't, for example, listen to flash audio on the internet? It is one thing to get it working with programmes that can be told to output to it, but what about Firefox, Youtube, BBC, etc, etc, etc."
That took a bit of googling, and a bit of trial and error. Anyone with similar needs should start at the Jackaudio FAQs. I tried a couple of different approaches, but settled on the one described here: Jack and Loopback device as Alsa-to-Jack bridge. Yes, it is techie to the point of adding a load-at-boot-time module to the kernel, but, for the most part, the command-line and scripting stuff can be copied or cut&pasted from the instructions in that link. I don't pretend to understand just what I was doing!
I found the answers to some technical how-to questions (but hey, it was a world away from plugging something in and installing the drivers in Windows) and that was satisfying, but the result is still unusable. Even when it is playing nicely, any video output screws it up. Even scrolling up and down a web page.
1. I did turn off all the Compiz 3-d effects and stuff, but it may still be clashing with the proprietary video drivers.
2. The next step would be to start on the ladder of low-latency and then realtime kernels. This is much scarier than loading modules.
3. It might be my hardware.
4. It might be my face!
The next chapter... one day maybe...