Diff between recordings and timeshift?

[capone]

I only watch tv in timeshift format. I always took to mean I was I was watching a higher-quality recording, as it recorded. But it seems like GB treats or handles them differently. Is this true, and if so, how is it different?

In playing w/ the vNivida decoder w/ HW accel on, I noticed it is only jerky when watching a recorded show. When I watch live tv timeshifted, it plays just fine. Every recording I have that I play is jerky. Both are using the nVidia decoder, and the only difference in the encoding settings (med and live) is < 3000 in video rate (audio the same).

[sub]

In playing w/ the vNivida decoder w/ HW accel on, I noticed it is only jerky when watching a recorded show. When I watch live tv timeshifted, it plays just fine.

They're pretty much the same, except for the profile that is used, which has a different bitrate.

[sub]

It maybe worth looking in your gbpvr.exe-native.log to see if any extra filters like ffdshow or reclock are being added, as these have the potential to interfere with smooth playback.

[capone]

ffdshow is used for both...I don't have reclock set up on this build.

I just checked the playbacks (for intervideo, as I don't have two nvidia examples handy). There is a difference: the parser vs the demultiplexer.

I don't know if there's a solution here or anything I'm looking for. I guess it was just finding a difference between the two playbacks, so I knew why they were outputting differently.

Recording:

16:20:36.343 VERBOSE getSetting(PreferredAudioRenderer)
16:20:36.406 VERBOSE getSetting(PreferredAudioDecoder)
16:20:36.468 VERBOSE audio decoder filter: InterVideo NonCSS Audio Decoder for Hauppauge
16:20:36.468 VERBOSE getSetting(PreferredDecoder)
16:20:36.531 VERBOSE video decoder filter: InterVideo NonCSS Video Decoder for Hauppauge
16:20:36.703 VERBOSE getSetting(ListGraphFilters)
16:20:36.703 VERBOSE Graph contains the following filters:
16:20:36.703 VERBOSE - Default DirectSound Device
16:20:36.703 VERBOSE - Video Renderer
16:20:36.703 VERBOSE - ffdshow Audio Decoder
16:20:36.703 VERBOSE - InterVideo NonCSS Video Decoder for Hauppauge
16:20:36.703 VERBOSE - InterVideo NonCSS Audio Decoder for Hauppauge
16:20:36.703 VERBOSE - MPEG-2 Demultiplexer

Timeshift:
GB-PVR Parser

16:22:42.312 VERBOSE Creating new graph
16:22:42.312 VERBOSE getSetting(PreferredAudioRenderer)
16:22:42.375 VERBOSE getSetting(PreferredAudioDecoder)
16:22:42.406 VERBOSE audio decoder filter: InterVideo NonCSS Audio Decoder for Hauppauge
16:22:42.406 VERBOSE getSetting(PreferredDecoder)
16:22:42.421 VERBOSE video decoder filter: InterVideo NonCSS Video Decoder for Hauppauge
16:22:42.437 VERBOSE Using GB-PVR Parser
16:22:42.468 VERBOSE Rendering graph
16:22:43.046 VERBOSE getSetting(ListGraphFilters)
16:22:43.046 VERBOSE Graph contains the following filters:
16:22:43.046 VERBOSE - Default DirectSound Device
16:22:43.046 VERBOSE - Video Renderer
16:22:43.046 VERBOSE - ffdshow Audio Decoder
16:22:43.046 VERBOSE - InterVideo NonCSS Video Decoder for Hauppauge
16:22:43.046 VERBOSE - InterVideo NonCSS Audio Decoder for Hauppauge
16:22:43.046 VERBOSE - GB-PVR Parser

[capone]

Btw, I always wanted to ask: what does setting the ffdshow for post-processing do in the CP? I never check it, but use ffdshow for post-proc, so I wondered when/why you would use it.

[sub]

I dont really have anything to suggest other than trying some other video decoders, and try it with ffdshow disabled to see if you can find some improvements.

what does setting the ffdshow for post-processing do in the CP? I never check it, but use ffdshow for post-proc, so I wondered when/why you would use it.

The way ffdshow works, you usually wouldnt have to check this setting. The default configuration for ffdshow is to be used in all playback. If you ffdshow isnt configured to automatically used, then you can use this check box to try to force it to be used.

[capone]

I dont really have anything to suggest other than trying some other video decoders, and try it with ffdshow disabled to see if you can find some improvements.

That's ok...it's not like I'm not watching stuff just fine. I was interested because the nVidia w/ the HW on looks great and uses less proc power. It works execept for w/ the recordings, which is why I got interested.

I assume there's no way to use the parser instead? NBD if there isn't, as I don't know if that would make the difference anyway.

The way ffdshow works, you usually wouldnt have to check this setting. The default configuration for ffdshow is to be used in all playback. If you ffdshow isnt configured to automatically used, then you can use this check box to try to force it to be used.

Ah...ok. It always seemed pretty forceful, so I wondered why. Maybe it would override setting the priority to zero, which I could see a use for if you used other media apps on the same system.

No for this, but this may come in handy in the future: If there were people having problems w/ mpeg2 files and not TS tv files, having GB treat them like TS tv files would solve that, and make one standard for mpeg 2 playback (and only one playback to support).

[sub]

I assume there's no way to use the parser instead?

The GB-PVR Parser is only used if the file is still being recorded.

No for this, but this may come in handy in the future: If there were people having problems w/ mpeg2 files and not TS tv files, having GB treat them like TS tv files would solve that, and make one standard for mpeg 2 playback (and only one playback to support).

I dont think this is widespread. In fact I think you're the only person who has mentioned this problem.

[capone]

I wasn't thinking for this, as it's not a GB problem, obviously. Besides, now that I understand the process more, I don't think it would matter. Like I said, it's my pet project. I did take the time to try the nvidia again, and the filters look the same as the intrvideo output.

Thx for taking a cpl of minutes on this. I always hope doing something like this begining to end may answer someone else's question w/o taking up anyone's time, if nothing else.