2.4.3 Can't Playback some recordings on Clients

[smajor]

For example, seeing this as a possible problem in the logs on my clients:

2012-03-24 19:46:46.881 [DEBUG][1] added decoder to graph
2012-03-24 19:46:47.143 [ERROR][1] ConnectPins: Failed to find output pin named ~CC
2012-03-24 19:46:47.143 [ERROR][1] ConnectPins: Failed to find output pin named ~CC Out

Show is Kitchen Nightmares. It played back just fine with 2.3.6 on the same client and still plays okay on the Server now that it's 2.4.3.

Client log attached.

[sub]

For example, seeing this as a possible problem in the logs on my clients:

2012-03-24 19:46:46.881 [DEBUG][1] added decoder to graph
2012-03-24 19:46:47.143 [ERROR][1] ConnectPins: Failed to find output pin named ~CC
2012-03-24 19:46:47.143 [ERROR][1] ConnectPins: Failed to find output pin named ~CC Out

Those errors are normal, and can be ignored. These CC pins are only available on some decoders.

Show is Kitchen Nightmares. It played back just fine with 2.3.6 on the same client and still plays okay on the Server now that it's 2.4.3.

Reproduce the problem and zip and attach the client and server logs and I'll take a look.

[mvallevand]

Those logs show an exit with a very large negative position.

Martin

[smajor]

Sure. Client logs in the first post, here are the server logs.

[sub]

You say "some recordings". Are the problem files all above 2GB?

[smajor]

Nope. I can playback recordings that are 6GB+ in size on the client just fine, alternately, it will fail on something just 1.7GB in size.

Recordings are all over the map in terms of date too. Some were recorded last September and fail along with that Kitchen Nightmares that was just recorded last night.

[sub]

There must be some pattern to it.

[smajor]

There must be some pattern to it.

I agree. What it is, I don't know.

Maybe the attached will help? Two log files from comskip. Awake is a recording that works along with Kitchen Nightmares that doesn't.

Maybe you'll see something about the embedded streams of the files that is different somehow?

If I share my recordings directory and map that as a Videos directory on my client, I can playback anything. Obviously that isn't using NPVRTSReader2.ax.

[sub]

On one of the problem recordings, are you able to cut a chunk of like 30MB from the start of the file, and reproduce the playback problem on the client with that file? If so, I could download it and try reproducing it here.

If I share my recordings directory and map that as a Videos directory on my client, I can playback anything. Obviously that isn't using NPVRTSReader2.ax

If you play a .ts file in NextPVR, even if it's on a mapped drive, then it should be using NPVRTSReader2.ax. It does excercise some slightly different areas of the reader, but it's still using it.

[smajor]

Sure, I used the old TSCutter program. Hope that doesn't change the file. It definitely still happened with the cut.

http://www.themajorshome.com/misc/sample.zip

Thanks!