Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[masterjoe]

As it is currently not possible to seek (change playback position) in transcoded video streams using DLNA I was thinking of another variant that MIGHT be easier to be implemented.

MC does not provide a Content Length header and therefore the renderer has no clue how to perform byte seeks. You say that it's impossible to determine the correct size of the transcoded video as the transcoder produces variable (unpredictable) frame sizes.

What if you would pretend that byte seeks and content length of the transcoded stream are the same as for the original file? Internally you would know that the video is in fact transcoded and interpret the byte offsets coming from a renderer as offsets into the original file and not the transcoded stream. Then you could easily calculate the time offset based on the byte offset and the length of the original file and use this time offset to seek the transcoded stream.

So in short:
- provide the Content Length from the original file
- interpret byte seeks as offsets based on the size of the original file
- calculate time offsets using the byte offset and the original content length and use the resulting time offset to do the seek in the transcoder

Would that be posible? If it doesn't matter that the renderer does not really know the correct length but just gets something to play with then it should work.

[AndrewFG]

Something like that. Yes.

[masterjoe]

Could the content length also be the frame count the original video is made of? Then the "byte offset" could me abused as frame number!
If the renderer does not need to know the REAL content length then this would also work and might even be better for the transcoder engine because it might internally work with frames?

The transcoder would then get the exact frame to which it shall seek.

[Hendrik]

This is no different to calculating the estimated final size, and the same applies as in the other thread, not soon. I'm going to close this as its really just the same discussion over and over again.