INTERACT FORUM
Networks and Remotes => Media Network => Topic started by: streamerguy on January 24, 2014, 03:54:47 am
-
I'm having problems with DLNA push play to my Marantz NA-11S1 streamer. The issue is that it stops random, sometimes after 10 songs, then after 100 songs. I tested with both polling mode on and off, and setnextsupport on and off, but nothing helps. With setnextsupport off, it doesn't play gapless (of course it does not).
Gapless is ok, but I found out that the gap between the first and second song is never gapless, the rest of the songs will play gapless.
The behavior I see when playback stops is that the first part of the song (about 2 MB) is send to the streamer and then it stops. This is send before the previous song ends, I suppose to enable gapless playback, so that the buffer of the streamer is filling with the next song.
I have tested DLNA pull as well with only the DLNA server running (no renderer and controller) and that ran for more than one day until I stopped it.
When this happens I can see the following messages in the logfile. Does this mean that the Marantz really sends the bye-bye message or does JRiver interpret an event as a bye-bye message?
Any ideas?
55147165: 8980: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (16 ms)
55147321: 4376: Sharing Plugins: CUDPSocketReader::Accept: Finish (41699 ms)
55147321: 7440: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55147321: 7440: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55147321: 7440: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768::upnp:rootdevice
55147321: 7440: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz NA-11S1
55147321: 7440: Sharing Plugins: CDLNADeviceConnectionStatus::SetConnected: Start
55147321: 7440: Sharing Plugins: CDLNADeviceConnectionStatus::SetConnected: Changing connected to 0 for device: Marantz NA-11S1
55147321: 7440: Sharing Plugins: CDLNADeviceConnectionStatus::SetConnected: Finish (0 ms)
55147321: 7440: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55147321: 4376: Sharing Plugins: CUDPSocketReader::Accept: Start
55147321: 4376: Sharing Plugins: CUDPSocketReader::Accept: Finish (0 ms)
55147321: 3012: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55147321: 3012: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55147321: 3012: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768::upnp:rootdevice
55147321: 3012: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz NA-11S1
55147321: 3012: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55147321: 4376: Sharing Plugins: CUDPSocketReader::Accept: Start
55147321: 4376: Sharing Plugins: CUDPSocketReader::Accept: Finish (0 ms)
55147321: 5996: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55147321: 5996: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.248: NOTIFY: http://239.255.255.250:1900*
55147321: 5996: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:alive: uuid:73796E6F-6473-6D00-0000-0011321d1b71::upnp:rootdevice
55147321: 5996: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55147321: 4376: Sharing Plugins: CUDPSocketReader::Accept: Start
55147321: 4376: Sharing Plugins: CUDPSocketReader::Accept: Finish (0 ms)
55147321: 6484: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55147321: 6484: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.248: NOTIFY: http://239.255.255.250:1900*
55147321: 6484: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:alive: uuid:73796E6F-6473-6D00-0000-0011321d1b71::upnp:rootdevice
55147321: 6484: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55147321: 4376: Sharing Plugins: CUDPSocketReader::Accept: Start
55147430: 4376: Sharing Plugins: CUDPSocketReader::Accept: Finish (109 ms)
55147430: 6292: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55147430: 6292: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55147430: 6292: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768
55147430: 6292: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz NA-11S1
55147430: 6292: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55147430: 4376: Sharing Plugins: CUDPSocketReader::Accept: Start
55147430: 4376: Sharing Plugins: CUDPSocketReader::Accept: Finish (0 ms)
55147430: 1836: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55147430: 1836: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55147430: 1836: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768
55147430: 1836: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz NA-11S1
55147430: 1836: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55147430: 4376: Sharing Plugins: CUDPSocketReader::Accept: Start
55147446: 4956: Handheld: CWMDMThread::Thread: Start
55147446: 4956: Handheld: CWMDMThread::Thread: Starting work loop
-
^
Several comments:
1) Concerning SetNextAVTransportUri not working on the first track..
When playing the first track of a playlist MC sends one SetAVTransportUri command followed by an SetNextAVTransportUri command; whereas on all subsequent tracks MC sends just a single SetNextAVTransportUri command.
For the first track the SetAVTransportUri command is sent immediately when you hit Play, and then MC waits for a "playing" signal from the player before sending the subsequent SetNextAVTransportUri command. So if the player does not send a "playing" signal, (or if MC does not observe the signal), then MC will not send the subsequent SetNextAVTransportUri command. And my suspicion is that when the player reaches the end of the first track and stops playing, it then sends a(nother) "stopped" signal to MC, and it is this signal that finally triggers (i.e. much too late) the SetNextAVTransportUri command to be sent.
So the question is whether the player is really sending a "playing" signal, and/or whether MC is not seeing that "playing" signal. You would have to do a Wireshark capture in order to find out what exactly is going on, and thus tell if the bug is in MC or in the player.
2) Concerning the random stopping after 10 .. 100 tracks
Your symptoms indicate that the player is indeed breaking off the HTTP download of the music stream. And the log indicates that the player is indeed sending a byebye notification. So IMHO this is surely a bug in your player.
-
Thanks Andrew,
I will send this information to Marantz. Hopefully they can fix this with a firmware upgrade.
-
Mezzmo v4.0 and Mezzmo Android will released in February
-
Hi Andrew,
I send your findings to Marantz and they tell me that they are not able to reproduce this issue on a test server.
Are there more (network related) reasons that MC sees a bye-bye message coming from the Marantz?
Thanks and regards
-
I send your findings to Marantz and they tell me that they are not able to reproduce this issue on a test server.
Are there more (network related) reasons that MC sees a bye-bye message coming from the Marantz?
Just a few ideas.
Your original log shows two IP addresses sending alive and bye-bye notifications; namely 192.168.1.248 and 192.168.1.245.
1) So did your receiver change its IP address during the session? Is the receiver getting its IP address dynamically via DHCP? And if so, perhaps you have a very short DHCP lease time (about the duration of 10..100 songs perhaps)? If so, then try setting your DHCP server to a) have a longer lease time, and b) to keep a reserved IP address for your receiver. Or alternatively set a static IP address in the receiver.
2) Similar to the above... Do you have two devices on your network using the same IP address? Maybe another device is broadcasting the troublesome bye-byes that mess up your receiver. If all your devices are using DHCP this should not be the case, but perhaps you have another device who has a static IP address lying within the DHCP server's assignable address range. It could for example be that your router's (or your wifi access point's) own IP address is 192.168.1.248 / 192.168.1.245, and if it is a UPnP enabled box, it would thus be sending its own alives and bye-byes on that address.
-
Hi Andrew,
Thanks for your answer.
I'm using DHCP with fixed leases for all my devices and the lease time is 24 hours. So I'm pretty sure my devices keep getting the same addres.
Device .245 is the Marantz NA-11S1 and .248 is a Synology Nas which I don't use for playback. It's just a backup unit of a friend.
Regards
-
Well something must be sending those bye-byes...
55147321: 7440: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55147321: 7440: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768::upnp:rootdevice
..
55147321: 3012: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55147321: 3012: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768::upnp:rootdevice
..
55147430: 6292: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55147430: 6292: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768
..
55147430: 1836: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55147430: 1836: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768
-
Hi Andrew,
I have been looking into the logfile again and it seems that it starts every with a "CTCPSocketReader::Write: Write failed". Then the Marantz starts sending bye-bye messages. Does this give a clue?
Thanks.
55226460: 1852: Reader: CWinINetReader::Open: Opening http://192.168.1.245:8080/RenderingControl/ctrl
55226460: 1004: Reader: CWinINetReader::Thread: Start
55226460: 1004: Reader: CWinINetReader::Connect: Start
55226460: 1004: Reader: CWinINetReader::Connect: Finish (0 ms)
55226460: 1004: Reader: CWinINetReader::DownloadFromHTTPURL: Start
55227490: 1004: Reader: CWinINetReader::DownloadFromHTTPURL: Success
55227490: 1004: Reader: CWinINetReader::DownloadFromHTTPURL: Finish (1030 ms)
55227490: 1004: Reader: CWinINetReader::Thread: Finish (1030 ms)
55227490: 1852: Reader: CWinINetReader::Open: Finish (1030 ms)
55227490: 1852: Reader: CWinINetReader::Close: Start
55227490: 1852: Reader: CWinINetReader::Close: Finish (0 ms)
55227490: 1852: Reader: CWinINetReader::Open: Start
55227490: 1852: Reader: CWinINetReader::Open: Opening http://192.168.1.245:8080/RenderingControl/ctrl
55227490: 3688: Reader: CWinINetReader::Thread: Start
55227490: 3688: Reader: CWinINetReader::Connect: Start
55227490: 3688: Reader: CWinINetReader::Connect: Finish (0 ms)
55227490: 3688: Reader: CWinINetReader::DownloadFromHTTPURL: Start
55227771: 3952: General: CMCUICore::SystemPowerManager_UpdateActions: Start
55227771: 3952: General: CMCUICore::SystemPowerManager_UpdateActions: UI Mode: -999; Playing: 0
55227771: 3952: General: CMCUICore::SystemPowerManager_UpdateActions: Finish (result: 0) (0 ms)
55228535: 3688: Reader: CWinINetReader::DownloadFromHTTPURL: Success
55228535: 3688: Reader: CWinINetReader::DownloadFromHTTPURL: Finish (1045 ms)
55228535: 3688: Reader: CWinINetReader::Thread: Finish (1045 ms)
55228535: 1852: Reader: CWinINetReader::Open: Finish (1045 ms)
55228535: 1852: Reader: CWinINetReader::Close: Start
55228535: 1852: Reader: CWinINetReader::Close: Finish (0 ms)
55229112: 4376: Sharing Plugins: CTCPSocketReader::Write: Write failed: 10054 (socket: 1684)
55229112: 4376: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (181445 ms)
55229128: 3952: General: CMCUICore::SystemPowerManager_UpdateActions: Start
55229128: 3952: General: CMCUICore::SystemPowerManager_UpdateActions: UI Mode: -999; Playing: 0
55229128: 3952: General: CMCUICore::SystemPowerManager_UpdateActions: Finish (result: 0) (0 ms)
55229830: 4148: Sharing Plugins: CUDPSocketReader::Accept: Finish (6927 ms)
55229830: 4732: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55229830: 4732: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55229830: 4732: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768::upnp:rootdevice
55229830: 4732: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz NA-11S1
55229830: 4732: Sharing Plugins: CDLNADeviceConnectionStatus::SetConnected: Start
55229830: 4732: Sharing Plugins: CDLNADeviceConnectionStatus::SetConnected: Changing connected to 0 for device: Marantz NA-11S1
55229830: 4732: Sharing Plugins: CDLNADeviceConnectionStatus::SetConnected: Finish (0 ms)
55229830: 4732: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55229830: 4148: Sharing Plugins: CUDPSocketReader::Accept: Start
55229923: 4148: Sharing Plugins: CUDPSocketReader::Accept: Finish (93 ms)
55229923: 888: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55229923: 888: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55229923: 888: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768
55229923: 888: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz NA-11S1
55229923: 888: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55229923: 4148: Sharing Plugins: CUDPSocketReader::Accept: Start
55230033: 4148: Sharing Plugins: CUDPSocketReader::Accept: Finish (110 ms)
55230033: 2356: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55230033: 2356: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55230033: 2356: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768::urn:schemas-upnp-org:device:MediaRenderer:1
55230033: 2356: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz NA-11S1
55230033: 2356: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55230033: 4148: Sharing Plugins: CUDPSocketReader::Accept: Start
55230142: 4148: Sharing Plugins: CUDPSocketReader::Accept: Finish (109 ms)
55230142: 788: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55230142: 788: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55230142: 788: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768::urn:schemas-upnp-org:service:RenderingControl:1
55230142: 788: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz NA-11S1
55230142: 788: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55230142: 4148: Sharing Plugins: CUDPSocketReader::Accept: Start
55230235: 4148: Sharing Plugins: CUDPSocketReader::Accept: Finish (93 ms)
55230235: 3260: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55230235: 3260: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55230235: 3260: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768::urn:schemas-upnp-org:service:ConnectionManager:1
55230235: 3260: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz NA-11S1
55230235: 3260: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55230235: 4148: Sharing Plugins: CUDPSocketReader::Accept: Start
55230345: 3952: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Start
55230345: 3952: General: CMainUIWnd::SetMCView: Start
55230345: 3952: General: CMainUIWnd::SetMCView: View info name: Player
55230345: 3952: General: CMainUIWnd::SetMCView: Hiding old view
55230345: 3952: General: CMainUIWnd::SetMCView: Creating new view
55230345: 3952: General: CMCViewContainerWnd::Create: Start
55230345: 3952: General: CMCViewContainerWnd::Create: Creating window
55230345: 3952: General: CMCViewContainerWnd::Create: Initializing
55230345: 3952: General: CViewHeaderWnd::Initialize: Start
55230345: 3952: General: CViewHeaderWnd::Initialize: Finish (0 ms)
55230345: 3952: General: CMCViewContainerWnd::Create: Finish (0 ms)
55230345: 3952: General: CMainUIWnd::SetMCView: Loading view
55230345: 4148: Sharing Plugins: CUDPSocketReader::Accept: Finish (110 ms)
55230345: 3632: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55230345: 3632: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55230345: 3632: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768::urn:schemas-upnp-org:service:AVTransport:1
55230345: 3632: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz NA-11S1
55230345: 3632: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55230345: 4148: Sharing Plugins: CUDPSocketReader::Accept: Start
55230345: 3952: General: CMJFileListCtrl::StartFileInsertion: Start
55230345: 3952: General: CMJFileListCtrl::StartFileInsertion: Finish (0 ms)
55230345: 3952: General: CMJFileListCtrl::FinishFileInsertion: Start
55230345: 3952: General: CMJFileListCtrl::SetItemCount: Start
55230345: 3952: General: CMJFileListCtrl::SetItemCount: Finish (0 ms)
55230345: 3952: General: CMJFileListCtrl::FinishFileInsertion: Finish (0 ms)
55230345: 3952: General: CMainUIWnd::SetMCView: Finishing view creation
55230345: 3952: General: CMainUIWnd::SetMCView: View creation time: 6,336
55230345: 3952: General: CMainUIWnd::Resize: Start
55230345: 3952: General: CMainUIWnd::Resize: Finish (0 ms)
55230345: 3952: General: CMainUIWnd::SetMCView: View show / update time: 3,930
55230345: 3952: General: CMainUIWnd::SetMCView: Finish (0 ms)
55230345: 3952: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Finish (0 ms)
55230407: 3952: General: CMJFileListCtrl::OnDestroy: Start
55230407: 3952: General: CMJFileListCtrl::OnDestroy: Finish (0 ms)
55230547: 4148: Sharing Plugins: CUDPSocketReader::Accept: Finish (202 ms)
55230547: 3132: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55230547: 3132: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55230547: 3132: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768::upnp:rootdevice
55230547: 3132: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz NA-11S1
55230547: 3132: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55230547: 4148: Sharing Plugins: CUDPSocketReader::Accept: Start
55230657: 4148: Sharing Plugins: CUDPSocketReader::Accept: Finish (110 ms)
55230657: 2648: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55230657: 2648: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55230657: 2648: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768
55230657: 2648: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz NA-11S1
55230657: 2648: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55230657: 4148: Sharing Plugins: CUDPSocketReader::Accept: Start
55230750: 4148: Sharing Plugins: CUDPSocketReader::Accept: Finish (93 ms)
55230750: 4136: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55230750: 4136: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55230750: 4136: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768::urn:schemas-upnp-org:device:MediaRenderer:1
55230750: 4136: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz NA-11S1
55230750: 4136: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55230750: 4148: Sharing Plugins: CUDPSocketReader::Accept: Start
55230859: 4148: Sharing Plugins: CUDPSocketReader::Accept: Finish (109 ms)
55230859: 3024: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
55230859: 3024: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.245: NOTIFY: http://239.255.255.250:1900*
55230859: 3024: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781a0768::urn:schemas-upnp-org:service:RenderingControl:1
55230859: 3024: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz NA-11S1
55230859: 3024: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
55230859: 4148: Sharing Plugins: CUDPSocketReader::Accept: Start
-
Socket Error 10054 means "Connection Reset by Peer"..
So in this case, MC was sending something to the Marantz (probably serving the stream to it), and the Marantz closed the socket. And then the Marantz started sending its bye-bye messages. And then presumably it actually went off line...
Now obviously it is hard to say why the Marantz closed its socket, and sent bye-byes. It could have been because it did not like what MC was trying to send to it. Or it could be because it got sick on its own.
Typically if a media server is pushing a stream to a renderer, then the renderer may at any time close the socket. Either because it does not like the format of the data being sent, or because it has stopped playing. So a 10054 error is very common. But you would certainly not expect a renderer to get so upset about the contents of data being pushed to it, that it would close the socket and go into a huff and then go offline. That is definitely very sick behaviour...
-
Thanks Andrew.
Can I send you the complete logfile? Maybe you can check if there is something else going on.
-
Thanks Andrew.
Can I send you the complete logfile? Maybe you can check if there is something else going on.
Ok. Please pm it to me.
-
Hi Andrew,
Please tell me how to add the attachment to a PM. It's about 4MB.
Thanks
-
Hi Andrew,
Ihave done some testing with a Marantz SR7008 reciever with the same results:
4635367: 3972: Reader: CWinINetReader::DownloadFromHTTPURL: Success
4635367: 3972: Reader: CWinINetReader::DownloadFromHTTPURL: Finish (0 ms)
4635367: 3972: Reader: CWinINetReader::Thread: Finish (0 ms)
4635367: 5804: Reader: CWinINetReader::Open: Finish (0 ms)
4635367: 5804: Reader: CWinINetReader::Close: Start
4635367: 5804: Reader: CWinINetReader::Close: Finish (0 ms)
4635367: 5804: Playback: CPlayerZone::DLNADeviceSubscription_PropertyChanged: Start
4635367: 5804: Playback: CPlayerZone::DLNADeviceSubscription_PropertyChanged: State changing from 2 to 3
4635367: 5804: Playback: CPlayerZone::DLNADeviceSubscription_PropertyChanged: Finish (0 ms)
4635367: 4264: Playback: CPlayerZone::DLNAProcessPlaybackState: Start
4635367: 4264: Playback: CPlayerZone::DLNAProcessPlaybackState: Finish (0 ms)
4635367: 5804: Reader: CWinINetReader::Open: Start
4635367: 5804: Reader: CWinINetReader::Open: Opening http://192.168.1.246:8080/RenderingControl/ctrl
4635367: 5312: Reader: CWinINetReader::Thread: Start
4635367: 5312: Reader: CWinINetReader::Connect: Start
4635367: 5312: Reader: CWinINetReader::Connect: Finish (0 ms)
4635367: 5312: Reader: CWinINetReader::DownloadFromHTTPURL: Start
4635461: 5312: Reader: CWinINetReader::DownloadFromHTTPURL: Success
4635461: 5312: Reader: CWinINetReader::DownloadFromHTTPURL: Finish (94 ms)
4635461: 5312: Reader: CWinINetReader::Thread: Finish (94 ms)
4635461: 5804: Reader: CWinINetReader::Open: Finish (94 ms)
4635461: 5804: Reader: CWinINetReader::Close: Start
4635461: 5804: Reader: CWinINetReader::Close: Finish (0 ms)
4635461: 5804: Reader: CWinINetReader::Open: Start
4635461: 5804: Reader: CWinINetReader::Open: Opening http://192.168.1.246:8080/RenderingControl/ctrl
4635461: 5592: Reader: CWinINetReader::Thread: Start
4635461: 5592: Reader: CWinINetReader::Connect: Start
4635461: 5592: Reader: CWinINetReader::Connect: Finish (0 ms)
4635461: 5592: Reader: CWinINetReader::DownloadFromHTTPURL: Start
4635539: 1328: Sharing Plugins: VHTTPMessage::ParseBody: Finish (203 ms)
4635539: 1328: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 192.168.1.246: NOTIFY: http://192.168.1.250:52101/eventSub
4635539: 1328: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
4635539: 1328: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (203 ms)
4635570: 5592: Reader: CWinINetReader::DownloadFromHTTPURL: Success
4635570: 5592: Reader: CWinINetReader::DownloadFromHTTPURL: Finish (109 ms)
4635570: 5592: Reader: CWinINetReader::Thread: Finish (109 ms)
4635570: 5804: Reader: CWinINetReader::Open: Finish (109 ms)
4635570: 5804: Reader: CWinINetReader::Close: Start
4635570: 5804: Reader: CWinINetReader::Close: Finish (0 ms)
4635585: 3664: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
4635585: 3664: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 192.168.1.246: GET: http://192.168.1.250:52100/AArs/3278.jpg
4635585: 3664: Sharing Plugins: VHTTPMessage::Write: Wrote 37828 bytes
4635585: 3664: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
4635757: 5808: Sharing Plugins: CUDPSocketReader::Accept: Finish (17191 ms)
4635757: 5832: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
4635757: 5832: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.246: NOTIFY: http://239.255.255.250:1900*
4635757: 5832: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781f20b8::upnp:rootdevice
4635757: 5832: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz SR7008
4635757: 5832: Sharing Plugins: CDLNADeviceConnectionStatus::SetConnected: Start
4635757: 5832: Sharing Plugins: CDLNADeviceConnectionStatus::SetConnected: Changing connected to 0 for device: Marantz SR7008
4635757: 5832: Sharing Plugins: CDLNADeviceConnectionStatus::SetConnected: Finish (0 ms)
4635757: 5832: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
4635757: 5808: Sharing Plugins: CUDPSocketReader::Accept: Start
4635788: 5260: Sharing Plugins: CTCPSocketReader::Write: Write failed: 10054 (socket: 1476)
4635788: 5260: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (4836 ms)
4635804: 4264: General: CMCUICore::SystemPowerManager_UpdateActions: Start
4635804: 4264: General: CMCUICore::SystemPowerManager_UpdateActions: UI Mode: -999; Playing: 0
4635804: 4264: General: CMCUICore::SystemPowerManager_UpdateActions: Finish (result: 0) (0 ms)
4635866: 5808: Sharing Plugins: CUDPSocketReader::Accept: Finish (109 ms)
4635866: 2408: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
4635866: 2408: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.246: NOTIFY: http://239.255.255.250:1900*
4635866: 2408: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781f20b8
4635866: 2408: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz SR7008
4635866: 2408: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
4635866: 5808: Sharing Plugins: CUDPSocketReader::Accept: Start
4635960: 5808: Sharing Plugins: CUDPSocketReader::Accept: Finish (94 ms)
4635960: 4500: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
4635960: 4500: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.246: NOTIFY: http://239.255.255.250:1900*
4635960: 4500: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781f20b8::urn:schemas-upnp-org:device:MediaRenderer:1
4635960: 4500: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz SR7008
4635960: 4500: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
4635960: 5808: Sharing Plugins: CUDPSocketReader::Accept: Start
4636069: 5808: Sharing Plugins: CUDPSocketReader::Accept: Finish (109 ms)
4636069: 3092: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
4636069: 3092: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.246: NOTIFY: http://239.255.255.250:1900*
4636069: 3092: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781f20b8::urn:schemas-upnp-org:service:RenderingControl:1
4636069: 3092: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz SR7008
4636069: 3092: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
4636069: 5808: Sharing Plugins: CUDPSocketReader::Accept: Start
4636069: 5808: Sharing Plugins: CUDPSocketReader::Accept: Finish (0 ms)
4636069: 3536: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
4636069: 3536: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.248: NOTIFY: http://239.255.255.250:1900*
4636069: 3536: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:alive: uuid:73796E6F-6473-6D00-0000-0011321d1b71::upnp:rootdevice
4636069: 3536: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
4636069: 5808: Sharing Plugins: CUDPSocketReader::Accept: Start
4636163: 5808: Sharing Plugins: CUDPSocketReader::Accept: Finish (94 ms)
4636163: 2968: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
4636163: 2968: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.246: NOTIFY: http://239.255.255.250:1900*
4636163: 2968: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781f20b8::urn:schemas-upnp-org:service:ConnectionManager:1
4636163: 2968: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz SR7008
4636163: 2968: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
4636163: 5808: Sharing Plugins: CUDPSocketReader::Accept: Start
4636178: 4132: Sharing Plugins: CUDPSocketReader::Accept: Canceled.
4636178: 4132: Sharing Plugins: CUDPSocketReader::Accept: Deleting socket
4636178: 4132: Sharing Plugins: CUDPSocketReader::Accept: Finish (28532 ms)
4636272: 4264: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Start
4636272: 4264: Sharing Plugins: CMCDLNA::DLNACore_DevicesChanged: Finish (0 ms)
4636272: 5808: Sharing Plugins: CUDPSocketReader::Accept: Finish (109 ms)
4636272: 1560: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
4636272: 1560: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.246: NOTIFY: http://239.255.255.250:1900*
4636272: 1560: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781f20b8::urn:schemas-upnp-org:service:AVTransport:1
4636272: 1560: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz SR7008
4636272: 1560: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
4636272: 5808: Sharing Plugins: CUDPSocketReader::Accept: Start
4636443: 5808: Sharing Plugins: CUDPSocketReader::Accept: Finish (171 ms)
4636459: 5180: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
4636459: 5180: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.246: NOTIFY: http://239.255.255.250:1900*
4636459: 5180: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781f20b8::upnp:rootdevice
4636459: 5180: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz SR7008
4636459: 5180: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
4636459: 5808: Sharing Plugins: CUDPSocketReader::Accept: Start
4636553: 5808: Sharing Plugins: CUDPSocketReader::Accept: Finish (94 ms)
4636553: 5212: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
4636553: 5212: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.246: NOTIFY: http://239.255.255.250:1900*
4636553: 5212: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781f20b8
4636553: 5212: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz SR7008
4636553: 5212: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
4636553: 5808: Sharing Plugins: CUDPSocketReader::Accept: Start
4636662: 5808: Sharing Plugins: CUDPSocketReader::Accept: Finish (109 ms)
4636662: 4788: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
4636662: 4788: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.1.246: NOTIFY: http://239.255.255.250:1900*
4636662: 4788: Sharing Plugins: CSSDPWorker::ProcessNotify: ssdp:byebye: uuid:5f9ec1b3-ff59-19bb-8530-0006781f20b8::urn:schemas-upnp-org:device:MediaRenderer:1
4636662: 4788: Sharing Plugins: CDLNADeviceConnectionStatus::NotifyReceivedByeBye: Bye-bye from device: Marantz SR7008
4636662: 4788: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
-
GetMediaInfo must work properly in your firmware for us to use SetNextAVTransportURI.
When we are in Play state we'll try ONCE to send the next track to the renderer.
If that fails we drop back to usual track transition logic until the next track is sent.
-
Hi Bob,
I don't understand exactly what you mean because I don't have issues with gapless playback. Only after the first song, there is a gap. The issue is that the streamer randomly stops with DLNA push.
Thanks
-
Hi Bob,
I don't understand exactly what you mean because I don't have issues with gapless playback. Only after the first song, there is a gap. The issue is that the streamer randomly stops with DLNA push.
Thanks
From what I understood from your post that wasn't the case when SetNext support was turned off. If this is not the case what I said doesn't apply.
-
Hi Bob,
Maybe you can give me an answer why playback stops?
Thanks
-
Hi Bob,
Maybe you can give me an answer why playback stops?
Thanks
Not really.
I think Andrew asked the right questions, specifically if the Marantz didn't like the format of one of the files it was sent. I've even run into a case where too large embedded cover art caused a problem.
Also, the Marantz firmware could be buggy and given the timing of certain events just error.
You might see if there is any sleep function on the receiver that you can disable for testing.
-
I think Andrew asked the right questions, specifically if the Marantz didn't like the format of one of the files it was sent. I've even run into a case where too large embedded cover art caused a problem.
That promotes me to ask another question. What format are you pushing to the Marantz? The cleanest thing to push to the player would be L16 No Header. Since that contains pure audio samples only, and there is no risk of any tags and other 'junk' getting in there...
-
I have been testing using the setting "Original" with flac files and "specified output format" 24 bits.
I just tested L16 and this format is played fine by the Marantz (indeed no format info on display), but L24 is not (file format error). I like of course to use 24 bits as I have many high res flac files.
Thanks.
-
I have been testing using the setting "Original" with flac files and "specified output format" 24 bits.
I just tested L16 and this format is played fine by the Marantz (indeed no format info on display), but L24 is not (file format error). I like of course to use 24 bits as I have many high res flac files.
Ok.
I am not surprised it won't play L24 since that is a very unusual format (basically invented by JRiver).
I think you should now go back to Marantz with this test case to prove to them that their 24bit Flac replay is broken. Please keep us posted...
-
And in the meantime you could try 24 bit wave. That might work.
-
And in the meantime you could try 24 bit wave. That might work.
Bob, the OP said his source material is 24bit Flac, and MC does not offer transcoding to Wav.
(This might get me started again on my favorite topic that MC ought to have an option to transcode automatically to the best quality choice out of the many formats that the render declares in its SinkProtocolInfo...)
-
After a few hours it stopped again using L16.
Now I have done some testing using PCM 24 bit and "Present Small Artwork" checked. Still the same results, both on the NA-11S1 and on the SR7008. Both stop after a random number of songs. If I push play again in MC, both start playing at the beginning of the last song.
The behavior I see in the Media Network Activity Log is that the first 2-3 MB of the next song are send to the device, then the cover art is send and then it stops. You even hear the first seconds of that song.
-
^
If it fails with L16 then the problem has nothing to do with the size of embedded cover art, and it has nothing to do with any other embedded meta data either. (This is because L16 is pure music samples only and does not carry anything else at all...)
EDIT: Oops. I reread your post again ...
There are two mechanisms to pass album art and other metadata to a UPnP renderer. One mechanism passes it embedded in the audio stream, and the other mechanism passes it as an argument in the SetAvTransportURI command.
So from rereading your post again, we seem to be talking about the second mechanism.
The option "Present (Small) Album Art" determines if MC shall include one or two AlbumArtURI URLs in the SetAvTransportURI metadata argument. Normally MC includes one URL for "medium" sized artwork, and the option "Present (Small) Album Art" means that MC shall include a URL for "small" sized artwork too => so in other words "Present Small" is probably neither the problem nor the solution.
From rereading your post again, it seems that your Marantz is choking after it does its HTTP GET to fetch an art image from MC for such an AlbumArtURI metadata tag. And that it is only choking after several such GET's have been done. So the question is why it is choking? I can think of a few potential reasons: a) an art buffer overflow in the renderer, b) something in the particular image that causes the choke, c) a memory or resource overflow due to either the renderer or MC not closing sockets on prior HTTP GETs.
Can you test your renderer again playing L16 formatted audio, from some audio tracks that do not have any album art in MC? Try making a short playlist of say two or three test tracks that don't have any art, and put this playlist on repeat. That will check if the issue is really due to the renderer's GETs on the artwork, or if it is another problem with the renderer.
-
Thanks Andrew,
Is there anything I can test or is this definitely a firmware issue? It' s strange that two different devices behave the same way or they share the same networking firmware.
Have you been able to take a look at the logfiles I have send you?
-
^
I modified my prior post; so please have a look at the corrected version above ..
-
Hi Andrew,
I took 4 files and removed the art using MC and it doesn't show the art anymore in MC. But I still see a .jpg file being send to the Marantz in the activity log. When I take a look at the Marantz I don't see the art of the current song, but instead I see a map icon.
Is this what you mean? Or are there some more DLNA settings to change? Only DLNA and DLNA extra are checked.
Thanks
-
After the second song it disappeared shortly from 'Playing Now" nn MC and after it came back there is only 1 song in the "playlist". After playing this song it stopped.
-
Now I see. I didn't test with L16. Will start testing from now on.
-
Now I'm testing with L16. After each wav file it send 6 or 7 times a jpg file (the map icon).
Sometimes during playback I see messages in the activity log like:
SUBSCRIBE:http://xxx.xxx.xxx.xxx:52100/Contentdirectory/Event
POST:http://xxx.xxx.xxx.xxx:52100/ContentDirectory/Control
I don't see these messages every time. So after starting another playlist I sometimes only see .wav and .jpg messages.
-
The streamer just stopped after only 5 songs. And again bye-bye messages in the MC log file.
-
Hi Andrew,
I was able to create a wireshark trace from this session. I can send it to you if you want.
Thanks.
-
Hi Andrew,
I was able to create a wireshark trace from this session. I can send it to you if you want.
Thanks.
Yes please.
-
You got PM.
-
You got PM.
I will examine your WireShark logs this evening...
Now I'm testing with L16. After each wav file it send 6 or 7 times a jpg file (the map icon).
That is odd. Can you please post the image?
Sometimes during playback I see messages in the activity log like:
SUBSCRIBE:http://xxx.xxx.xxx.xxx:52100/Contentdirectory/Event
POST:http://xxx.xxx.xxx.xxx:52100/ContentDirectory/Control
I don't see these messages every time.
The SUBSCRIBE command is a background activity of MC which is asynchronous to the playing process. The POST commands are sent every time that MC issues a command to the player (new track/pause/play/volume/fwd/rew/etc.) and every time it requests the player for information (position/status/volume etc.)
-
Hi Andrew,
Don't mind the jpg file send 6 or 7 times. I discovered is was due to the fact that I had a session opened to the web interface of the player.
So MC needs to send the POST commands always? Because sometimes I start playback and I see these messages. Currently the streamer is playing and I only see GET messages for the flac (changed back to original in DLNA settings) and jpg files, no POST messages.
Thanks.
-
Currently the streamer is playing and I only see GET messages for the flac (changed back to original in DLNA settings) and jpg files
Puzzled. I looked at all of your WireShark captures and I did not see any GET commands from the Marantz to MC for any music streams at all. (One of your captures had a GET from Winamp to MC for a music stream). But there is no evidence in any of your captures that anything was actually being streamed at all...
-
Hi Andrew,
In the large wireshark file I send to you, I see 3 times a GET for a .wav file and 3 times for a .JPG file.
It's easier to see if you click on Analyze and then Expert Info. Then choose the Chats tab.
Thanks
-
Hi Andrew,
Is there something I need to test at this point?
Thanks
-
Is there something I need to test at this point?
I examined your Wireshark capture again. The only HTTP GET transactions that relate to music streaming from MC are ones like the following:
GET /Music/F100648.wav HTTP/1.1
Host: 192.168.1.250:52100
Icy-MetaData: 1
Connection: close
transferMode.dlna.org: Streaming
User-Agent: WinampMPEG/2.8
Accept: */*
HTTP/1.1 200 OK
transferMode.dlna.org: Streaming
Content-Type: audio/L16;rate=192000;channels=2
Server: Windows, UPnP/1.1 DLNADOC/1.50, JRiver/19
Content-Length: 261888000
Accept-Ranges: bytes
Connection: close
Date: Thu, 20 Mar 2014 20:14:03 GMT
As you can see, the User Agent is "WinampMPEG/2.8" which (IMHO) does not look to be a likely user agent name for a Marantz receiver. So I wonder if your problem is that you have other things going on on your LAN that may be confusing things? Do have anyone at home using WinAmp??
-
I don't understand. I'm sure no one is using Winamp. It was installed a year ago, but I uninstalled it after a few days.
-
I don't understand.
Me neither :o I am just telling you what I see in your network traffic.
-
You could install device spy (uPNP tools for developer).
Install the firefox addon "live http headers" (install firefox if you don't have it).
Find the Marantz in device spy.
Get the presentation page or xml url for the Marantz from device spy
Open it in firefox.
In firefox Tools->live http headers.
Reload the page
and you'll see the firefox get and the Marantz reply with the Marantz user agent.
-
Hi Bob.
Is this what you mean?
http://192.168.1.245:8080/description.xml
GET /description.xml HTTP/1.1
Host: 192.168.1.245:8080
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Connection: keep-alive
Cache-Control: max-age=0
HTTP/1.1 200 OK
Content-Type: text/xml;charset="utf-8"
Content-Language: en
Content-Length: 3142
----------------------------------------------------------
In the release notes of version 19.0.123 there is something about DLNA NOTIFY. Has that something to do with the issues I have?
-
... you'll see the firefox get and the Marantz reply with the Marantz user agent.
Hi bob,
AFAIK a renderer should include User Agent headers in its GET or POST requests -- but it is wrong to expect User Agent headers in renderer's HTTP/1.x 200 OK responses.
OTOH a renderer should include a Server header in its HTTP/1.x 200 OK responses; but as the OP's prior post indicates, it seems that in this case the renderer is not offering that. And IMHO that alone indicates to me that the renderer is not compliant.
-
In the release notes of version 19.0.123 there is something about DLNA NOTIFY. Has that something to do with the issues I have?
No.
-
Hi bob,
AFAIK a renderer should include User Agent headers in its GET or POST requests -- but it is wrong to expect User Agent headers in renderer's HTTP/1.x 200 OK responses.
OTOH a renderer should include a Server header in its HTTP/1.x 200 OK responses; but as the OP's prior post indicates, it seems that in this case the renderer is not offering that. And IMHO that alone indicates to me that the renderer is not compliant.
I was expecting to see the Server header in the presentation page, I tried it with a few renderers here and it worked.
I was wondering if perhaps the Marantz was using some winamp code as it's renderer.
-
Hi Bob and Andrew,
So the conclusion is that the Marantz is not fully DLNA compliant?
-
So the conclusion is that the Maranftz is not fully DLNA compliant?
I would not make that conclusion yet. However the logs you submitted don't show a clear picture and don't even seem to come from a Marantz device so it is hard to say. Is there some way that you can test on a lan where only the HTPC and the receiver are present and nothing else?
-
I'm currently testing with a laptop with a clean JRiver installation directly connected to the Marantz using a switch to test a standalone situation as you asked to do.
After playing about 40 songs without any issues, it keeps repeating the same song. On the JRiver gui it says it's playing the song before this song and this information is on the Marantz as well.
Any idea?
-
I'm currently testing with a laptop with a clean JRiver installation directly connected to the Marantz using a switch to test a standalone situation as you asked to do.
After playing about 40 songs without any issues, it keeps repeating the same song. On the JRiver gui it says it's playing the song before this song and this information is on the Marantz as well.
Any idea?
It looks as though with this configuration we made some progress.
Just to sure, can you please confirm that the Marantz now continues to be visible in MC's list of players? i.e. Has the prior problem, where the Marantz (or some other device which MC had perceived as being the Marantz) was sending premature bye-byes and going offline, now gone away?
Concerning the freeze after 40 songs, I have just one suggestion. I noticed in your Wire Shark capture that a lot of the HTTP traffic between MC and whatever player was captured, was using "HTTP Connection: keep-alive" so that consecutive HTTP commands were re-cycling the same single TCP socket session. I have seen AV servers and renderers that can't reliably maintain a TCP socket session for an indefinite period of time (perhaps they have a resource leak or something). And so in my case (Whitebear) I have always used "HTTP Connection: close" and force closed the respective socket so that each subsequent HTTP command must open a fresh new TCP socket. This is only a hypothesis, and to test if the problem applies to your Marantz, it would require bob to modify MC in a test build. The risk is that it might break other renderers...
-
Hi Andrew,
It's still playing without issues (more than 100 songs). Only the repeated song. Let's wait until tomorrow and see if it still plays without stopping.
Thanks.
-
Hi Andrew,
My findings until now with the "standalone" test:
- No stops using the Audiophile DLNA preset (wav 24 bits). 250+ songs without stopping. (only the repeating song issue yesterday). No bye-bye messages in the JRiver logfile.
- Now I changed to original DLNA preset (flac SD and High-res mixed) and now it stopped twice (JRiver only sends about 2MB and I hear 1 or 2 seconds of that song) , but started automatically playing the next song. I have never seen that it moves forward to the next song automatically.
When this happens I see the bye-bye messages in the logfile again.
Thanks.
-
Hi Andrew,
My findings until now with the "standalone" test:
- No stops using the Audiophile DLNA preset (wav 24 bits). 250+ songs without stopping. (only the repeating song issue yesterday). No bye-bye messages in the JRiver logfile.
- Now I changed to original DLNA preset (flac SD and High-res mixed) and now it stopped twice (JRiver only sends about 2MB and I hear 1 or 2 seconds of that song) , but started automatically playing the next song. I have never seen that it moves forward to the next song automatically.
When this happens I see the bye-bye messages in the logfile again.
Thanks.
I am pleased that you finally succeeded !!
This strongly indicates that your Marantz is choking on something in your Flacs. I am guessing that it is probably something in the meta data (tags) that causes it to choke rather than the Flac compressed music stream. If you want, you could test this by trying to play a tagless Flac file (note that it would have to be a Flac entirely without any Flac-tag elements in it, since a file having null value Flac-tag elements would probably also fail...)
This problem might be a fundamental problem of the Marantz; in which case you should complain to Marantz and send them some of your Flacs as test cases.
Or it might be due to some particularly exotic meta data element introduced by your ripping/tagging software. Did you rip/tag with MC or with something else?
Personally I am always in favour of streaming pure PCM (under pure PCM I include L16, L24, tagless WAV, and tagless AIF) since all these formats contain just audio samples only, and the stream comprises a regular steady data flow at constant bit-rate.
-
Hi Andrew,
And the Marantz finally stopped after around 70 songs using flac (original) playback....... :( Again byebye messages in the JRiver logfile and this time it didn't move to the next song.
So it's better to use PCM 24 bit instead of original? Does this not harm the audio quality?
It is still a mystery when I use my HTPC connected to the network that the Marantz stops. Remember, this is a standalone configuration with a fresh JRiver install. Do you think it makes sense to remove JRiver completely from my HTPC and do a fresh installation with the latest version?
Thanks
-
So it's better to use PCM 24 bit instead of original? Does this not harm the audio quality?
Streaming in PCM 24 bit will certainly not harm your audio quality. At some point in the chain between the original file on the server and the destination DAC in the renderer, some entity has to unpack the Flac data blocks and reassemble them as individual audio samples. If you stream in Flac then the unpacking and reassembly is done within the renderer, whereas if you stream in PCM (L24, AIF, WAV) then it is done within MC. (And indeed, since MC is on a grown up computer with lots of CPU horsepower and RAM, it can probably do the job faster and smoother than the renderer could).
Do you think it makes sense to remove JRiver completely from my HTPC and do a fresh installation with the latest version?
No. I don't think that would make any difference.
-
Hi Andrew,
Currently I'm using PCM 24 bits as I can't use L24. I still see information on the display of the Marantz. I suppose that's because tagging information is still send. I don't understand why I have issues with flac and not with PCM. Or it was just luck that it didn't play songs with "strange" tagging information during my test using PCM 24 bits.
Is there a way that MC can check for "wrong" tags?
Thanks
-
Currently I'm using PCM 24 bits as I can't use L24.
There are three ways of streaming audio samples as follows; all have exactly the same audio sample content, and all work equally well.
- L24 = 24 bit audio samples sent in high byte, middle byte, low byte order; the HTTP Content-type header gives bit depth, channel width, sample rate
- AIF = 24 bit audio samples sent in high byte, middle byte, low byte order; the start of the stream has a header giving bit depth, channel width, sample rate
- WAV = 24 bit audio samples sent in low byte, middle byte, high byte order; the start of the stream has a header giving bit depth, channel width, sample rate
I still see information on the display of the Marantz. I suppose that's because tagging information is still send.
Correct. The meta data is sent via the UPnP / DLNA commands. If the file is a Flac, Mp3 etc. the meta data might also be duplicated as embedded tags within the stream itself. However in all cases the renderer is required to use the former (UPnP) meta data rather than the latter (embedded) meta data, so essentially this duplicate embedded meta data is just a waste of space and time.
I don't understand why I have issues with flac and not with PCM. Or it was just luck that it didn't play songs with "strange" tagging information during my test using PCM 24 bits.
PCM is pure audio samples only. There is nothing else in the stream that might cause a renderer to choke. Each sample is sent one after the other. All are exactly the same size, structure and tempo from beginning to end. So if the renderer is able to play the first sample it requires no special smarts for it to keep on clocking the samples through to the end of the stream. On the other hand, in Flac, Mp3 and other compressed audio formats, the audio samples are squeezed up into blocks using data compression algorithms so some samples are essentially longer (more bytes) than others. This means that the renderer needs to be cleverer and keep track of what is going on. Also if there is embedded meta data in the stream, the renderer needs to have sufficient smarts to detect that those bytes are not audio samples and to discard them.
Is there a way that MC can check for "wrong" tags?
We don't know if your tags are actually "wrong" -- it could be that the tags are just fine, but that the renderer is "broken". But in any case if you send PCM there won't be any duplicate embedded tags, so the problem does not arise.
-
I'm still having these issues. I hoped that a firmware update from Marantz (if it is a Marantz issue) would fix this. in the meantime I upgraded to MC20, but again, nothing improved.
Someone having an idea or experiencing the same issues with other renderers from Marantz or other brands?
Thanks
-
I'm still having these issues. I hoped that a firmware update from Marantz (if it is a Marantz issue) would fix this. In the meantime I upgraded to MC20, but again, nothing improved.
When you say "still having these issues" can you please confirm exactly what issues you mean? Is it still the original problem where the Marantz goes bye-bye (goes offline) after playing several Flac tracks? Did you identify a particular Flac track that always causes this problem? In which case can you please upload that file somewhere that I can look at it? And is the problem solved by having MC Always Convert to L24? Or L16? And if so, why aren't you using that solution?
-
Hi Andrew,
Thanks for your reply.
Yes, I still have the original problem where the Marantz goes bye-bye. This is not with one particular flac file, but totally random. Also converting to a specific file type doesn't help.
I send this issue to Marantz support and they are not able to reproduce this (at least that's what they tell me). So I am curious if more people are facing this issue, or do I have a broken device.
-
I sent you a Private Message...
-
I sent you a PM back...
-
Thanks for this thread. I've seen somewhat similar behavior ("Song Playing Twice" thread) where the display shows a previous song while a new song is playing. The fix recommended in that thread was to disable DLNA Device SetNext (which I've done). From the info in this Marantz thread, I'll also change the audio output from Original to PCM24 in case my renderers are having any issues with metadata tags.
-
Correct me if I'm wrong, but as far as I know, I will lose gapless playback with this setting.
-
Correct me if I'm wrong, but as far as I know, I will lose gapless playback with this setting.
Weell, I would say that you are wrong :)
As far as I can remember from all your postings, streamerguy, you never complained about a problem with tracks playing twice. And as far as I recall from the report that you sent me by PM via DropBox, that report shows that your player does support SetNextAVTransportURI (please check the report again to be sure). So if those things are true, I would say that the suggestion of KDuff is quite irrelevant to your case.
Of course you are free to try if turning off MC's SetNextAVTransportURI support for your renderer would solve your problem. In which case please let us know. And in that case, it is indeed true that if you would turn off MC's SetNextAVTransportURI support, you would indeed lose gapless playback.
-
I already played with this setting, but it didn't solve the random stops.
And yes, my player supports SetNextAVTransportURI.
-
Are you wired or wireless?
-
Hi Bob.
I'm wired.