Cancel recording (which wasn't even recording), crash (enclosed)

[sub]

There might be a few reason why you get no video with ffdshow. You may need to add nextpvr.exe to the application white list in the ffdshow settings or ffdshow will be non-functional.

[glassvial]

Done, now it plays but it's choppy and looks like crap! I can't win.

[sub]

At the end of day, if you use the same decoders and video renderer as you used in GBPVR, then it should look no different. Both use directshow to do the playback, and how well it works comes down to which directshow components you're using.

[johnsonx42]

perhaps you weren't really using ffdshow with gb-pvr... the fact that you had it selected doesn't necessarily mean it was actually being used. if you look in the gb-pvr logs it should report the actual graph that got used.

[glassvial]

Which log would it be in? Because I'm pretty sure GBPVR is/was using ffdshow.

[johnsonx42]

the pvrx2-native.exe.log will list the decoders used for playback; iirc it parses the graph after it gets created, and will show if any extra decoders got inserted because a chosen decoder failed to hook up. I admit I'm probably wrong, but this scenario is possible and would explain why you're not getting the same results with npvr.

[glassvial]

Well here's a snip from that log:

2011-01-15 02:14:08.387 VERBOSE Graph contains the following filters:
2011-01-15 02:14:08.387 VERBOSE - Default DirectSound Device
2011-01-15 02:14:08.387 VERBOSE - Video Renderer
2011-01-15 02:14:08.387 VERBOSE - ffdshow Video Decoder
2011-01-15 02:14:08.387 VERBOSE - ffdshow Audio Decoder
2011-01-15 02:14:08.387 VERBOSE - MPEG-2 Demultiplexer

I'm guessing thats what we were looking for, looks like it's using ffdshow (and like I said, it's displaying/playing properly, smoothly, and proper AR)

:confuzzled: