2:05 a.m.
Is there a good command-line audio player for fc5? I just want something
simple that I can use via PuTTY to play .oggs and internet radio streams.
I tried a program called 'orpheus', but it stopped working almost
immediately ('cannot open the mixer device: /dev/mixer' and 'The ogg
player program has terminated.').
Thanks much!
2:40 a.m.
On Fri, 2006-12-29 at 02:05 -0600, Peter Horst wrote:
Is there a good command-line audio player for fc5? I just want
something simple that I can use via PuTTY to play .oggs and internet
radio streams.
ogg123 can play ogg files, mplayer can handle whatever codecs you have
to hand, both from a CLI. Not sure what happens as far as sound
handling over PuTTY, but maybe you just want to remote control sound
from the box.
5:18 a.m.
Peter Horst wrote:
Is there a good command-line audio player for fc5? I just want
something
simple that I can use via PuTTY to play .oggs and internet radio streams.
I tried a program called 'orpheus', but it stopped working almost
immediately ('cannot open the mixer device: /dev/mixer' and 'The ogg
player program has terminated.').
It could be a permission problem.
Check the owner and permissions of /dev/mixer when you're
logged in on the console and when you're logged in via
ssh/PuTTY.
Mogens
--
Mogens Kjaer, Carlsberg A/S, Computer Department
Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark
Phone: +45 33 27 53 25, Fax: +45 33 27 47 08
Email: mk(a)crc.dk Homepage: http://www.crc.dk
9:02 a.m.
Thanks very much - everything works when I su to root. The permissions
of the device in question follow - what is the rational thing to do
here? I don't want to include myself in the 'root' group, do I? And what
the heck is '14,'? And 'c' as a file type? A few new ones on me...
crw------- 1 root root 14, 0 Dec 29 00:18 mixer
Mogens Kjaer wrote:
Peter Horst wrote:
> Is there a good command-line audio player for fc5? I just want something
> simple that I can use via PuTTY to play .oggs and internet radio streams.
>
> I tried a program called 'orpheus', but it stopped working almost
> immediately ('cannot open the mixer device: /dev/mixer' and 'The ogg
> player program has terminated.').
It could be a permission problem.
Check the owner and permissions of /dev/mixer when you're
logged in on the console and when you're logged in via
ssh/PuTTY.
Mogens
1:32 p.m.
Quoting Peter Horst <phorst(a)speakeasy.net>:
Thanks very much - everything works when I su to root. The
permissions
of the device in question follow - what is the rational thing to do
here? I don't want to include myself in the 'root' group, do I? And
what the heck is '14,'? And 'c' as a file type? A few new ones on me...
crw------- 1 root root 14, 0 Dec 29 00:18 mixer
Part of the problem is that the permissions get change when someone
logs in on the local machine. (Ssh logins do not count.) This is
controlled by console.perms and is designed to give the person logged
in localy control of specific devices, sound being one of them. Now,
if you are loggind in at the console, and then ssh into the machine,
the permissions are correct for you to play sounds. But if someone
else is logged in, or no-one is logged in, then ther permissions are
set to prevent what you are trying to do. (It used to be a common
prank to to a remote login and play something on the machine when
someone else was logged in...)
Mikkel
1:49 p.m.
mikkel(a)infinity-ltd.com wrote:
Quoting Peter Horst <phorst(a)speakeasy.net>:
> Thanks very much - everything works when I su to root. The permissions
> of the device in question follow - what is the rational thing to do
> here? I don't want to include myself in the 'root' group, do I? And
> what the heck is '14,'? And 'c' as a file type? A few new ones on
me...
>
> crw------- 1 root root 14, 0 Dec 29 00:18 mixer
>
Part of the problem is that the permissions get change when someone
logs in on the local machine. (Ssh logins do not count.) This is
controlled by console.perms and is designed to give the person logged
in localy control of specific devices, sound being one of them. Now,
if you are loggind in at the console, and then ssh into the machine,
the permissions are correct for you to play sounds. But if someone
else is logged in, or no-one is logged in, then ther permissions are
set to prevent what you are trying to do. (It used to be a common
prank to to a remote login and play something on the machine when
someone else was logged in...)
Mikkel
Ah, thank you. Is there a way to "fake" being logged in on the
console?
I would like to leave this particular machine sitting in the closet and
only ever login via ssh....
12:59 p.m.
On Fri, 2006-12-29 at 13:49 -0600, Peter Horst wrote:
Ah, thank you. Is there a way to "fake" being logged in on
the console?
I would like to leave this particular machine sitting in the closet and
only ever login via ssh....
First, sorry if this is double posted. I didn't see my first post come
through the list.
Anyway, to try and answer your question.
You can try running everything within a screen session.
1) Start screen by typing screen on the command line
2) execute what you want to keep running
3) detach from the screen session by doing <CTRL>-A, then D
4) exit from your shell session.
To re-attach to that screen session, log back into the system and type
screen -r
HTH,
--
Doug
Registered Linux User #285548 (http://counter.li.org)
----------------------------------------
Random Thought:
"To IBM, 'open' means there is a modicum of interoperability among some of
their
equipment."
-- Harv Masterson
7:55 a.m.
Ski Dawg wrote:
On Fri, 2006-12-29 at 13:49 -0600, Peter Horst wrote:
> Ah, thank you. Is there a way to "fake" being logged in on the console?
> I would like to leave this particular machine sitting in the closet and
> only ever login via ssh....
First, sorry if this is double posted. I didn't see my first post come
through the list.
Anyway, to try and answer your question.
You can try running everything within a screen session.
[snip]
I've been running screen now for a couple of days - what an
extraordinarily useful program. Once I learned how to name the
individual buffers (CTRL-a A) and access the scrollback buffer (CTRL-a
[), I was in business. I log into my "server" via PuTTY on my laptop,
and I've always had a ton of trouble with wireless network flakiness
destroying sessions midway through. Now with screen I don't have to
worry about that. If the network goes down, it doesn't matter. I just
log back in and run 'screen -D -R' and I'm exactly where I left off.
Thanks for the pointer.
6:05 p.m.
Peter Horst wrote:
mikkel(a)infinity-ltd.com wrote:
> Quoting Peter Horst <phorst(a)speakeasy.net>:
>
> > Thanks very much - everything works when I su to root. The permissions
> > of the device in question follow - what is the rational thing to do
> > here? I don't want to include myself in the 'root' group, do I? And
> > what the heck is '14,'? And 'c' as a file type? A few new ones
on
> me...
> >
> > crw------- 1 root root 14, 0 Dec 29 00:18 mixer
> >
> Part of the problem is that the permissions get change when someone
> logs in on the local machine. (Ssh logins do not count.) This is
> controlled by console.perms and is designed to give the person logged
> in localy control of specific devices, sound being one of them. Now,
> if you are loggind in at the console, and then ssh into the machine,
> the permissions are correct for you to play sounds. But if someone
> else is logged in, or no-one is logged in, then ther permissions are
> set to prevent what you are trying to do. (It used to be a common
> prank to to a remote login and play something on the machine when
> someone else was logged in...)
>
> Mikkel
>
>
Ah, thank you. Is there a way to "fake" being logged in on the console?
I would like to leave this particular machine sitting in the closet and
only ever login via ssh....
You can modify the console.perms, and the udev rules so that the
permissions let you use the sound device. The console.perms rule are
in a directory off of /etc/security. (I can not check the name right
now.) I don't remember where the udev rules for sound are. I should
be back home in another day or so, and can check on this if you can
not find them...
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
4:06 p.m.
On 12/29/06, Peter Horst <phorst(a)speakeasy.net> wrote:
Is there a good command-line audio player for fc5? I just want
something
simple that I can use via PuTTY to play .oggs and internet radio streams.
I tried a program called 'orpheus', but it stopped working almost
immediately ('cannot open the mixer device: /dev/mixer' and 'The ogg
player program has terminated.').
have you looked at mpd? http://www.musicpd.org/
It runs as a daemon, and accepts remote connections, there are
multiple client's to interface with the daemon, some gui's and some
text clients.
--
Rob
11:28 a.m.
Rob Brown-Bayliss wrote:
On 12/29/06, Peter Horst <phorst(a)speakeasy.net> wrote:
> Is there a good command-line audio player for fc5? I just want something
> simple that I can use via PuTTY to play .oggs and internet radio streams.
>
> I tried a program called 'orpheus', but it stopped working almost
> immediately ('cannot open the mixer device: /dev/mixer' and 'The ogg
> player program has terminated.').
have you looked at mpd? http://www.musicpd.org/
It runs as a daemon, and accepts remote connections, there are
multiple client's to interface with the daemon, some gui's and some
text clients.
Thanks for the tip - I am having terrible trouble setting this up (even
without trying to bring ALSA into it) - is there perhaps a simpler
package/repo/rpm setup that I have missed? Every single one of the MPD
dependencies has given me grief so far - I'm getting the idea that maybe
this is more of a Debian-centric thing... What am I missing?
Thanks!
6329
days inactive
6333
days old
10 comments
6 participants
participants (6)
-
Mikkel -
Mogens Kjaer -
Peter Horst -
Rob Brown-Bayliss -
Ski Dawg -
Tim