Vizio TV playback freezing

Greetings all. Haven't been around the forums in a while but I came across some strange behavior with a VIZIO TV. I looked at some of the existing topics with similar issues only to see that they mostly went unresolved so, I don't really have high expectation for a fix. It seems that any video streamed to my VIZIO TV (model: M322i-B1), using the Vizio profile of course, is able to play back just fine but only for about 30-35 minutes before it freezes. I made sure that my router (a Netgear R7400) has IGMP enabled as well as uPNP running. But after enabling debug/verbose logging (in the log4j file) and trying a few different files, It does seem that it may just be an issue with the TV since playback of most everything can be initiated. I'll attach part of the log which shows a couple of errors with playback of one MKV file in particular (containing regular Dolby AC3) however, the same kind of freezing playback of another file (with E-AC3 audio) did not list or show any sort of warnings or errors in the log which I thought was odd. I am currently running Serviio v2.1 just in case that makes any difference. Thanks for any suggestions in advance.

2022-01-25 08:44:01,525 INFO [PlaybackEventsManager] Playback of media item 15459 (Amadeus [Amadeus.mkv]) has started at 0% on Identifier=192.168.1.13, Profile=Vizio TV, Name=Vizio TV
2022-01-25 08:44:08,955 INFO [PlaybackEventsManager] Playback of media item 15459 (Amadeus [Amadeus.mkv]) has stopped at 0% on Identifier=192.168.1.13, Profile=Vizio TV, Name=Vizio TV
2022-01-25 08:44:15,612 WARN [ProcessExecutor] Process cmd has a return code of 1! This is a possible error. Detailed output follows.
frame= 103 fps= 24 q=0.0 size= 0kB time=-577014:32:22.77 bitrate= -0.0kbits/s speed=N/A
frame= 113 fps= 23 q=0.0 size= 0kB time=-577014:32:22.77 bitrate= -0.0kbits/s speed=N/A
frame= 123 fps= 23 q=0.0 size= 0kB time=-577014:32:22.77 bitrate= -0.0kbits/s speed=N/A
Too many packets buffered for output stream 0:0.
Conversion failed!
2022-01-25 08:45:09,513 ERROR [ResourceTransportRequestHandler] Error while processing resource, sending back 500 error. Message: FFmpeg execution failed
java.io.IOException: FFmpeg execution failed
at org.serviio.delivery.resource.transcode.FileBasedTranscodingDeliveryStrategy.createInputStream(FileBasedTranscodingDeliveryStrategy.java:49)
at org.serviio.delivery.resource.transcode.AbstractAVTranscodingDeliveryEngine.retrieveTranscodedResource(AbstractAVTranscodingDeliveryEngine.java:137)
at org.serviio.delivery.resource.AbstractDeliveryEngine.deliver(AbstractDeliveryEngine.java:97)
at org.serviio.delivery.MediaResourceRetrievalStrategy.retrieveResource(MediaResourceRetrievalStrategy.java:152)
at org.serviio.delivery.GETMethodProcessor.retrieveResource(GETMethodProcessor.java:96)
at org.serviio.delivery.GETMethodProcessor.buildDeliveryContainer(GETMethodProcessor.java:46)
at org.serviio.delivery.AbstractMethodProcessor.handleRequest(AbstractMethodProcessor.java:133)
at org.serviio.delivery.ResourceDeliveryProcessor.deliverContent(ResourceDeliveryProcessor.java:81)
at org.serviio.upnp.webserver.ResourceTransportRequestHandler.handleRequest(ResourceTransportRequestHandler.java:82)
at org.serviio.upnp.webserver.AbstractRequestHandler.handle(AbstractRequestHandler.java:66)
at org.apache.http.protocol.HttpService.doService(HttpService.java:423)
at org.serviio.upnp.webserver.ServiioHttpService.doService(ServiioHttpService.java:78)
at org.apache.http.protocol.HttpService.handleRequest(HttpService.java:341)
at org.serviio.upnp.webserver.WebServer$WorkerThread.run(WebServer.java:204)
2022-01-25 08:45:09,513 ERROR [ResourceTransportRequestHandler] Error while processing resource, sending back 500 error. Message: FFmpeg execution failed
java.io.IOException: FFmpeg execution failed
at org.serviio.delivery.resource.transcode.FileBasedTranscodingDeliveryStrategy.createInputStream(FileBasedTranscodingDeliveryStrategy.java:49)
at org.serviio.delivery.resource.transcode.AbstractAVTranscodingDeliveryEngine.retrieveTranscodedResource(AbstractAVTranscodingDeliveryEngine.java:137)
at org.serviio.delivery.resource.AbstractDeliveryEngine.deliver(AbstractDeliveryEngine.java:97)
at org.serviio.delivery.MediaResourceRetrievalStrategy.retrieveResource(MediaResourceRetrievalStrategy.java:152)
at org.serviio.delivery.GETMethodProcessor.retrieveResource(GETMethodProcessor.java:96)
at org.serviio.delivery.GETMethodProcessor.buildDeliveryContainer(GETMethodProcessor.java:46)
at org.serviio.delivery.AbstractMethodProcessor.handleRequest(AbstractMethodProcessor.java:133)
at org.serviio.delivery.ResourceDeliveryProcessor.deliverContent(ResourceDeliveryProcessor.java:81)
at org.serviio.upnp.webserver.ResourceTransportRequestHandler.handleRequest(ResourceTransportRequestHandler.java:82)
at org.serviio.upnp.webserver.AbstractRequestHandler.handle(AbstractRequestHandler.java:66)
at org.apache.http.protocol.HttpService.doService(HttpService.java:423)
at org.serviio.upnp.webserver.ServiioHttpService.doService(ServiioHttpService.java:78)
at org.apache.http.protocol.HttpService.handleRequest(HttpService.java:341)
at org.serviio.upnp.webserver.WebServer$WorkerThread.run(WebServer.java:204)
2022-01-25 08:45:15,675 WARN [ProcessExecutor] Process cmd has a return code of 1! This is a possible error. Detailed output follows.
frame= 103 fps= 24 q=0.0 size= 0kB time=-577014:32:22.77 bitrate= -0.0kbits/s speed=N/A
frame= 114 fps= 23 q=0.0 size= 0kB time=-577014:32:22.77 bitrate= -0.0kbits/s speed=N/A
frame= 125 fps= 23 q=0.0 size= 0kB time=-577014:32:22.77 bitrate= -0.0kbits/s speed=N/A
Too many packets buffered for output stream 0:0.
Conversion failed!
2022-01-25 08:46:09,810 ERROR [ResourceTransportRequestHandler] Error while processing resource, sending back 500 error. Message: FFmpeg execution failed
java.io.IOException: FFmpeg execution failed
at org.serviio.delivery.resource.transcode.FileBasedTranscodingDeliveryStrategy.createInputStream(FileBasedTranscodingDeliveryStrategy.java:49)
at org.serviio.delivery.resource.transcode.AbstractAVTranscodingDeliveryEngine.retrieveTranscodedResource(AbstractAVTranscodingDeliveryEngine.java:137)
at org.serviio.delivery.resource.AbstractDeliveryEngine.deliver(AbstractDeliveryEngine.java:97)
at org.serviio.delivery.MediaResourceRetrievalStrategy.retrieveResource(MediaResourceRetrievalStrategy.java:152)
at org.serviio.delivery.GETMethodProcessor.retrieveResource(GETMethodProcessor.java:96)
at org.serviio.delivery.GETMethodProcessor.buildDeliveryContainer(GETMethodProcessor.java:46)
at org.serviio.delivery.AbstractMethodProcessor.handleRequest(AbstractMethodProcessor.java:133)
at org.serviio.delivery.ResourceDeliveryProcessor.deliverContent(ResourceDeliveryProcessor.java:81)
at org.serviio.upnp.webserver.ResourceTransportRequestHandler.handleRequest(ResourceTransportRequestHandler.java:82)
at org.serviio.upnp.webserver.AbstractRequestHandler.handle(AbstractRequestHandler.java:66)
at org.apache.http.protocol.HttpService.doService(HttpService.java:423)
at org.serviio.upnp.webserver.ServiioHttpService.doService(ServiioHttpService.java:78)
at org.apache.http.protocol.HttpService.handleRequest(HttpService.java:341)
at org.serviio.upnp.webserver.WebServer$WorkerThread.run(WebServer.java:204)

[atc98092]

It's interesting that the error is related to FFMPEG processing, which wouldn't seem to be an issue specific to a particular player. I can say that in my experience the Vizio TVs don't play back DLNA media very well. But my experience is only with a couple of smaller TVs.

Perhaps try a different profile, just as a test. The Roku TV profile would likely handle any transcoding your TV might require. Samsung, Sony and LG all offer more robust support for DLNA media (not a lot more, but more), so those profiles might not transcode everything you need.

A very belated thank you for the advice atc98092. After trying a lot of different configuration combinations, I've decided to just dig up an old Roku stick and use that instead. Thanks again.

[atc98092]

I think that's a far better choice than using the smart functions. I've noticed on a couple of Vizio TVs I've used recently they don't even support DLNA at all anymore. Their loss...