Jump to content

DLNA - PURE Evoke F4 radio


aequoushumor

Recommended Posts

aequoushumor

All,

 

I'm doing some DLNA-streaming-testing with the beta-branch of the Emby-server (currently 3.1.254.0 beta). My television set (LG Webos) is showing up in the emby-device-list and starting a stream to the tv is working just fine. 

 

Unfortunately my PURE Evoke F4 internet radio is not showing up in the device-list and therefore it's not possible to stream music to the device. 

 

In the menu's of the radio itself, emby-server is showing and it is possible to select the 'songs' view and start to play music from there. However when selecting the 'albums' view, I'm getting a media server connection error.

 

I already did some testing with other DLNA-servers (twonkymedia and BubbleDlna). With these servers, the radio was showing up as a DLNA-renderer/receiver and it's possible to start a stream. On the radio itself, the 'album' view is accessible without error.

 

I'm seeing an error in the emby-logs when I try to open the 'albums' view. Full log attached. F4 has IP 192.168.1.86, ubuntu-server 192.168.1.20

 

2016-12-14 19:52:45.5702 Debug UpnpContentDirectory: Received control request X_BrowseByLetter
2016-12-14 19:52:45.5747 Error UpnpContentDirectory: Error processing control request
    *** Error Report ***
    Version: 3.1.254.0
    Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh
    Operating system: Unix 4.4.0.53
    64-Bit OS: True
    64-Bit Process: True
    Mono: 4.6.2 (Stable 4.6.2.7/08fd525 Mon Nov 28 20:49:26 UTC 2016)
    Processor count: 2
    Program data path: /var/lib/emby-server
    Application directory: /usr/lib/emby-server/bin
    MediaBrowser.Common.Extensions.ResourceNotFoundException: Unexpected control request name: X_BrowseByLetter
     at Emby.Dlna.ContentDirectory.ControlHandler.GetResult (System.String methodName, System.Collections.Generic.IDictionary`2[TKey,TValue] methodParams) [0x00107] in <66aef2809f3e4008989715e56e912f50>:0
     at Emby.Dlna.Service.BaseControlHandler.ProcessControlRequestInternal (MediaBrowser.Controller.Dlna.ControlRequest request) [0x00083] in <66aef2809f3e4008989715e56e912f50>:0
     at Emby.Dlna.Service.BaseControlHandler.ProcessControlRequest (MediaBrowser.Controller.Dlna.ControlRequest request) [0x0001e] in <66aef2809f3e4008989715e56e912f50>:0
    MediaBrowser.Common.Extensions.ResourceNotFoundException
     at Emby.Dlna.ContentDirectory.ControlHandler.GetResult (System.String methodName, System.Collections.Generic.IDictionary`2[TKey,TValue] methodParams) [0x00107] in <66aef2809f3e4008989715e56e912f50>:0
     at Emby.Dlna.Service.BaseControlHandler.ProcessControlRequestInternal (MediaBrowser.Controller.Dlna.ControlRequest request) [0x00083] in <66aef2809f3e4008989715e56e912f50>:0
     at Emby.Dlna.Service.BaseControlHandler.ProcessControlRequest (MediaBrowser.Controller.Dlna.ControlRequest request) [0x0001e] in <66aef2809f3e4008989715e56e912f50>:0 

emby-log.txt

Link to comment
Share on other sites

Hi, thanks for the report. I can make the error go away, although we have not yet implemented X-BrowseByLetter so I'm not sure what the result is going to be. It's either going to be blank or just send back everything i would imagine.

Link to comment
Share on other sites

aequoushumor

Will this make the Pure evoke radio available as an DLNA-player in the emby-webinterface ? This feature is actually more important to my setup than the error in the 'album' view.

Link to comment
Share on other sites

Probably not, no. I don't have one of those devices for testing so I'm afraid I'm not sure what the issue is. if you attach the complete server log then perhaps i'll be able to spot something.

Link to comment
Share on other sites

what are the contents of these two urls?

2016-12-14 19:52:29.2270 Info HttpClient: HttpClientManager GET: http://192.168.1.86:33459/93b2abac-cb6a-4857-b891-0019f58294b3.xml
2016-12-14 19:52:29.3302 Info HttpClient: HttpClientManager GET: http://192.168.1.86:33459/xml/AVTransport2.xml
Link to comment
Share on other sites

aequoushumor

Thx Luke,

 

In "Version 3.1.6193.13362 dev" the radio is detected and can be selected in the dropdown list. I will do some testing streaming music to the dlna-device.

Link to comment
Share on other sites

aequoushumor

Here are the results of the tests I did with the PURE evoke F4 radio (192.168.1.86): 

 

The device is detected correctly now and shows up in the device-list.

 

  • It's possible to start streaming an album, but streaming stops after 1 song.
  • The "now playing" - view does not provide any information. No album-art, no progress-bar
  • The 'next' 'previous' 'stop' and 'pause' buttons are greyed out
  • 'shuffle' button is grayed out
  • the volume and mute-buttons are working correctly

There are quite some error-reports in the log file (see attachment). Emby server is running on ubuntu 16.04 and version is : Version 3.1.256.0 beta

 

emby-log.txt

Link to comment
Share on other sites

aequoushumor

Can I fix this myself by creating a custom DLNA-profile for the Evoke F4 ?

Or will it require devolpment on the server side ?

Link to comment
Share on other sites

  • 1 month later...
aequoushumor

Luke,

 

Any update on this ?

 

Version 3.1.278.0 beta is still giving me the issues :

 

 

  • It's possible to start streaming an album, but streaming stops after 1 song.
  • The "now playing" - view does not provide any information. No album-art, no progress-bar
  • The 'next' 'previous' 'stop' and 'pause' buttons are not available
  • 'repeat' button is grayed out
  • the volume and mute-buttons are working correctly

 

  • It's possible to start streaming an album, but streaming stops after 1 song.
  • The "now playing" - view does not provide any information. No album-art, no progress-bar
  • The 'next' 'previous' 'stop' and 'pause' buttons are greyed out
  • 'shuffle' button is grayed out
  • the volume and mute-buttons are working correctly
Link to comment
Share on other sites

It's using a newer upnp protocol version which we haven't implemented yet. That's why some commands work, which are the same as the older protocol, and that's why others don't. We will look to support it in a future release. Thanks.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...