Posts: 31
Joined: Sep 2008
Reputation:
0
By the way, I have "VSyncControl=V3" which should mean that the vsync slider in Catalyst is in the rightmost position (=ON).
Posts: 3,555
Joined: Oct 2003
Reputation:
12
tslayer
Team-XBMC Developer
Posts: 3,555
Did you try the patch yet?
42.7% of all statistics are made up on the spot
Always read the XBMC online-manual, FAQ and search the forum before posting.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules.
For troubleshooting and bug reporting please make sure you read this first.
Posts: 476
Joined: Nov 2007
tslayer, can you tell us a bit more about XBMCs behaviour that leads to that error when trying to initialize VSYNC? I mean, what exactly is XBMC checking for? General VSYNC support of the driver? Or specifically VSYNC for OpenGL? Is there a difference at all?
boba
Posts: 38
Joined: Jun 2008
Reputation:
0
kknull
Junior Member
Posts: 38
I had the same problem with ati x1600
now I tried with "vsync default off except application setting" in catalyst control center
and "vsync on during playback" in xbmc
and now seems to work fine.. cpu < 10%
catalyst 8.9
xbmc beta1
Posts: 38
Joined: Jun 2008
Reputation:
0
kknull
Junior Member
Posts: 38
Hi, I forget to say that I use the nopat kernel option (I don't know if can be important...) because I get some flickering and slowlyness without it starting from catalyst 8.8
Posts: 38
Joined: Jun 2008
Reputation:
0
kknull
Junior Member
Posts: 38
... and I didn't applied any patches (I think... I will contact the package maintainer...)
Posts: 476
Joined: Nov 2007
shagworthy_uk Wrote:So after killing powernowd cpu is at 1% when idle... I recommend killing powernowd before testing any config as this can be a red herring.
I am getting "some" tearing during video playback now so may play with the settings again now that powernowd is not amplifying the issue (or appearing to)
On a side note, in the latest build (15682) livetv works again for myth protocol so im really cooking on gas now!
Powernowd isn't "amplifying" anything. Of course your cpu usage in% is higher when powernowd has your cpu throttled to let's say 1ghz instead running at 2.5 ghz .... makes sense, doesn't it? You gotta choose if you want to have your cpu running full speed all the time, thus eating more juice, or if you want powernowd to clock it down when not needed.
boba
Posts: 4,997
Joined: May 2004
Reputation:
12
What choice is there to make? XBMC is consuming the same amount of CPU regardless. But w/o scaling you're eating WAY more power. The obvious choice is to reenable scaling and just remember that your CPU is scaled so the numbers are larger.
Posts: 59
Joined: Jun 2008
Reputation:
0
I totally agree and totally understand how stepping/scaling works, all i was saying was: if your trying to fine tune your CPU usage, if you disable powernowd while you are doing it you will get accurate results instead of mixed results with powernowd running. Yes powernowd should be re-enabled after you have fixed the CPU usage issues. I also said/meant: "appear to be amplifying" as in "perceived to be...".
ASRock Ion 330 | 6TB Drobo | Pioneer PDP-4270XD (s/pdif) | Sony DAV-DZ810W | Logitech Harmony 885 (MCE remote emulation)| diNovo Mini
