I did it...I took the plunge. I opted to switch to 64Studio

  • jukingeo
Posted: Thu, 07/24/2008 - 13:39
Hello all, As you all may know from my prior postings, I been on Ubuntu Studio now for about 2 months. I been having continued problems with the Ubuntu Hardy Heron version and it has gotten to the point where I was searching for a new distribution that could handle audio/video editing work. After much fence sitting, smoke coming out of the head, and debating, I ended up with three options: 1) Stick with Ubuntu Studio (at least until the next release) 2) 64Studio 3) JackLab Out of the three, I heard of constant troubles with Ubuntu Studio...mainly because it is new and they really don't have all the kinks worked out of it. But it still looked good enough for me to mess around with. Besides of the three OS's, Ubuntu Studio was the only one that could partially support my SoundBlaster X-Fi card. JackLab proved to be a strong initial contender and I was going back and forth on this one. It has much going for it such as just about all drivers for hardware ready to go...so it would seem that JackLab was more plug-n-play. Also JackLab came set up with WineAsio for VST plug-in support. THAT was a strong point and it almost sealed the deal for me. Two things hindered this decision: 1) JackLab is OpenSuSE/Red Hat based, which would mean a new learning curve. I wasn't too fond of the idea of the countless hours I spent on Ubuntu Studio to have the knowledge I gained there not be garnered in this new OS. 2) The support just doesn't seem to be there. The forums are like a ghost town. I did sign up to the forums and when I posted there it would take DAYS for a response, whereas I did get used to having a response within hours over in the Ubuntu forums. Enter 64Studio This one I was totally unsure of. But right off the bat it had quite a few positives going for it: 1) Rock Solid build like JackLab 2) Better support than JackLab (but not as good as Ubuntu) 3) A familiar Debian based architecture, meaning less of a learning curve But being Debian, I was worried about configuring my system. Would I have the same troubles as I did with Ubuntu? Also it didn't seem that 64 Studio came with Wineasio set up for VST plug-in capability So, mainly because of my Soundblaster X-Fi issue, I decided to stick with Ubuntu Studio for a while just to learn some of the nice Linux applications it came with. In addition, I didn't own a DVD burner in which that was needed to burn the iso images for either JackLab OR 64Studio. However, that thought was short lived with I had a large problem with my system and my Windows installation became the victim of a partitioning error (my fault). So I decided to make changes to my system prior to reinstalling Windows. I changed my sound card from a SB X-Fi down to a SB Live (which is much more Linux compliant than the X-fi) and I installed a new DVD burner (since I am going to work with video anyway, having a DVD burner would be a necessity). Anyway, the change in sound cards caused a MAJOR problem with my video driver. So now I was out TWO operating systems. I went back to reinstall Windows and I got that up and running. But now it knocked out my Grub bootloader! At this point, because I had the DVD burner, there was nothing stopping me from switching OS's right then and there. Since it appeared Ubuntu Studio was now royally messed up via both Grub AND the video driver. Also I remembered that the OS didn't get as good reviews as either JackLab or 64Studio. So it was back to the fence, splinters in my butt, and smoke coming out of the ears. I decided that the knowledge garnered from my experiences with Ubuntu Studio and good support were paramount over features. I didn't want to loose more time on relearning a different OS. So it became very clear that 64Studio would be the choice. I broke-in my DVD burner last night with a fresh burn of a 64Studio installation .ISO. While I am on the thought of burning. I do have to say that most threads recommend the InfraBurner for burning of iso images. Forget about that program, it will NOT let you change the burning speed. Install this program instead. Click on the link below and scroll down to the Burn CDCC program: http://www.terabyteunlimited.com/downloads-free-software.htm I set it to 1x speed (I know rediculously slow) and it burned the disk in a few minutes. The installation seemed to go without a hitch but I do have a problem with Grub still (see my other posting in regards to Grub). However, I found I was able to get into 64Studio by doing a warm boot into the computer's boot menu and select the primary (first hard drive). Then Grub would come up and I could get into 64Studio. Overall impressions are FAN-TAS-TIC. The thing looks like Ubuntu Studio. So I know I would be in for less of a learning curve. First thing I looked for were my applications. Just about all of them were there as they were in Ubuntu Studio. I did find that Open Office, Evolution and Firefox was missing. BUT a quick find of Synaptic and I solved that problem by installing those packages. One thing though...I didn't need to install Firefox because 64Studio has a version of it already...but it is under the name IceWizard or something like that. I opened up Jack and the coveted real-time box was ticked. (I had a problem with this in Ubuntu Studio as well. Jack wouldn't run with RT, ticked. It kept crashing. I learned that my custom kernel that I needed to support the SB X-Fi card was NOT a real time kernel and this issue wouldn't be fixed unless I replaced the audio card. A good reason to get rid of the X-Fi, if you ask me). I only poked around very little in 64Studio as it was late and I was tired. My head was ready to hit the keyboard! So I will be looking foward to playing around with it some more tonight. I do have a question: Does anyone have some good links or advice for setting up WineAsio for use with VST plug-ins? Geo

