LiveTV Freezes after 1-2 seconds

[mvallevand]

In those Reader.log stops delivering data

Code:

21:24:05.526    CVirtualFile::Read(buf, 169200) from 1861200. Current file 0.
21:24:05.526    CVirtualFile::Read() from disk (raw no slip)
21:24:05.526    57716 bytes read. NOT ALL BYTES READ!
21:24:05.526    FillBuffer()
21:24:05.526    CVirtualFile::Read(buf, 169200) from 1918916. Current file 0.
21:24:05.526    CVirtualFile::Read() from disk (raw no slip)
21:24:05.526    0 bytes read. NOT ALL BYTES READ!

But the file is growing

Code:

2013-01-17 21:24:02.708    [DEBUG][29]    Network Recorder C:\Temp\live-FOX NEWS-6909.ts GET_FILE_SIZE  750308
2013-01-17 21:24:12.708    [DEBUG][29]    Network Recorder C:\Temp\live-FOX NEWS-6909.ts GET_FILE_SIZE  5057576

Maybe the reader doesn't like zero bytes read?

Martin

[sub]

That is a side effect of it not using the 'NPVR Writer'. When the writer is used, the reader knows a lot about what is going on with the data (for both live tv and in-progress recordings), and knows that more data will be appearing soon etc. Without this it assumes it's playing an already complete recording, and if it bumps into the end of the file then it thinks it has reach the end of playback.

[bigzaj]

A side effect due to SageDCT? Is there anyway around this?

[sub]

A side effect due to SageDCT?

That, and Network Recorder plugin.

Is there anyway around this?

Unfortunately other than switching to a supported cablecard device like HDHomeRun Prime, or Hauppauge DCR-2650, there is no workaround at this stage

We're slowly working though it. Neither Martin or myself have a Ceton cablecard device and access to usable tv signal, so I'm not sure we're the best team for the job

[mvallevand]

Try bumping the buffer time from 3000 to 5000 NextPVR might stay far enough behind.

Martin

[bigzaj]

That worked with my two channels tested. I will go ahead and import a channel guide and try it with multiples. Slow channel changes now though.

[mvallevand]

That is a side effect of it not using the 'NPVR Writer'. When the writer is used, the reader knows a lot about what is going on with the data (for both live tv and in-progress recordings), and knows that more data will be appearing soon etc. Without this it assumes it's playing an already complete recording, and if it bumps into the end of the file then it thinks it has reach the end of playback.

A network tuner will only stop on error or when NRecord tells it too stop. Couldn't you change the assumption to be an in-progress growing recording?

Martin

[sub]

Unfortunately it's not that straight forward. If it thinks it's a in-progress recording, then it has stacks of bits of code that communicate stuff in shared memory with the writer. None of that would work, and would need different implementations. This share memory stuff flows on to lots of different components, even streaming to clients etc.

You've been getting lucky playing these files when you'd not managed to bump into the end. As far as the app was concerned, it thought these were completed recordings no longer being written to.

[sub]

I'll have a try tomorrow at improving the situation.

[mvallevand]

I'll have a try tomorrow at improving the situation.

Thanks sub, I will update my plugin on this thread, in case you need it. I've made my test mode a bit more robust so plays through all these files now. I also will exit the plugin at EOF and the lease fails nicely after that.

Martin