Someone declared the special encode on YouTube "Content Made For Kids", which seems to have disabled the ability to add it to a playlist.
PS: Nevermind, I bypassed it.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Not a big deal, but it is a bit strange that the description of this movie showcases the Burst Chaser x Air Sliding movie that this very movie obsoletes.
Like, was it obsoleted or not? :P
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Someone went back in time to 0000 in Unix Time(Maybe their time machine only accept Time Coordinates in Unix Time). And reposted all the TASs in order.
New Movies
Recent movies published:
RSS Feed
1970-01-01
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
I like that there's a second slower YT video encode just in case the use can't access YT's speed controls or YT decides to delete that feature.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
I'm sure there was probably a modem accessory for the PSX, but do you really need to specify that the multiplayer was "offline"?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Does this TAS hold the record for fastest time between game release and TAS publication?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Publication for new run's description points to an obsoleted run of Hero's Quest. There is a newer run of Hero's Quest at http://tasvideos.org/3639M.html .
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Thank God this game supported widescreen for all five of the people who owned widescreen capable displays with video input.
And thank you to the Encoder who went through the trouble of making a separate encode.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Will I get banned if I post an encode that is banned in the thread for a movie(or another thread)?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Do you know who does NDS encodes? Still one of the few systems capable of high res emulation that we don't have high res encodes for.
Yeah, that's banned cause the HiRes is complete garbage since it can't get certain effects working.
TL;DR: feos placed it in 3 publications (2015) ,adelikat caught wind of it. Not allowed.
(Same reason for the PSXjin version of this, which is even worse since it does incorrect transparency.)Encoders Corner is a great place to check if you're going to ask questions like that.
Special case here since a new topic was made recently which was then pointed to the post that said it became banned.
"I removed the post"
Wow, you guys literally banned it. Well...I gotta go see a man about a horse...I guess.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
So, the "Native" one is somewhere near 320x240, and the other encode is just a full screen filter/upscale of that?
You're correct in regards to this game's native resolution (which is 320x240) but no, the other encodes are not upscales.
xnamkcor wrote:
No Encode at a higher resolution?
There are several available in my previous post at 480p, 720p and 1080p respectively. This is in addition to both the regular and brightened Youtube encodes available on the publication page.
I apologize if my wording on the previous post was somewhat ambiguous. I tried to keep it straight to the point, but I'll go a bit of detail in the hope it clarifies what to expect from each encode:
After resyncing (this was an easy project, as it only required a single savestate) I dumped this movie three separate times. The first dump I did was at the game's internal resolution with graphical enhancements such as anti-aliasing and anisotropic filtering. I used this dump for the encodes on the publication page and for the standard lossless encodes.
The second dump I did was at 2880x2160 (4K, with a 4:3 aspect ratio); again with graphical enhancements. This was used for the 4K Youtube encodes and was downscaled for each of the additional resolution encodes.
The final dump I did was at the game's internal resolution without any graphical enhancements. This was used for the native lossless encodes and is intended for viewers who'd prefer to see the run looking closer to the original hardware (albeit, not by much).
You can generally check the Youtube encode to see what kind of video to expect from the additional resolution videos. If it's clear and not upscaled, then the encoder was able to dump from the emulator at a higher resolution and likely will have used that footage for any high resolution encodes they may have made available. If it looks like it's been upscaled, then you'll likely not have any luck (it can be for any number of reasons, such as the run only syncing with certain settings or perhaps the core only outputs at that particular resolution).
Whilst I have provided upscaled additional resolution encodes (only for 2D games) in the past, when I started offering lossless encodes they took the place of any upscaled additional encodes I might provide. If I've provided lossless encodes in a post, then all additional resolutions available in that same post are rendered either at, or above, the resolution they specify.
Ah. Thank you.
I usually prefer High Res with no graphical enhancements, but that's such an odd combo anyway.
Do you know who does NDS encodes? Still one of the few systems capable of high res emulation that we don't have high res encodes for.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
So, the "Native" one is somewhere near 320x240, and the other encode is just a full screen filter/upscale of that? No Encode at a higher resolution? Does the Emulator/Plugin you use to playback this movie not support higher resolutions?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Can anyone give a quick summary of why a 22 Minute publication obsoleted an 11 Minute publication?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
The bootup in this video prevents all epileptic seizures? That's amazing.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Any chance of a camera hack? Would that break the Autoscrolling segments? Don't camera hack during those stages?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
I thought the YouTube uploads were for ease of watching, not frame by frame analysis. For that I use the archive or torrent downloads.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Spikestuff, please be sure to check your PMs regarding the encode before uploading additional versions.
Edit: Since this is already published, I'm posting here as well as I am requesting that the published encode be switched to the one I posted ( https://www.youtube.com/watch?v=0XIvYyTgGMI ). Spikestuff and I have had an on-going discussion via PM and while I appreciate the efforts he put into his encode, I disagree with the settings he used.
I chose to encode with Jabo 1.6.1 at 60fps while Spikestuff insisted on using Glide at 30fps. I disagree with this decision. I'll document some of the reasons here for your consideration. In looking at Spikestuff's encode ( https://www.youtube.com/watch?v=DvZXJByOXBo ) I noticed many situations that felt "choppy." I stepped through these areas frame by frame and confirmed that this is due to multiple missing frames. For example, if you watch Luigi Raceway starting at 10 seconds, you'll notice the timer jumps right over the following values:
10"03
10"10
10"33
10"56
10"96
11"06
11"20
11"36
11"49
11"56
11"73
12"16
12"29
12"49
13"29
...
These frames are present in my 60fps version.
https://www.youtube.com/watch?v=0XIvYyTgGMI
This is an issue that I expected with a 30fps encode and it's something that I discussed on the IRC chat with Mitjitsu and others and that I referenced in my earlier post in this thread. This happens because some frames only appear on-screen for 1/60th of a second and a 30fps may exclude these mistakenly. Spikestuff insisted that the command he used did not do this and that he had checked "every frame" of the video. I see the issue in many places in the video that has been published.
There are also many video errors when using Glide compared to the console verification movie (issues that Jabo 1.6.1 does not have). The issues include jumbotrons (black on Glide), boost ramps (incorrectly animated), flowing water (incorrectly mapped and animated), polygon exclusions (too many polygons shown on screen at times for Glide), and Peach's castle (edges of the picture shown incorrectly). These are just some examples. I know Jabo is not perfect but the issues I'm aware of are less noticeable than those of Glide.
For reference, everything I've mentioned above is available at: http://imgur.com/a/0WW0F
Console verification video for reference:
https://www.youtube.com/watch?v=TfcLIzYQSpM
I also simply prefer the Jabo features such as anti-aliasing and anisotropic filtering.
I'm requesting that the encode be switched to the one I uploaded and I'm happy to provide the downloadable versions as well. I'd like to hear others' opinions.
Is there a "widescreen hack" in an approved emulator that can read the movie file submitted? Would it affect the gameplay?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
"Compatibility" Encode hosted on archive seems to be missing the subtitles. "Modern" on archive seems to have subtitles.
Downloading them via torrent to check those too. Will use YAMB for now.
Edit: "512kb.mkv" torrent has subtitles. "512kb.mp4" from Archive does not have subtitles.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Also this archived page is broken lol .
Anyways, it appears the link was expired since 2011. At least 2 other people have asked for a backup, but it appears no one saved it. Sorry for your lose.
Are bots even programmed to read that in any meaningful way?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
http://tasvideos.org/1418M.html
I tried contacting both parties and at least one replied saying they don't even have it themselves. Does anybody have a backup of the file?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
That was really nice to watch.
Too bad the password algorithm can't hold the info of the Zero Saber independently of the 8 Mavericks defeated, since the passwords generated after obtaining it seem to be invalid. It would be great to start a run from a cracked password which gives you the Saber at beforehand, so it could be used in all 8 stages.
If I can modify the RAM to think I have the sabre, but not have any bosses defeated, then save it to the memory card, could that count as "start from save" if my changes are cromulently stored as save data?
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
Is it just me, or does it look like the wireframe Sigma model is just a sprite with scaling and rotating added? The SNES seemed to at least do maths to render geometry.
They probably didn't want to emulate the Cx4 chip (which is used for the 3D geometry effects in SNES X2 and X3) for this version.
And I guess nobody told them PSX can do 3D out of the box.
"The guy was fatally injured and wants to be covered by God's tears (rain) before he dies. God is too busy to bother because it wastes frames."
Frames 16:26
I think it's been that way for about 3 days.