Time to make Touch web Service less experimental

[fred250]

well i found the problem

Code:

long bytesToReadRemaining = (this.EndRangeBytes[i] - this.StartRangeBytes[i]) + 1;

was using the requested, unaltered start/end bytes which would give a negative value for bytes remaining and the tsstreamer would close the connection (not the samsung player)

changing it to

Code:

long bytesToReadRemaining = this.InternalRequestedFileInfo.Length - startpos + 1;

I can now jump to about minute 31 out of 34, im sure there is another tiny bug I can fix to jump the entire way. Also I don't have to handle the timeline myself or anything, and it mostly just now works (all that is required on my player is im passing in an additional &guid parameter to the video player and I call a seek request before jumping)

So, what I'm doing is.
# For a file with 1000 bytes (just an example )
# For the initial stream request i respond with Content-Range: bytes 0-1000/1000 and Content-Length: 1000
# When a request comes in, I alter the requested start byte with the adjusted byte eg, change 500 to 300
# I respond with Content-Range: bytes 500-1200/1200 and Content-Length: 1200
# I then just adjust the start range to and respond with bytes 300 to 1000, the player thinks its bytes 500 to 1200

And I can now successfully watch the entire faulty videos provided by stustunz and smacrae.

so Fred, well done you have solved the problem I've been having with the samsung player, just need to polish it up and hopefully get sub to add it or to get it into NEWA.

This will make smacrae very happy

Great work!

I was posting my answer while you fixed it - just ignore!

[sub]

Reven, if you were playing say a half hour recording, and the timeline made your Samsung player report the length as only 5 minutes, does the player let you attempt to seek past 5 minutes?

[reven]

I know if the player reported it as 5mins, but that file grew over time then it lets me play beyond 5mins (in progress recordings can go past the end time, bug I need to fix to extended the timeline).

Ill try tonight to see what happens if i force the byte end range to be lower than the actual one. But the 2 sample files I have are reported with the correct length using freds tsstreamer (using nextpvr ?f=[filename] makes the player report a 34mins file as 10ish minutes).

Sub, I'll polish up the code and send it to you later this week (fred250 are you ok with me sending sub the code? I assume yes )

[fred250]

Sub, I'll polish up the code and send it to you later this week (fred250 are you ok with me sending sub the code? I assume yes )

Of course you can send sub the code, but be sure you polish well
Actually I don't think sub will need the code though. If you got a proper streamer to start with adding this seek-preset-thing is fairly simple.

/Fred

[nitram]

Has anyone ever completed a PC client with Touch that also plays video from your npvr service? It's very useful to be able to manage recordings from any remote machine, playing the recordings would be a great bonus.

[mvallevand]

Has anyone ever completed a PC client with Touch that also plays video from your npvr service? It's very useful to be able to manage recordings from any remote machine, playing the recordings would be a great bonus.

If you mean into a PC browser, basic HTML5 support in general isn't good for standard mpeg-ts playback. I added Touch support (X-NEWA web client) into XBMC so that it would run on any PC that XBMC supports.

Martin

[fred250]

Has anyone ever completed a PC client with Touch that also plays video from your npvr service? It's very useful to be able to manage recordings from any remote machine, playing the recordings would be a great bonus.

Hi,

Since my Smart TV app for Samsung and LG is HTML5/ Javascript I actually use Chrome while developing and debugging. That said, you can easily use it on a PC for managing recordings. I do it myself from time to time.

Playing .ts-files is not that easy. I have experimented using the VLC-web-plugin and it kind of works but seeking in files does not and aspect ratio is wrong.
Hopefully the VLC plugin gets better in the future.

I'm not ready to release my source code to the public just yet, not because is secret or anything just that it's not ready. But if you're interested and not afraid of Javascript I'll give you a copy to play with – just PM me.

/Fred