Revision (current)
Last Updated by CloakTheLurker on 1/30/2024 11:05 AM
----
You can directly edit a movie input file. You can change things like header information, or you can change input directly. The idea is to change some input earlier in the movie without changing whatever comes after it.
Here's the catch: It doesn't always work. In fact, it usually doesn't work.
Since games are often dependent on previous input or condition, changing something in the past may cause the rest of the movie to [DesyncHelp|fail to sync]. You can correct the desyncs case by case, but often there will be many and it is too time-consuming to do.
Some movie file formats, such as [https://fceux.com/web/FM2.html|FM2], are in plain text form. You can use a text editor such as [https://github.com/notepad-plus-plus/notepad-plus-plus|Notepad++] to edit it. On the other hand, some formats, such as [EmulatorResources/VBA/VBM|VBM], are in binary form. In this case, you must use a hex editor such as [http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm|Xvi32] or a file editor e.g. [https://sourceforge.net/projects/tas-editor|TAS Movie Editor] designed for such purpose (see the [/Forum/Topics/4448|forum thread] for some information).
__You are responsible for your own movie. Make backups before editing it. Please read [DesyncHelp], as it covers necessary precautions in case something goes wrong.__
%%TOC%%
! Movie formats
Please read the proper movie format specification for the emulator you are using, under [EmulatorResources]. You may need to refer to it several times. It tells you how movie files are recorded, so you can try to edit it directly.
! When to use input editing
* Input editing can be used to copy input (say from a previous TAS) into your TAS. Input editing does not ensure that the newly modified movie [Desync Help|plays as intended]; it may or may not.
* Input editing can also be used to try to correct desyncs by adding or deleting inputs from the movie input file. This is time-consuming unfortunately.
* Input editing can even be used to insert repetitive input, although if an emulator supports it, Lua scripting is better used for this task.
Editing the movie file can be done just to change header info. This is easy to do so it will not be covered in this page.
!! Plaintext files
[https://files.tasvideos.org/1853/site_images/InputFileEditing1.png|right]
Plaintext files are files that contain plaintext, that is, text that is easy to read in a text editor. For changing input, the text editor should number lines and have the ability to jump to any desired line. Notepad++ does this.
Most plaintext movie formats begin with a header of some number of lines, followed by the first frame of input (frame 0). For example, in the image on the right, the header (not shown) is 18 lines long, and the first frame of input (frame 0) begins on line 19. Thus the current line shown (line 1929) corresponds to frame 1910 (1929-19).
In general, if you want to go to frame N, and B is the number of lines in the header, then frame N is at the following line:
N + B
To change the input, just edit it directly. Review the movie format specification as to how it works. In the image on the right, the current line shows that on frame 1910, left (L), B, and right shoulder (E) are pressed. According to [EmulatorResources/Desmume/DSM|DSM], if you wanted to change input so that the right shoulder is not pressed, change the E to a period (.) . Then, if you want to press the left shoulder instead, change the period just before where the E used to be to a W. (It can actually be changed to anything other than a space or period, but for consistency...)
To insert input, you can just copy and paste from another file. Keep track of where it begins. Also, keep track of where it ends unless you don't care about the input after that point. You must also change the movie length (in the header) to be longer. If you don't know, make it longer than normal. If it is too long, you can fix it in emulator easily. If it is too short, it won't play all the input.
An inbuilt [EmulatorResources/TASEditor|TAS Editor] tool of FCEUX is quite useful too.
!! Binary files
Binary files, on the other hand consist of a bunch of bytes not intended for human reading. When viewed in a text editor, one would only see garbage (although some plaintext might be seen if the file stores some plaintext, such as comment and author fields). To view them properly, it requires a hex editor.
Because binary files are harder to edit, and the size of plaintext is no longer a factor in this day and age (submissions are placed in ZIP files anyway), future format specifications encourage the use of full plaintext files. However, there are still binary formats for the older emulators.
! Bytes
Bytes are always displayed as a two-digit hexadecimal number. Hexadecimal numbers use base 16, unlike decimal numbers which use base 10. The digits go as follows: 0, 1, 2, ..., 9, 10=A, 11=B, 12=C, 13=D, 14=E, 15=F. The next number is the hexadecimal number 10, which is 1*16 + 0 = 16 in decimal. For example, the hexadecimal number 1234 is 1*16^3 + 2*16^2 + 3*16 + 4 = 4660 in decimal. Hexadecimal numbers with 2 or more digits are usually prefixed with 0x to avoid confusion.
Any number of bytes can represent anything you want it to represent. For example, a byte can represent a number from 0 to 255 (unsigned), or it can represent a number from -128 to 127 (signed), or it can represent a byte of plaintext, or it can represent input. Bytes like those that represent input are bitfields. Each byte has 8 bits and each bit represents whether something is on or off. Bitfields are easier to demonstrate in binary (base 2). A bit is either on (1) or off (0).
76543210
bit 0: 0x01
bit 1: 0x02
bit 2: 0x04
bit 3: 0x08
bit 4: 0x10
bit 5: 0x20
bit 6: 0x40
bit 7: 0x80
For example, the bitfield 01101001 means that bits 0, 3, 5, and 6 are on and bits 1, 2, 4, and 7 are off. It has the hex value 69 (0x01+0x08+0x20+0x40).
Numbers (larger than 255) that require two or more bytes to store are typically stored in little-endian format. That is, the byte order is reversed when viewed in a hex editor. For example, the byte sequence 00 AB CD 12 represents the hex number 12CDAB00 (if it represents a number at all). To avoid confusion, byte sequences are given with spaces in-between the bytes. Big-endian formats (the opposite) are used occasionally in other systems. In all movie formats, little-endian is used.
The bytes in a file are addressed starting with 0. Bytes can hold values that are used as pointers (numbers indicating the address in which something such as input begins). This is important when storing sets of information that do not have a fixed length. Unlike plaintext files, the beginning of input cannot be recognized unless it is declared.
! Binary movie formats
[https://files.tasvideos.org/1853/site_images/InputFileEditing2.png|right]
Binary movie formats begin with a header, followed by input. In most cases, the header contains a pointer to the controller (input) data, although in some cases, the beginning of input is set as some address, say, byte 0x200. For example, in [http://code.google.com/p/snes9x-rr/w/list|SMV] files, bytes 0x1C to 0x1F contain a pointer to the beginning of input. From the image on the right, 0x1C to 0x1F contains B0 00 01 00, so the beginning of input starts at byte 0x100B0.
To find out a particular frame where input is stored, we need to find out:
* where the beginning of input is, and
* how many bytes per frame.
The movie format specification should tell you how many bytes per frame, and where the pointer to the controller data is located if there is one, or the start of input if not. Remember that the first frame is frame 0. If N is the frame number, A is the number of bytes per frame, and B is the location of beginning of input, frame N is located with the following simple formula:
A*N + B
Remember that you have to convert all numbers to either decimal, or hexadecimal. You can use a calculator such as Windows Calculator to do the conversion and calculation for you. Also remember that if you are recording with two or more controllers, the bytes per frame will be different than normal.
For the image to the right, [http://code.google.com/p/snes9x-rr/w/list|SMV] says A is 2 and we know B is 0x100B0. Let's say we want to go to frame 32856. 32856=0x8058, so using the hex mode of a calculator, 2*0x8058 + 0x100B0 = 0x20160. Select {{Address -> Goto...}} and enter 20160 as the address in hexadecimal. This will result in the image below.
To change input, check the format specification carefully and then make the changes. Remember that inputs are stored as bitfields, so to toggle a button press, you need to change the corresponding bit.
In the image below, frame 32856 (address 0x20160) contains the byte sequence 00 20 (remember, since A=2, there are two bytes per frame). According to [http://code.google.com/p/snes9x-rr/w/list|SMV] (which gives it in big-endian form, as it is displayed), this means the select key (0x0020) is pressed, and that key only. To add pressing the right key to the input, change 00 20 to 00 21 (since right is 0x0001). If instead you wanted to add B, change 00 20 to 00 A0 (since B is 0x0080).
To insert input, copy and paste from another file. Check Xvi32 as it is not intuitive (you have to mark a block first, then say block copy or block paste). Keep track of where it begins. Also, keep track of where it ends unless you don't care about the input after that point. You must also change the movie length (in the header) to be longer. If you don't know, make it longer than normal. If it is too long, you can fix it in emulator easily. If it is too short, it won't play all the input. Check the specs for where the movie length is and remember that it is 4 bytes and little-endian.
[https://files.tasvideos.org/1853/site_images/InputFileEditing3.png|right]
!! Binary formats which do not have constant bytes per frame.
[http://code.google.com/p/mupen64-rr/wiki/M64|M64] is slightly different in that it ignores lagged frames. Thus the movie file counts by non-lagged inputs rather than frames. This is easy to work around as the emulator window includes the non-lagged input count.
[http://code.google.com/p/fceu/wiki/FCM|FCM] (an old binary format used by FCEU) uses a compressed form rather than a per-frame basis, which makes it very difficult to edit. You can convert it to [EmulatorResources/Famtasia/FMV|FMV] (an even older format from an obsolete emulator) using [http://bisqwit.iki.fi/source/nesmock.html|Nesmock], edit it, and convert it back.
!! Does it work?
It works if what you intended occurs when you play back in emulator. This is an issue when changing input previously in the movie.
If it doesn't work, either give up, or edit some more. Of course, you should keep the editor open until you are done. When you are finished, close the editor right away. This prevents an overwriting accident.
__Always recreate savestates that occur past where you edited the movie.__ If you don't, and you use those savestates, you will either:
* Erase all the hard work you did to edit the file, or
* End up with a wrecked movie after finding out 5 hours later.
See [DesyncHelp].
!! Case Study: SNES Mega Man X: Eliminating a missed shot
At or near frame 58090, [user:DeHackEd] discovered a missed shot while climbing the last
segment of Boomer Kuwanger's stage. The targeted enemy was destroyed in 3 hits,
but 4 shots were fired. Having already done a boss battle and started on the next
level, DeHackEd did not want to rerecord over his work to fix it, but the stray shot
still had to be eliminated.
The first step is to find where the shot is stored. Here is the header for the SMV.
It is the same as the one in the SMV format section.
53 4D 56 1A 01 00 00 00 77 77 77 77 69 29 00 00
2B B0 01 00 01 01 00 00 20 00 00 00 C3 00 00 00
1F 8B 08 00 00 00 00 00 00 03 ED C1 31 01 00 00
The controller offset is {{0xC3}} (195 bytes).
The frame number is near 58090 and there are 2 bytes per frame,
so our starting point will be {{195 + 2*58090 = 116375}} ({{0x1C697}}).
Here is some of the file's contents around that area as viewed from a hex editor.
(Hex position) (bytes)
0001C670 81 80 81 80 81 80 81 80 81 80 81 80 81 80 81 80
0001C680 81 00 81 00 81 30 81 __00 C1 00 81 00 C1 00 81 00__
0001C690 __C1 00 81 00 41__ c0 81 80 81 80 81 80 81 80 81 80
0001C6A0 81 80 80 80 81 80 82 80 82 80 82 80 82 80 82 80
Remember that each line is an even number of bytes, but our starting offset is an
odd number. The portion in bold is found to be our 7 frames consisting of shooting.
This is because firing is by having one frame pressing Fire (Y), one frame without,
one frame with Fire held, and so on. The code for Y is {{00 40}} which shows up in
alternating frames in the bolded section.
We now have our choice of which frame we want to eliminate. For simplicity, DeHackEd
eliminated the last one. Thus the movie's line
0001C690 C1 00 81 00 __4__1 c0 81 80 81 80 81 80 81 80 81 80
becomes
0001C690 C1 00 81 00 __0__1 c0 81 80 81 80 81 80 81 80 81 80
After watching the movie again to ensure the shot was eliminated and there were no
desyncs (there were not), recording resumed.