> By the way, I am making my own MAME re-write, just finished with frame-stepping
> algorithm, accompanied with numerous changes to how timing and general frame and
> audio syncing is handled there. Those changes fixed all the visual glitches and audio
> hiccups and crackling MAME is cursed with, as you know, or do you not?
>
> Auto frame skipping algorithm is wrong. Some kind of attempt at telecine on the fly,
> but that doesn't work, it can not work. It's like dividing 5 by 3 and expecting to
> get a whole number as the result. There are only two properly working frameskip
> values in MAME: 6 and 9, (from 60fps -> 30fps, 15fps), but even using those would
> still leave you with audio syncing issues. You know what I'm talking about? Let me
> know if you wanna hear more.
Video and audio syncing are particularly important when running on 15KHz arcade monitors. If you don't get any interest here from the core MAME people, you might want to drop by the GroovyMAME forum over on BYOAC... http://forum.arcadecontrols.com/index.php?board=52.0
I think that GroovyMAME has some custom code that attempts to sync sound and video and I'm sure Calamity and BitByteBit would be interested in hearing about your methods for frameskipping.
GroovyMAME support forum on BYOAC
|
Index 
Flat 
Re: Why are MAME INPUT_ABSOLUTE_{MIN/MAX} 17 bits?
Reply
