The reason I did this is that I have a moderate sized collection (around 45,000 FLAC files) and some of it comprised stuff that I'd like to keep, but play so infrequently that I'd not wish it to clutter up my main music collection (when browsing album covers, for example).
I run two media servers (Twonky and MinimServer) on my Qnap and there is no problem in doing so. I hope you find this " solution" workable in your unique circumstances. Simply store the kiddie data in a different place, so that you can point each DLNA Server it a different data path to keep the two "navigation trees" pointing to completely different content. There are probably a 1/2 dozen DLNA Servers compatible with your NAS. Everyone wins.Ĭheck out the App Center on your NAS. and you can choose Twonkymedia for all your Movies, TV Shows, and Music. Kids can choose the "kiddie" DLNA Server. If you do this, both DLNA Servers will be accessible on all your devices.
#Asset upnp large music collections install#
It would be far less work to simply install a second ( but completely different) DLNA Server for your children. Setting up parallel Twonky instances is next to impossible, due to the way DLNA works. I thought maybe editing the navigation tree (I have a custom one anyway) and using the "Compilation"-Folder feature I could workaround the problem, but I could not find a solution yet. However, at the start of my DLNA clients, I want to choose whether I want to listen to music or audiobooks.
Now I do want the children's audiobooks on the server, so that we can play them everywhere through DLNA. Likewise, random shuffle will bring up children's audiobooks in between my rock songs. Now my navigation tree "Artist" is littered with the audiobooks.
However, I now added my children's audiobooks to a separate directory. Twonky runs fine on my Qnap with a huge collection of Music. STurtle wrote:Is it possible to run two Twonky instances on one Qnap? Or can I virtually separate one Twonky server?
0 kommentar(er)
