View Issue Details

IDProjectCategoryView StatusLast Update
0018704MMW 5Playbackpublic2022-02-04 00:48
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version5.0.2 
Target Version5.0.3Fixed in Version5.0.3 
Summary0018704: Playback is broken after failed casting
DescriptionIn some cases, casting to a particular device may fail. When the user then tries to switch audio to the 'Internal Player' and/or terminate the Casting process
--> Attempts to playback internally fail until MM is restarted.
TagsNo tags attached.
Fixed in build2605

Relationships

related to 0017799 closedLudek Cast to chromecast mini fails when casting is initiated during playback 
related to 0018808 closedLudek First file fails to play on Chromecast 

Activities

Ludek

2022-01-27 19:58

developer   ~0066786

Last edited: 2022-01-27 20:17

Fixed in 2604.

I also found why the casting failed on the second device (buffering endlessly) and fixed it.
+ fixed some further issues (where multiple Chromecast client profiles could be accidentally created in Media Server > Clients list)

peke

2022-01-29 09:03

developer   ~0066802

Verified 2604

Tested with google nexus player, Bubble UPNP (as second cast device).

Also retested with failover from two internal sound cards (MB embed and USB) Just in case.

Ludek

2022-01-31 18:43

developer   ~0066810

Last edited: 2022-02-01 11:49

Note that these must be tested with Google cast devices (not DLNA/UPnP)

Based on the user's log from ticket [Ticket # 3650] this issue can still happen.
i.e. endless buffering when switched to certain Chromecast device.

EDIT: I was finally able to simulate this sporadically, though still not sure what's causing this, to be figured out...

EDIT2: It seems that the key to replicateis to start playback of a track to Internal player and once track is playing switch to a Chromecast device
=> endless buffering
If the playback is started after the switch then this bug never occurs.

Ludek

2022-02-01 12:41

developer   ~0066813

Fixed in 2605

peke

2022-02-03 23:03

developer   ~0066847

Verified 2605

Re EDIT2: Good catch, I was only being able to replicate using those steps in 2604, but it worked ok in 2605.

lowlander

2022-02-04 00:48

developer   ~0066848

First try this worked as designed on 2605