Quote:
Originally Posted by Dr.Venom
Hopefully the logs provide some clue as to what is happening..
|
I think it simply means it fails to recover if frames mismatch at least once. Nothing happens if fields match when switching to interlace.
Unfortunately I am not sure when I can test real interlaced modes again. (
http://eab.abime.net/showpost.php?p=810833&postcount=11 unless that one supports real interlace. I don't want to mix red and green drivers..)
Quote:
|
On another note, when running only tinylauncher from workbench (a small tool to launch WHDload stuff easily) the cpu usage seems much higher with this A1200/AGA/CE config for 2.4.1 and 2.4.2b1 compared to 2.4.0. According to the onscreen leds it uses between 60-70% cpu (averaging at about 60% and spiking regurlarly to 70%) on 2.4.1 and 2.4.2b1. That's on a Core I7-920 clocked at 4.2Ghz. On 2.4.0 using the same setting uses between 40%-60%, averaging at about 50%.
|
I wouldn't care much about CPU% because method to calculate changes all the time and some waits may have been replaced with busy waits (no buffer = busy waits are usually better. Minimum wait is 1ms, which is very long time)