You are right

  • Quentin Harley
  • 05/24/07
  • Fri, 07/25/2008 - 19:02
My main sound card is the combination of a 16ch i/o ADAT device plus the RME Hammerfall... USB midi only

USB Midi

  • Quentin Harley
  • 05/24/07
  • Fri, 07/25/2008 - 05:57
After struggling with a cheap sound card with built in midi ports, I ditched it as well in favour of an Edirol UM1SX. It is a usb device by Roland, and it offers only one port in and out, but it works out of the box, and I never had any issues getting it to work. I had to change my device order though, and for that check out the FAQ section.

What does life need?

  • jukingeo
  • 07/02/08
  • Fri, 07/25/2008 - 17:06
What does life need? Definitely MORE COWBELL!! Hello Quentin, I heard there are issues with USB and audio in Linux and that you could never get the performance of either PCI or Firewire. Granted that is what I heard in Ubuntu, 64Studio is a slightly different animal and may handle USB better. But even in Windows, I only used USB for Midi NEVER audio. So I am pretty much going to stick to my guns and stay with either Firewire or PCI. At any rate, I ended up going the PCI route. In a lucky strike, I landed a really nice ECHO MONA sound device. It is a beauty! It is also Linux Compliant. Check this out: http://www.echoaudio.com/Products/Discontinued/Mona/index.php The only thing it lacks is Midi, but I could always use a multi in/out USB device for that, such as a MIDIMAN MIDISPORT. I know I am going to need more than 2 midi in's anyway. But with 4 full pre-amp ins and 6 outs all jacks XLR balanced...I think it will handle my audio needs very well. It also sports both SPDIF and Optical digital I/O's as well. Geo

Configuring a RT kernel

  • porisija
  • 09/29/07
  • Thu, 07/24/2008 - 16:47
The most reliable way to build your own RealTime kernel is to use Ingo Molnar's realtime patch, but that involves some expert skills. Furthermore doing the patching is not sufficient if you wish to make a vanilla Linux installation realtime capable. PAM has to be configured too by editing /etc/limits.conf - check your 64Studio limits.conf-file with this command: cat /etc/limits.conf | less I recommend too sticking to the older SoundBlaster cards and ditching the X-Fi until ALSA has a driver for that. Or better yet, for the same money purchase a M-Audio Audiophile 24/96 card or some other M-Audio Delta series card. Reason: TJW - "they-just-work". Cheers!

@ porisija

  • sonictwin
  • 07/18/08
  • Thu, 08/21/2008 - 21:57
The correct path is /etc/
security/limits.conf Just to clarify :)

< Do you need to do that to

  • jukingeo
  • 07/02/08
  • Thu, 07/24/2008 - 17:22
<> Do you need to do that to get WineAsio and VST aps working? <> The X-Fi has been ditched. I reinstalled the old Soundblaster Live that came with the machine. The M-Audio delta series was the first series I looked into, but the features were just not enough for me unless you went for the huge 1010 model. Also another problem is that the M-Audio cards do not have mic pres. You have to buy that extra. Another problem is that the more affordable cards are also lacking midi input. So yeah, the card saves you money initially, but it could cost you more in the long run. At any rate, I landed this last night on Ebay: http://www.echoaudio.com/Products/Discontinued/Mona/index.php Pretty nice, huh? It is Linux/Alsa compliant. It is a 4in/6out unit. It has four pres and metering on the inputs and it has 6 XLR/RCA for the outputs. It has full optical AND SPDIF digital in/outs. The only thing that it lacks is Midi. But since I am working on a large midi project down the road, I will need something anyway with more than one set of ins/outs. So I can get a USB midi interface and should be good to go. Geo


  • Quentin Harley
  • 05/24/07
  • Thu, 07/24/2008 - 14:38
Depending on your version: i386: http://www.64studio.com/howto_vst amd64: http://www.64studio.com/node/636 (just up to the point before installing Reaper) Cheers,