Hi, I was wondering if there's any tool to edit the .m64 files? I mean, like coping the info of one file to another?
I want to test some stuff I always wondered on F-zero X, like giving the exact same input to different cars to see how they behave. And it could be also useful to do runs of individual tracks & then just compile them in a single file...
So, the problem there's really no tool for the N64 (apart of doing it manually with a HEX editor) is that each game runs at a diferent rate so there's an issue with the frames, and that's why you can't save with the movie editor tool, correct?
Well, I'll try messing around with both a HEX editor & the movie editor. Thanks :)
So, the problem there's really no tool for the N64 (apart of doing it manually with a HEX editor) is that each game runs at a diferent rate so there's an issue with the frames, and that's why you can't save with the movie editor tool, correct?
That shouldn't be a problem for a movie editing tool. What it comes down to is one number it can't know (movie duration), which isn't used for anything else in the saving process and doesn't need to be exactly right for the movie to play. All it has to do is make a conservative guess about that number (or ask the user to make that guess) then save it like a normal movie.
In fact, if the user can correctly answer the question "what is the average frame rate during the frames you edited", there is no guesswork, that's all the information it needs. (That question should be worded differently to be technically correct, to differentiate between the terms "frame" and "input sample", but it gets the point across.)
Hex editing is sufficient. Also, this movie editor tool is advertised as supporting Mupen64 movie editing.
I haven't finished implementing M64 support because, frankly, there's been very little demand for it. The main reason I think is that since there are so many different input values to display, it just looks jumbled. I was looking for a better way of handling input in the application, but didn't end up finding anything I liked.
I guess I can finish what I started though and just implement a write routine for M64 files ... seeing as it's basically ready to go anyways.
Joined: 3/18/2006
Posts: 971
Location: Great Britain
It is very good.
BTW, I'll just say what I did:
I got desyncs where the program would delay input by +1 frame. I fixed this by clicking "reload" option and then deleting 1 frame of input in the program after I finished editing the m64.
After that everything worked fine.
I got desyncs where the program would delay input by +1 frame. I fixed this by clicking "reload" option and then deleting 1 frame of input in the program after I finished editing the m64.
After that everything worked fine.
Joined: 11/18/2006
Posts: 2426
Location: Back where I belong
I'm having major problems getting either tool to work. I understand that the TAS movie editor doesn't support saving .m64 files, so that's out. I tried Zefris' tool, and I'm getting some weird results.
I have an old movie that lasts roughly 20,000 input frames. I found I can improve a spot at around 13,000 input frames (by enough to make it worth my while), so now I have two movies. My original, with 20,000 input frames, and my new, faster movie with just under 14,000 input frames. I have opened and watched them both through with Mupen and they both work correctly, and show the correct number of frames and length of movie.
HOWEVER, when I open up my faster movie in Zefris' program (old version), it shows that I have 20,000 input frames! I've tried just erasing the "extra" frames, and hexing in what I want from the other movie, but that causes Mupen to show that the normal frames and the input frames are the same, causing playback to end waaay before it should. I don't know why my faster movie would still show 20,000 frames, since that data should now be gone from the file. Does anyone have any idea what's going on and why I'm having problems?
