View Issue Details

IDProjectCategoryView StatusLast Update
0021123MMW 5Casting (Google Cast / UPnP)public2024-08-06 17:40
Reporterlowlander Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version5.1 
Target Version5.1.1Fixed in Version5.1 
Summary0021123: Casting keeps turning on client after user turned off client (Denon)
DescriptionWhen casting to the DLNA client of the Denon receiver and turning the receiver itself off, it keeps turning on with the next file. MediaMonkey seems unaware that the device was powered off.
Steps To Reproduce1 Turn on DLNA client
2 Cast to DLNA client from MMW
3 Turn off DLNA client
--> MMW turns it back on with the next file in the queue
TagsNo tags attached.
Fixed in build3042

Relationships

related to 0020555 feedbacklowlander Issues with HEOS / Denon 

Activities

Ludek

2024-08-02 10:41

developer   ~0076548

Last edited: 2024-08-02 10:41

The power/off state isn't something that can be controlled via DLNA..

It's up to the client renderer device whether it wake-ups once a file is sent to it...

As for auto-transition to the next file: This is because Denon sent STOPPED play state and thus MM5 think that it finished playback of this song and initiated playback of another song..
I could modify and leave the playback stopped once the STOPPED state isn't sent near to the end of the file, but the consequence would be that playback would be interrupted once Denon has an issue to play a file (e.g. shortened file)..

Ludek

2024-08-02 11:20

developer   ~0076550

Fixed in 3042

It now transitions to the next file only when state was changed from PLAYING -> STOPPED and the position was lower than 2 seconds (trouble to play a file) or position was near to the end of the file (Length - 5 seconds)
i.e. it eliminates the cases when STOPPED state came in the middle of playback and MM5 was still transitioning to the next file, now it does nothing

lowlander

2024-08-06 17:40

developer   ~0076594

Verified on 3042. Turning off the Denon itself doesn't cause MediaMonkey to keep turning it on. MediaMonkey will still turn it back on when user uses Play in MediaMonkey as you'd expect.