Looks very clean. 60 fps effect on YouTube ftw. ;-)
Did you use any additional filters (maybe new deinterlacers or other stuff to smooth the picture even more) besides the "Weave" feature to merge 2 frames to 1? I wonder because your video seems to look a bit different on YouTube than mine.
True, but this requires additional effort on my part.
Apart from what seemed like interlacing artifacts (could be a playback problem on my end), the video was entertaining and I enjoyed most of the music. Nice job :)
Sounds like EmuDX: http://en.wikipedia.org/wiki/EmuDX
I had this same exact idea I presented on here a while back. Mine was to have packs for the emulator which were specific to the games. They could contain graphics, sound, and when and what to replace.
This has been discussed before on the ZSNES board as well. It's possible, but not very feasible. Very game specific. Will probably never happen to more than one or two games someone might do out of spite to show everyone it can be done.
This idea has been brought up on several boards that I've gone to in the past. I even went so far as to dummy up a joke "XTREME" version of a NES emu I was working on to sort of poke fun at the idea. I really don't like this idea at all. It could definately be done. It's not even that it would be hard (in fact, unless I'm mistaken, older versions of some emus did something similar by using "graphics packs" for some games which uses compression schemes which had not yet been cracked). It's just that this fundamentally goes against what emulation is: the recreation of the behavior of a system through software. Not to mention it would clash and look poorly on older systems (like NES). NES's megaman's graphics and animation style compliment each other. And SNES Megaman X's graphics and animation style compliment each other. Ripping one away from the other and mixing them up would look really crappy and awkward. Imagine MMX graphics with MM's 3 frame walking animation -- it would look stupid. Also -- on older systems this could comprimise emulation accuracy. NES games rely on some raster effects that involve pixel placement (sprite 0 hit). Failure to emulate the normal rastering process means PPU flags will not be raised (or will be raised at the wrong time).
The emulator would not touch the game itself in any way, and would still emulate the game exactly in the same way as always. The only difference is that when the game tells the "hardware" (which is emulated by the emulator) to draw a certain tile or sprite, the emulator instead draws the enhanced version of that tile/sprite graphic on screen. This will not affect the game itself in any way, only how it looks to the user.
Courtesy aside, even if it is free distribution, it's still an act of redistribution, which most primary creators hold all rights to. Sure, if someone didn't want their work on YouTube, they could ask that it be taken down: however, what are the odds that said person is going to be expecting their run to be online/go looking for it? It seems, to me, that the person wanting to post the run online should approach the person for their permission, rather than posting it and expecting that the author will find out/contact them if they want it removed.
And don't edit the avis.
You have to have the permission of the original author of the runs before you can host them.
YouTube drawns in all the wrong sorts
Because a game is in a different language, it's instantly a completely different game? To be blunt, I find that idea completely absurd.
file header:
- Signature (8 chars)
- Colon (1 char )
- Version (4 chars)
- Delimiter (1 char )block structure:
- Name (3 chars )
- Colon1 (1 char )
- Size (6 chars )
- Colon2 (1 char )
- Data ([Size] bytes)"NAM" (cartridge name)
"CPU" (CPU status)
"REG" (CPU registers)
"PPU" (PPU status, basically registers $2100+ with some modifications)
"DMA" (DMA registers)
"VRA" (VRAM)
"RAM" (WRAM)
"SRA" (SRAM, always $20000 bytes)
"FIL" (FillRAM, 32 KB storing the last values of the registers $xx:0000..$xx:7FFF, regardless if mapped or not)
"APU" (APU status, optional)
"ARE" (only if "APU" is present: APU registers)
"ARA" (only if "APU" is present: APU RAM)
"SOU" (only if "APU" is present: other sound data)
"SA1" (SA-1 status, optional)
"SAR" (only if "SA1" is present: SA-1 registers)
"SP7" (SPC7110 status)
"RTC" (S7RTC status)