Mame Video Capturing: Unterschied zwischen den Versionen

keine Bearbeitungszusammenfassung
Keine Bearbeitungszusammenfassung
Keine Bearbeitungszusammenfassung
 
(8 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt)
Zeile 1: Zeile 1:
= Introduction =
=important=
{| cellspacing=0 cellpadding=3 style="text-align: center; color:black;width:100%;"
|style="background-color: #FFF6AD;border: 1px solid #B5B5B5" |[[Image:Postponed.png|30px]] '''Caution:''' This is a very old article highlighting the ''best (without framedrops)'' possible way to capture mame gameplay around 2008
|}
 
This article has been written around 2008 when emulating games in MAME was way more difficult as it is today in {{CURRENTYEAR}}. Emulating games at that time required a lot of CPU and there often was simply not enough performance left for capturing said games without loosing frames in the process. Both MAME and the conventional capture systems used were prone to frameskips. This article -at that time- tried to mitigate these issues by showing an alternative capture method (albeit more complex).
 
[[Benutzer:Subarashii|subarashii]] ([[Benutzer Diskussion:Subarashii|Diskussion]]) 00:45, 24. Dez. 2022 (CET)
 
=Introduction=


== Motivation behind this guide ==
== Motivation behind this guide ==
Zeile 14: Zeile 23:


= Requirements =
= Requirements =
== Knowledge and skills ==
*Basic understanding of mame and emulation in generall
*dos navigation and writing basic batch files


== Software ==
== Software ==
Zeile 109: Zeile 124:
You will find your mng file inside the '''snap''' folder and the wave inside the '''root folder''' of your mame(where the mame exe is). The mng stream file needs to be extracted to an usable png image sequence. AdvanceCOMP will do that work for us:
You will find your mng file inside the '''snap''' folder and the wave inside the '''root folder''' of your mame(where the mame exe is). The mng stream file needs to be extracted to an usable png image sequence. AdvanceCOMP will do that work for us:


*Extract the contents of advancecomp archive into a folder. The easiest way to deal with the next commandline commands is to copy your mng and wave file into your extracted AdvanceCOMP folder.
*Extract the contents of advancecomp archive into a folder. The easiest way to deal with the next commandline commands is to copy your mng and wave file into your extracted AdvanceCOMP folder. Note: I am using a different version of Super Street Fighter 2 Turbo ind this example. Its the japanese version and is named ssf2jx instead of ssf2t.
 
[[Image:VideoEdit_AdvanceComp.png]]
[[Image:VideoEdit_AdvanceComp.png]]


Zeile 132: Zeile 148:
* If you are recording kaillera matchvideos or local ones make sure to have enough space on your hdd. Mng and the resulting png sequences tend to be very large. Their size is similar to uncompressed avi material.
* If you are recording kaillera matchvideos or local ones make sure to have enough space on your hdd. Mng and the resulting png sequences tend to be very large. Their size is similar to uncompressed avi material.


== Putting it all together ==
=== Putting it all together ===


I am not going to do any detailed introduction on virtual dub. Just the things you need to know to complete this part. Open up virtual dub and choose the '''first!''' png file of the sequence:
I am not going to do any detailed introduction on virtual dub. Just the things you need to know to complete this part. Open up virtual dub and choose the '''first!''' png file of the sequence:
Zeile 152: Zeile 168:
== Capturing with aviwrite (new & easy method) ==
== Capturing with aviwrite (new & easy method) ==


This method follows a different new approach. Newer mame versions support a avi writing method to ease up things. Please take a look at these two sections before you read on. They explain the commandline structure and how to write own batch scripts for recording.
:[[Mame_Video_Capturing#Explanation_in_detail:]]
:[[Mame_Video_Capturing#Writing_your_own_batch_file_and_recording]]


= Postproduction =
Instead of using this line([[Mame_Video_Capturing#Introduction: | from above example]):


You can do additional work like resize the video, add some filter and do other editing. Remember: Uncompressed video files are very large! Try a lossless codec like lagarith to preserve quality for further editing. Select file and then Save as AVI to save your footage.
<code>MameUI32.exe ssf2t -pb ssf2t.inp -mngwrite ssf2t.mng -wavwrite ssf2t.wav</code>


If your framerate was 60 you are done. This is probably what you wanted in the first place Sit back and enjoy your crisp, fluid 60fps video footage. If your framerate was odd ( like 59.634 for CPS2 games ) then adjust it to match 60fps. Trust me you will not notice the difference between 59.634 and 60.
you have to change it into:


<code>MameUI32.exe ssf2t -pb ssf2t.inp -aviwrite ssf2t.avi</code>


Contact, credits and final notes
The resulting file will be saved in your snap folder. It wil contain sound so there is no need to write a wave file inside the command line. This method is very easy to use.


If you have further questions or suggestions feel free to contact me:
= Postproduction =
via MSN schwarzpantsu at hotmail.com
via MIRC (quakenet) #hardedge
via www.hardedge.org forums (subarashii)
via www.cyberfanatix.com forums (schwarzpantsu)


You can do additional work like resize the video, add some filter and do other editing. Remember: Uncompressed video files are very large! Try a lossless codec like lagarith to preserve quality for further editing. Select file and then Save as AVI to save your footage.


 
If your framerate was 60 you are done. This is probably what you wanted in the first place Sit back and enjoy your crisp, fluid 60fps video footage. If your framerate was odd ( like 59.634 for CPS2 games ) then adjust it to match 60fps. Trust me you will not notice the difference between 59.634 and 60.
 
Copyright (c) subarashii 2008