|
Post by gregd on Dec 20, 2012 10:32:33 GMT -5
Too much fun yesterday. Mpd is really cool.
After getting mpd installed things just fell into place.
Last night I had to go into my new-since-the-last-time-she-visited router to add my visiting daughter's laptop and phone MAC addresses to the wifi filter. While I was there it was an easy tweek to find the music server and give it a fixed ip address.
Then, of course, I went poking around the mpd config file and found the line to have it accept client requests from the network. Kill and restart mpd. Install an mpd client on my desktop Linux box, and in no time at all I was controlling the playlist from across the room.
Went over to google play and checked out the comments on the mpd clients, installed Droid MPD Client on my phone, and after a few screen touches I'm controlling the playlist from my phone. Simple, effective, attractive interface. It is just TOO COOL!
The only downside is the remote for my XDA-2 was DOA and is on its way back for repair/replacement, so I can't adjust the volume from the couch quite yet. But it is really great being able to pull up anything at all in my music collection just by poking at my phone.
greg121986 - thanks for the offer but mpd's example config file was sufficiently self-documenting to get me through to the end.
XDA-2 and Linux?? Just TOO COOL!! ;D
|
|
|
Post by dad311 on Dec 20, 2012 11:20:35 GMT -5
Too much fun yesterday. Mpd is really cool. After getting mpd installed things just fell into place. Last night I had to go into my new-since-the-last-time-she-visited router to add my visiting daughter's laptop and phone MAC addresses to the wifi filter. While I was there it was an easy tweek to find the music server and give it a fixed ip address. Then, of course, I went poking around the mpd config file and found the line to have it accept client requests from the network. Kill and restart mpd. Install an mpd client on my desktop Linux box, and in no time at all I was controlling the playlist from across the room. Went over to google play and checked out the comments on the mpd clients, installed Droid MPD Client on my phone, and after a few screen touches I'm controlling the playlist from my phone. Simple, effective, attractive interface. It is just TOO COOL! The only downside is the remote for my XDA-2 was DOA and is on its way back for repair/replacement, so I can't adjust the volume from the couch quite yet. But it is really great being able to pull up anything at all in my music collection just by poking at my phone. greg121986 - thanks for the offer but mpd's example config file was sufficiently self-documenting to get me through to the end. XDA-2 and Linux?? Just TOO COOL!! ;D Be careful using with Mac tables for security it's very easy to spoof a Mac address.
|
|
|
Post by knickerhawk on Jan 2, 2013 9:54:00 GMT -5
It appears that the XDA-2 is not fully compatible with linux. The alsa driver in linux has issues with the CM-6631 chip and this has been known for months now. I did not know this until the last few days. The problem happens when trying to switch between the different sample rates. The linux driver does not negotiate the proper sample rate with the XDA-2. So if you play a 16/44.1K track and than change to a 24/192K track, the XDA-2 will play it at 44.1K until you stop the track and replay it again. This has to be done with every track when changing sample rates. I also have issues with trying to get the XDA-2 to get the proper sample rate on the first play of a song when first powered up. I can never get it to play at the correct sample rate. When I do get the correct sample rate, say 44.1K the sound is not so great. There is almost some distortion and crackling in the tracks. This has put a bad taste in my month and I am pretty upset about the whole situation. - Garrett I've had a pretty similar experience when I hooked up my new XDA-2 to my Synology DS213+ NAS, which apparently is Linux based. Previously this NAS worked perfectly with an Audioquest Dragonfly dac plugged directly into one of its usb ports. 44/16 and 96/24 flac files played losslessly with no problems using the AudioStation music server app that Synology includes with this NAS. When the XDA-2 is hooked up to the NAS via a usb cable, the first track played always sounds muted with a very tinny, garbled sound. If I restart the track or play another track, the XDA-2 kicks in correctly and plays the current track and all subsequent tracks with no problems (no clicks, noise, etc.) UNTIL it encounters a track with a different resolution. Then I have to restart the new track to get the XDA-2 to play it at the right resolution. The dac sounds great (even though it isn't really burned in yet), but there's no way I can explain to my wife why I'm making her jump through hoops to use this new audio component! Worse yet, if I put the XDA-2 in standby mode, it somehow locks up the Synology AudioStation music server. When I restart the XDA-2, the only way to get it to play music is to restart the music server. Definitely not a spouse-friendly solution! I'm a complete Linux neophyte and really don't want to try to work around this limitation in the NAS by either loading something like MPD or one of the other Linux audio apps. I'd like to keep the XDA-2, as I've also purchased a XSP-1 and XPA-200 and want to connect everything together with XLRs and have a consistent visual "package" of components in my main system. However, I'm quickly losing hope that there's any simple (and/or cheap) solution. Does anyone have any suggestions?
|
|
|
Post by GreenKiwi on Jan 2, 2013 10:45:47 GMT -5
Is your xda one that has the original firmware? Or updated?
|
|
|
Post by knickerhawk on Jan 2, 2013 12:16:19 GMT -5
Is your xda one that has the original firmware? Or updated? It was shipped last week, so I'm assuming it has the new firmware. I also don't think the symptoms I'm experiencing are the same as the problems noted about the first firmware version. I don't have any of the intermittent noise/screeching problems. Everything plays beautifully after the initial restart to kick-in the correct sampling rate.
|
|
hegge
Seeker Of Truth
Posts: 2
|
Post by hegge on Apr 22, 2013 11:47:37 GMT -5
It appears that the XDA-2 is not fully compatible with linux. The alsa driver in linux has issues with the CM-6631 chip and this has been known for months now. I did not know this until the last few days. The problem happens when trying to switch between the different sample rates. The linux driver does not negotiate the proper sample rate with the XDA-2. So if you play a 16/44.1K track and than change to a 24/192K track, the XDA-2 will play it at 44.1K until you stop the track and replay it again. This issue is fixed in Linux kernel v3.9-rc6 or newer. git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=690a863ff03d9a29ace2b752b8f802fba78a842f
|
|
|
Post by knickerhawk on Apr 24, 2013 15:15:29 GMT -5
It appears that the XDA-2 is not fully compatible with linux. The alsa driver in linux has issues with the CM-6631 chip and this has been known for months now. I did not know this until the last few days. The problem happens when trying to switch between the different sample rates. The linux driver does not negotiate the proper sample rate with the XDA-2. So if you play a 16/44.1K track and than change to a 24/192K track, the XDA-2 will play it at 44.1K until you stop the track and replay it again. This issue is fixed in Linux kernel v3.9-rc6 or newer. git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=690a863ff03d9a29ace2b752b8f802fba78a842fThis is interesting information. It looks like you posted it on that site. Were you involved in developing the fix? My problem is that I'm a complete Linux luddite and, worse, I'm dependent on the Linux kernel and ALSA that's embedded in Synology's NAS system. I assume there's no way for me to perform the update without major hacking. Correct? I wonder if bringing this to Synology's attention would get them to act on it. One more question. If this code is in ALSA, does that imply that the whole Linux kernel has to be updated or just ALSA? Thanks.
|
|
|
Post by GreenKiwi on Apr 24, 2013 18:52:53 GMT -5
Synology might respond and/or at least tell you when the kernel might show up in their kernels. I have a synology too and probably wouldn't be messing around inside either.
The do seem reasonably responsive to things.
You might try filing it as a "bug" with this link as to the way to fix the bug.
Btw, I saw a recent DSM update, it might be worth at least seeing whether or not this is in that fix.
|
|
|
Post by knickerhawk on Apr 24, 2013 20:09:00 GMT -5
Synology might respond and/or at least tell you when the kernel might show up in their kernels. I have a synology too and probably wouldn't be messing around inside either. The do seem reasonably responsive to things. You might try filing it as a "bug" with this link as to the way to fix the bug. Btw, I saw a recent DSM update, it might be worth at least seeing whether or not this is in that fix. Yeah, I plan to give it a try, but in the past Synology support has been pretty vague about when/if the problems with supporting USB Audio Class 2 will be addressed. Before this most recent upgrade to DSM and Audio Station, the response I got was "maybe this upcoming release will solve your problem." Unfortunately, the lastest update didn't help at all. As I understand it, this most recent upgrade of DSM will be the last with the current ancient version of the Linux kernel. If so, that should be good news for those of us trying to get things to work between Synology and the XDA-2.
|
|
hegge
Seeker Of Truth
Posts: 2
|
Post by hegge on Apr 25, 2013 13:48:20 GMT -5
It looks like you posted it on that site. Were you involved in developing the fix? Yes. You can take a look at thread.gmane.org/gmane.linux.alsa.user/36935 for more details than you probably want. My problem is that I'm a complete Linux luddite and, worse, I'm dependent on the Linux kernel and ALSA that's embedded in Synology's NAS system. I assume there's no way for me to perform the update without major hacking. Correct? I wonder if bringing this to Synology's attention would get them to act on it. If you can't build your own kernel for the device, I think you should do as greenkiwi suggests and open a bug with the device vendor. It looks like those NAS boxes use a 3.2 kernel. I just tested the patch I linked to earlier on the latest 3.2 stable kernel (3.2.42), and it appears to work fine. You probably want to include that information in your correspondence with Synology.
|
|
|
Post by knickerhawk on Apr 25, 2013 16:57:51 GMT -5
It looks like you posted it on that site. Were you involved in developing the fix? Yes. You can take a look at thread.gmane.org/gmane.linux.alsa.user/36935 for more details than you probably want. My problem is that I'm a complete Linux luddite and, worse, I'm dependent on the Linux kernel and ALSA that's embedded in Synology's NAS system. I assume there's no way for me to perform the update without major hacking. Correct? I wonder if bringing this to Synology's attention would get them to act on it. If you can't build your own kernel for the device, I think you should do as greenkiwi suggests and open a bug with the device vendor. It looks like those NAS boxes use a 3.2 kernel. I just tested the patch I linked to earlier on the latest 3.2 stable kernel (3.2.42), and it appears to work fine. You probably want to include that information in your correspondence with Synology. I'll try passing that info on to Synology. Where did you find the information about Synology NAS's using a 3.2 kernel? I think a big part of my problem is that my particular Synology NAS (the 213+) and quite a few of the other models don't use one of the newer Linux kernels. A couple of months ago (before the most recent DSM upgrade was installed) I used Putty to ascertain that the Linux version on my 213+ is version 2.6.32.12. The version of ALSA was 1.0.24. Does that mean that your patch isn't likely to work for my particular NAS model because of the outdated version of the Linux kernel? FYI, I have two problems when I connect my XDA-2 DAC to my Synology 213+ and use the Audio Station application as the music player. The first problem is that I have to turn the XDA-2 on first and then reboot the NAS before they'll recognize each other. As long as I leave the XDA-2 on, I can play music. The second problem is the sampling rate error that your patch appears to correct. Would be great to fix that problem even if the first one isn't necessarily addressed by your patch. Thanks again for all your efforts!
|
|
|
Post by odedia on Jun 16, 2013 10:58:50 GMT -5
I'm thinking about getting an XDA-2 and would appreciate some thoughts from everyone if possible. I have a NAS4FREE (previously FreeNAS) box running on a custom built PC. It's using FreeBSD. I also have a rev B. raspberry pi, an Apple TV, and a Boxee Box. Correct me if I'm wrong, but it is my understanding that the best audio quality will be achieved if I hook up the XDA-2 directly via the USB connection, right? Both AppleTV and Boxee Box will require me to connect via Toslink optical cable, meaning it would only send out PCM data. If I'm not mistaken, there are zero "jitter" issues when connected via USB in comparison. So, is there a way to connect the XDA-2 directly to my NAS box? There's no GUI installed or anything, it's just a web based server. I guess the more feasible option would be to install some version of Linux on the raspberry pi and connect that via its network cable to the NAS box. Any recommendations on installations? I really just want something that will look pretty in terms of UI and navigation. The PI will be connected to the receiver via HDMI for on-screen navigation and via USB to the XDA-2 for music playback. I guess that using OpenElec or Rasplex is not an option here because I want audio going through USB instead of HDMI, right? Third option: use the toslink on AppleTV/Boxee Box and completely ignore the USB connection. Will that really "degrade" the audio quality? Will I miss out on 24bit/192khz goodness? If it's becoming too complicated, I might just keep using my AVR as the audio player . My Onkyo 818 not only supports samba network folders, but can even playback DSD files, which results in spectacular sound.
|
|
idm
Seeker Of Truth
Posts: 1
|
Post by idm on Mar 10, 2017 11:38:42 GMT -5
I am new to the forum, I just thought to mention here that the rpi with libreelec Kodi works with the xda-2. System -> audio output -> audio output device, select alsa:usb2.0........s/pdif or analog, s/pdif outputs the proper bit rate analogue is fixed to 48kb/s.
|
|