Can only view QAM in Timeshift now

[Snooze]

All of a sudden, I cannot view some of my QAM channels without LiveTV disabled in config. Do these logs give any clues? I didn't pick at it at all...

EDIT: And in Timeshift, audio sounds like it is in fast forward, and the video stutters. So that renders Timeshift useless too.

[sub]

All of a sudden...

Whenever people say this, I always guess they're using the 'system default' decoders, and they've either installed or uninstalled or changed some setting in some other app, which has changed the system default decoder.

Surely enough, your logs indicate you're using 'system default' decoder.

Try some other decoders.

[Snooze]

I don't see how that would explain only SOME QAM channels work,some do not. They all work in timeshift, but the quality is poor.

I have it set to use MPV Decoder Filter for video, system default for audio decoder, AC3 Filter for AC3 decoder and system default for audio rendered (see my sig) and it has always worked. I haven't done a thing to the PC that I can think of. It is a dedicated machine.

I reinstalled all my codecs, still is the same few channels not playing.

[whurlston]

In the ffdshow Video Decoder configuration, disable the "Raw" codec (bottom of the codec list).

Code:

2009-09-19 12:40:49.500    VERBOSE    Graph contains the following filters:
2009-09-19 12:40:49.500    VERBOSE     - Default DirectSound Device
2009-09-19 12:40:49.500    VERBOSE     - Video Renderer
2009-09-19 12:40:49.500    VERBOSE     - BDA MPEG2 Transport Information Filter
2009-09-19 12:40:49.500    VERBOSE     - GB-PVR PSI Parser
2009-09-19 12:40:49.500    VERBOSE     - MPA Decoder Filter
[B][color=Red]2009-09-19 12:40:49.500    VERBOSE     - ffdshow raw video filter[/color][/B]
2009-09-19 12:40:49.500    VERBOSE     - MPV Decoder Filter
2009-09-19 12:40:49.500    VERBOSE     - GB-PVR Flow Status
2009-09-19 12:40:49.500    VERBOSE     - MPEG-2 Demultiplexer
2009-09-19 12:40:49.500    VERBOSE     - GB-PVR TS Mon
2009-09-19 12:40:49.500    VERBOSE     - Hauppauge WinTV 418 TS Capture
2009-09-19 12:40:49.500    VERBOSE     - Hauppauge WinTV 418 BDA Tuner
2009-09-19 12:40:49.500    VERBOSE     - Microsoft ATSC Network Provider

[Snooze]

Thank you whurlston. Before you replied I unistalled, Ccleaned and reinstalled K-Lite codec pack, FFDshow and AC3 Filter. I checked ffdshow as to make sure Raw filter was disabled, and it was. I get the same results only SOME QAM channels work, others don't... attached are new logs if you can take another look.

[whurlston]

It's still being loaded. Using GraphStudio or GraphEdit, insert the "ffdshow raw video filter" into a new graph. In the Codec properties, you should only see the "Raw video". Disable it there.

[Snooze]

Ok, I did that, and I can see in the logs what your watching for. I used graphstudio, confirmed twice it was disabled there and in Video Decoder Configuration, and it is still loading. What else can i try?

[whurlston]

Just to confirm, you disabled it in both the "ffdshow Video Decoder" and "ffdshow raw video filter"? If so, try adding pvrx2.exe to the list of "do not use" apps for ffdshow.

If that doesn't work, post a set of logs showing you tuning a channel that works and then a channel that doesn't work.

[Snooze]

Yes, I confirmed it again. All disabled.

EDIT: Before you waste any more of your time, I see what the problem is. Since I have this problem http://forums.nextpvr.com/showthread.php?t=43719 I need to switch back and forth from 96 DPI and 120 DPI.

Well, I had switched back to 120 DPI this morning, not thinking it was going to bomb my mapping.

For some forsaken reason, when I switch between the two, my Digital Channel Mapping gets screwed up. I know it shouldn't be related, but that's what happens. Looks like I am stuck with using 96DPI until the next release. Isn't windows wonderful? That explains why it worked in timeshift I think.

So now I rescanned my digital channels and started PVRX2, still nothing, same problem. Go back into config and check the mappings, it looks like it was when I okay out last time, but selecting on one of the problem channels didnt display anything like it did the first time I confirmed it. RESCANNED AND MAPPED AGAIN :mad: Now it works. The Scanning is real flaky in this release, although I like the new interface, it just doesn't seem to make the changes stick very well for me.

I know I am not touching my DPI settings again, but should I still leave FFDshow Raw disabled and list of "do not use" apps for ffdshow?

[whurlston]

You should be able to undo the changes to ffdshow.