Re: NTSC VIC-II timing

From: groepaz_at_gmx.net
Date: Wed, 21 Jun 2017 19:01:25 +0200
Message-ID: <2643057.LaFJv6b0So@rakete>
On Wednesday 21 June 2017, 18:53:45 silverdr@wfmh.org.pl wrote:
> > On 2017-06-21, at 18:34, groepaz@gmx.net wrote:
> >> The simple way is to disable interrupts and write a loop that samples
> >> $d012, counting the cycles that go between changes. I do not know if
> >> exactly such implementation is available anywhere.
> > 
> > [snip]
> > 
> > i wouldnt call that exactly simple :) counting cycles always needs to be
> > cycle exact code - which is far from that.
> > 
> > instead, simply check the number of scanlines -
> 
> It's could be expected but I only now noticed that the two NTSC variants in
> question differ also in number of scanlines. Difference, which may possibly
> be used to detect the variants similarly to the method used for PAL/NTSC
> detection.

yup, look at the "graham method" on that codebase page - it cant get any 
simpler :)

-- 

http://www.hitmen-console.org    http://magicdisk.untergrund.net
http://www.pokefinder.org        http://ar.pokefinder.org

It is essential to understand that everybody sucked in the beginning. 
<Kristofer Dahl>



       Message was sent through the cbm-hackers mailing list
Received on 2017-06-21 17:07:24

Archive generated by hypermail 2.2.0.