07814: All systems that do screen resolution change.: MNG recording for systems that change screen resolution

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07814	Graphics	Trivial	Always	Dec 9, 2020, 03:31	Dec 13, 2020, 23:49

Tester	Hirudov	View Status	Public	Platform
Assigned To		Resolution	Open	OS
Status [?]	Confirmed			Driver
Version	0.226	Fixed in Version		Build
		Fixed in Git Commit		Github Pull Request #

Summary	07814: All systems that do screen resolution change.: MNG recording for systems that change screen resolution
Description	When MAME records the video output to MNG file for systems that change screen resolution, the MNG container doesn't reflect the change! This makes the software for MNG processing that I use to crash, rendering the MNG recording useless. Example platforms that change screen resolution very often are IBM5150, but there are many others. Easiest way to fix this issue is to make MAME record separate .mng file every time a screen resolution change happens. I am not sure if this will lead to desync with .wav files, if they are written at the same time. It could be better to make separate .wav file at the same time as well. See my bug report https://mametesters.org/view.php?id=7673 for more information (bug was fixed).
Steps To Reproduce	Start MAME from command line with: mame64 ibm5150 -mngwrite ibm5150.mng -wavwrite snap/ibm5150.wav After the BASIC interpreter loads, type in the BASIC prompt: SCREEN 1 SCREEN 2 Exit the emulator.
Additional Information	The ,mng file created with the example in the "Steps To Reproduce" is impossible to process. if -aviwrite is used instead of -mngwrite, the resulting avi file is good for use, but with each resolution change, additional editing or split of the file is needed for video processing.
Github Commit

Flags
Regression Version
Affected Sets / Systems	All systems that do screen resolution change.

Attached Files

No.18257 Tafoid Administrator Dec 13, 2020, 23:49	I can confirm the MNG seems to freeze in my replay (used MNGer). I'm not sure if there is a solution or if you can select a new resolution via -snapsize trigger to allow you to make the MNG record larger than what is expected or it changes to.