Denon DNP-F109 seek problem
|
13-08-2013, 19:10
Post: #1
|
|||
|
|||
Denon DNP-F109 seek problem
Hi,
I've a Denon DNP-F109 digital network player and play to it from MinimServer using BubbleUPnP as the control point. When playing from MinimServer, it is not possible to pause or seek an MP3 file. When playing from proxified MinimServer (using BubbleUPnP Server), it works. When I try to seek or pause with regular MinimServer, I get an 'action failed' error in BubbleUPnP and the MinimServer trace-log shows no related output. When doing the same with proxified MinimServer, it works and the trace-log shows some related output, please see the attachment. The converation in this thread may be related to this problem. Thanks! |
|||
13-08-2013, 23:08
Post: #2
|
|||
|
|||
RE: Denon DNP-F109 seek problem
(13-08-2013 19:10)winxi Wrote: Hi, To debug this further, I would need to see a Wireshark trace of the interactions between the Denon and the BubbleUPnP proxy for a successful MP3 seek, including browsing to the MP3 track and selecting it for playing. This means you would need to run the BubbleUPnP proxy on a machine that can also run Wireshark (e.g., a Windows PC). To keep the Wireshark output as small as possible, please play an MP3 file with a low bitrate and perform the seek as soon as possible after the track starts to play. Please terminate the Wireshark trace as soon as the seek has been successful, then zip the Wireshark pcap file and upload it to my FTP server. Thanks! |
|||
14-08-2013, 22:08
Post: #3
|
|||
|
|||
RE: Denon DNP-F109 seek problem
(13-08-2013 23:08)simoncn Wrote: To debug this further, I would need to see a Wireshark trace of the interactions between the Denon and the BubbleUPnP proxy for a successful MP3 seek, including browsing to the MP3 track and selecting it for playing. This means you would need to run the BubbleUPnP proxy on a machine that can also run Wireshark (e.g., a Windows PC). I've done the test and uploaded the file to your ftp. This was my first time using Wireshark, so I hope I did everything right. The setup during the test was: -> Wireshark on my Win 8 PC (192.168.0.107) -> BubbleUPnP on my LG Nexus 4 (192.168.0.105) playing to the -> Denon (192.168.0.109) from MinimServer on the -> Synology NAS (192.168.0.251) proxified by BubbleUPnP Server on the Win 8 PC I should add that the Denon is somewhat special when it comes to seeking. It won't let seek FLAC or WAV files even from proxified MinimServer. However, the MP3 file I used for the test is seekable with proxified MinimServer, but not with regular MinimServer. |
|||
15-08-2013, 00:29
(This post was last modified: 15-08-2013 00:32 by simoncn.)
Post: #4
|
|||
|
|||
RE: Denon DNP-F109 seek problem
(14-08-2013 22:08)winxi Wrote: I've done the test and uploaded the file to your ftp. This was my first time using Wireshark, so I hope I did everything right. Thanks for doing this. As far as I can see, this Wireshark capture doesn't show the control point browsing to the MP3 track before selecting it for playing. It seems to start at the point where the track is selected for playing. Could you upload another Wireshark capture showing the browsing activity only, please? |
|||
15-08-2013, 10:42
Post: #5
|
|||
|
|||
RE: Denon DNP-F109 seek problem
(15-08-2013 00:29)simoncn Wrote: As far as I can see, this Wireshark capture doesn't show the control point browsing to the MP3 track before selecting it for playing. It seems to start at the point where the track is selected for playing. Could you upload another Wireshark capture showing the browsing activity only, please? I repeated the test with the same setup and uploaded the Wireshark trace to you ftp. This is what I did this time: I browsed in BubbleUPnP to the MP3 file and selected it to play on the Denon. I thought i did the browsing step for the previous trace also. It may be that in my first attempt BubbleUPnP used it's own cache for browsing, so it didn't show up in the Wireshark trace. |
|||
15-08-2013, 12:00
(This post was last modified: 15-08-2013 12:02 by bubbleguuum.)
Post: #6
|
|||
|
|||
RE: Denon DNP-F109 seek problem
To make finding the cause of this issue easier, I have compared the DIDL-Lite sent to the Denon (via SetAVTransportURI) between the proxy and the non-proxy minimserver.
As a side note, BubbleUPnP log output always contains the DIDL-Lite sent to a renderer. DIDL-Lite is identical except for the protocolInfo part: minimserver: protocolInfo="http-get:*:audio/mpeg:*" proxy minimserver: protocolInfo="http-get:*:audio/mpeg:DLNA.ORG_PN=MP3;DLNA.ORG_OP=01;DLNA.ORG_CI=0" The important part is DLNA.ORG_OP=01, with the second digit 1 indicating that http range based seek is supported. And this might explain why FLAC seeking may fails since DLNA.ORG_OP is never transmitted in that case since there is no DLNA profile for FLAC (eg a DLNA.ORG_PN value associated to FLAC). It will be worth trying to set DLNA.ORG_OP=01 for FLAC and others types (WAV) just in case it works by miracle. |
|||
15-08-2013, 12:18
Post: #7
|
|||
|
|||
RE: Denon DNP-F109 seek problem
(15-08-2013 12:00)bubbleguuum Wrote: To make finding the cause of this issue easier, I have compared the DIDL-Lite sent to the Denon (via SetAVTransportURI) between the proxy and the non-proxy minimserver. Thanks for this information! Quote:And this might explain why FLAC seeking may fails since DLNA.ORG_OP is never transmitted in that case since there is no DLNA profile for FLAC (eg a DLNA.ORG_PN value associated to FLAC). I'd be very happy to test this ![]() |
|||
15-08-2013, 17:27
Post: #8
|
|||
|
|||
RE: Denon DNP-F109 seek problem
(15-08-2013 12:00)bubbleguuum Wrote: The important part is DLNA.ORG_OP=01, with the second digit 1 indicating that http range based seek is supported. Thanks. This will be fixed in the next release of MinimServer. (15-08-2013 12:00)bubbleguuum Wrote: It will be worth trying to set DLNA.ORG_OP=01 for FLAC and others types (WAV) just in case it works by miracle. I'm away from home at the moment. I'll send you a test build when I return. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)