Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
07013 Misc. Minor Always 8 days ago 8 days ago
Tester wuemura View Status Public Platform MAME (Official Binary)
Assigned To Resolution Unable to reproduce OS Windows 10 (64-bit)
Status [?] Closed Driver pong.cpp
Version 0.198 Fixed in Version Build 64-bit
Summary 07013: breakout: MAME takes double the time to complete a 30s task
Description
Robbbert - When you use -str, the seconds is the number of emulated seconds, not real seconds. Since your machine is so slow, it takes twice as long to run.
http://mametesters.org/view.php?id=7011

Sorry, this is not true.
If you use -srt in ANY OTHER MACHINE than pong MAME will respect the 30s task, including machines that require much more processing power.

My report is not invalid!
Steps To Reproduce
mame breakout -str 30
Additional Information
Flags
Regression Version
Affected Sets / Systems breakout
Attached Files
 
Relationships
There are no relationsihp linked to this issue.
Notes
1
User avatar
No.15140
Tafoid
Administrator
8 days ago
Wuemera,
Again, you have opened a bug report which was confirmed not to be happening using proper recording tools. Just because you are not getting the answer you want and you have this need to be right about everything by reopening/recreating closed bugs. This is unacceptable. One more time and I will permanently viewerize your account. Please be mindful of future reports and keeping replies on-topic to the issue, please.

The reason why this isn't an issue, if it wasn't clear, is that whatever you are recording with (outside of MAME), is not respecting the emulation speed. You using -str 30 in mame will run for 30 emulated seconds which in reality could take any length of time to render in real time. Your external to MAME Windows tool doesn't know anything about these 30 seconds and is recording for as long as your computer is outputting to the window. When you use -aviwrite, the rendered/uncompressed recording is recording and timing it so that it matches 100% speed when played back regardless of what speed it is showing when you actually record the clip.

So, yes, this is not a bug. If you want 100% represented emulation speed in your recordings, use -aviwrite.

Closing.