0 Members and 1 Guest are viewing this topic. Read 267939 times.
Terry, stupid question but doesn't a new environment (friends house) require major edits to fstab and mpdconfig as the network, permissions, ip address, music file locations, etc are all different.
Not a stupid question at all. The answer is yes. We just setup his network to mimic mine. EVERYTHING works fine except for GMPC and NCMPC. I can't figure it out. Doesn't matter now as we gave up.
Did you chnage the IP address the ncmpc and gmpc will connect to on the new network?
Everything was working fine. I could use WinSCP to SSH into the Alix and the Alix saw the Windows share just fine. The only thing that wouldn't work is GMPC. Then I also couldn't get NCMPC to work either. It doesn't make any sense why it didn't just work. Oh well, I'm heading home now anyway...
Because GMPC or any client need the correct IP and port of the MPD daemon their connecting to. If your Alix was on a new network with an IP of 10.x.x.x and your GMPC was setup to connect to 192.x.x.x, i.e., the IP address of the Alix on your home network, then it can't connect.
I think I can answer apart of my own question now having stumbled across this site after visiting the Voayage MPD pages.http://kubotayo.web.fc2.com/voyagempd.html#voyagempd075It says "Recently Linux 3.0 was released. Force threaded irq-handlers is effective in this version without RT patches." which I take to mean some aspects of the RT kernel are availalbe, or at least irq tuning can be done. But the real question is it of value when you're just using a computer for audio playback?
Just wanted to add my experience to this thread. I bought the Voyage MPD starter kit from the Voyage Store. Assembled it rather fast, setup an NFS share, powered it up and it it was live. It was pretty cool to PuTTy into the system and issue commands to play music, all within an hour of opening the box. I then started to scan the forums to see how to configure it. After a couple of hours of research, I realized there was a guide in the box it came in, doh! Still, the guide leaves a lot unsaid. Glad I finally found this thread. My main playback was jRiver 16, from a local library on my desktop computer running Windows 7 into a Audinst HUD-Mx1 DAC. I have a Windows Home Server 2011 setup, and I toss a copy of my lossless rips and downloads on a server folder there. I assumed I needed to mount using an NFS share, as that was all the information I could find with Google. I realized I had an issue with permissions, and everytime I added a new album, I would run a chmod -R 777 /mnt/public. I got pretty good at that, and kept telling myself I would fix the permissions once I got tired of that.In the middle of this thread, someone mentions SAMBA and CIFS. So I tried that out last night, and after some effort, got it to work. It turned out the majority of the issues I had was due to permissions on the Windows Home Server, somehow I managed to totally mess the share permissions up when using NFS, and I had to log in as Administrator and take ownership of the entire folder and propagate them down. After that, it was pure bliss. I could even update the database from within my MP clients! Really, it was rather simple once I realized what it was that I needed. That was the hard part, realizing what you actually need in your system. It was very much like any music player setup, except configuring from the command line. Setup your library. Point MPD at the share. Configure it for bit perfect playback. Pretty much the same thing I did for jRiver. If anyone has a similar setup, please feel free to ask me any questions.