Shouldn't it be the exact reverse? I mean in the cases of runs that have been console-verified? Shouldn't it be the console version that's considered the main primary version, with perhaps an ancillary version of the run that has been "fixed" to run on the emulator, if necessary?
TASes on the site do not aim to only work on console.
That's why I said "in the cases of runs that have been console-verified". If a run has not been console-verified, then it would need to have only the emulator version.
The other problem is people who want to play back these tases will not know that the main file is actually the console verified one, where it might not sync. It’s just a step that is completely unnecessary and would cause confusion, especially to encoders looking to re-encode older movies.
Have two links, one for the version that works on the console, and one that works on the emulator. The official time should be that of the console.
That’s already the case. I would be against having the console verified version of the movie take priority over the emulator one. Because like I said, the site does not make console verification a priority, so why would you make the time equivalent to the console rather than the emulator?
[14:15] <feos> WinDOES what DOSn't
12:33:44 PM <Mothrayas> "I got an oof with my game!"
Mothrayas Today at 12:22: <Colin> thank you for supporting noble causes such as my feet
MemoryTAS Today at 11:55 AM: you wouldn't know beauty if it slapped you in the face with a giant fish
[Today at 4:51 PM] Mothrayas: although if you like your own tweets that's the online equivalent of sniffing your own farts and probably tells a lot about you as a person
MemoryTAS Today at 7:01 PM: But I exert big staff energy honestly lol
Samsara Today at 1:20 PM: wouldn't ACE in a real life TAS just stand for Actually Cease Existing
That’s already the case. I would be against having the console verified version of the movie take priority over the emulator one. Because like I said, the site does not make console verification a priority, so why would you make the time equivalent to the console rather than the emulator?
If I might throw my oppinion in: I'd say because consoles are the "real deal". Emulators aren't the real deal. They AIM to be the real deal, but in the end they aren't.
Another thing: http://tasvideos.org/ConsoleVerifiedMovies.html:
Since they started, tool assisted speedruns were designed to make it theoretically possible, given super-human abilities, to recreate them on an actual console.
Console is not always the exact same time though. SNES, GBA (for game saving), and any disc based games can have variants in loading times, lag, and others. most of it is not deterministic like emulation would. So no, it would not be as easy as timing it on console.
[14:15] <feos> WinDOES what DOSn't
12:33:44 PM <Mothrayas> "I got an oof with my game!"
Mothrayas Today at 12:22: <Colin> thank you for supporting noble causes such as my feet
MemoryTAS Today at 11:55 AM: you wouldn't know beauty if it slapped you in the face with a giant fish
[Today at 4:51 PM] Mothrayas: although if you like your own tweets that's the online equivalent of sniffing your own farts and probably tells a lot about you as a person
MemoryTAS Today at 7:01 PM: But I exert big staff energy honestly lol
Samsara Today at 1:20 PM: wouldn't ACE in a real life TAS just stand for Actually Cease Existing
Well then it seems to me as if verification on these consoles is pretty much impossible...
On consoles, where it is still very possible though, console verification just seems to be way more absolute then verification on an emulator.
It doesn't make sense to me to do timing based on console because 1. sometimes verification can be sorta segmented (see Mario Kart 64) and 2. our encodes use emulators and it would make sense to have the timing be accurate to the encode.
[16:36:31] <Mothrayas> I have to say this argument about robot drug usage is a lot more fun than whatever else we have been doing in the past two+ hours
[16:08:10] <BenLubar> a TAS is just the limit of a segmented speedrun as the segment length approaches zero
Hm.. Yep, yep, the thing with the resets is hard, because it is literally impossible to verifie them in one single sitting. But from a tas-timing perspective it seems acceptable to add all the individual files up and go with the sum of these, doesn't it?
Memory wrote:
and 2. our encodes use emulators and it would make sense to have the timing be accurate to the encode.
Isn't the purpose of making encodes the publication of a run? I don't understand why these exact encodes should be the main focus point when it comes to vailtity of a tas.
Furthermore, although I don't know how how he did it, TiKevin83 uploaded some very good looking movies of console verifications recently.
Ambassador, Moderator, Site Developer, Player
(120)
Joined: 3/17/2018
Posts: 348
Location: Holland, MI
I don't think we can necessarily make console-packaged movies the "definitive" version of a movie due to the inaccessibility of console verification to judges and the numerous platforms that don't have even a start at verification.
That being said, per dwangoAC's message I'm working to make sure that all resyncing efforts have been thoroughly documented and to improve how the publication page can store that information in the future. I've been adding documentation as needed while giving several more movies the verified flag.
for KiwiCracker - current documentation is on runs.tas.bot. The GBC page documents how movies are exported and played back across GB/GBC by exporting for GBI, there's some preliminary work on GBA, and prepackaged GBI movies for several GB/GBC/GBA runs are available on the runs page. Alyosha is using this same pipeline for some recent work on GBHawk. It's also been used by dwangoAC, entrpntr, and CasualPokePlayer. If you have more questions there's a thread on verification efforts that would be more appropriate.
I don't think we can necessarily make console-packaged movies the "definitive" version of a movie due to the inaccessibility of console verification to judges and the numerous platforms that don't have even a start at verification.
Yeah, I also don't expect console verifications to ever be the main files/movies for judges to work with. I never ever had something to do with console verifications, but it sounds like a LOT of work and thus it sound impossible to establish this as a casual thing for all end every movie.
I was just thinking about the ones that have such a console verification and how to deal with movies like these.
TiKevin83 wrote:
for KiwiCracker - current documentation is on runs.tas.bot. The GBC page documents how movies are exported and played back across GB/GBC by exporting for GBI, there's some preliminary work on GBA, and prepackaged GBI movies for several GB/GBC/GBA runs are available on the runs page. Alyosha is using this same pipeline for some recent work on GBHawk. It's also been used by dwangoAC, entrpntr, and CasualPokePlayer. If you have more questions there's a thread on verification efforts that would be more appropriate.
Wow, this is epic! I never knew about this website, this is amazing :D
Thanks, I'll look into the other thread adressed by you ^^
