Actually, H.263 is a low bitrate video standard designed for video conferencing and the like, and isn't even part of the MPEG standard.
Also, if people use an "older version of VLC", then they have MKV support. It's slightly broken (something to do with seeking), but I don't think it's even been fixed in recent versions anyway (or maybe it has; I haven't bothered checking).
Warp wrote:
While we are at it, many people still have trouble playing any h264 material, so for them we should also offer a regular old mpeg4-encoded alternative. Preferably in a WMV file so that Windows Media Player will be directly able to show it without problems.
Windows Media Video is its own (proprietary) codec, as is Windows Media Audio.
As noted in the "recent encodings and VLC" thread, there isn't always a player available that can handle recent encodings. Is it reasonable to expect all of our Mac users to upgrade their operating systems just so they can use a newer version of VLC?
Well, we expect them to be able to decode H.264 video. What exactly would they use for that?
He COULD just try to beat the current published one. It's almost guaranteed that he's going to need all the tricks in the book (and maybe some new ones) to be any faster anyway.
Unless there's a way for mupen64 Re-Record to somehow directly access x264, which I'm trying to find out, then I would have to use something else (hence XviD)
Use the VfW version. It's not as efficient in encoding (meaning larger bitrates for the same quality), but it should work.
A full "zero fill" of zeros then ones renders all but the absolute best forensics tools unable to recover data. DoD specs specify at least 17 passes IIRC.
Also, Derakon is talking about how a 0 might actually be 0.3 if it was previously a 1 and 0.0 if it was always a 0.
Fact: If we do just go on without the reset, MupenPlus will come out like a week after we finish the run.
Fact: As much as you may deny it, if someone submitted a near-identical run which used a reset instead of a deathwarp, it would be published, which is a huge slap in the face.
If the movie is already done, then not submitting it would be a waste of work. You might as well throw your own pizza away because you know someone else's pizza will taste better if/when it's done.
I made a test encoding using Glide64, and it looks nearly perfect. The menus are the only problem visual that I can see.
http://glasnost.us/~ccfreak2k/papermario-glide64.avi
Replace "avi" with "mkv".
Since that seems to be solved, is there anything stopping a run now?
Hey, that gives me an idea. If the "DS" is visible, you could show the input on it, too. So when A is being pressed in the movie, the A on the DS would be pressed as well. And so on. It would probably be a bitch to implement, though. But it would make the movie extra 1337. :)
That's actually similar to the idea I wrote in the DS group some time ago. I like and fully endorse your idea. :)
I dunno. Some emulators (like the iPhone NES emulator) do this and I always found it kinda cheesy and distracting.
Reviving the thread for technical updates. I've been screwing around with different plugins, and here's some preliminary results:
Glide64 'Napalm' Public Release 1.0: Menu objects are corrupted while spinning as they always have been, and there's very small (sub-pixel) seams between polygons, but there's no flickering issue, and even Bowser's star rod transformation seems to be accurate from my recollection. I'm going to test it some more with/without the "official" wrapper (zeckensack's glide wrapper would be used instead). So far, this seems to be the best candidate in terms of graphical accuracy.
Aristotle's Mudlord & Rice Video: Graphics are nearly perfect, but something hangs at the transition between the "zoom in" part of when the castle is risen and when Peach/Mario stop running around. OpenGL renderer gets past this, but the dark scene following it has dark characters/flickering. Still testing this one.
glN64 v0.4.1: Flickering seen, so I rejected it.
As for mupen64plus: getting the last SVN revision to compile and run has been an exercise in pain. I did manage to get it to compile, but it crashed when loading Paper Mario, presumably because it did not have valid sound or RSP plugins loaded, and compiling the plugins is a continuation of said pain. It seems they have put off Windows compatibility for now. The best bet is to patch 1.3, as AFAIK it should compile in Windows (it even has an official release of sorts). Maybe someone can port the mupen64-rr patch to it.
1) How much better is H.264 compared to WMV9? (Specifically for 59.94fps game footage, some of which was captured from emu and some of which was captured from consoles via S-Video at high color resolution.)
Probably as better as it is with DivX or a comparable MPEG4 codec. Note, however, that Windows Media Video is proprietary, and decoding support on platforms other than Windows is hacky at best.
2) Is there anything wrong with using a GUI H.264 encoder like VirtualDub rather than the command-line stuff written in your guide?
VirtualDub doesn't properly support B-frames (and neither does the VFW version of x264, really), so quality will be lower at the same bitrate, although I'm not sure by how much. If you really want a GUI, give MeGUI a whirl.
3) Is H.264 fully supported by WMP yet? If not, should i try to use MPEG-4 instead? It's almost the same thing right?
Windows Media Player uses VFW codecs, so as long as you have a decoder for H.264 (MainConcept or ffmpeg both work), they should work fine. Also, H.264 is technically identical to MPEG-4/AVC.
This is driving me crazy. Why is it so impossible to find a decent balance between quality, compatibility, and ease of use?
Encoding is easy once you have everything set up correctly.
1. Nitsuja's run used both Sonic and Tails, which gives a lot more options than Sonic alone.
Controlling two characters is also usually more entertaining (and faster, depending on the game). This a good reason why the old run SHOULD have been obsoleted.
On the topic of "one track" runs, there is a category for "single track" movies. Perhaps the removal of this category will eliminate such movies from tasvideos.
I'm not sure how, but publication got screwed up. The torrent file is added, but I am unable to download it from the movie page, and the tracker is not accepting it.
However, I will admit that they should not be representative of TASVideos in general. They wouldn't be my first choice as a representative movie to show people new to the site.
That is not valid C89/C99/C++.
main must return an int.
I'd've sworn otherwise, I rather habitually void main for trivial programs.
edit: I suppose it's probably not standards-compliant though.
Current standards for both C and C++ both explicitly state that main() must be int, although most compilers will only warn if main() is some other type. The reasoning is that the caller expects an int to be returned that it can interpret as an error code.
EDIT: Here's something to ponder: http://homepages.tesco.net/J.deBoynePollard/FGA/legality-of-void-main.html
You'll get screened going out because we don't want you bringing on things that could allow you to crash or, worse, control a plane and use it as a giant missile. By "we" I mean "the guv'ment". There's no point in screening you going out because you could just get whatever you needed on the street.
Ah, makes sense.
(I presume you meant "coming in" in the last sentence.)
I meant it as "going out of the airplane/airport", i.e. the paradigm of the airport.
Prepare to have the most unpleasant trip through security on your way back.
Wouldn't the most mad events take place when arriving, not when leaving? One wouldn't think that they'd be more concerned about terrorists coming to the country than of terrorists leaving the country :) Not to imply that I were one. Which I'm not. A terrorist, that is. :)*
*) Counter-false lie? Ref. many comedy routines…
I'm gonna take the bait here (since I can't tell if you're joking or not).
You'll get screened going out because we don't want you bringing on things that could allow you to crash or, worse, control a plane and use it as a giant missile. By "we" I mean "the guv'ment". There's no point in screening you going out because you could just get whatever you needed on the street.
