- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
06291 | Interface | Major | Have not tried | Jul 12, 2016, 02:12 | Jul 16, 2016, 19:51 |
Tester | Tafoid | View Status | Public | Platform | MAME (Official Binary) |
Assigned To | Jezze | Resolution | Fixed | OS | Windows Vista/7/8 (64-bit) |
Status [?] | Resolved | Driver | |||
Version | 0.175 | Fixed in Version | 0.176 | Build | Normal |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 06291: carpolo: Unable to view recorded video made with -video bgfx/-window | ||||
Description | In this one example, a video created from this game using the SHIFT+ALT+F12 to start and stop the recording does not play (show video) in linux and windows attempts | ||||
Steps To Reproduce |
mame64 carpolo -video bgfx -window- Start game and start recording by hitting SHIFT+ALT+F12 - Record for a second or so, the HD space will fill up quick! - Exit MAME .. AVI will write and mention frames captured in dialog Attempt to play this file in VLC, Winamp or even Window Media Player - there is no video |
||||
Additional Information |
May be somewhat related to another issue with normal -aviwrite for shangon: http://mametesters.org/view.php?id=6286 |
||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | carpolo | ||||
Attached Files
|
MPCHC print screen.jpg (1,897,516 bytes) Jul 12, 2016, 03:29 Uploaded by B2K24 MPCHC print screen MAME 0.175 | ||||
Relationships
There are no relationship linked to this issue. |
Notes
3
No.12930
B2K24 Senior Tester
Jul 12, 2016, 03:26
|
I created a 4 second clip and Windows 10 default app gives me error code 0xc00d36c4 - file format may be unsupported, file extension may be incorrect, or file may be corrupted. Attempting to play with MPCHC or WMP gives me the results in attached pic when jumping through the video. General |
---|---|
No.12937
Jezze Developer
Jul 13, 2016, 20:24
edited on: Jul 13, 2016, 20:25 |
If I had to guess, I would say the reason for this issue is the odd width/height of the video, that either is not written correctly by MAME (which I doubt) or cannot be read by the player. The most video players don't support an odd video resolution, maybe FFplay is capable. |
No.12948
Jezze Developer
Jul 16, 2016, 18:55
|
Should be fixed with https://github.com/mamedev/mame/commit/89af2864ed8c2bde525532d1bf72542da2c76ae0 |