Start streaming to TV super slow start and/or TV crash

[america94]

Hello,

Been using Mezzmo for years and I love it. The past few months though, using same PC, TV and configuration as I always did, a LOT of videos that I stream to my TV (Samsung old C series without transcoding as I always did) show "Preparing to play" for up to a minute before starting playback... often, "Preparing to play" stays on a long time, and the TV crashes and restarts on its own.

The same video will sometimes start eventually or crash the TV.

Some movies at 5gb will start instantly, and some TV shows at 600mb will never play and crash the TV.

I tried with transcoding ON without any improvement. Reset the DB changed nothing either.

Would sending you a log help with a specific file that either crashes or takes forever to start? If so, please remind me of the proper steps to create a useful log.

thanks!

[Peter]

Hi,
possibly transcoding is failing or the profile is not correctly set for the TV. Please enable dihttp://www.mezzmo.com/wiki/doku.php?id=using_logging&s[]=diagnostic then after restarting your Mezzmo media server try playing a file on the TV then after the file fails to play send us the logs to support [at] conceiva [dot] com

[america94]

Hi,
possibly transcoding is failing or the profile is not correctly set for the TV. Please enable dihttp://www.mezzmo.com/wiki/doku.php?id=using_logging&s[]=diagnostic then after restarting your Mezzmo media server try playing a file on the TV then after the file fails to play send us the logs to support [at] conceiva [dot] com

I have sent the logs to the provided email address. PS I never used transcoding before, and am using the same Samsung C profile as always.

[Peter]

The logs show network congestion is the likely cause due to too much UPnP traffic, disabling UPnP on your router and on the device at 10.33.113.100 should help to resolve the issue.

[america94]

The logs show network congestion is the likely cause due to too much UPnP traffic, disabling UPnP on your router and on the device at 10.33.113.100 should help to resolve the issue.

After working with Peter, we tested pre-transcoding a problematic file in matroska container and it started in barely a second. I now know Mezzmo is not the culprit. Thanks!