by proteus » Tue Oct 31, 2023 11:44 pm
Update,
I just sat and watched the MM5 window via Remote Desktop (always open).
Playing a playlist (no shuffle) via cast to my Kef LS50.
MM5 (MM 5.0.4.2692) is on a machine with cable to router, LS50 is WiFi to router.
1) At the beginning of the 2nd track and tracks after (usually) there is a pause and a message:
"The 'LS50' player is turned off or inaccessible" - this self corrects after a short pause.
2) After a few (?) tracks we get a message (it disappears fast, so is it approximately) :
Playback failed, 'LS50' cannot decode XX.mp3
A very short time later the MM5 window goes white, and MM5 is unresponsive.
Suggestions:
A) I'm inclined to think this is not RD related, its just that RD users wouldn't see the message only the final state.
B) Since other players work OK, and some (all?) behavior is track related it looks to me like an MM5 issue.
Update 2
The above is with WASAPI, if I use DirectSound or waveOut the "cannot decode" message always occurs on the first track transition. It is not related to the actual song so the inability to decode does not refer to the data.
Update 3
Back to WASPI
I just noticed something else odd, when the turned off or inaccessible message occurs the Cast button goes 'off' and taping it shows "internal player" not "LS50" selected in the dropdown (both are there). But the cast does play the next song (see self correct above) on LS50.
[b]Update[/b],
I just sat and watched the MM5 window via Remote Desktop (always open).
Playing a playlist (no shuffle) via cast to my Kef LS50.
MM5 (MM 5.0.4.2692) is on a machine with cable to router, LS50 is WiFi to router.
1) At the beginning of the 2nd track and tracks after (usually) there is a pause and a message:
[i]"The 'LS50' player is turned off or inaccessible" [/i]- this self corrects after a short pause.
2) After a few (?) tracks we get a message (it disappears fast, so is it approximately) :
[i]Playback failed, 'LS50' cannot decode XX.mp3
[/i]
A very short time later the MM5 window goes white, and MM5 is unresponsive.
Suggestions:
A) I'm inclined to think this is not RD related, its just that RD users wouldn't see the message only the final state.
B) Since other players work OK, and some (all?) behavior is track related it looks to me like an MM5 issue.
[b]Update 2[/b]
The above is with WASAPI, if I use DirectSound or waveOut the "cannot decode" message always occurs on the first track transition. It is not related to the actual song so the inability to decode does not refer to the data.
[b]Update 3[/b]
Back to WASPI
I just noticed something else odd, when the [i]turned off or inaccessible[/i] message occurs the Cast button goes 'off' and taping it shows "internal player" not "LS50" selected in the dropdown (both are there). But the cast does play the next song (see self correct above) on LS50.