I used something called lsnes-sdl.exe.
It probably has VSync enabled, which synchronize the fps to the refresh rate of your monitor, which is most likely 60 hz.
Is there any way to make it run faster? Snes9x blazes along (900 fps). The fastest speed I've seen in lsnes is 60 fps. I've tried setting the speed to turbo and infinite with no significant change in speed.
The only thing I had to sync it was program the bot to skip 1 frame ahead, which I guess All-Stars wasn't so picky about.
I've successfully verified KFCMARIO's Lost Levels run!
My initial attempts were met with failure because the audio would gradually go out of sync with the video. Initially I thought that this was because the simulated gameboy did not use exactly 60 fps as its framerate, so I tried various other plausible framerates. Eventually I found to my surprise that there is no constant framerate which could work.
How are Gameboy TAS encodes rendered?
This would of course do automatic frame dropping and duplication to make everything stay in sync.
Btw, haven't heard of any complaints about desyncs and the disk swap feature, so I'm kinda surprised that dolphin is more stable than another emulator which emulates an even older console.
I've considered this, but I'm not sure how to tell when the GBA is polling for input.
This movie needs at least one tag, for Genre, which should be Platform, right? Currently, there are none, which is never supposed to happen.
Looks like it'll sync fine if you add in a few more frames at the game select screen.
The reason for PS2 games not being allowed on the site yet is that PCSX2 is far from ready for TASing, the build used for TASes by the Japanese is quite bad, I guess they just have inhuman patience.
You mean the VI's in the image? Is it because the frame dump only dumps frames where the VI increases?
Is it possible to have the lost levels run sync on the normal Mario All-Stars rom? And would it still be a valid verification if done on the normal version of All-Stars rom?
In particular, when I try to use the FreeDos floppy .img file, it defaults to 1 Side, 63 Sectors, and "Unsatisfiable" Tracks.
I might try to take on the SNES as well by seeing if I can get an lsnes movie to playback on a real SNES. Has anyone actually tried that yet?
Is it possible/allowed to use a rewriteable cartridge for this? That'll make testing much cheaper.
I have put some considerable time into trying to get Lynx to behave but my results so far have been a complete failure. Can someone, anyone, please look at these movie files and tell me what the heck is going on? If someone could please take a look, I'd appreciate it. I'm running Mednafen Rerecording 1.1 Frontend 1.0 on Windows 7. Thanks for any thoughts you have
My build does not put sound and video together. As for being picky about adding/dropping frames, it just seems like a lazy way of fixing the issue to me. It would make sense to me for each frame to be accounted for equally.
RachelB gave me the build I am using, but I'm fairly certain it does not have the AVhack. My next question is what would be the advantage of the AVhack if it is adding and deleting frames all willy nilly? Wouldn't that cause inconsistency from what the AVI file should be?
I checked in VirtualDub how many frames both of my AVIs took for minimizing VIs vs minimizing frames. You were correct Ilari, that minimizing VIs is faster although it results in a higher frame count in Dolphin (but you established that as incorrect).
For almost all cases, there seems to be 2 frames per VI, at least for non-loading. The frame counter increments during load screens, but VIs stop. Counting the frames seems like the most reliable timing method, since it includes loading time. Logic tells me that lower frame #s = shorter AVI. I will do an encode later today comparing both the less VIs vs less frames. However, it may just be a labeling error from the developers. Notice how on the left, VIs is about 1/2 of the frames, but on the right VPS is double FPS. I just assumed the left was correct, since VIs pause during loading. Ilari saying that the VI counter should go up during loading sounds incorrect to me, but I could be wrong.
I would think the obvious answer would be to minimize the frame count, but TASvideos uses the number of VIs to determine the movie length. I submitted a dtm to the new WIP section, and it displays the VIs as the # of frames.