[0.9211] Recording service grabs 100%CPU

[venger]

Hi all,

Has anyone had any occassion when their recording service is grabbing approx. 100% CPU?

I am finding that the recording service CPU usage shoots up to almost 100% when:
(1) there is a CPU spike usage from another app - say I am surfing, downloading, and the recording service is recording TV
(2) my PC wakes up from hibernate to record TV

I also find that when this happens I can't manually use Task Mgr to terminate the service - if i restart the service, it just shoots up to 100% again.
So to recover, I have to CANCEL recording thru GBPVR - and this is hard to do when the GUI is crawling due to the service grabbing 100% CPU

note: this happens whether or not I set the new ForceRecordingServicePriorityHigh flag in config.xml

[venger]

Hi again,
Just to report that yesterday, my recording service started grabbing 100% CPU again
It happened when I tried to do a "Quick Record" on a TV show that had already started. The recording service CPU usage just went quickly to 100% and stayed there. When I terminated using Task Mgr and restarted it, it again used up 100% cpu.

Sub, maybe there's an evil infinite loop in the recording service?

To be honest - due to lack of other ppl having this problem, I am thinking that there is a bug in the BDA driver for the Compro Videomate DVB-T300.

Anyway, after work today, I will do a full delete/cleanup and reinstall of GBPVR. I might even go back to the older 0.91xx version.

thanks,

[herbs]

Nope with the latest I had the same problem and recordings failed to stop, I went back down to 0.91.08 I think and that is fine. I have the older nova-t so its not related to the Compro mate drivers.

[Darx-starz]

I have a Nova-t 90002 and I get recordings that fail to stop. I am on the latest version. I thought it was becuase I had a PVR150 and 350 installed and the old drivers were causing a problem with the new card. If I keep the machine powered it does not happen. Its only when it comes up from hibernate. I had 1 recording that went on all day while was out. That was a very big file. gb-pvr would not play it :-) I am now getting random crashes of gb-pvr and the module its faulting on is the cyberlink mux for the nova-t.

[venger]

hey there again,

just completed my clean install.. and sadly, still having the same problem...
below are the logs....
the log entries in BOLD looks suspect.. but i am really not sure if these could cause the 100% CPU load ?

22:35:00.640 INFO Log started
22:35:00.640 INFO BDARecorder:::StartRecording(Compro VideoMate T300, 1, C:\Documents and Settings\thom\My Documents\My Movies\FRIDAY NIGHT FOOTBALL PORT ADELAIDE V HAWTHORN\FRIDAY NIGHT FOOTBALL PORT ADELAIDE V HAWTHORN_20050617_20302345-2.mpg, T:C8,191500,0,0,7~P:1025~V:512~A:650~TXT:576~N:>Nine Digital)
22:35:00.656 INFO Initializing DVB-T tuning request.
22:35:00.656 INFO tuning@1
22:35:00.656 INFO tuning@2
22:35:00.656 INFO tuning@3
22:35:00.656 INFO tuning@4
22:35:00.656 INFO tuning@5
22:35:00.656 INFO tuning@6
22:35:00.656 INFO tuning@7
22:35:00.656 INFO tuning@8
22:35:00.656 INFO tuning@8
22:35:01.765 VERBOSE About to auto detect correct tuner filter
22:35:01.781 VERBOSE Looking for associated filter
22:35:01.781 VERBOSE - VideoMate BDA Digital Capture
22:35:01.781 VERBOSE Successfully auto detected tuner filter: VideoMate BDA Digital Capture
22:35:01.781 VERBOSE ConnectPins: 'MPEG2 Transport' to 'MPEG-2 Stream'
22:35:01.781 VERBOSE getSetting(EPGProcessingMode)
22:35:01.796 VERBOSE Mapping Video PID 512
22:35:01.796 VERBOSE Mapping Audio PID 650
22:35:01.796 VERBOSE Mapping Teletext PID 576
22:35:01.812 VERBOSE FindFilterByName failed to locate filter: GB-PVR DVB-WST Subtitle
22:35:01.812 VERBOSE getSetting(BDAMultiplexer)
22:35:01.812 VERBOSE Initialzing Cyberlink mux
22:35:01.812 VERBOSE Setting IID_IMpgMuxer3
22:35:01.812 VERBOSE Setting IID_IMpgMuxerInfo
22:35:01.812 VERBOSE SetMuxInfo2() did not return S_OK
22:35:01.812 VERBOSE Finished initialzing Cyberlink mux
22:35:01.828 VERBOSE ConnectPins: 'Video' to 'Video In'
22:35:01.828 VERBOSE ConnectPins: 'Audio' to 'Audio In'
22:35:01.828 VERBOSE ConnectPins: 'Output' to 'Input'
22:35:02.109 VERBOSE locked=1 present=1 strength=2147483647 quality=25
22:35:04.531 VERBOSE getSetting(ListGraphFilters)
22:35:04.531 VERBOSE Graph contains the following filters:
22:35:04.531 VERBOSE - MPEG-2 Sections and Tables
22:35:04.531 VERBOSE - BDA MPEG2 Transport Information Filter
22:35:04.531 VERBOSE - GB-PVR Writer
22:35:04.531 VERBOSE - CyberLink MPEG Muxer
22:35:04.531 VERBOSE - MPEG-2 Demultiplexer
22:35:04.531 VERBOSE - VideoMate BDA Digital Capture
22:35:04.531 VERBOSE - VideoMate BDA DVBT Tuner
22:35:04.531 VERBOSE - Microsoft DVBT Network Provider
22:35:04.531 VERBOSE getSetting(SaveGraphFiles)
22:35:04.531 VERBOSE BDARecorder::StartRecording() finished

[venger]

Hi all,

Have finally tracked down an old post that suggests that all these problems are due to particular mux filters.
Namely, PDMPGMUX.AX.

I have unregistered it - so will have to wait and see if it does the trick
Will let ya'll know k..

Its Friiiiiiday... woohoo...

Here's the post:

Guy Guy is offline
Junior Member

Join Date: Mar 2005
Posts: 14
Default
Update on my own system's stability:

I have now managed to get rid of the 100% CPU usage problem. This, I think, was being caused by a mux filter called PDMPGMUX.AX which is installed by cyberlink's powercinema alongside mpgmux.ax. This seems to be an audio mpeg filter....system seems to work fine without it (on the PC at least).

Well system nearly works fine....I'm now moving on to the problem that results from not having PDMPGMUX - GBPVR and recording service are crashing when I try to use the MVP to view live TV (with PDMPGMUX installed, playback on the MVP works occasionally, but then hits 100% cpu usage - without it, the whole service crashes immediately the MVP requests a live TV stream).

Ho Hum one step closer I suppose.

g.

[venger]

BTW,

Herbs and Darx-Starz.. thanks heaps.. i was starting to worry that I was all alone with my problem
In fact, I then started using your ids to trace thru all the old posts - and that's how I found the mention of the PDMPGMUX.AX filter.

Well.. at the moment, after unregistering that mux, recording seems to be working a treat!.. fingers crossed.....

thanks again,

[venger]

Hi all...

I unregistered the PDMPGMUX.AX - and now all my recordings are finally occurring.... no more 100CPU% !!

Just a huge thank you to everyone who helped ... esp. Herbs who led me to the trail in the first place...