[Dilligaf]

When viewing a live channel on one client skip forward/back works normally. If I then go to view the live stream on a second or third client skip forward/back on these clients skips between the beginning of the file (where the channel was first tuned) and live tv stream, short/long skip times are seemingly ignored. I've seen this behavior with multiple clients and versions, can anyone else check this and see if they can duplicate this behavior?

[krustyreturns]

I just now started a channel on a spare computer then used my devel machine to start watching the same channel, on this second machine skip forward and skip backward is working for me. I did have trouble getting the second machine to start viewing the stream at the correct time, the first couple of times I tried, it started at the original beginning of the stream, but the third time I tried it started at the correct point, that's when I tested skipping forward and back.

Do you also have trouble getting the second client to start at the right point?

My devel machines are standard def, I can get hi-def ota on them on a clear day but its raining heavy today (which is really good news). Can you try on standard def?

EDIT:
Scratch that, I just tried again and it happened to me too, same as you reported

[Dilligaf]

Cool, I'm not imagining things

[scarecrow420]

in general i have found that ff/rw and skipping around in timeshifted TS files seems to be quite hit and miss. The way I made the second client jump to the current position in an already running TS file may be somehow related as it was a bit of a hack... basically any attempt at setting a starting position got overwritten by ffmpeg doing the decoder pass followed by the actual pass, so I had to save the position we want to jump to, then wait until the ReadLiveStream() call comes through (which happens once XBMC is actually playing the video) and at that point i set the file position. I dont know enough about these things to understand how that could affect the seeking within the file etc...

I also have had occasion where the 2nd client doesnt start from the current point, but stopping and starting again it does. Cant say ive had the skip bug but I dont do this much, and aso I skip around in the file even less, so i am not a good usecase. Im sure if i sat down to test it I would also be able to reproduce it

[krustyreturns]

Have you ever looked to see if we can just tell xbmc to start playing at the time we want? This happens with 'resume' on recordings, we just want to be able to do the same for the ts data in live streams.

(1000th post)

[scarecrow420]

congrats on 1000th post!

As i said, when you set the requested start field it gets lost (after ffmpeg does the 1st pass descriptor scan it sets the position back to 0 rather than the requested start position that had been set). When XBMC does the resume stuff, it sets the start position after the 1st descriptor pass. This is from memory/experimentation when i was doing that 2nd client change, we can always revisit it to see if I was just wrong somehow

[Dilligaf]

Fixed with pre-release provided by Krusty