I'm running Fedora 10 with the gnome desktop. I installed the mpd (music player daemon) on my file server (where all the music lives) and gmpc on my laptop. These things come from rpmfusion. Every sound application on my machine is able to make noise except gmpc. It doesn't have a config panel so there doesn't seem to be any way to choose between sound systems or any such nonsense. It displays all the files on the server so communication is established. Network monitor shows increased network traffic from my server when I'm playing a song, so I'll assume that music is actually flowing on the net. Has anyone got this thing to work? I would rather not have music cluttering up every box in the house when it is aviailable via server... wcn
Am Mittwoch, den 10.03.2010, 11:16 -0700 schrieb Wendell Nichols: ...
gmpc on my laptop. These things come from rpmfusion. Every sound application on my machine is able to make noise except gmpc.
Same here. Maybe this entry in /var/log/messages is related:
Mar 11 09:15:44 rodolfoap pulseaudio[9143]: main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /bin/ dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.
Cheers. ---------------------------------------------- Rodolfo Alcazar Portillo - nospaze@gmail.com otbits.blogspot.com / counter.li.org: #367962 ---------------------------------------------- To rephrase, spam is not the answer. Spam is the question. Death is not the answer, but pretty close to it. -- Vadik
On 03/11/2010 01:26 AM, NoSpaze wrote:
Am Mittwoch, den 10.03.2010, 11:16 -0700 schrieb Wendell Nichols: ...
gmpc on my laptop. These things come from rpmfusion. Every sound application on my machine is able to make noise except gmpc.
Same here. Maybe this entry in /var/log/messages is related:
Mar 11 09:15:44 rodolfoap pulseaudio[9143]: main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /bin/ dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.
Cheers.
Rodolfo Alcazar Portillo - nospaze@gmail.com otbits.blogspot.com / counter.li.org: #367962
Auggggh! I finally understand! The people who wrote the mpd (music player daemon) and the clients created a fully networked architecture for playing music where the DAEMON PLAYS THE MUSIC! This is not streaming media at all. The daemon has to be on your local machine which completely defeats the purpose of consolidating your music on a central server. I started all this because playing music off nfs mounts caused all sorts of problems when I put my laptop on and off the docking station (network interruption and nfs problems galore!). I can't for the life of me imagine why anyone would set out to architect it this way but its usless to me :( wcn
On Thu, 2010-03-11 at 10:13 -0700, Wendell Nichols wrote:
Auggggh! I finally understand! The people who wrote the mpd (music player daemon) and the clients created a fully networked architecture for playing music where the DAEMON PLAYS THE MUSIC! This is not streaming media at all. The daemon has to be on your local machine which completely defeats the purpose of consolidating your music on a central server. I started all this because playing music off nfs mounts caused all sorts of problems when I put my laptop on and off the docking station (network interruption and nfs problems galore!). I can't for the life of me imagine why anyone would set out to architect it this way but its usless to me :(
In 'landscape' type offices it is ideal. Instead of everyone playing their own music, people forgetting to turn off the music when they go, etc... Set up one system with decent speakers and mpd. Then everyone can add music to the queue, pause it when needed (boss on the phone) and so on.
Ideal for any setting where you want one dedicated system to power the music but distributed control. Not what you wanted. Wrong tool :-)
birger
On 03/11/2010 10:27 AM, birger wrote:
On Thu, 2010-03-11 at 10:13 -0700, Wendell Nichols wrote:
Auggggh! I finally understand! The people who wrote the mpd (music player daemon) and the clients created a fully networked architecture for playing music where the DAEMON PLAYS THE MUSIC! This is not streaming media at all. The daemon has to be on your local machine which completely defeats the purpose of consolidating your music on a central server. I started all this because playing music off nfs mounts caused all sorts of problems when I put my laptop on and off the docking station (network interruption and nfs problems galore!). I can't for the life of me imagine why anyone would set out to architect it this way but its usless to me :(
In 'landscape' type offices it is ideal. Instead of everyone playing their own music, people forgetting to turn off the music when they go, etc... Set up one system with decent speakers and mpd. Then everyone can add music to the queue, pause it when needed (boss on the phone) and so on.
Ideal for any setting where you want one dedicated system to power the music but distributed control. Not what you wanted. Wrong tool :-)
birger
Well I went back and tried a solution that I originally rejected because I thought it was "clunky".. turns out I was wrong (again). I installed mt-daapd server on my server. Changed the mp3 dir in the config file to point to my music dir, and started the server. You can logon to a local web page with the admin password, but its unnecessary. Then install rhythmbox on your laptop, start it and select File->Connect to Daap Share.. fill in the dialog and your local daap server gets added to the shared tree tab. all my music is there, and indexed FAST. This is what I've been looking for. I'll experiment with the playlists to see how convenient it is.. but its already much better than playing music off shares... thnx wcn