Ranger if you believe the E series and M series to be that different then post some logs. I was posting mine as added info. I believe that the problems are the same, since you and I see the same negative buffers when large files are transcoded.
------------------
@exsport thanks for looking at this. I did comment that line last night during testing with no luck. But I will do it again this afternoon and post logs. I'd be willing to try several things at once and post relevant logs. Or since Ranger doesn't want us distracted he can post logs as described in DeFlanko's signature, I will just watch. My kid is really tired of me obsessing over this anyway.
We have been all over the place in this thread. Since you mention that about device spy and mp4, I'll sum up below:
Short mp4 files work, long ones don't unless plugged in via usb:
As dbq-anderson posted almost a year ago:
With all that said, I have gotten my .mp4 files to stream fine...as long as they're shorter than about 23 1/4 minutes. VERY weird. Any files that are longer than about 1400 seconds won't even start playing and result in orange error messages at the bottom right of the TV app stating that the video and audio codecs are not supported. I know they are supported because up to that length, they stream just fine and as mentioned above, if I pull the files to a USB drive and connect it to the TV, I can play any length I want to just fine.
This is my exact same issue. It is also one of the issues posted in the Vizio M series threads:
I can play files that are up to 21 m 16 s so far, but video with the same media info that's 46 m does not work.
mp4 files work if they are short, or are plugged in via usb. If they are longer they have orange "video codec not support, audio codec not support" (broken english messages FTW). The folks at Vizio said directly to me on the phone two days ago that this is a limitation of vizio tvs. So they have to be transcoded (as ranger posted: "These files NEED transcoded: .mp4 (avc/aac), .avi (mpeg4-divx5/mp3)"
Streaming works fine, transcoding doesn't:
Ranger says "This file plays fine" and posts a pic from an avi (streaming not transcoded) over an hour long. I have a long .mpg file that streams fine.
Meanwhile, any long files that are transcoded see this:
12-01 08:28:44 Buffer read ArrayIndexOutOfBoundsException error:
12-01 08:28:44 readCount: "576460752303419392"
12-01 08:28:44 maxMemorySize: "209715200"
That is the exact same thing I see with the exact same numbers, but posted from one of ranger's posts. I see it for a large mp4 file, the above was from a large avi file that wasn't the right format to stream and needed to be transcoded. The log file I posted that ends in 2 has this error.
Another user already posted about this in the PSU forums:
In all the logs that I have seen from Visio customers, the TV requests a few chunks of data right at the start of the file which kicks the transcode process off. After a few seconds it then requests a chunk of data right from the very end of the file! at this point we say that we cannot possibly service that request because the transcoder is nowhere near that point of the file and the wait time would be large.
All other devices Sony, Samsung etc. etc. request small, incremental chunks of data that are always behind the transcoder write head, meaning that we can always service that request. We have a spoofing mechanism in place that just generates random data when the device requests it at the end of the file and I think that it is this random data that is causing the issue.
The mechanic of the streaming is what is breaking the transcoding, not the actual format of the files.
Vizio is not the only ones who act like this, there are a couple more but, the vast majority behave correctly. That is why we built the 'back door' into the tvmobili media server for clients that do behave this way.
SO THE QUESTION IS:
If we transcode the file to the exact thing it needs to be transcoded to, will it matter?
I for one will continue to try any .conf file that you post, and I hope that somehow we will find the right thing and it will transcode to one of these and work fine, but it looks like no matter what we transcode to, we're going to get this (from my debug file that ends in 2 where I commented out the bottom line and added: TranscodeVideo=MPEGPSAC3 TranscodeAudio=LPCM):
Code: Select all
TRACE 2013-12-04 23:21:18.575 [New I/O worker #7] Matched media renderer "Vizio Smart TV - DeFlanko TEST with TranscodeVandA" based on address /192.168.1.114
TRACE 2013-12-04 23:21:18.575 [New I/O worker #7] Received on socket: CONNECTION: Keep-Alive
TRACE 2013-12-04 23:21:18.575 [New I/O worker #7] Received on socket: DATE: Thu, 05 Dec 2013 05:21:21 GMT
TRACE 2013-12-04 23:21:18.575 [New I/O worker #7] Received on socket: HOST: 192.168.1.137:5001
TRACE 2013-12-04 23:21:18.575 [New I/O worker #7] Received on socket: RANGE: bytes=576460752303419392-
TRACE 2013-12-04 23:21:18.575 [New I/O worker #7] Received on socket: transferMode.dlna.org: Streaming
TRACE 2013-12-04 23:21:18.575 [New I/O worker #7] Received on socket: USER-AGENT: IPI/1.0 UPnP/1.0 DLNADOC/1.50
TRACE 2013-12-04 23:21:18.575 [New I/O worker #7] Recognized media renderer: Vizio Smart TV - DeFlanko TEST with TranscodeVandA
TRACE 2013-12-04 23:21:18.575 [New I/O worker #7] HTTP: get/0$7$4$1/1.mp4 / 576460752303419392--1
TRACE 2013-12-04 23:21:18.575 [New I/O worker #7] discover 0 refresh forced: false
TRACE 2013-12-04 23:21:18.575 [New I/O worker #7] discover 0$7 refresh forced: false
TRACE 2013-12-04 23:21:18.575 [New I/O worker #7] discover 0$7$4 refresh forced: false
TRACE 2013-12-04 23:21:18.575 [New I/O worker #7] Asked stream chunk : ByteRange [start=576460752303419392, end=-1] of 1.mp4 and player MEncoder
TRACE 2013-12-04 23:21:18.576 [New I/O worker #7] Ready to Stop: false
DEBUG 2013-12-04 23:21:18.576 [New I/O worker #7] Setting InputStream new position to: 576,460,752,303,419,392
TRACE 2013-12-04 23:21:18.576 [New I/O worker #7] Sending 8646911282403872767 bytes.
TRACE 2013-12-04 23:21:18.576 [New I/O worker #7] Suspend Read: readCount=576460752303419392 / writeCount=38252544
TRACE 2013-12-04 23:21:19.603 [Timer-2] buffered: -576,460,752,264,372,224 bytes / inputs: 1
TRACE 2013-12-04 23:21:21.604 [Timer-2] buffered: -576,460,752,262,883,328 bytes / inputs: 1
TRACE 2013-12-04 23:21:23.604 [Timer-2] buffered: -576,460,752,261,314,560 bytes / inputs: 1
TRACE 2013-12-04 23:21:25.604 [Timer-2] buffered: -576,460,752,259,182,592 bytes / inputs: 1
TRACE 2013-12-04 23:21:26.077 [New I/O worker #7] Resume Read: readCount=576460752303419392 / writeCount=44584960
INFO 2013-12-04 23:21:26.077 [New I/O worker #7] Buffer read ArrayIndexOutOfBoundsException error:
INFO 2013-12-04 23:21:26.077 [New I/O worker #7] readCount: "576460752303419392"
INFO 2013-12-04 23:21:26.077 [New I/O worker #7] maxMemorySize: "209715200"
TRACE 2013-12-04 23:21:26.078 [New I/O worker #7] Suspend Read: readCount=576460752303419392 / writeCount=44584960
But as I said I will post another log file when I get home as you suggested.
Ranger if you want to just test with your TV so we don't get distracted, test and post log files as described in DeFlanko's signature and I will just monitor the thread in hopes of a solution.