turn off EPG processing to save a lot of CPU cycles

[LeechBot]

I posted this at DVBN, but I guess it's more appropriate here. With 1.4i my CPU usage has gone from 5-10% on all channels to 25-35% on most of the channels I tune to, including Sirius radio channels. People say this is because the channels that are on the same tp as the 9-day EPG will now eat up the CPU because EPG processing has been fixed in 1.4i. I've had to switch both my computers back to 1.4h to fix the problem. If EPG processing were optional, I could save a lot of CPU power, and I never use the EPG at all.

[LeechBot]

Are there any thoughts about this? I mean, 1.4i uses five times the CPU cycles as 1.4h for an EPG list I, and maybe other people, never use,and I'd really like to be able to upgrade from 1.4h.

[yovagg]

You can not select "Options -> Preferences -> Localization : Customize settings for North America" on a daily basis. Then, if you need to scan the channels then select the option for you to use "NA Fast Scan".

This is just a trick to this version. But it works.

[LeechBot]

You can not select "Options -> Preferences -> Localization : Customize settings for North America" on a daily basis. Then, if you need to scan the channels then select the option for you to use "NA Fast Scan".

This is just a trick to this version. But it works.

Thanks for this suggestion. It looks like it's working. It's the only feedback I've gotten in eight months, so I was worried no one else cares too much about DD using so much of the CPU for things you never use. I didn't even get a single response at DVBN either. Is there another site besides this one and DVBN where we can get support for DD?

[yovagg]

You know, none of my friends worry to see how much consumes your CPU. I am a little minimalist and testing found this solution. When I try to explain how to improve care about or listen. I suppose that not only will my friends.

This site is good, better than DVBN for DD, but rather must be read and be somewhat risky.

[jman11]

I tried this trick and it didn't seem to work for me, though I am not quite clear on the steps. Do I just disable the "Customize for NA" option? Do I need to rescan the channels?

Any help would be appreciated, thanks.

[Nokios]

I did not bother to answer because I did not notice any increase in CPU usage between the different versions of DDream although I monitor it very carefully!...
I do not know why you are suffering from this.

I think that the great majority of DD users have never had the problem you describe so nobody answered you !

[LeechBot]

I did not bother to answer because I did not notice any increase in CPU usage between the different versions of DDream although I monitor it very carefully!...
I do not know why you are suffering from this.

I think that the great majority of DD users have never had the problem you describe so nobody answered you !

Actually, it would be helpful if people reported that they do not have this problem because that information would help determine the source of the problem that some of us are having with DD unnecessarily hogging the CPU.

[Dabbith]

The "problem" with the new version is that it supports extended EPG data. That data comes down very quickly (as high as a few thousand events per second). To try and process all that data takes quite a bit of CPU time on an older machine.

If you're using DVBEPG as your EPG, you can select the option to turn off DVBDream's internal parser.

If not, you could try to find a eitparser.dll from an older version and use that. (I'm going by memory, but I'm pretty sure that's the right file).

[Dabbith]

The "problem" with the new version is that it supports extended EPG data. That data comes down very quickly (as high as a few thousand events per second). To try and process all that data takes quite a bit of CPU time on an older machine.

If you're using DVBEPG as your EPG, you can select the option to turn off DVBDream's internal parser.

If not, you could try to find a eitparser.dll from an older version and use that. (I'm going by memory, but I'm pretty sure that's the right file).

[LeechBot]

The "problem" with the new version is that it supports extended EPG data. That data comes down very quickly (as high as a few thousand events per second). To try and process all that data takes quite a bit of CPU time on an older machine.

If you're using DVBEPG as your EPG, you can select the option to turn off DVBDream's internal parser.

If not, you could try to find a eitparser.dll from an older version and use that. (I'm going by memory, but I'm pretty sure that's the right file).

I never use any EPG whatsoever. Is there some way to just permanently turn all that stuff off?

[Dabbith]

You could try deleting/renaming eitparser.dll, I'm not sure if that'll cause a problem in dream or not. If it does, I would install DVBEPG and set it to disable the internal parser.

[LeechBot]

You could try deleting/renaming eitparser.dll, I'm not sure if that'll cause a problem in dream or not.

I'm trying this now and it looks good so far. For example, even after implementing the earlier suggestion to unselect "Options -> Preferences -> Localization : Customize settings for North America" I would still get 20% CPU usage when tuning to CNN, and possibly certain other channels. Now that I deleted eitparser.dll, CNN only takes up 6% CPU like all the rest of my channels. And I don't see any side effects in DVBDream yet.

[LeechBot]

The solution to the problem was so simple. How come, in seven months, no developer of DD ever read this thread? Should we even bother posting in feature requests?