Ok so I'd like to get to the point I'm looking for.
Are AviSynth encoders going to use this function in their future YouTube encodes? Of course, it will depend on the game and its flickers. I won't use it on Metal Slug 4 for example.
function TASBlend(clip c) {
#Thanks to creaothceann for this function!
Interleave(Layer(SelectEvery(c, 4, 0), SelectEvery(c, 4, 1), level=int(round((2.0 / 3) * 257))),
\ Layer(SelectEvery(c, 4, 2), SelectEvery(c, 4, 3), level=int(round((1.0 / 3) * 257))))
}
(In case you missed it, creaothceann, I had to correct some things in it.)
I'd like to encode this, but I've tried in v0.0.3.03 and v0.0.5.01 and...
That black stuff appears frequently during this stage.
I've looked in the options, and I'm not sure if something would solve this issue. Is there a way to cover this black thing? If not, then I guess I'll encode this leaving that black thing.
Of course, your original point has been proven. I still wonder what happened with my video, though. It seemed to have its vertical resolution cut in half.
Your video was uploaded on March 2nd, 2011. Maybe YouTube has improved since then.
This is another reason why I asked, "Are you sure YT quality is great?" YouTube has been known to cut the vertical resolution in half, and then up scaling it again, effectively losing 50% of the vertical resolution.
I don't think so, my friend.
I did a test. I've made this 1920x1080 picture (look closely), and I shoved it in a short uncompressed AVI file.
The results are here. If you have a 1080p monitor/TV, set this video to 1080p and look closely. I can distinguish all the black lines from the pink ones. If you were right, I would've seen a single color. Am I right?
I see your lines, but the color is completely wrong after the YouTube transcode.
Well... COMPLETELY is too much. It's still pink, right?
But it still proves my point. YouTube doesn't cut the vertical resolution in half.
I'm looking forward to seeing Google+ being released to the public. But so far, it lacks three things Facebook has that I like.
First of all, I like to have the full version of my avatar as the profile picture. So far, Google+ won't let me do that, restricting my picture to square.
Second and third, it would be fun if Google+ had something like fan pages and groups. But I guess they will come up later.
Other than that, it's pretty much Facebook, but with an easier way to manage friends.
Looks a lot better than I expected. Though, it would be nice to have another example that uses a bit more scrolling at higher speeds.
I'll make one on Sonic Advance 2 then.
Here it is. I've picked a stage full of flicker and colors.
Aktan wrote:
This is another reason why I asked, "Are you sure YT quality is great?" YouTube has been known to cut the vertical resolution in half, and then up scaling it again, effectively losing 50% of the vertical resolution.
I don't think so, my friend.
I did a test. I've made this 1920x1080 picture (look closely), and I shoved it in a short uncompressed AVI file.
The results are here. If you have a 1080p monitor/TV, set this video to 1080p and look closely. I can distinguish all the black lines from the pink ones. If you were right, I would've seen a single color. Am I right?
A quick question - all of this seems to be based on the fact that youtube... sucks. Seriously, seriously, sucks.
It doesn't suck. It just lacks 60 fps. It's probably the only site (this, and Archive) that supports 4K resolution and 3D playback options (useful for Virtual Boy movies). Plus, a lot of users don't have a time limit!
It just needs 60 fps support.
I agree with you about the nearest neighbor scaling, but no streaming site supports it yet.
For 1080p, it doesn't look THAT bad. I think I've seen worse.
A quick question - all of this seems to be based on the fact that youtube... sucks. Seriously, seriously, sucks.
It doesn't suck. It just lacks 60 fps. It's probably the only site (this, and Archive) that supports 4K resolution and 3D playback options (useful for Virtual Boy movies). Plus, a lot of users don't have a time limit!
It just needs 60 fps support.
Agreed! I love the first one. This should be tested with some Megaman X flicker too.
Take a look at this.
So yeah, I've applied the TASBlend function on Mega Man X. Again, it looks good.
The AVS script for this clip is here.
I've also tested this function on a recent game. More specifically, the PC version of Super Street Fighter IV Arcade Edition. It was captured at 60 fps using Fraps, lossless enabled. Sadly, TASBlend doesn't do much on this game, so it's not worth uploading.
Dada wrote:
Looks a lot better than I expected. Though, it would be nice to have another example that uses a bit more scrolling at higher speeds.
I remember playing this on some kind of Sonic compilation game.
I'm seeing some people voting No because it's an ear rape. I don't think this is a reason to reject this movie. Y'know, there's a movie that got published that sounds louder and uglier than this.
This run reminds me of [1813] NES The Bugs Bunny Crazy Castle by Brandon in 40:50.61. I voted Meh on this one, because it showed effort, but I found it boring to watch.
Flicky looks a lot like that game, but you can jump, and you have to get to a certain point to make what you've collected count.
I find this as boring as Brandon's run. I would have voted Meh again, but I've seen this doesn't break each level's unassisted record. For this, I have to vote No.
Sorry.
So yeah. I've encoded the same Super Metroid clip I've used for my other tests, using both frame blending techniques mentionned.
33% + 66%, 66% + 33%33% + 66%, 50% + 50%, 66% + 33%, 50% + 50%
If one of them is going to be adopted in the official encoding rules, I'll take creaothceann's function, and make an AviSynth function called "TASBlend", requiring only a clip, so we can use it as easily as clip.TASBlend().
EDIT: I personally like the first frame blending method. What do you think?
You won my Yes vote on Athena's fight, .. and after seeing Blue Mary humiliating Rugal in the end... voting Strong Yes here \o/ (was that a spoiler?) x_x'
Mister Epic wrote:
Sorry, but an usual combo video is more impressive than your TAS, and it's not even a TAS.
No vote.
Sorry, but this usual combo video was very much less impressive than this TAS, it uses unrelated background music, and it doesn't even fight against CPU.
But the combos are better. If x2poet did at least these kind of combos in a real fighting situation, I would have voted yes. But sadly, his combos were smaller and less impressive to watch.
By the way, I wouldn't be able to do better. I've tried TASing a fighting game, and it's hard.
And also, the music doesn't count.
It may be possible to TAS Flash games using Hourglass.
There's a website (www.swf-to-exe.com) that converts an SWF file into an EXE file. You upload an SWF you ripped from a Flash games website, and then it creates a standalone executable file that doesn't require Flash Player to be installed.
Here's an example I did with Alien Hominid: http://www.mediafire.com/?od5joax7gty0ypb
Do you think such executables are compatible with Hourglass?
How about we get rid of expressions such as "SD", "HD", "Standard", "Primary", "Native" and "#X" and simply label them according to the website it's meant for? Like an "Archive.org encode", a "Download encode", a "YouTube encode", etc.
That is nearly exactly what people were using... before they realized they could save a lot of keystrokes by referring to them as 512kb, HD and SD, respectively.
You mean there are people who are too lazy to type "YouTube", or even "youtube", instead of "HD"?
----
Also, I got an idea for HD encodes. I think it should be the encoder's choice to encode in HD or not for YouTube and Dailymotion. Is HD encoding something an encoder must make for streaming sites that support it?
Which is exactly why "SD" is a bad term for a video which uses the resolution of the original console. In TV technology "SD", or "standard resolution", is 576 scanlines in PAL systems and 480 scanlines in NTSC systems, which is certainly significantly higher than the typical vertical resolution of old consoles, which were typically at most 240 pixel lines (usually less than that).
"SD", if talking about an NTSC game, would imply a resolution of 640x480 pixels (for a 4:3 aspect ratio video). However, in this context it's really referring to the native resolution of the console, which is typically something like 256x192 or the like.
I wasn't talking about "Standard" as "SD". I was talking about "TASVideos' Standard". You know what I mean?
"Standard" seems to be a pretty good word for which people are used to, right? How about we use this? Just take off "Definition" from "SD".
Some people might be used to "standard" when talking about TV. It really doesn't give the same impression when talking about video game footage resolution as "native" or "original" do.
But video games are mostly shown on a TV. Anyway... I got what is probably a better idea.
How about we get rid of expressions such as "SD", "HD", "Standard", "Primary", "Native" and "#X" and simply label them according to the website it's meant for? Like an "Archive.org encode", a "Download encode", a "YouTube encode", etc.
That black stuff appears frequently during this stage.
I've looked in the options, and I'm not sure if something would solve this issue. Is there a way to cover this black thing? If not, then I guess I'll encode this leaving that black thing.
