There is an easier one:
The third and fourth terms combined are greater than 1/4+1/4=1/2
The next four terms combined are greater than 1/8+1/8+1/8+1/8=1/2
The next 8 terms combined...
so the series
1/1+1/2+1/3+1/4+1/5+1/6+1/7+1/8+1/9+...
is greater than
1/1+1/2+1/4+1/4+1/8+1/8+1/8+1/8+1/16+...
which can be rearranged as
1+1/2+2*1/4+4*1/8+8*1/16+16*1/32+32*1/64+...
which simplifies to 1+1/2+1/2+1/2+1/2+1/2+1/2+...
which is divergent, and a positive series that is larger than a divergent positive series is itself divergent.
TASes should be made with a clean ROM, with no scene intros or anything like that; I hope the WIP can be edited to remove just the input that was used to banish the intro.
(Btw, why do you insist in using "o" instead of "B"? You are the only person I have ever seen using that, and it's really confusing. It seems to be confusing even for yourself, given your "definition" of "o". What's wrong with "kB"?)
I'm honestly surprised that you don't use "o"; then again maybe it's only common where Romance languages are spoken.
Everything is calculated between frames, it's like this for most systems:
render frame, update internal state
make calculations based on current state and input
render frame, update internal state
make calculations...
I'm not sure what parts of the Internet sixofour frequents (maybe porn-sharing forums where split RARs are popular), but I see zips all the time (7zip is less common, and bz2 is mostly for Linux apps).
I'm getting the increasing impression from this and other threads that sixofour is an idiot and/or a troll.
arukAdo wrote:
Ah and yeah its all in ko.. doesnt matter ... but for the record 8 byte = 1 octect
^^Yeah, isn't it scary? Nintendo is allowing a game that mocks the sensibilities of Christianity to be released.
Still I thout that "God" and "Death" would be too abstract to do anything in the game.
IMO the first thing we'll see on GameFAQs after the leak is a complete glossary of this game, produced by disassembling the ROM; it will probably be the largest text file on GameFAQs.
That's not the point.
The point is that there are no free software RAR compressors. It's an industrial secret. Your data is held ransom by a company.
That's what proprietary means.
I should mention that Alexander and Eugene Roshal (RAR means Roshal ARchive) are a bit more generous than the worst-case scenario, like they allow WinRAR to be used by individuals (as opposed to corporations, governments, or nonprofits) for free as fully-functional, non-time-limited trialware, and for Windows you even get a GUI, and there actually is a free-software RAR de-compressor: http://en.wikipedia.org/wiki/Unrar
The free and open-source Unrar is not as feature rich as the license-encumbered UnRAR being offered by the Roshals' RARLAB, but even though you get to use or distribute UnRAR for free and can even access the source code, you are not free to do modify the source code, so it is not free.
I think the ultimate worry is what happens when the Roshals stop being so nice, charge people in order to use WinRAR, and close up the UnRAR tool and make proprietary extensions to RAR so the old free tools don't work with newer RAR files? RARLAB is perfectly within its rights to do that, and the developers of the free Unrar would only be able to get around that by clean-room reverse-engineering the new format and defending in court that they did not look at any Roshal source code, which is apparently so hard to do that they didn't even reverse-engineer the current RAR3 format!
In conclusion: Relying on an automated process like NesVideoAgent to open RARs is a bad idea because of the potential for vendor lock-in.
Also, because the command-line versions of RAR for non-Windows systems are not free, I don't believe they can legally be operated from open-source frontends (unlike typical GNU command-line utilities for which free GUI frontends exist, like gparted for parted or gmplayer for mplayer).
I tried to upload the "yellow" version of my test encode, in which I replaced "blue" with "yellow" in the Lua script, but I guess I need to learn how to encode for YouTube because it currently looks terrible.
The un-encoded AVI can be found here: http://www.mediafire.com/file/ziz2drhm2oo/SITD.avi