Search the Community
Showing results for tags 'amm'.
Found 1 result
Simple explanation for this. Aurender didn't make their own player. They are using MPD and trying to pass it as their ownership, which it's definitely not, and doing so without even mentioning MPD or the GPL license on their homepage or anywhere in the firmware. A while ago a developer made a separate fork of MPD with an Upnp plugin for MPD, (which eventually made it into MPD master). The way the Upnp plugin worked within the contraints of the MPD API was to use the "browse" feature of a MPD client to, well browse, the directoy structure of an Upnp server. Aurender forked this Upnp-fork of MPD, and my guess is that they modified the Upnp code to browse network shares instead of Upnp servers. Since MPD (and subsequently Aurender) does not read tags while playing, but only when scanning files, it makes sense that Aurender threw something of a hack (yes, that would be AMM) together to somehow support metadata when using the NAS feature. Those who are a little familiar with MPD or Linux might wonder why Aurender simply didn't just mount the network share from NAS and symlink to it from the music directory, and at the same sidestep the need for AMM. The answer to that is: I am not sure, maybe because symlinking still requires a rescan of the music directory for MPD to pickup the symlink. It would be rather illogical if the customer added a NAS share, but was told that they need to wait for rescan of all their music, including the new music on the added NAS, before they could even manually browse the NAS. It could potentially take many many hours just to add a NAS. Also, to rely on the OS mounting the network share could have unforeseen consequences. As an Aurender is meant to be an "applience", it *could* make sense to let the player handle the network shares itself, which points back to a rewrite of the MPD Upnp plugin to support network shares. As a consequence, this requires the use of AMM running on a MAC or PC, for the metadata to show when playing songs from a NAS. Proof: https://github.com/aurender/mpd-upnp And I believe they even licensed the mPad app. (mPad has since been improved, and using the iOS7 look, while the Aurender app is still an iOS4/iOS5/iOS6 app). How weird is that Aurender gets pretty much universal praise for their app, whereas ..say Bryston sometimes are criticised for relying on mPad. (which in it's current form is a better looking, with better usability than the forked Aurender app). Btw using a Samba/NFS share directly as music directory in user space is now a feature of mainline MPD, so I would recommend Aurender to once again refork MPD. MPD does not support multi "music directories" yet (and I think there's already a request for this feature), but that feature would be trivial to implement. Then Aurender music library could support both internal storage and NAS at the same time, and have the possibility to rescan both music directories regardless of one another. That would get rid of AMM once and for all. Then again, that might be what they already planning to do.. But please take a lesson from Bryston and give credit where due, and don't try to blatantly steal open source software. I know you don't want to hand out the source code of your players, and that is the reason you try to hide the origin of your players software. After all, the W20 costs 17000$+ USD, so it's fully "understandable" that you don't want this associated with a small open source project. But as much as you want to, the Aurender playback software ownership does not belong to you, and you are required by the GPL License to hand out the source code by your customers request.