Re: Running jackd/qjackctl as normal user

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Running jackd/qjackctl as normal user

wg2002a
Thomas,

On my Debian system, I have the following modules loaded.  You may or may not need all of them:

snd_pcm_oss
snd_mixer_oss
snd_seq_oss
snd_seq_midi
snd_rawmidi
snd_seq_midi_event
snd_seq
snd_seq_device
snd_seq_dummy
snd_pcm


When some of these modules are loaded, the module will create the device node(s) under /dev directory.  If you dont have these sound related modules loaded, you may not have the device nodes under /dev directory.

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

to see if you have any of those device nodes, and what group can read/write to those device nodes.  If you can't decipher the output from the above commands, post it here, I would like to see that info for a Fedora system, too.  I haven't looked much at RedHat for sometime, let alone MIDI stuff there.  No big deal.

It may be a different group name under Fedora instead of "audio" (under Debian).  If such is the case, you may have to modify the one-line commands I posted earlier, change all the occurences of "audio" to the actual name of the group that have read/write permission to the sound related device nodes above.

----

Also Darcy mention adding to /etc/security/limits.conf:

<user>  -  rtprio  95
<user>  -  memlock  512000
<user>  -  nice  -19

You can actually use the group-name instead of user-id (i.e. "audio" for my Debian system).  With group name, you can login as a different user, also belonging to that group and can still run the audio related apps, without having to add 3 more lines per user.

Jimmy


> Date: Sun, 09 May 2010 00:30:35 -0400
> From: Darcy Kahle <[hidden email]>
>
> 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 <[hidden email]
>
> > <mailto:[hidden email]>>
> wrote:
> >
> >
> >     > Date: Sat, 8 May 2010
> 01:40:18 -0400
> >     > From: "D. Michael
> McIntyre"
> >     <[hidden email]
> >     <mailto:[hidden email]>>
> >     >
> >     > 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
> >     [hidden email]
> >     <mailto:[hidden email]>
> - use the link
> >     below to unsubscribe
> >     https://lists.sourceforge.net/lists/listinfo/rosegarden-user
> >
> >
> >
> ------------------------------------------------------------------------
> >
> >
> ------------------------------------------------------------------------------
> >
> >   
> >
> ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Rosegarden-user mailing list
> > [hidden email]
> - 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
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user
>
>
> End of Rosegarden-user Digest, Vol 48, Issue 13
> ***********************************************
>


     

------------------------------------------------------------------------------

_______________________________________________
Rosegarden-user mailing list
[hidden email] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Reply | Threaded
Open this post in threaded view
|

Re: Running jackd/qjackctl as normal user

Darcy Kahle
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 [hidden email]

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 <[hidden email]
      
[hidden email]>
      
wrote:
    
     > Date: Sat, 8 May 2010
      
01:40:18 -0400
    
     > From: "D. Michael
      
McIntyre"
    
     <[hidden email]
     [hidden email]>
     >
     > 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
     [hidden email]
     [hidden email]
      
- use the link
    
     below to unsubscribe
     https://lists.sourceforge.net/lists/listinfo/rosegarden-user



      
------------------------------------------------------------------------
    
      
------------------------------------------------------------------------------
    
   

      
------------------------------------------------------------------------
    
_______________________________________________
Rosegarden-user mailing list
[hidden email]
      
- 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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


End of Rosegarden-user Digest, Vol 48, Issue 13
***********************************************

    


      


  

------------------------------------------------------------------------------


_______________________________________________
Rosegarden-user mailing list
[hidden email] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Reply | Threaded
Open this post in threaded view
|

Re: Running jackd/qjackctl as normal user

wg2002a


--- On Sun, 5/9/10, Darcy Kahle <[hidden email]> wrote:

>  
> I looked on my system (Centos 5), and sequencer is owned by
> my userid,
> and the root groupid
>

Darcy,

On my Debian system

   ls -altr /dev | grep sequencer ; ls -altr /dev | grep dsp ; ls -altr /dev | grep midi

give me:

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,   2 May  6 20:10 midi
crw-rw----+  1 root audio    14,   9 May  6 20:10 dmmidi


which means "root" is the user who owns those device nodes, and "audio" is the group associated with them.

The "c" in the first column means the device node is a "character" device.  The very next 3 characters (rw-) in this case means the user who owns the device has permission to read and write, but not execute regarding that device node (treated same way as a file).  The very next 3 characters are permissions for the group.  Following by 3 characters denoting permissions for everyone.

Let's say you may see:

crw-rw----+  1 tester1 tester1    14,   1 May  6 20:10 sequencer
crw-rw----+  1 tester1 tester1    14,   8 May  6 20:10 sequencer2

that means someone (or setup scripts, hot-plug scripts) have already set the user "tester1" as the owner of sequencer device nodes, and also set the group "tester1" to be associated with that device node (often called group ownership of the file/device node).

Note that for most *nix/*BSD/Linux system, when a user account is created, a group with the exact same name is also created, but not the other way around.  Don't confuse a group name with a user name.  Group names of the system is listed in /etc/group file.  User names are listed under /etc/passwd and /etc/shadow files.

If what you have works for you and you don't need other users to have access to such file/device nodes then you don't have to change anything.  But you now know the different choices you have relating to file/device permissions.

Be careful if you add other users to your own userid's group.  It means they can often read and write to any file that your userid's group is associated with.

Often it's more troublesome when someone delete or change your files, while it is useful to allow them to read some of your files/directories.  That's the reason a generic group is created to share specific set of file/directory/device permissions, like "audio", "modem", "dialout" groups, but not share other resource a particular user has that other users should not have access to.

Root user is the system admin and can change all permissions at will, that's why Linux/*nix/*BSD are really careful about root password.

Jimmy



     

------------------------------------------------------------------------------

_______________________________________________
Rosegarden-user mailing list
[hidden email] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Reply | Threaded
Open this post in threaded view
|

Playback/transport question.

Henry W. Peters
Howdy RG folk! First off; congratulations on a newer, improved RG (v.
10.04.1). I did a fresh install, on a fresh install of Debian Squeeze,
all went perfectly smoothly (relatively speaking... no such animal as
absolutely smoothly in Linux! far as I am aware :)).

Any way I have a (possibly simpleminded) question regarding:

A.) What is the "Media Record" macro... ? & is there a way (or a
equivalent) to connect for use (i.e., to activate record), this
keybinding (or macro) on a standard PC keyboard, or perhaps on my
programmable Logitec wireless mouse? I also tried to follow a previous
discussion on keybindings, & fear that this might have something to do
with any possible answer to this question (but oh well).

B.) I have been also longing (but too dang lazy to) ask, is there a way
to "scrub" play midi or audio besides "selecting" the notes or regions,
etc.?

Like I said, probably simple-minded, but I did look at the help manual &
tutorial, either missed it, or was not there.

Thanks again, for making Linux so much more actually functional!

Regards,

Henry



------------------------------------------------------------------------------

_______________________________________________
Rosegarden-user mailing list
[hidden email] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user