Page 1 of 1
Raumfeld support

Posted:
Mon Jun 20, 2016 10:52 am
by rwitkamp
I like the SubSonic server very... very much. As a user of Raumfeld streaming devices, I would like to have SubSonic as a DLNA server for my Raumfeld app. I have enabled DLNA in SubSonic but when I select it in the Raumfeld app, I do not see any albums, artists, songs... nothing. Other DLNA servers like twonkymedia worked fine with Raumfeld. Is there any possibility to show SubSonic in my Raumfeld app? or another way of supporting Raumfeld from Subsonic?
Regards,
Ron
Re: Raumfeld support

Posted:
Mon Jun 20, 2016 11:13 am
by acroyear
hmm...I've had problems with the DNLA connection for years. Never could quite get it to work.
When the Google Cast support comes out, you could manage it that way, theoretically. Not sure how well that would work using a tablet/phone to control it.
Beyond that? well, since it isn't an open platform for adding/submitting services, it is up to them, not any community, to add Subsonic support directly.
Re: Raumfeld support

Posted:
Mon Jun 20, 2016 11:29 am
by acroyear
Actually, the DNLA does work in principle. I have it working right now (6.02 beta) on VLC 2.
The problem is that the startup/init is *slow*, because it basically is exporting your entire collection* to the client at once. The client didn't render for a good 7 or 8 minutes after I clicked "expand node" 'til it could load the entire tree (and VLC doesn't have a 'please wait' indicator). Once in, though, it is playing my collection with no issues.
So consider that: try to connect to the UPNP again and just give it time. no promises, though.
*update: the structure and metadata. it isn't actually sending any files down to the client 'til you click to play something.
Re: Raumfeld support

Posted:
Tue Jun 21, 2016 4:59 am
by rwitkamp
Is there a SubSonic beta program? Is there a way to join beta-testing?
Regards,
Ron
Re: Raumfeld support

Posted:
Tue Jun 21, 2016 5:49 pm
by acroyear
Any beta release from SubSonic is publicly available. I only mentioned the beta because I'm actually one release behind the current (6.0).