Crash after which no casting devices can be found

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: Crash after which no casting devices can be found

Re: Crash after which no casting devices can be found

by Platonius » Wed Oct 18, 2023 1:35 am

For those with similar problems: this should be fixed in 2820.

Re: Crash after which no casting devices can be found

by Lowlander » Mon Oct 09, 2023 12:00 pm

Is the problem on build 2817?

Re: Crash after which no casting devices can be found

by Platonius » Mon Oct 09, 2023 2:35 am

And as sudden as it disappeared... I was greeted with the same problem this morning.

On starting MM5 it stated the googlecast device was unavailable, and now I'm again left with only the internal speaker.

*EDIT* Standalone install of MediaMonkey_5.0.4.2692 does show casting devices...

Re: Crash after which no casting devices can be found

by Platonius » Mon Oct 02, 2023 2:02 am

And as sudden as the problem appeared, it has disappeared after 2 weeks.

Nothing has changed in my network or devices and nothing has changed with MM5...

Re: Crash after which no casting devices can be found

by Platonius » Wed Sep 27, 2023 7:56 am

Multiple restarts, as it has been a week since the problem occured. Tried a fresh install (with and without database/ini/json).
Portable install also doesn't see any external devices. Turning Windows firewall off also doesn't help.

Logfile clearly shows MM5 isn't able to find anything (while I'm actually using Spotify at this moment to play music to my speaker).
[9912] MM5 [17480](R) TRemotePlayers.RefreshAvailablePlayers: LastUpdate since 10110
[9912] MM5 [17480](R) Performance warning: doOnChange is called too often, consider using beginUpdate/endUpdate (OT: sharedlist, id: -1), JS callstack:
[9912] UPnP: Get Renderers
[9912] UPnP: Get renderers
[9912] MM5 [17480](R) TRemotePlayers._addStoredPlayers
[9912] MM5 [17480](R) **********Performance warning: Class TSharedList<UpNp.IRemotePlayer> doesn't implement its own createInstance.
[9912] MM5 [17480](R) --Remote players: 1:
[9912] MM5 [17480](R) {"udn":"","name":"","last_seen":"","volume":1,"ip":"","protocol":""}

And that's it. Nothing else found. Just prints an empty player.

Re: Crash after which no casting devices can be found

by Lowlander » Wed Sep 27, 2023 5:11 am

Have you tried a PC restart? How about a fresh portable install (in separate location) does it see the devices?

Crash after which no casting devices can be found

by Platonius » Wed Sep 27, 2023 4:06 am

A few days ago MM5 (V2814) crashed while playing on my google cast speaker.

Since that time MM5 has been unable to find google devices. They don't even show up in the logfile as being found (network scan shows that they are there and Spotify has no problem finding and using them).

Upgrading to V2816 has no effect (except for it being extremely slow and mostly crashing on startup). Removing MediaMonkey.ini and persistent.json for a fresh start has no effect.

LAST_REMOTE_PLAYERS section in persistent.json has by now become empty, though my speaker is still in the ini as DLNA_Player_Name and in the json under maintainDB/Sytem/DLNA_Player_Name.

Already created a ticket (#6310) but after a week still no reply. So I hope others are able to help me.

Top