TVplugin - avoiding RTSP in multiseat mode (test plz). (2 Viewers)

[disaster123]

Ambass
Nice to hear from you. I'm not if i understand you correctly. Do you mean that there is a general problem with caching in case we use SMB? If it is like that - why not closing and reopening the file in every request?

 

[Ambass]

I do not know how SMB works. But I just consider you've found it's necessary to close & re-open tsbuffer file due to cache effects, so we can suspect same kind of problem with data file.

In this case, we could have inconsistency between file pointers from tsbuffer file up-to-date and "old" cached ts data file.... Read method will return crazy data.

Closing and re-opening data file after closing re-opening ts buffer file could help. It's to be checked !.

 

[tourettes]

4TR is not open source isn't it? Otherwise perhaps someone can borrow the code

https://mp-plugins.svn.sourceforge.net/svnroot/mp-plugins/trunk/plugins/ForTheRecord

For The Record makes playback over UNC optional (default is RTSP) for live TV only, recordings are always played over UNC (which works just great, including comskip).

Sure, but it uses the same TsReader (most likely ) and will not help...

 

[disaster123]

Ambass
ah OK now i understand. I can check this if you want?

The most crazy thing is - that only the integrity part is buffered - the rest of the buffer file wasn't cached so you got an integrity error. First i thought it must be a bug in tswriter - but it isn't i've printed out the content of buffer file via tswrite after writing it and it was fine. But at the same time you've different content in tsreader (only sometimes) AND you have it only for the integrity part - i've double checked this with a lot of debugging.
I've also found some posts where many people say that the buffering in SMB is really crazy.

tourettes
ah OK dot-i has reported he uses RTSP in live TV and only UNC for recordings. So he doesn't run into these issues.

 

[Ambass]

Yep, you can check. I've really no extra time for this.

 

[disaster123]

Ambass
Absolutly no problem.
I will check the following:
- can we remove the sleep
- is it possible to close and reopen the buffer file every time before we read from it
- is it possible to close and reopen the TS Datafile every time before we read from it

Any other ideas to check?

 

[disaster123]

I've now also found out that tsreader is jumping between ts files - that can't be OK i think.

09-02-2009 15:37:17.300 [560]Current File Changed to O:\VID.TIME\live1-0.ts.tsbuffer3.ts newposid: 3 oldposid: 1
09-02-2009 15:37:19.173 [560]Current File Changed to O:\VID.TIME\live1-0.ts.tsbuffer1.ts newposid: 1 oldposid: 3
09-02-2009 15:37:19.679 [560]Current File Changed to O:\VID.TIME\live1-0.ts.tsbuffer3.ts newposid: 3 oldposid: 1
09-02-2009 15:37:21.755 [560]Current File Changed to O:\VID.TIME\live1-0.ts.tsbuffer1.ts newposid: 1 oldposid: 3
09-02-2009 15:37:22.061 [560]Current File Changed to O:\VID.TIME\live1-0.ts.tsbuffer3.ts newposid: 3 oldposid: 1
09-02-2009 15:37:24.269 [560]Current File Changed to O:\VID.TIME\live1-0.ts.tsbuffer1.ts newposid: 1 oldposid: 3

I'll try to fix this also

 

[gibman]

try the attached tsreader.ax

seems to work for me...

using 20 mb TS buffer setup in tvserver (which should give a lot of file changes when using h264 and other high bitrate contents).

reports plz

/gibman

 

[disaster123]

Can you please provide also a patch / diff file - so that i can see what you've changed? I'm still working on my changes.

 

[Ambass]

I've now also found out that tsreader is jumping between ts files - that can't be OK i think.

I'll try to fix this also

TsReader is always opening/closing file in file duration thread...It's a normal behaviour.