Re: What HW/SW do people have working?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Larry David wrote: > figure all this stuff out - I like the FOSS philosophy, and really hope Linux keeps growing - but it sounds like it may be a bit early for the humble user to try doing music with it. Am I wrong? > Probably :) In all seriousness, you will be as successful as you want > to be. As you say in a later post, you get what you pay for, in the > FLOSS world what you pay is your level of personal responsibility. > You > may have to go and find solutions to your issues, you may even have to > submit bug reports. > >> Interesting way to look at it. I am really drawn to the FLOSS thing, >> but its all new to me and I'm just getting my bearings. I can't tell >> yet whether as a "working musician" it will be better or worse in >> terms of getting things done - which at the end of the day is what >> its all about for me. > > - From my own experience, there have been many hours of frustration (I > switched to Linux as my Desktop OS about 10 years ago, and as my DAW > about 6 years ago). Things have gotten a lot better over the > years, and > I expect them to improve more in the future. In the end I have found > solutions or workarounds to almost all of my problems. Something that > cannot be said for the other two OSs that I have used over the years. > >> Hmm, I have been fortunate enough to have not owned a Windoze machine >> since 96 or 97, so I don't have recent experience with it. DP with >> MOTU hardware on my Macs however has been really solid - almost >> completely plug and play - and certainly very useable. > I have used Macs since the 80s, Windows since the early 90s, and Linux since ~98. I can say that Apple and Microsoft gave the personal computer a jump start, but all they have done since is hold us back. > The biggest challenge for me, was that I had to change my > workflow. I > was used to doing everything the Cubase way (ie. inside of Cubase). > Once I was able to get my head around jack and what it allows you > to, I > have not looked back. > > Anyway, my current setup is this: > AMD 64 (939) 4400+ X2, 3 GB of RAM. Standard SATA hard drive. > RME 9652 + RME ADI-8 DS + Alesis XT ADAT for 16 channels of > simultaneous > input. > M-Audio Axiom > > I like the RME PCI/PCIe stuff because it sounds great and is well > supported under Linux (ie. I do not have to do anything to get it to > work, it simply works). It is a shame that their firewire stuff does > not work, but RME is to blame for that. > > Before making a hardware purchase, do your research. I put this at > the > end so that you would remember it. Do your research! > >> Thanks for the info, that's really helpful. My next machine will be >> a laptop for work, that I will play with at home for music (I'm an >> independent contractor so I buy my own computers...). I've heard >> that Linux DAWs on laptops can be real buggers, if you get bad >> interrupt/bios something or other going on. Also I have 2 FW >> interfaces (though most Linux laptops I've seen - or Windows for that >> matter - no longer come with FW ports so I might have to switch to >> USB 2.0), and those aren't very friendly with Linux either (MOTU 828 >> mk II which FFADO website says is basically not supported, and the >> above mentioned Onyx 400F, also unsupported by FFADO). > For now, I would stick with Intel based machines. Your best bet would be to get Intel graphics, chipset/CPU, and Wifi. All of these should work out of the box. Very recent ATI video adaptors supported by the RadeonHD driver may be OK as well. I am a big fan of the Dell Latitude series. They are money but more solidly built than their other lines, and most of their competitors. They are also better bang for the buck when compared to Apple laptops at the same price point. My next laptop will be a Latitude E6400. I am currently using a Latitude D830. The one thing I dislike about the 830 is the nVidia GPU it came with. >> So does anyone have a Linux DAW running well on a laptop? I want to >> do my research before I buy! (Somehow that sounds vaguely familiar, >> like I've read that recently somewhere it'll come to me later...) > I do some work on the laptop, mostly mixing and editing stuff. I do actual recording on a Desktop PC with the 9652. I have not really messed with the USB devices too much so I cannot provide much help there. I am a big fan of the 9652 but you probably already knew that :) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkl/Ur8ACgkQwRXgH3rKGfNZDACdG3JkwTy+TyyuuKhtyXVOXPUO CF4An3pfnAK63ub6X5zqPKNekATkpeAp =hiLD -END PGP SIGNATURE- -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: What HW/SW do people have working?
Thanks Mac, A Lilnux laptop would have to do double duty for me; mobile office for work, and DAW for home. I will need wifi and Open Office (or equivalent) for work - need to be able to get online wirelessly from many different locations. Is the wifi problem you have related to something you have enabled/disabled for your DAW or is it just a coincidence? ld On Jan 27, 2009, at 6:56 AM, sue...@empire.net wrote: >> >> >> Original Message: >> - >> From: Larry David larrydavi...@comcast.net >> Date: Mon, 26 Jan 2009 21:33:39 -0500 >> To: ubuntu-studio-users@lists.ubuntu.com >> Subject: Re: What HW/SW do people have working? >> >> >> > >> >> >> So does anyone have a Linux DAW running well on a laptop? I want to >> do my research before I buy! (Somehow that sounds vaguely familiar, >> like I've read that recently somewhere it'll come to me >> later...) >> > > Hi Larry, > > My UBS 8.0.4 amd64 with firepod using Jack/freebob was solid (not > counting > the wifi that I can't get to work and is not important in DAW > land)...until > I took it upon myself to tinker with things like building the > latest Jack. > > The latop is a Dell XPS1530. > > Regards, > Mac > > > mail2web.com – What can On Demand Business Solutions do for you? > http://link.mail2web.com/Business/SharePoint > > > > -- > Ubuntu-Studio-users mailing list > Ubuntu-Studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/ > listinfo/ubuntu-studio-users -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: What HW/SW do people have working?
> > >Original Message: >- >From: Larry David larrydavi...@comcast.net >Date: Mon, 26 Jan 2009 21:33:39 -0500 >To: ubuntu-studio-users@lists.ubuntu.com >Subject: Re: What HW/SW do people have working? > > > > > >So does anyone have a Linux DAW running well on a laptop? I want to >do my research before I buy! (Somehow that sounds vaguely familiar, >like I've read that recently somewhere it'll come to me later...) > Hi Larry, My UBS 8.0.4 amd64 with firepod using Jack/freebob was solid (not counting the wifi that I can't get to work and is not important in DAW land)...until I took it upon myself to tinker with things like building the latest Jack. The latop is a Dell XPS1530. Regards, Mac mail2web.com What can On Demand Business Solutions do for you? http://link.mail2web.com/Business/SharePoint -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: What HW/SW do people have working?
On Mon, 26 Jan 2009 15:48:49 -0700 Gustin Johnson wrote: > I like the RME PCI/PCIe stuff because it sounds great and is well > supported under Linux (ie. I do not have to do anything to get it to > work, it simply works). It is a shame that their firewire stuff does > not work, but RME is to blame for that. Afaik there are firewire drivers for RME, just not in yet. I think you can find some more information on the RME forums. Not sure if the guy who writes them is related to RME but he sure is a big fan. hth -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: What HW/SW do people have working?
Larry David wrote: > So does anyone have a Linux DAW running well on a laptop? I want to > do my research before I buy! (Somehow that sounds vaguely familiar, > like I've read that recently somewhere it'll come to me later...) Yes. I posted my setup in our earlier conversation. Still at the FFADO wiki. http://subversion.ffado.org/wiki/A My Dell M1210 cost $600 on ebay. There are others there quite consistently. YMMV. -Scott -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: What HW/SW do people have working?
On Jan 26, 2009, at 5:48 PM, Gustin Johnson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Larry David wrote: >> Thanks Scott. I've gotten the impression that using audio/MIDI >> hardware on a Linux machine is sort of the opposite of plug-and-play; > > I have yet to actually use a computer that was "plug and play". They > all have little quirks and limitations. I will leave it at that since > Apple has a special place in my heart; the dark, bitter, cold, jaded, > and twisted part, so I doubt I can provide anything resembling an > unbiased comparison. Wow. I have my own beefs with Apple, but I'll leave that alone. :-) I agree and almost mentioned in my previous post, no computer DAW is plug and play (and I never claimed Apple was - only that it worked most of the time). I've been thinking about some of the debugging I've done with my Macs trying to get my DAW running. I have a Mackie Onyx 400F I bought a couple years ago when it first came out - amazing pres, but was just plain broken as a FW interface on both my G4 macs. It was well documented on forums and such - Apple blamed Mackie, Mackie blamed Apple, etc. I guess there are new drivers available recently that fixes it - years after initial release. That was a long and frustrating experience, but I must say it was the exception not the rule. But it has made me wonder how the situation would have been different if the driver/SW/OS were all open source - I couldn't have done much about the bugs, but surely someone else could have - more people probably than Apple and Mackie have had working on the problem. I guess I still have to get a feel for how big the Linux Audio community is, and the number of people who are actually working on bugs. Beggars can't be choosers, so I guess general users just wait it out until they are fixed? > >> and if your experience is typical, then that is an understatement. >> So is this kind of sleuthing and experimenting typical to get a Linux >> machine to do music? I'm not a programmer and don't have time to > > The bad news: There will be some sleuthing and experimenting. > The good news: You have already done this before. If you can use > google, ask questions, and follow directions you should be able to get > around most of the problems you encounter. > > I know you have said that your Mac experience was plug and play, > but it > really wasn't. Actually I never said so, see above; but I agree with the general idea that any DAW will require some set up. > You did have to learn how to use the software, you built > up a workflow, etc. There was actually a lot you had to figure out. Indeed. > >> figure all this stuff out - I like the FOSS philosophy, and really >> hope Linux keeps growing - but it sounds like it may be a bit early >> for the humble user to try doing music with it. Am I wrong? >> > Probably :) In all seriousness, you will be as successful as you want > to be. As you say in a later post, you get what you pay for, in the > FLOSS world what you pay is your level of personal responsibility. > You > may have to go and find solutions to your issues, you may even have to > submit bug reports. Interesting way to look at it. I am really drawn to the FLOSS thing, but its all new to me and I'm just getting my bearings. I can't tell yet whether as a "working musician" it will be better or worse in terms of getting things done - which at the end of the day is what its all about for me. > > - From my own experience, there have been many hours of frustration (I > switched to Linux as my Desktop OS about 10 years ago, and as my DAW > about 6 years ago). Things have gotten a lot better over the > years, and > I expect them to improve more in the future. In the end I have found > solutions or workarounds to almost all of my problems. Something that > cannot be said for the other two OSs that I have used over the years. Hmm, I have been fortunate enough to have not owned a Windoze machine since 96 or 97, so I don't have recent experience with it. DP with MOTU hardware on my Macs however has been really solid - almost completely plug and play - and certainly very useable. > > The biggest challenge for me, was that I had to change my > workflow. I > was used to doing everything the Cubase way (ie. inside of Cubase). > Once I was able to get my head around jack and what it allows you > to, I > have not looked back. > > Anyway, my current setup is this: > AMD 64 (939) 4400+ X2, 3 GB of RAM. Standard SATA hard drive. > RME 9652 + RME ADI-8 DS + Alesis XT ADAT for 16 channels of > simultaneous > input. > M-Audio Axiom > > I like the RME PCI/PCIe stuff because it sounds great and is well > supported under Linux (ie. I do not have to do anything to get it to > work, it simply works). It is a shame that their firewire stuff does > not work, but RME is to blame for that. > > Before making a hardware purchase, do your resear
Re: What HW/SW do people have working?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Larry David schrieb: > On Jan 25, 2009, at 10:51 PM, Scott wrote: > > > Now this is very interesting. RT means "real time", right? Is there > some real time capability that Linux has for processing audio that > Mac does not? I think, it is more or less the same as capable. In Linux you can have much better results with cheap hardware since the drivers do not try to implement any marketing policies- there is only one Linux driver for all cards, that come with a given chipset so you get the same driver for a cheap card with a decent chipset as you get for a pro-card with the very same (there are cards out there for Euro 50 and for Euro 500 - all with the same envy24-chip...). It takes a bit more configuration to make the stuff run but basically all of this is a 30-min point/click operation and should be done within a day even for someone, who has installed Linux the first time. In the end you can do the same: run your computers soundsystem stable with latencies below 10ms (and down to freakin fractions of a single millisecond, if you run one synth and a simple recorder only...) > true, that would be a big deal for me. And you say the apps are > awesome - I know about Ardour; is it really as good or better than > say Digital Performer or Logic or Protools (which I understand it is > trying to emulate)? Depends: I mostly record guitars/vocs etc accompanied by programmed drum loops - I have to programm the drums with a standalone seq plus sampler for Ardour 2.7 does NOT have MIDI-Tracks. I also use a standalone Guitar-Amp emulation for its quite clumsy to build an amp in ardour itself, so its basically the same, as if I would record from a real amp - - very OK with me... In the end I am perfectly happy with it and get quite OKayish results: http://lapoc.de/demos/lapoc-sos-ashita-141008.ogg - and that result-thing is, what one is out for is it not ? ;-) > What other music/audio apps are so great? Specimen (Sampler), Seq24 (fast, trustable sequencer), Hydrogen (Drumsequencer-suite), Rosegarden (big sequencer with scoreeditor), Qtractor (lean and mean audio/MIDI sequencer), AMS (great powerfull Modular-Synth - I build my guitamp with that), LMMS - fruityloops-like sequencer with a set of his own plugins A diversity of synths and more and more cool FX-plugins (LADSPA and LV2) we saw 2 new great releases of plugin-sets in this very week... There is a lot... But be careful: about 50% of the software available is abandoned/not working/experimental - all the tools named above belong to the other 50% see you ;-) HZN -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkl+Sx4ACgkQ1Aecwva1SWPauwCfWs6y1fEDLZNL9wSML0pF6LMo AYcAni2ThufZQU5s5o4seUBucBoGxlJm =hGYi -END PGP SIGNATURE- -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: What HW/SW do people have working?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Larry David wrote: > Thanks Scott. I've gotten the impression that using audio/MIDI > hardware on a Linux machine is sort of the opposite of plug-and-play; I have yet to actually use a computer that was "plug and play". They all have little quirks and limitations. I will leave it at that since Apple has a special place in my heart; the dark, bitter, cold, jaded, and twisted part, so I doubt I can provide anything resembling an unbiased comparison. > and if your experience is typical, then that is an understatement. > So is this kind of sleuthing and experimenting typical to get a Linux > machine to do music? I'm not a programmer and don't have time to The bad news: There will be some sleuthing and experimenting. The good news: You have already done this before. If you can use google, ask questions, and follow directions you should be able to get around most of the problems you encounter. I know you have said that your Mac experience was plug and play, but it really wasn't. You did have to learn how to use the software, you built up a workflow, etc. There was actually a lot you had to figure out. > figure all this stuff out - I like the FOSS philosophy, and really > hope Linux keeps growing - but it sounds like it may be a bit early > for the humble user to try doing music with it. Am I wrong? > Probably :) In all seriousness, you will be as successful as you want to be. As you say in a later post, you get what you pay for, in the FLOSS world what you pay is your level of personal responsibility. You may have to go and find solutions to your issues, you may even have to submit bug reports. - From my own experience, there have been many hours of frustration (I switched to Linux as my Desktop OS about 10 years ago, and as my DAW about 6 years ago). Things have gotten a lot better over the years, and I expect them to improve more in the future. In the end I have found solutions or workarounds to almost all of my problems. Something that cannot be said for the other two OSs that I have used over the years. The biggest challenge for me, was that I had to change my workflow. I was used to doing everything the Cubase way (ie. inside of Cubase). Once I was able to get my head around jack and what it allows you to, I have not looked back. Anyway, my current setup is this: AMD 64 (939) 4400+ X2, 3 GB of RAM. Standard SATA hard drive. RME 9652 + RME ADI-8 DS + Alesis XT ADAT for 16 channels of simultaneous input. M-Audio Axiom I like the RME PCI/PCIe stuff because it sounds great and is well supported under Linux (ie. I do not have to do anything to get it to work, it simply works). It is a shame that their firewire stuff does not work, but RME is to blame for that. Before making a hardware purchase, do your research. I put this at the end so that you would remember it. Do your research! Hth, -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkl+Pc0ACgkQwRXgH3rKGfMASACaA3xfTdsCNqytag4TOdmlhE5K aK0AoJwOGzn4LnB5zjj/CdmxjB40DW3E =780F -END PGP SIGNATURE- -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: What HW/SW do people have working?
On Jan 26, 2009, at 1:46 AM, Scott wrote: > This may answer your questions about xruns, > latency, etc. > > http://subversion.ffado.org/wiki/SomeNotesOnLatency > > Pay attention to the section titled "So why is the latency higher > than on OS XYZ?" In > any case, Thanks, that was very informative. (And I looked up xrun on wikipedia - duh - don't know why I didn't think of that before asking...) > >> Now this is very interesting. RT means "real time", right? Is >> there some real >> time capability that Linux has for processing audio that Mac does >> not? > > I don't know. I can run Linux on commodity hardware but a Mac > costs bank. Woo hoo! I will shamelessly adopt that phrase into my vocabulary. "_" costs bank! 10 coolness points... > A recent > email thread on the ffado-users list (or was it this list?) > discussed why Apple and > Microsoft wouldn't devote the resources to making an RT version of > their OS because > the proaudio community is too small to bother supporting, or > perhaps they just can't > do it. Again... I'm not a kernel hacker, I'm just good at > following directions. As the link you posted above suggests, Apple may think that < 10ms latency is good enough - and hence no need for an RT version of Mac OS (do I sound like I know what I'm talking about yet??... :-) This brings up the question of why RT capability is needed in the first place. Again based on your link above, latency below 10 ms may be undetectable when playing soft synths (since it takes about 3 ms for sound to travel 1 m - can you notice a difference in latency if you move closer or further from your speakers when plugged directly into an amp? I can't...) So that leaves the ability to playback and record at the same time (forgot the fancy term for that ...). I can see the usefulness of that for punching into a multitrack recording, but Digital Performer 4 on my old powerbook can do that very easily if I tell it where to punch in beforehand (which is not a big limitation) - it just preloads buffers or whatever so that there is no glitch/delay when the punch happens. Seems like a Linux DAW could be programmed to do the same thing - so what is the great benefit of RT? > >> I really want to be convinced that Linux is the way to go - >> cheaper machine and >> free SW - can't beat that with a stick. But I'm very skeptical - >> you get what you >> pay for and all that... > > You can always contribute to the cause. Donate buttons are on the > right side of the > page at http://ardour.org. Hehe, well thanks for the tip, but I was actually not so concerned about the "pay" part as much as the "get" part. Ardour is what it is whether I pay for it or not. (And I would gladly make at least a token donation if I ended up using it.) I'm more concerned about how functional it could be if it is developed for free - I mean a man's gotta make a living and that sounds like more than a full time job. > >> ld > > BTW, I loved Curb Your Enthusiasm. :^) Thank you. I have moved on to other things now, obviously. I had my fortune in the stock market and now live in a van down by the river; hence my interest in a Linux machine for music, since a new Mac costs bank, baby! ld > > -- > Ubuntu-Studio-users mailing list > Ubuntu-Studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/ > listinfo/ubuntu-studio-users -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: What HW/SW do people have working?
sue...@empire.net wrote: > - I was under the impression that to get rt kernel in 8.10 the kernel had > to be compiled locally. So was I. I've heard that the RT kernel I'm using "isn't very good". However, it's working for me. The guide I posted on the wiki says just run 'sudo apt-get install linux-rt' so that's pretty easy. > - do you have any comparison between the freebob drivers and the ffado. (I > realize the later are the new generation, do they improve life with > firewire?) I didn't get involved in this project until recently when the FFADO driver become more stable. I've never used freebob. > - have you attempted to use more than one audiofire12? (i.e. two = 24 > channels in) No. My laptop only has one built-in firewire port. I have an ExpressCard with a TI chipset firewire adaptor but merely plugging it in causes my machine to hang. If I can get it to work perhaps I'll get another AF12 and do some testing. If anyone wants to send one to me that'd be cool :^). -Scott -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: What HW/SW do people have working?
Scott, Couple of questions: - I was under the impression that to get rt kernel in 8.10 the kernel had to be compiled locally. - do you have any comparison between the freebob drivers and the ffado. (I realize the later are the new generation, do they improve life with firewire?) - have you attempted to use more than one audiofire12? (i.e. two = 24 channels in) BR, Mac Original Message: - From: Scott ubuntustu...@troutpocket.org Date: Sun, 25 Jan 2009 13:34:20 -0800 To: ubuntu-studio-users@lists.ubuntu.com Subject: Re: What HW/SW do people have working? Larry David wrote: > Hi - I'm a Mac user and musician. I'm thinking of switching to Linux > with my next laptop, and am wondering what people are using for audio/ > MIDI interfaces, and what software - DAW, plugins, softsynths, etc.? I have a little Dell XPS 1210 which I recently got working for my modest little music studio. All the details were in this post to the FFADO list: http://sourceforge.net/mailarchive/forum.php?thread_name=496C1F6E.9080701%40 troutpocket.org&forum_name=ffado-user Here it is in all its posterity: Well, I got it all working. I wanted to share my progress with everyone by editing the wiki but I don't have access to that. Here's what I did (in a nutshell): My Kit: Dell XPS M1210 laptop 1GB RAM Intel T5600 1.8GHz Core2Duo Intel 945GM Video controller Sigmatel 9220 internal audio controller Internal Ricoh Co Ltd R5C832 IEEE 1394 Controller http://tinyurl.com/clr43l EchoAudio Audiofire12 http://www.echoaudio.com/Products/FireWire/AudioFire12/index.php Ubuntu Studio 8.10 with RT (realtime) kernel Steps: 1. Install UbuntuStudio 8.10. 2. Install all updates via update manager 3. Install RT kernel ~$ sudo apt-get install linux-rt 4. Install ffado drivers and accompanying libraries In Synaptic Package Manager choose Settings/Repositories. In the Software Sources window choose the Third-Party Software tab. Add the following: deb http://www.ffado.org/apt gutsy contrib Reload your package manager and install the following: ffado-dbus-server ffado-mixer-qt4 ffado-tools jackd-firewire-driver libffado2 libffado2-dev (just in case) 5. Configure grub to boot RT kernel by default ~$ sudo vim /boot/grub/menu.lst edit the line: default 0 to say default 4 or whatever number (counting from 0) is your rt entry in the file. If you don't do this you have to manually choose it at boot every time. 6. Add yourself to the disk and audio groups. If the audio group doesn't already exist you can create it with the optional first command. ~$ sudo groupadd audio (optional step if audio group doesn't exist) ~$ sudo adduser disk ~$ sudo adduser audio 7. Adjust limits.conf to accommodate your RT kernel. ~$ sudo su -c 'echo @audio - rtprio 99 >> /etc/security/limits.conf' ~$ sudo su -c 'echo @audio - nice -19 >> /etc/security/limits.conf' ~$ sudo su -c 'echo @audio - memlock unlimited >> /etc/security/limits.conf' 8. Reboot to your RT kernel! After you system is up and running you'll have to start jackd. I recommend using qjackctl to do this as it has a patchbay manager. Make sure everything is plugged in and running then start qjackctl (found in Sound & Video/Audio Production/JACK Control) 9. You must install the raw1394 kernel module. Unfortunately my ability to get this to stick hasn't worked. No problem, just run the following short command after each boot: ~$ sudo modprobe raw1394 10. Here are the changes I made to the default jackd config by clicking Setup: Driver = firewire Realtime (checked) Priority = 70 Frames/Period = 64 Sample Rate = 48000 Periods/Buffer = 3 Port Maximum = 128 Interface = hw:0 Start Delay = 2 11. Click the Patchbay button. Click the New button and let it discover your port configurations itself. Mine showed System with 12 capture ports listed under Output and it showed System with 12 playback ports under Input. Select System in both windows and choose Connect. You may have to click the Activate though I don't really know exactly what that does. Click the start button and pray for no xruns. Following these exact steps I've been able to successfully record in Ardour for 30ish minutes without xruns or program errors. It may go longer but I haven't bothered trying yet. The big hurdle I encountered was outdated information on many websites. First of a
Re: What HW/SW do people have working?
Larry David wrote: > On Jan 25, 2009, at 10:51 PM, Scott wrote: > >> Larry David wrote: >>> Are you using a Linux machine regularly to do audio/MIDI and finding it >>> solid >>> and useable, or is this still mostly an experiment to see what you can get >>> running and for how long? >> I'm not doing any MIDI, just audio recording 12 tracks in Ardour. It's >> working >> 100% with no xruns or crashes. My longest continuous session was 45 minutes >> before I stopped it to save. I'm actually a little surprised it's working so >> well in 8.10 considering it was complete trash in 8.04. > > I see, that's very interesting. Please forgive my complete ignorance of all > things > Linux, but what's an xrun? Do you know why Ardour works for you in 8.10 and > didn't > in 8.04? I mean did you figure something out or did you do everything the > same and > it just worked differently? I did everything in 8.10 as I did it in 8.04. I honestly don't know what's different since I'm just a user, not a programmer. This may answer your questions about xruns, latency, etc. http://subversion.ffado.org/wiki/SomeNotesOnLatency Pay attention to the section titled "So why is the latency higher than on OS XYZ?" In any case, > Now this is very interesting. RT means "real time", right? Is there some > real > time capability that Linux has for processing audio that Mac does not? I don't know. I can run Linux on commodity hardware but a Mac costs bank. A recent email thread on the ffado-users list (or was it this list?) discussed why Apple and Microsoft wouldn't devote the resources to making an RT version of their OS because the proaudio community is too small to bother supporting, or perhaps they just can't do it. Again... I'm not a kernel hacker, I'm just good at following directions. > I really want to be convinced that Linux is the way to go - cheaper machine > and > free SW - can't beat that with a stick. But I'm very skeptical - you get > what you > pay for and all that... You can always contribute to the cause. Donate buttons are on the right side of the page at http://ardour.org. > ld BTW, I loved Curb Your Enthusiasm. :^) -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: What HW/SW do people have working?
On Jan 25, 2009, at 10:51 PM, Scott wrote: > Larry David wrote: >> Are you using a Linux machine regularly to do audio/MIDI and finding >> it solid and useable, or is this still mostly an experiment to see >> what you can get running and for how long? > > I'm not doing any MIDI, just audio recording 12 tracks in Ardour. > It's working 100% > with no xruns or crashes. My longest continuous session was 45 > minutes before I > stopped it to save. I'm actually a little surprised it's working > so well in 8.10 > considering it was complete trash in 8.04. I see, that's very interesting. Please forgive my complete ignorance of all things Linux, but what's an xrun? Do you know why Ardour works for you in 8.10 and didn't in 8.04? I mean did you figure something out or did you do everything the same and it just worked differently? > > About 5 years ago I had an old DAW that ran in NT4 and used a PCI > audio capture card. > It crashed about 1 in 5 times and both the hardware and software > folks claimed that > was normal. There was no win2k or newer support and it suffered > from a 1/2 second > recording delay. That was the biggest pain because it required > tons of > post-production editing. I think Windows machines crash more and are generally not as good for music apps as Macs - I know that's a generalization and I'm not trying to be a snob - but Mac has always catered more to multimedia, and Windows to business. The fact that Mac OS only runs on Apple machines, and MOTU hardware and software is developed and tested on the exact same machines that users have, makes it run a lot more smoothly than Windows DAWs. There are still problems occasionally of course, but like I said before, Mac+MOTU just plain works 99.9% of the time. > > RT provides for only a 2ms delay which is a dream... I just hit > record and can punch > in/out at will then export to an audio file. Even a Mac or PC > can't match that. If > it wasn't for RT capability I wouldn't have bothered with Linux. > The fact that my day > to day work takes place in the context of Linux helps, but it > wasn't the deciding > factor in choosing an OS to host my audio tools. I'd use a > Nintendo if the quality > and applications were as awesome as those available to Linux :^). Now this is very interesting. RT means "real time", right? Is there some real time capability that Linux has for processing audio that Mac does not? Does the Mac CoreAudio or whatever it is not provide the same functionality? I've never heard it claimed that Linux was *better* than Macs (or anything else) for music/audio, but if that's true, that would be a big deal for me. And you say the apps are awesome - I know about Ardour; is it really as good or better than say Digital Performer or Logic or Protools (which I understand it is trying to emulate)? What other music/audio apps are so great? I really want to be convinced that Linux is the way to go - cheaper machine and free SW - can't beat that with a stick. But I'm very skeptical - you get what you pay for and all that... But maybe the FOSS movement/whatever can change that, at least with regards to SW. ld > > -Scott > > -- > Ubuntu-Studio-users mailing list > Ubuntu-Studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/ > listinfo/ubuntu-studio-users -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: What HW/SW do people have working?
Larry David wrote: > Are you using a Linux machine regularly to do audio/MIDI and finding > it solid and useable, or is this still mostly an experiment to see > what you can get running and for how long? I'm not doing any MIDI, just audio recording 12 tracks in Ardour. It's working 100% with no xruns or crashes. My longest continuous session was 45 minutes before I stopped it to save. I'm actually a little surprised it's working so well in 8.10 considering it was complete trash in 8.04. About 5 years ago I had an old DAW that ran in NT4 and used a PCI audio capture card. It crashed about 1 in 5 times and both the hardware and software folks claimed that was normal. There was no win2k or newer support and it suffered from a 1/2 second recording delay. That was the biggest pain because it required tons of post-production editing. RT provides for only a 2ms delay which is a dream... I just hit record and can punch in/out at will then export to an audio file. Even a Mac or PC can't match that. If it wasn't for RT capability I wouldn't have bothered with Linux. The fact that my day to day work takes place in the context of Linux helps, but it wasn't the deciding factor in choosing an OS to host my audio tools. I'd use a Nintendo if the quality and applications were as awesome as those available to Linux :^). -Scott -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: What HW/SW do people have working?
Ok, well that's not so bad. I actually like CLI for certain things, and know some Unix. It seems like the hard part is not downloading/ installing stuff, but figuring out what to install and what not to, with what options, parameters, etc. And it seems that most modern audio/MIDI hardware is not supported - like my MOTU 828 mkII (which is several years old and now outdated by the new mkIII). Then people talk about how many minutes they can run Ardour without any crashes or problems and I'm thinking this is still the bleeding edge. I deal with bugs and glitches sometimes with Digital Performer on my Macs, but in general it just works. Are you using a Linux machine regularly to do audio/MIDI and finding it solid and useable, or is this still mostly an experiment to see what you can get running and for how long? Many thanks for the shared wisdom... (and anyone else with experience to share please chime in) ld On Jan 25, 2009, at 9:33 PM, Scott wrote: > There was definitely no programming skill involved. All I did was > install some > packages from the repo. If you started with a blank mac or windows > machine you'd go > through similar steps to get it up and running. My command line > stuff can all be done > in the GUI if cli isn't your bag. > > It's definitely worth doing in Linux for the RT kernel > capabilities. Anyway, the > entire process took about 10 minutes with a fast download connection. > > -Scott > > Larry David wrote: >> Thanks Scott. I've gotten the impression that using audio/MIDI >> hardware on a Linux machine is sort of the opposite of plug-and-play; >> and if your experience is typical, then that is an understatement. >> So is this kind of sleuthing and experimenting typical to get a Linux >> machine to do music? I'm not a programmer and don't have time to >> figure all this stuff out - I like the FOSS philosophy, and really >> hope Linux keeps growing - but it sounds like it may be a bit early >> for the humble user to try doing music with it. Am I wrong? >> >> Thanks again, >> ld >> >> >> On Jan 25, 2009, at 4:34 PM, Scott wrote: >> >>> Larry David wrote: Hi - I'm a Mac user and musician. I'm thinking of switching to Linux with my next laptop, and am wondering what people are using for audio/ MIDI interfaces, and what software - DAW, plugins, softsynths, etc.? >>> I have a little Dell XPS 1210 which I recently got working for my >>> modest little music >>> studio. All the details were in this post to the FFADO list: >>> >>> http://sourceforge.net/mailarchive/forum.php?thread_name=496C1F6E. >>> 9080701%40troutpocket.org&forum_name=ffado-user >>> >>> Here it is in all its posterity: >>> >>> Well, I got it all working. I wanted to share my progress with >>> everyone by editing >>> the wiki but I don't have access to that. Here's what I did (in a >>> nutshell): >>> >>> My Kit: >>> Dell XPS M1210 laptop >>> 1GB RAM >>> Intel T5600 1.8GHz Core2Duo >>> Intel 945GM Video controller >>> Sigmatel 9220 internal audio controller >>> Internal Ricoh Co Ltd R5C832 IEEE 1394 Controller >>> http://tinyurl.com/clr43l >>> >>> EchoAudio Audiofire12 >>> http://www.echoaudio.com/Products/FireWire/AudioFire12/index.php >>> >>> Ubuntu Studio 8.10 with RT (realtime) kernel >>> >>> Steps: >>> 1. Install UbuntuStudio 8.10. >>> >>> 2. Install all updates via update manager >>> >>> 3. Install RT kernel >>> ~$ sudo apt-get install linux-rt >>> >>> 4. Install ffado drivers and accompanying libraries >>> In Synaptic Package Manager choose Settings/Repositories. In the >>> Software >>> Sources window choose the Third-Party Software tab. Add the >>> following: >>> deb http://www.ffado.org/apt gutsy contrib >>> Reload your package manager and install the following: >>> ffado-dbus-server >>> ffado-mixer-qt4 >>> ffado-tools >>> jackd-firewire-driver >>> libffado2 >>> libffado2-dev (just in case) >>> >>> 5. Configure grub to boot RT kernel by default >>> ~$ sudo vim /boot/grub/menu.lst >>> edit the line: >>> default 0 >>> to say >>> default 4 >>> or whatever number (counting from 0) is your rt entry in the >>> file. If you >>> don't do this you have to manually choose it at boot every time. >>> >>> 6. Add yourself to the disk and audio groups. If the audio >>> group doesn't already >>>exist you can create it with the optional first command. >>> ~$ sudo groupadd audio (optional step if audio group doesn't exist) >>> ~$ sudo adduser disk >>> ~$ sudo adduser audio >>> >>> 7. Adjust limits.conf to accommodate your RT kernel. >>> ~$ sudo su -c 'echo @audio - rtprio 99 >> /etc/security/ >>> limits.conf' >>> ~$ sudo su -c 'echo @audio - nice -19 >> /etc/security/limits.conf' >>> ~$ sudo su -c 'echo @audi
Re: What HW/SW do people have working?
On Sunday 25 January 2009 09:21:19 am Larry David wrote:
> Hi - I'm a Mac user and musician. I'm thinking of switching to Linux
> with my next laptop, and am wondering what people are using for audio/
> MIDI interfaces, and what software - DAW, plugins, softsynths, etc.?
>
> It looks like developers are doing lots of exciting things with Linux
> and music (at CCRMA etc.), but what is the state of things for users
> who just want to make music and not tinker with code and spend lots
> of time debugging? Does anyone have a setup that just works?
>
> Thanks for the info.
>
> ld
Check out the LAU {Linux Audio Users} list. Very active list.
http://lad.linuxaudio.org/subscribe/lau.html
the archive is a treasure trove
http://lalists.stanford.edu/
Tom
--
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: What HW/SW do people have working?
There was definitely no programming skill involved. All I did was install some packages from the repo. If you started with a blank mac or windows machine you'd go through similar steps to get it up and running. My command line stuff can all be done in the GUI if cli isn't your bag. It's definitely worth doing in Linux for the RT kernel capabilities. Anyway, the entire process took about 10 minutes with a fast download connection. -Scott Larry David wrote: > Thanks Scott. I've gotten the impression that using audio/MIDI > hardware on a Linux machine is sort of the opposite of plug-and-play; > and if your experience is typical, then that is an understatement. > So is this kind of sleuthing and experimenting typical to get a Linux > machine to do music? I'm not a programmer and don't have time to > figure all this stuff out - I like the FOSS philosophy, and really > hope Linux keeps growing - but it sounds like it may be a bit early > for the humble user to try doing music with it. Am I wrong? > > Thanks again, > ld > > > On Jan 25, 2009, at 4:34 PM, Scott wrote: > >> Larry David wrote: >>> Hi - I'm a Mac user and musician. I'm thinking of switching to Linux >>> with my next laptop, and am wondering what people are using for >>> audio/ >>> MIDI interfaces, and what software - DAW, plugins, softsynths, etc.? >> I have a little Dell XPS 1210 which I recently got working for my >> modest little music >> studio. All the details were in this post to the FFADO list: >> >> http://sourceforge.net/mailarchive/forum.php?thread_name=496C1F6E. >> 9080701%40troutpocket.org&forum_name=ffado-user >> >> Here it is in all its posterity: >> >> Well, I got it all working. I wanted to share my progress with >> everyone by editing >> the wiki but I don't have access to that. Here's what I did (in a >> nutshell): >> >> My Kit: >> Dell XPS M1210 laptop >> 1GB RAM >> Intel T5600 1.8GHz Core2Duo >> Intel 945GM Video controller >> Sigmatel 9220 internal audio controller >> Internal Ricoh Co Ltd R5C832 IEEE 1394 Controller >> http://tinyurl.com/clr43l >> >> EchoAudio Audiofire12 >> http://www.echoaudio.com/Products/FireWire/AudioFire12/index.php >> >> Ubuntu Studio 8.10 with RT (realtime) kernel >> >> Steps: >> 1. Install UbuntuStudio 8.10. >> >> 2. Install all updates via update manager >> >> 3. Install RT kernel >> ~$ sudo apt-get install linux-rt >> >> 4. Install ffado drivers and accompanying libraries >> In Synaptic Package Manager choose Settings/Repositories. In the >> Software >> Sources window choose the Third-Party Software tab. Add the >> following: >> deb http://www.ffado.org/apt gutsy contrib >> Reload your package manager and install the following: >> ffado-dbus-server >> ffado-mixer-qt4 >> ffado-tools >> jackd-firewire-driver >> libffado2 >> libffado2-dev (just in case) >> >> 5. Configure grub to boot RT kernel by default >> ~$ sudo vim /boot/grub/menu.lst >> edit the line: >> default 0 >> to say >> default 4 >> or whatever number (counting from 0) is your rt entry in the >> file. If you >> don't do this you have to manually choose it at boot every time. >> >> 6. Add yourself to the disk and audio groups. If the audio >> group doesn't already >>exist you can create it with the optional first command. >> ~$ sudo groupadd audio (optional step if audio group doesn't exist) >> ~$ sudo adduser disk >> ~$ sudo adduser audio >> >> 7. Adjust limits.conf to accommodate your RT kernel. >> ~$ sudo su -c 'echo @audio - rtprio 99 >> /etc/security/limits.conf' >> ~$ sudo su -c 'echo @audio - nice -19 >> /etc/security/limits.conf' >> ~$ sudo su -c 'echo @audio - memlock unlimited >> /etc/security/ >> limits.conf' >> >> 8. Reboot to your RT kernel! >> >> After you system is up and running you'll have to start jackd. I >> recommend using >> qjackctl to do this as it has a patchbay manager. Make sure >> everything is plugged in >> and running then start qjackctl (found in Sound & Video/Audio >> Production/JACK Control) >> >> 9. You must install the raw1394 kernel module. Unfortunately my >> ability to get this >>to stick hasn't worked. No problem, just run the following >> short command after >>each boot: >> ~$ sudo modprobe raw1394 >> >> 10. Here are the changes I made to the default jackd config by >> clicking Setup: >> Driver = firewire >> Realtime (checked) >> Priority = 70 >> Frames/Period = 64 >> Sample Rate = 48000 >> Periods/Buffer = 3 >> Port Maximum = 128 >> Interface = hw:0 >> Start Delay = 2 >> >> 11. Click the Patchbay button. Click the New button and let it >> discover your >> port conf
Re: What HW/SW do people have working?
Thanks Scott. I've gotten the impression that using audio/MIDI hardware on a Linux machine is sort of the opposite of plug-and-play; and if your experience is typical, then that is an understatement. So is this kind of sleuthing and experimenting typical to get a Linux machine to do music? I'm not a programmer and don't have time to figure all this stuff out - I like the FOSS philosophy, and really hope Linux keeps growing - but it sounds like it may be a bit early for the humble user to try doing music with it. Am I wrong? Thanks again, ld On Jan 25, 2009, at 4:34 PM, Scott wrote: > Larry David wrote: >> Hi - I'm a Mac user and musician. I'm thinking of switching to Linux >> with my next laptop, and am wondering what people are using for >> audio/ >> MIDI interfaces, and what software - DAW, plugins, softsynths, etc.? > > I have a little Dell XPS 1210 which I recently got working for my > modest little music > studio. All the details were in this post to the FFADO list: > > http://sourceforge.net/mailarchive/forum.php?thread_name=496C1F6E. > 9080701%40troutpocket.org&forum_name=ffado-user > > Here it is in all its posterity: > > Well, I got it all working. I wanted to share my progress with > everyone by editing > the wiki but I don't have access to that. Here's what I did (in a > nutshell): > > My Kit: > Dell XPS M1210 laptop > 1GB RAM > Intel T5600 1.8GHz Core2Duo > Intel 945GM Video controller > Sigmatel 9220 internal audio controller > Internal Ricoh Co Ltd R5C832 IEEE 1394 Controller > http://tinyurl.com/clr43l > > EchoAudio Audiofire12 > http://www.echoaudio.com/Products/FireWire/AudioFire12/index.php > > Ubuntu Studio 8.10 with RT (realtime) kernel > > Steps: > 1. Install UbuntuStudio 8.10. > > 2. Install all updates via update manager > > 3. Install RT kernel > ~$ sudo apt-get install linux-rt > > 4. Install ffado drivers and accompanying libraries > In Synaptic Package Manager choose Settings/Repositories. In the > Software > Sources window choose the Third-Party Software tab. Add the > following: > deb http://www.ffado.org/apt gutsy contrib > Reload your package manager and install the following: > ffado-dbus-server > ffado-mixer-qt4 > ffado-tools > jackd-firewire-driver > libffado2 > libffado2-dev (just in case) > > 5. Configure grub to boot RT kernel by default > ~$ sudo vim /boot/grub/menu.lst > edit the line: > default 0 > to say > default 4 > or whatever number (counting from 0) is your rt entry in the > file. If you > don't do this you have to manually choose it at boot every time. > > 6. Add yourself to the disk and audio groups. If the audio > group doesn't already >exist you can create it with the optional first command. > ~$ sudo groupadd audio (optional step if audio group doesn't exist) > ~$ sudo adduser disk > ~$ sudo adduser audio > > 7. Adjust limits.conf to accommodate your RT kernel. > ~$ sudo su -c 'echo @audio - rtprio 99 >> /etc/security/limits.conf' > ~$ sudo su -c 'echo @audio - nice -19 >> /etc/security/limits.conf' > ~$ sudo su -c 'echo @audio - memlock unlimited >> /etc/security/ > limits.conf' > > 8. Reboot to your RT kernel! > > After you system is up and running you'll have to start jackd. I > recommend using > qjackctl to do this as it has a patchbay manager. Make sure > everything is plugged in > and running then start qjackctl (found in Sound & Video/Audio > Production/JACK Control) > > 9. You must install the raw1394 kernel module. Unfortunately my > ability to get this >to stick hasn't worked. No problem, just run the following > short command after >each boot: > ~$ sudo modprobe raw1394 > > 10. Here are the changes I made to the default jackd config by > clicking Setup: > Driver = firewire > Realtime (checked) > Priority = 70 > Frames/Period = 64 > Sample Rate = 48000 > Periods/Buffer = 3 > Port Maximum = 128 > Interface = hw:0 > Start Delay = 2 > > 11. Click the Patchbay button. Click the New button and let it > discover your > port configurations itself. Mine showed System with 12 > capture ports listed > under Output and it showed System with 12 playback ports > under Input. Select > System in both windows and choose Connect. You may have to > click the Activate > though I don't really know exactly what that does. > > Click the start button and pray for no xruns. Following these > exact steps I've been > able to successfully record in Ardour for 30ish minutes without > xruns or program > errors. It may go longer but I haven't bothered trying yet. > > The b
Re: What HW/SW do people have working?
Larry David wrote: > Hi - I'm a Mac user and musician. I'm thinking of switching to Linux > with my next laptop, and am wondering what people are using for audio/ > MIDI interfaces, and what software - DAW, plugins, softsynths, etc.? I have a little Dell XPS 1210 which I recently got working for my modest little music studio. All the details were in this post to the FFADO list: http://sourceforge.net/mailarchive/forum.php?thread_name=496C1F6E.9080701%40troutpocket.org&forum_name=ffado-user Here it is in all its posterity: Well, I got it all working. I wanted to share my progress with everyone by editing the wiki but I don't have access to that. Here's what I did (in a nutshell): My Kit: Dell XPS M1210 laptop 1GB RAM Intel T5600 1.8GHz Core2Duo Intel 945GM Video controller Sigmatel 9220 internal audio controller Internal Ricoh Co Ltd R5C832 IEEE 1394 Controller http://tinyurl.com/clr43l EchoAudio Audiofire12 http://www.echoaudio.com/Products/FireWire/AudioFire12/index.php Ubuntu Studio 8.10 with RT (realtime) kernel Steps: 1. Install UbuntuStudio 8.10. 2. Install all updates via update manager 3. Install RT kernel ~$ sudo apt-get install linux-rt 4. Install ffado drivers and accompanying libraries In Synaptic Package Manager choose Settings/Repositories. In the Software Sources window choose the Third-Party Software tab. Add the following: deb http://www.ffado.org/apt gutsy contrib Reload your package manager and install the following: ffado-dbus-server ffado-mixer-qt4 ffado-tools jackd-firewire-driver libffado2 libffado2-dev (just in case) 5. Configure grub to boot RT kernel by default ~$ sudo vim /boot/grub/menu.lst edit the line: default 0 to say default 4 or whatever number (counting from 0) is your rt entry in the file. If you don't do this you have to manually choose it at boot every time. 6. Add yourself to the disk and audio groups. If the audio group doesn't already exist you can create it with the optional first command. ~$ sudo groupadd audio (optional step if audio group doesn't exist) ~$ sudo adduser disk ~$ sudo adduser audio 7. Adjust limits.conf to accommodate your RT kernel. ~$ sudo su -c 'echo @audio - rtprio 99 >> /etc/security/limits.conf' ~$ sudo su -c 'echo @audio - nice -19 >> /etc/security/limits.conf' ~$ sudo su -c 'echo @audio - memlock unlimited >> /etc/security/limits.conf' 8. Reboot to your RT kernel! After you system is up and running you'll have to start jackd. I recommend using qjackctl to do this as it has a patchbay manager. Make sure everything is plugged in and running then start qjackctl (found in Sound & Video/Audio Production/JACK Control) 9. You must install the raw1394 kernel module. Unfortunately my ability to get this to stick hasn't worked. No problem, just run the following short command after each boot: ~$ sudo modprobe raw1394 10. Here are the changes I made to the default jackd config by clicking Setup: Driver = firewire Realtime (checked) Priority = 70 Frames/Period = 64 Sample Rate = 48000 Periods/Buffer = 3 Port Maximum = 128 Interface = hw:0 Start Delay = 2 11. Click the Patchbay button. Click the New button and let it discover your port configurations itself. Mine showed System with 12 capture ports listed under Output and it showed System with 12 playback ports under Input. Select System in both windows and choose Connect. You may have to click the Activate though I don't really know exactly what that does. Click the start button and pray for no xruns. Following these exact steps I've been able to successfully record in Ardour for 30ish minutes without xruns or program errors. It may go longer but I haven't bothered trying yet. The big hurdle I encountered was outdated information on many websites. First of all, the Ricoh 1394 controller does not work with 8.04.1 RT kernel. It is working wonderfully with my 8.10 RT kernel. I hope someone can update the page at: http://subversion.ffado.org/wiki/HostControllers to show that success has been had with the Ricoh R5C832 1394 controller and perhaps reference this guide. Guides from which I shamelessly ripped off information: https://help.ubuntu.com/community/UbuntuStudioPreparation http://www.ffado.org/?q=release/apt -Scott -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
What HW/SW do people have working?
Hi - I'm a Mac user and musician. I'm thinking of switching to Linux with my next laptop, and am wondering what people are using for audio/ MIDI interfaces, and what software - DAW, plugins, softsynths, etc.? It looks like developers are doing lots of exciting things with Linux and music (at CCRMA etc.), but what is the state of things for users who just want to make music and not tinker with code and spend lots of time debugging? Does anyone have a setup that just works? Thanks for the info. ld -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
