I wonder how your 43GB encode is so much better than mine
No need to wonder when you can just look at it. Not that this is something to compete/find offense over.
So, how did you encode it?
My guess is with a series of 24-bit bitmaps interleaved with waveform audio. YouTube does the rest. It would be less than that, but YouTube doesn't support Lossless codecs.
"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
When asking something politely, it helps to be polite. One cannot just pretend to be polite or say so later.
"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 wonder how your 43GB encode is so much better than mine when mine is 43GB as well! How did you encode it? Maybe by dropping every other frame (to make it effectively 30fps) you succeeded to preserve twice as good quality? If so, I really can still improve mine.
PS: I don't think null frames add anything to file size anyway.
If you both have the same key frames and the only difference is some missing B frames that are redundant frames, then there would be little reason for either a full 60FPS version or a version with less than 60 FPS would be that much different in size. Especially if rounding to the nearest GB.
"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
It's comical that personal hate gets in the way of obvious proof my encode is objectively better. You people are a bunch of immature children, not to mention disrespectful to the author that gave you this potentially popular run. And Nahoc, the mods can ban me, but you can go fuck yourself. You should have nothing to do with the publishing of this run due to me being involved. You are trash and your ex-friends all think so. I don't care if this doesn't get the link changed or progresses towards it. You're a garbage human being and your actions now and in the past prove it.
Now to anyone with a fucking brain that has some power here, look at the fact that my encode is FAR superior (seriously, choppy frames AND the compression are absolutely ugly as fuck) and it's by the authors' request that it links to mine. That's all I have to say. And again, FUCK you Nahoc, you're disgusting.
We could take your encode and host it on TVC. That way we would be using an "objectively better" encode and satisfying the requirement that it be on the TVC channel.
"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
We'll be keeping the official encode on TVC. Sorry sonicpacker.
Did anyone besides the person who uploaded to YT make a hi-res "modern" 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
Look at a bunch of people who don't know what they're talking about as opposed to the maker of the run and experienced TASers? Great idea, but I think I'll pass.
Hey, homerfunky, should I watch your run?
"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
Well, the North American release of Lufia 2 is hardly a centerpiece of quality SNES programming. The game already had an abnormal amount of glitches added to its localization. Actually surprised a glitched run took so long. The Level 0 glitch had been a widely experienced glitch since it had been released in the states.
The most I would have predicted it would be used for would be an early stat boost, but the excessive time needed after each battle might have nullified that time gain.
"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
Short, Lufia 2, TAS, with commentary? What is this? My birthday?
Looks like the author is glitching into the Debug Menu's flag or scene menu.
"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
This must be the favorite TAS of all Jehova's witnesses, because of so many animations of doors being opened.
And they actually get to go inside.
"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
Now I can listen to that infernal ticking the way it was meant to be heard.
Edit: A note to people making text commentary, It's always unnerving when there are long bouts of "silence" and I start to wonder if my subtitles stopped working.
"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 there a system in place for noting what the actual "updates" were?
Yeah, the maintenance logs
I flipped the stereo channels, because apparently the current a/v sync has some issues with it
Does that mean I need to reflip it when watching? Also that log only says the video file was changed. No notation about the reason.
"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 there a system in place for noting what the actual "updates" were?
"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
At least we haven't started console verifying handheld games yet. I wonder what decides if a post is to short. And I hope it isn't some sort of attempt at ensuring post content is meaningful because we all know verboseness does not equate to meaningful content.
"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
HQ Archive.org. Sorry, I forgot to specify.
Setting MPC to use an audio offset of ±2000ms fixed it. Usually "laggy" issues are variable and setting a solid offset wouldn't help.
"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 getting an offset of 2 seconds on the audio, from the beginning.
"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 we annoy the author of bsnes if his "accurate" emulator doesn't accurately emulate the transistor logic of the controller ports?
Something says my post lines are too short, so I shall recall my childhood in the frozen tundra of Madagascar. It was a good decades. We had just defeated the Japanese and gained independence. Little did we know, independence was just the start of our struggles. Now that we were sovereign, we could not depend on out samurai robot overlords. Long story short, we all died.
"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 we'll be seeing more Hardmode TASs? Would they obsolete the current runs even if they don't beat their time? Or will the JP and US versions get separate entries?
"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
How many frames would it take to turn on the Arranged Music, and would that be acceptable?
"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
How many frames would it take to turn on the Arranged Music, and would that be an acceptable speed/entertainment trade-off?
Iirc it wouldn't even considered be a speed/entertainment trade-off since it doesn't happen during gameplay
TASVideoAgent wrote:
Mothrayas: While the viewers generally seem to prefer stereo sound, I don't see it as something worth rejecting runs over. I do recommend picking stereo sound for any future runs (time lost selecting it will not be counted for judging, as it does not slow down gameplay).
Ah, I thought TAS went by "From Power On". Does it go from "Game Start"?
"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
How many frames would it take to turn on the Arranged Music, and would that be an acceptable speed/entertainment trade-off?
"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
Am I to understand that on a real "console" the rest would trigger the BIOS/Boot screen? If we ever verify this for real hardware, would we need a separate input recording to account for that time?
"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 guessing that even if you went to 90, there wouldn't be any sort of indicator that it's over.
PS: It'd be cool to see a Vs TAS where two TASers make their inputs at certain intervals.
"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
Am I reading the entry correctly? This is an any% glitch/ram corruption run that lasts over 3 hours? My main excuse for not playing this game was not having enough time and it seems more true that I thought.
"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 watched the entire run, and at no point was Luke ever a boss. Luke is the Player Character.
"I also can't agree with the difficulty chosen here, because it does not affect the gameplay, it only increases the player's damage."
Are you referring to Damage Dealt by Player or Damage Received by Player?
Uh, increasing the player's attack damage has the same exact effect as increasing each enemy's health in this case, so that's just semantics
"Uh, increasing the player's attack damage has the same exact effect as increasing each enemy's attack damage in this case, so that's just semantics"
Fixed that for you.
"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 policy was to play on hardest difficulty.
Tried reading the thread?
All I saw was someone saying you take more damage on hard.
I did not realise we were allowed to decide a game was to challenging.
It'd be understandable if "hard" resulted in a game breaking glitch, but just making it harder or longer to complete seems like sort of a silly excuse.
It's not an excuse, and it has nothing to do with being "too challenging." Check the guidelines:
Guidelines wrote:
Where a game has multiple difficulty levels, it is preferred to play on the hardest difficulty level (for more interesting gameplay) unless the only difference between difficulty levels is enemy/boss hit points, in which case the easiest difficulty levels are preferred in the interest of speed. If the difference in difficulty is inapplicable for your run, for example, you trigger the end game sequence right from the start, then selecting the hardest mode is unnecessary.
I watched the entire run, and at no point was Luke ever a boss. Luke is the Player Character.
"I also can't agree with the difficulty chosen here, because it does not affect the gameplay, it only increases the player's damage."
Are you referring to Damage Dealt by Player or Damage Received by Player?
"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
