Shortly after I burned my first ISO of PCLinuxOS, I configured my first serious desktop with a dual boot of Ubuntu Studio 8.04 and XP. As I recall I had many growing pains configuring my audio with UbuStu, however, at some point I was successful and was able to recompose a song I wrote in high-school using Rosegarden.
At some point, I decided to upgrade to UbuStu-9.04 as I had been enjoying the usability of Ubuntu-9.04 (Jaunty) and 9.10 (Karmic) at school. Sadly, I had some major issues with this install that forced me to move to Ubuntu-9.10. I knew I would probably try UbuStu-9.10 when it was released with the hope that the earlier incompatibility would be corrected. It seemed to work okay, however I could not get it to work with my Ralink Wirless card. Also, I was frustrated that the UbuStu developers didn't include some of the slick upgrades (namely the Ubuntu Software Center) that is steadily improving the usability of Ubuntu. I had no way of accessing the web without "ruining my life" so I moved on to 9.10 and decided to go on a significant "shopping spree." I installed loads of science, education and music apps from the Software Center, as well as the kernel-rt from synaptic.
The most significant challenge was getting the JACK audio server to run and I eventually found that I had to add my user to the "audio" and "pulse" groups under System -> Administration -> Users and Groups. The follwing URLs were helpful for me:
http://ubuntuforums.org/showthread.php?t=600626
http://ubuntuforums.org/showthread.php?t=1336078
http://ubuntuforums.org/showthread.php?t=453486
and most significantly:
http://ubuntuforums.org/showthread.php?t=1143784
I still get the following error from Rosegarden however:
System timer resolution is too low
Rosegarden was unable to find a high-resolution timing source for MIDI performance.
You may be able to solve this problem by loading the RTC timer kernel module. To do this, try running sudo modprobe snd-rtctimer in a terminal window and then restarting Rosegarden.
Alternatively, check whether your Linux distributor provides a multimedia-optimized kernel. See http://rosegarden.wiki.sourceforge.net/Low+latency+kernels for notes about this.
The genesis of this blog consists of the desire to track personal growth regarding: 1. Deployment of a linux digital audio workstation having the goal and mind-set of inexpensive expression whilst achieving computing and musical maturity. 2. General interests with an emphasis on linux, music, homebrewing, chemistry and some philosophizing. 3. Keeping a journal somewhere that I know I cannot lose it.
Showing posts with label Kernel. Show all posts
Showing posts with label Kernel. Show all posts
2.14.2010
10.31.2009
64 Studio: A solid DAW Desktop....almost
After the failure that was ubuntu studio 9.04, I thought I would look into any other possible solutions to my ultimate DAW desktop. Reading about the different choices, I settled on 64 Studio to try next, due in part to the fact that it is very similar to ubuntu with its debian roots. My first attempt at installation failed on one of the install steps, likely due to a bad burn/image download. I tried again, unscientifically adjusting all the variables: I downloaded the latest beta instead of the pronounced stable release (2.1) and I burned to a DVD-R instead of a DVD+R. The install completed.
One of the key comparisons made between 64 Studio and Ubuntu Studio is that the 64 Studio team was more selective in the applications added, and overall have worked harder at optimizing the "real-time" (RT) kernel to produce the lowest latencies in audio work. One of the problems I had recently with Ubuntu was the sound stopped working and sound is pretty critical for an audio studio. So far, the sound drivers are all working fine with 64 Studio, I just had to adjust the ALSAMixer the first go to get the correct channel unmuted.
But 64 Studio has yet to be completely trouble-free. For whatever reason, the latest kernel build 2.6.29 was not picking up my Ralink wireless network card. I did a little research and found someone else had this same problem but fixed it by rolling back the kernel to 2.6.26-1. I had to get creative with the network cables in the house to get them to stretch, but once connected to the WEB, I found that the commands: apt-get install kernel did not work right away, but somehow I eventually got it to work after running the update manager and installing a couple hundred other packages first.
I rebooted into the new kernel and sure enough, a wireless network option was now present in the network configuration dialog. Then in the course of an hour, I somehow picked up the wireless signal (rather quickly as I recall) and then later lost it and could not retrieve it. Somehow having success initially and then ending up back where you were feels worse then just failing at the outset!
One of the key comparisons made between 64 Studio and Ubuntu Studio is that the 64 Studio team was more selective in the applications added, and overall have worked harder at optimizing the "real-time" (RT) kernel to produce the lowest latencies in audio work. One of the problems I had recently with Ubuntu was the sound stopped working and sound is pretty critical for an audio studio. So far, the sound drivers are all working fine with 64 Studio, I just had to adjust the ALSAMixer the first go to get the correct channel unmuted.
But 64 Studio has yet to be completely trouble-free. For whatever reason, the latest kernel build 2.6.29 was not picking up my Ralink wireless network card. I did a little research and found someone else had this same problem but fixed it by rolling back the kernel to 2.6.26-1. I had to get creative with the network cables in the house to get them to stretch, but once connected to the WEB, I found that the commands: apt-get install kernel did not work right away, but somehow I eventually got it to work after running the update manager and installing a couple hundred other packages first.
I rebooted into the new kernel and sure enough, a wireless network option was now present in the network configuration dialog. Then in the course of an hour, I somehow picked up the wireless signal (rather quickly as I recall) and then later lost it and could not retrieve it. Somehow having success initially and then ending up back where you were feels worse then just failing at the outset!
Subscribe to:
Posts (Atom)