97.7 CPU Usage

[madcat]

Hi,

I'm having CPU usage issues which I didn't have before.

I don't know if something changed recently (I did the DB converstion lately), but at least at the begining (after the 97.7 upgrade) it was working fine, now it's almost impossible to watch live TV.

When doing live TV, cpu is about 35% all the time (this may have been the case with prev. version). When changing channels, it's at 100% (this is new), and the GBPVR.exe-native.log log is filled with many (100-200 every time) lines of:
"VERBOSE GetFilterProperty - IKsPropertySet->Get propertry failed"

Now, I saw other threads - I went to direct.ini, and changed, under the
[Hauppauge WinTV PVR2 USB2] section from
INIT_MODE=IVAC
to:
INIT_MODE=DEFAULT
doesn't seem to change anything. Still same lines in log.

(BTW - what needs to be restarted for it to take effect?)

What am I missing?[ATTACHMENT NOT FOUND]

[sub]

To get rid of the messages in the log you could try setting INIT_MSP=0

[zehd]

I've just converted to 97.7. It's stable ebough that I won't be looking back. And Sub doesn't want us to look back anyway... :-)

But I also have CPU issues. Just playing a Medium recorded Mpeg2 (season recording) the CPU is at 35 % now, where it used to be no more than 10-15

It's a bare bones config. Comskip, running parrelel (in config panel)

I'm also using ffdshow, but not for MPEG playback. It is not running during playback.

I also have an GBPVR recorded episode transcoded with Mencoder into Xvid 2800 bitrate that won't play at all. Very stuttery, blotchy.

It played perfectly in 96.12. It even played across the network with Huappauges MediaMVP software..

[ATTACHMENT NOT FOUND]

[madcat]

Ok, this got read of the log lines.
However, CPU still jumps to around 100% on each channel change.
Or, pressing the "Guide" button during LiveTV (that brings the small guide at the bottom), caused 100% cpu for almost 10 seconds.

Both actions get to the point where you see TV signal starts to slow or freeze for a second, and then continues.

What else can I be looking for?

[zehd]

Ok, this got read of the log lines.
However, CPU still jumps to around 100% on each channel change.
Or, pressing the "Guide" button during LiveTV (that brings the small guide at the bottom), caused 100% cpu for almost 10 seconds.

Both actions get to the point where you see TV signal starts to slow or freeze for a second, and then continues.

What else can I be looking for?

I've always had a bit of that with LiveTV. (96.08 - 97.7) Once the channel is changed and I'm viewing it, I can pop out of liveTV and then in, and it's better.

I found that a pain, but not bad enough to get squeaky about...

[madcat]

I understand what you're saying, but what I see now is new, and there's nothing new installed or changed except the 97.7 upgrade and the DB conversion, so I just wondered.

I mean, if you "zap" few channels up/down, the TV is impossible to watch for 5-10 seconds... this is not fun for zapping, and for sure fails the WAF.

Sub - the fact that those lines are not in the log - what are they actually? and they were not there in 96, so, what I'm saying is, they are not printed out, but if they are a symptom of something else that is working in the background, what is that "something"? can it be disabled, or is it related to the upgrade, etc.