This is a very minor issue, but the term "movie file" has always bothered me, because it sounds a bit misleading. AFAIK, the term itself comes from the very first emulators that existed (or one of the very first) to refer to the file that records timed controller button presses and can be used to replicate gameplay, and the term has stuck ever since.
I understand that after over 10 years the term is pretty much de facto "standardized", but it still nevertheless bothers me how misleading it sounds. The problem is that to me it sounds confusingly similar to "video file", which is generally understood to be a file containing video material (eg. in mpeg format). Of course the terms are different, but to the average person they may sound interchangeable.
These keypress files are not video files, obviously. Calling them "movie files", however, may confusingly sound like they are. This may happen when the term is used eg. in events like the GDQ events, or other shows, and it may cause misunderstandings for the casual viewer.
I think "keypress file", which I have been using here, is a much better term. It's much more accurate, and causes a lot less potential confusion. It gives a much better picture of what kind of file it is. Of course it's not the only option. Maybe "button press file", or "controller input file", or something along the lines.
Just throwing some ideas out there.
Joined: 4/21/2004
Posts: 3517
Location: Stockholm, Sweden
I honestly haven't heard a single person complaining about this other than you. Has it really bothered you that much? And others? In my book, this really is a low priority, if any at all. Why fix when something is not broken? Movie file is just fine. I really have a hard time seeing anyone being bothered by this.
It confused me way back when, but only briefly (this was on SNES9x super old version). I realized quickly that the AVI recording was what I wanted to record the video.
The term input file also exists and is reasonably common. Some newbies do seem to struggle with the distinction between movie files and encodes. I'm not sure if a change in nomenclature is going to help this.
I actually agree that, to outside non-TAS audiences, the term 'movie file' may be misleading. However, your term, 'keypress file' is also misleading, particularly in formats where there are more than keys to be pressed. Is there a separate 'mouse file' or a 'button file' or a 'C-stick file'?
If changing the term becomes a higher priority to this, and other TAS-related communities, I would throw my support behind "input file" or "input-and-timing file". Or, as is the case with some games "playback file".
I am still the wizard that did it.
"On my business card, I am a corporate president. In my mind, I am a game developer. But in my heart, I am a gamer." -- Satoru Iwata
<scrimpy> at least I now know where every map, energy and save room in this game is
Joined: 4/17/2010
Posts: 11492
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
We had severe problems when we tried to adapt the terminology to Russian, starting with my Wikipedia article created back in 2010.
The word movie doesn't translate to Russian well, and it by no means is comprehended as a file. I now have a word that would work way better, it's the word "Replay". That word would be unique and have no mental noise coming from its other meanings. But that is only an issue in Russian. I don't think I know what is problematic about it in English, but I haven't yet read the thread.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
A movie file can contain much more than keypresses: reset button presses, savestates (comparable to keyframes in video files), author info, comments... Theoretically you could even include instructions for controlling the whole interface, including loading ROMs, connecting controllers etc.
That doesn't mean that the term should remain misleading. In vernacular, "movie" and "video" mean pretty much the same thing. Neither of them convey the notion that the file contains timed controller input data; on the contrary, "movie" easily conveys something that the file is definitely not (ie. a video capture of the game).
Even if "keypress file" (or "button press file", or "controller input file") might not be all-encompassing, at least it's significantly more descriptive, accurate and less misleading.
There is enough confusion among the casual spectator about how TASes work. We don't need to add anything more to it by using confusing terminology.
i like the "playback file" option as submitions are basicaly files that hold all the informations so it can play back a run the way it's author intended"
simple and clear
Moderator, Senior Ambassador, Experienced player
(907)
Joined: 9/14/2008
Posts: 1014
I'm fine with using different verbiage on-screen at GDQ events. I'd probably lean toward "TAS replay file" or something similarly specific. Movie file may be what we've called it forever but I can agree that it definitely confuses newcomers and those unfamiliar with this domain. Inside of TASVideos, however, I have no good reason to actively change everything over to different terminology.
I've been using the phrase "input file" lately, since outside of the metadata (which contains header and platform and sync settings and whatnot) it's just a record of the inputs. If you unzip a bk2 file, the fun stuff is in the "Input Log," so it makes sense to me to call it an input file. It's still a record of recorded inputs though.
playback or input file seems a nice way to name it,but i also don't find it a very relevant issue
I want all good TAS inside TASvideos, it's my motto.
TAS i'm interested:
Megaman series, specially the RPGs! Where is the mmbn1 all chips TAS we deserve? Where is the Command Mission TAS?
i'm slowly moving away from TASing fighting games for speed, maybe it's time to start finding some entertainment value in TASing.
But on the other hand, I don't think there is any harm in gradually phasing the usage. If people just start saying eg. "input file", that usage will start getting more popular.
As said, the reason to do this is to avoid needless confusion among new users.
"Input file" is my favoured term, I think. Sometimes I use "recording" which is very neutral and generic, which makes it not-ideal (it isn't inaccurate but it also isn't very descriptive).
I've also worked on a rerecording framework which uses the term "log" internally to describe the file in question, but that wasn't my choice and may just have been chosen to be short (I use "recording" in the UI).
Replay file works, since while I can't remember where I read it from, there was a "movie file" for some types of games (not accepted in this site) that saved internal game values rather than solely input.
I typically refer to it as input file or key input file in other communities as well. If at some point the site administration decides to make a move on this matter, I would support it and suggest "input file" as, at the same time, the most descriptive and the least controversial name.
http://www.youtube.com/Noxxa
<dwangoAC> This is a TAS (...). Not suitable for all audiences. May cause undesirable side-effects. May contain emulator abuse. Emulator may be abusive. This product contains glitches known to the state of California to cause egg defects.
<Masterjun> I'm just a guy arranging bits in a sequence which could potentially amuse other people looking at these bits
<adelikat> In Oregon Trail, I sacrificed my own family to save time. In Star trek, I killed helpless comrades in escape pods to save time. Here, I kill my allies to save time. I think I need help.