Streaming process

[trummel]

Could some kind person explain to me the process that NextPVR goes through when streaming an MP4 (previously transcoded with ffmpeg from .ts) to a client using port 8866.

The reason for asking is that I am getting about 450ms lip sync delay on the video when I use VLC on a client pc with this:-

Code:

http://192.168.0.101:8866/stream?mode=http&mime=video/mp4&f=F:%5CMedia%5Ctemp%5CStrictly%20Come%20Dancing%5CStrictly.Come.Dancing.S13E08.Part.One.mp4

But if I use VLC to access the file directly with this:-

Code:

F:\Media\temp\Strictly Come Dancing\Strictly.Come.Dancing.S13E08.Part.One.mp4

(F: mapped to \\192.168.0.101)
There is no discernible lip sync issue.

I'm using VLC here to try to reduce unknowns and because it lets me adjust the sync. However the real issue is on my Samsung TV's which exhibit the same problem, but with no way to adjust it.

I don’t want to start messing with decoders etc that I'm assuming aren't used, but without understanding what is going on I cant guess what to look at. I dont think the ts to mp4 transcode is responsible as it plays fine however I play it on the server.

Some recorded programs seem better than others, but 'Strictly' seems to be a problem every week and it driving the boss nuts!

[sub]

Could some kind person explain to me the process that NextPVR goes through when streaming an MP4 (previously transcoded with ffmpeg from .ts) to a client using port 8866.

There is nothing special about this. The client just downloads the file over HTTP. It's not "streaming" in the sense of doing anything special. It's exactly the same as downloading a text file or jpg. ie, server sends http header saying the size of the file that follows, then sends the data in the file. In this case it's only the client that's interpreting it as audio/video and playing it. NextPVR has no idea what the file is.