From: Darcy K. <dar...@sy...> - 2010-05-09 14:44:16
|
I looked on my system (Centos 5), and sequencer is owned by my userid, and the root groupid jimmy wrote: > > Anyway, you can try some, or all of the following commands: > > ls -altr /dev | grep sequencer > ls -altr /dev | grep sequencer2 > ls -altr /dev | grep dsp > ls -altr /dev | grep audio > ls -altr /dev | grep midi > ls -altr /dev | grep mixer > > > > >> Date: Sun, 09 May 2010 00:30:35 -0400 >> From: Darcy Kahle <dar...@sy...> >> >> Under RedHat (and RedHat-based, like Centos - what I am >> running), you >> have to add the following lines to >> /etc/security/limits.conf: >> >> <user> - rtprio 95 >> <user> - memlock 512000 >> <user> - nice -19 >> >> Use your own user name in place of <user>. To >> my knowledge, the kernel >> already does Real-Time, so you do not need to mess with the >> kernel >> >> Thomas Sattler wrote: >> >>> Jimmy, >>> >>> Thanks for your reply; I have issued: >>> >>> ls -altr /dev/ | grep audio >>> >>> and it does nothing. I am on Fedora 11, not a >>> >> "studio" distro; I've >> >>> used Red Hat Linux back to the 6.1 days, so staying >>> >> with Fedora was an >> >>> easy decision. Since I have a Quad-core >>> >> processor and 6 GB of memory, >> >>> I don't have any latency issues that I can see. >>> >>> >>> >>> >>> On Sat, May 8, 2010 at 8:00 PM, jimmy <wg...@ya... >>> >>> <mailto:wg...@ya...>> >>> >> wrote: >> >>> > Date: Sat, 8 May 2010 >>> >> 01:40:18 -0400 >> >>> > From: "D. Michael >>> >> McIntyre" >> >>> <mic...@ro... >>> <mailto:mic...@ro...>> >>> > >>> > On Saturday 08 May 2010, >>> >> Thomas Sattler wrote: >> >>> > >>> > > Hmmmmm..... >>> > > >>> > > I don't see any red >>> >> LED anyplace. Only yellow. >> >>> > >>> > Audio is busted. >>> >> These tracks should probably be >> >>> > showing white >>> >> (colorless, >> >>> > ie. of no useful type) >>> >> LEDs instead of yellow, but we'll >> >>> > never sort that mess >>> > out. >>> > >>> > Oh well. >>> > >>> > > But here is the >>> >> interesting part: I start >> >>> > qjackctl as root (because >>> >> it >> >>> > > doesn't work right >>> >> otherwise). But I start >> >>> > Rosegarden with my normal >>> >> user >> >>> > > account, and 1.7.3 >>> >> always complained that Jack is not >> >>> > running. >>> > >>> > That's because you have >>> >> to run JACK and whatever >> >>> > applications you want to >>> >> use >> >>> > it with as the same >>> >> user. Typically you run on a >> >>> > setup that allows you to >>> >> run >> >>> > all of this as your user, >>> >> but that kind of setup is >> >>> > something best left to >>> >> the >> >>> > studio-oriented distro >>> >> variants these days. I'm not >> >>> > going to get into that. >>> > >>> > > I ignored >>> > > this, since it >>> >> worked. 10.4.1 doesn't complain >> >>> > about Jack, but I see no >>> > > red LED. >>> > >>> > It does complain about >>> >> JACK, it just does so quietly. >> >>> > You should see a /!\ >>> > warning icon in the >>> >> bottom right corner of the screen, and >> >>> > if you click it, it >>> > will inform you that >>> >> audio is busted. >> >>> > >>> > You need to figure out >>> >> why QJackCtl doesn't work as your >> >>> > user, but that's more >>> > of a problem than I'm >>> >> willing to deal with. What >> >>> > matters for your most >>> > immediate purposes is >>> >> that you're going to have to manually >> >>> > reassign these >>> > broken audio tracks to a >>> >> MIDI device to get them to work. >> >>> > -- >>> > D. Michael McIntyre >>> >>> >>> >>> You should not run Jack >>> >> (jackd) as root user. This is the problem >> >>> for most distributions out >>> >> there that are ignorant of how to setup >> >>> properly for MIDI/audio apps. >>> >>> If you can only run >>> >> jackd/qjackctl as root, it is because the user >> >>> account you run under is not >>> >> part of the "audio" group. I assume >> >>> "audio" group is also the case >>> >> with your distribution, if that is >> >>> the case, substitute whatever >>> >> group name that owns the devices >> >>> listed below. >>> >>> On my system, the command >>> >>> ls -altr /dev/ | grep >>> >> audio >> >>> will show: >>> >>> >>> crw-rw----+ 1 root >>> >> audio 14, 1 May 6 20:10 >> sequencer >> >>> crw-rw----+ 1 root >>> >> audio 14, 8 May 6 20:10 >> sequencer2 >> >>> crw-rw----+ 1 root >>> >> audio 14, 3 May 6 20:10 >> dsp >> >>> crw-rw----+ 1 root >>> >> audio 14, 4 May 6 20:10 >> audio >> >>> crw-rw----+ 1 root >>> >> audio 14, 2 May 6 20:10 >> midi >> >>> crw-rw----+ 1 root >>> >> audio 14, 0 May 6 20:10 >> mixer >> >>> crw-rw----+ 1 root >>> >> audio 14, 9 May 6 20:10 >> dmmidi >> >>> All of which are Alsa devices >>> >> (some of those may be Alsa emulation >> >>> of OSS devices), which means >>> >> only root user and any user belong to >> >>> the audio group can read and >>> >> write to these device(s). >> >>> If you run jackd from a user >>> >> account that doesn't belong to the >> >>> audio group, then jackd won't >>> >> be able to access (read/write to) >> >>> the devices listed >>> >> above. You will need to add that user account >> >>> to the audio group, log out >>> >> and log back in for it to take effect. >> >>> You don't even have to log out and >>> >> log back in, try "su - >> >>> <useraccount>" >>> >> (substitute <useraccount> with the actual user >> >>> account id) from the command >>> >> line will let you log-in to a new >> >>> session only for that >>> >> commandline window, which you can launch >> >>> jackd there as a quick way to >>> >> test. >> >>> I assume your account doesn't >>> >> belong to the audio group. You can >> >>> change that. From the >>> >> commandline, try >> >>> su - >>> >>> (need to enter root password) >>> >> that commandline window will log in >> >>> as root user. For the >>> >> command below, substitute "guest" with your >> >>> actual userid (that needs to >>> >> be added to the audio group). From >> >>> the root command prompt, try: >>> >>> >>> tmpId="guest" ; >>> >> tmpgroups=` /usr/bin/groups ${tmpId} | sed -e >> >>> "s~.*: ~~" | sed -e "s~$~ >>> >> audio~" | sed -e "s~ ~,~g" ` ; >> >>> /usr/sbin/usermod -G >>> >> "${tmpgroups}" "${tmpId}" ; /usr/bin/groups >> >>> "${tmpId}" >>> >>> >>> The one-line above include >>> >> multiple commands that will change the >> >>> "guest" account (change >>> >> "guest" to your actual userid) to add that >> >>> user to the "audio" >>> >> group. After that, you can try logout and >> >>> login again (or "su - guest") >>> >> to try running jackd/qjackctl under >> >>> that userid. >>> >>> You may also want to check to >>> >> see if your kernel has "high >> >>> resolution timer" compiled-in, >>> >> very useful relating to MIDI >> >>> latency issues. >>> >>> Jimmy >>> >>> >>> >>> >>> >>> >>> >>> >> ------------------------------------------------------------------------------ >> >>> >>> >> _______________________________________________ >> >>> Rosegarden-user mailing list >>> Ros...@li... >>> <mailto:Ros...@li...> >>> >> - use the link >> >>> below to unsubscribe >>> https://lists.sourceforge.net/lists/listinfo/rosegarden-user >>> >>> >>> >>> >> ------------------------------------------------------------------------ >> >>> >> ------------------------------------------------------------------------------ >> >>> >>> >>> >> ------------------------------------------------------------------------ >> >>> _______________________________________________ >>> Rosegarden-user mailing list >>> Ros...@li... >>> >> - use the link below to unsubscribe >> >>> https://lists.sourceforge.net/lists/listinfo/rosegarden-user >>> >>> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> ------------------------------------------------------------------------------ >> >> >> >> ------------------------------ >> >> _______________________________________________ >> Rosegarden-user mailing list >> Ros...@li... >> https://lists.sourceforge.net/lists/listinfo/rosegarden-user >> >> >> End of Rosegarden-user Digest, Vol 48, Issue 13 >> *********************************************** >> >> > > > > > > |