Open malespiaut opened 4 months ago
-aviwrite
blindly adheres and has no provision for in-flight resolution changes;-aviwrite
should be put in the air and destroyed like in skeet shooting. I seriously doubt you get much out of a CPC before it starts doing resolution changes and breaks your capture, consider using app alternatives such as OBS Studio for grabbing MAME video output instead.MAME else adds extra resolution beyond standard border in spectrum-based drivers. But output screen can be cutted to the lower values. As far as I remeber @ICEknigh7 knows how.
I don't know how MAME does it here, but I think that any cropping should be left to the views and shaders, instead of having it hardcoded to the assumed but sometimes incorrect values.
Using a real monitor with a V-hold knob indeed allows us to see parts of the screen which MAME won't be able to display due to not having an uncropped view available, including some initial and trailing partial scanlines which I'm not sure can be emulated yet:
(Image taken from a ZX Spectrum +2A, just for illustrative purposes)
-aviwrite
should be put in the air and destroyed like in skeet shooting. I seriously doubt you get much out of a CPC before it starts doing resolution changes and breaks your capture, consider using app alternatives such as OBS Studio for grabbing MAME video output instead.
Hello @angelosa,
I was planning to use OBS / ffmpeg x11grab at first. But the advantage of an integrated video recording option is to have pixel-perfect and frame perfect recording, and without having to worry about video compression (which will be taking care of later, during post-processing).
I do understand that it is a burden for developpers, and it would be justified to remove it from MAME; but I also think that this is, in my humble opinion, a killer feature if it's being kept in and taken care of.
I was planning to use OBS / ffmpeg x11grab at first. But the advantage of an integrated video recording option is to have pixel-perfect and frame perfect recording, and without having to worry about video compression (which will be taking care of later, during post-processing).
Very unconvinced by this statement:
-aviwrite
by itself creates this big and giant "unfiltered" output that first and beforemost depends on HDD space and speed throughput;unfiltered
, it doesn't do anything like 4:3 and it's straight unusable by anything non-canonical (cfr. pce
for a laugh)-mngwrite
/-wavwrite
combo.Yeah, OBS is the way to go for recording MAME in the proper aspect ratio. If you need a "crisp pixel" look, just use the default bgfx shader and set prescale to 3 in mame.ini.
MAME version
0.264 (unknown)
System information
OS: Arch Linux, 64-bit, kernel 6.8.5-zen1-1-zen
Locale: en_US.UTF-8
RAM: 16GB
CPU: 11th Gen Intel i7-1165G7 (8) @ 4.700GHz
GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics]
INI configuration details
No response
Emulated system/software
Amstrad CPC6128 (cpc6128)
Incorrect behaviour
MAME reports a screen resolution of 704×144 while the Amstrad CPC 6128 normally have a resolution of 768×272.
While this doesn't impact gameplay, it does impact video recording via the
-aviwrite
option, and may be the source of some emulation bugs.Expected behaviour
MAME should report a video resolution of 768×272 when launching the
cpc6128
, as it is the Full-Screen Mode 2 resolution (see: https://www.cpcwiki.eu/index.php/Video_modes).Steps to reproduce
Launch MAME for the
cpc6128
machine, and see the MAME boot message.For video recording, launch MAME for the
cpc6128
machine with the-aviwrite test.avi
option, and view thetest.avi
result.Additional details
No response