It would be so nice if avi record will work exactly like in chinese Nestopia plus. Like if you apply some x3 or x4 video filter - you get avi with that filter in correct x3 or x4 resolution with all video settings / filter settings you made.
edit: for example - official Nestopia ignores filter settings, but at least made avi with correct resolution and with filter.
Fceux completely ignores filters.
This should be an option somewhere; not just hardcoded to one or the other.
The type of CPU is known simply from looking at the motherboard. Very often this is a "off-the-shelf" part from a well-known manufacturer, and not something developed exclusively for a particular console (there are exceptions though). These manufacturers publish data sheets, manuals etc. because they want system builders and programmers be able to use the CPU.
From that you can build a CPU emulator, and guess at the RAM map (i.e. which parts of the system are connected to which CPU addresses). For example the 6502 has a "zero page" in the first 256 bytes which are fast to access, a stack in the next 256 bytes, and some fixed pointers at the end of the address space. From that you can assume that there's RAM mapped at the beginning and ROM at the end of the address space.
When you manage to get the emulated CPU to run the first few bytes, you can follow the binary game code and see what it's doing. By writing test ROMs and connecting them with the real hardware you can explore the machine's behavior.
And this Bizhawk TAS is finally faster than snes9x's old TAS thanks for this skip!
Yet due to emulation differences, it's 141 frames faster ahead of published TAS!
You have to multiply the number of frames of each movie by the number of bugs in the emulator, so TASes on Bizhawk win easily every time. ;)
Neon Genesis Evangelion[Anime] - I can't really remember this series well. I only started watching it because it was said to be one of Gainax Studio's finer works. The last few episodes really lost me. Heard the movie was good but never watched it.
EoE is much better than the end of the series, imo.
...and there's also the Rebuild movies.
If you can't find these specific RAM Adresses or collections called RAM Maps online, then your only option is to search for them in the emulator itself by using the RAM Search.
How applicable can this be, considering all the CPU emulation difficulties that slow down the cores?
What difficulties?
When this question comes up, people are essentially saying that parts of the emulated system should be separated and distributed to several CPU cores. However, a CPU core works best when it can run separately from others - because it doesn't have to wait for data to arrive / wait for synchronization (the other core must finish its current task, check for waiting queries, and send its "ready!" signal). As you can see from these numbers, synchronization (mutexes) are relatively slow. If I can fit most of the system state into the L1 cache and much of the data/instruction stream into the L2 cache, I'm going to be more than 4 times faster working with L2 cache data than working with another core.
GPUs go the "separate the cores" way even further: these SMs / CUs are slower than a CPU and have less cache associated with them. This doesn't help for a console like the SNES where every part of the system can influence another part of the system at a rate of ~21MHz (every ~46.56ns).
I also provided images. Frame by frame to show why this happened on different frame rates.
Normal N64 Speed (Dupe frames, and the "missing" frame): http://imgur.com/a/d2dOB
Half the N64's Speed (Missing/Dupe frames): http://imgur.com/a/U8UYQ
True 30fps (No Missing/Dupe frames): http://imgur.com/a/asbLd
