Personnellement, je préfère dire TASeur puisque "TASer" peut faire penser à un verbe à l'infinitif ou au mot Anglais. Pour la prononciation, Je penche plus pour "TAZeur" puisque qu'un 'S' enter deux voyelles donne le son "Z". (Et quand on dit "tasseur", je pense a un mec qui tasse des choses genre dans une poubelle xD)
Grincevent wrote:
phoenix1291 wrote:
Grincevent wrote:
pour le "movie" changé en "TAS" [...]
il faudrait au minimum parler de "fichier movie" si on veut le garder.
Effectivement, je pense qu'il faudrait déjà définir ce qu'est le Movie, ce qu'il englobe etc.
Et comme tu le soulignes, le Movie et le fichier Movie, c'est encore autre chose.
D'où encore une fois mon questionnement sur la pertinence ou non d'un lexique -
généralisé - et - multilingue - etc ou non
Je pense que le souci du mot "movie" se pose aussi en anglais, enfin le fait qu'il puisse désigner plusieurs choses, du fichier d'inputs jusqu'à une publication entière sur le site.
Au final ça fait que mon avis est de l'éviter en le remplaçant quand on peut, selon le sens dont il se rapproche le plus dans le contexte: TAS, fichier movie, publication... Et comme souvent en traduction, on peut toujours tenter d'éviter certains termes qui posent problème en reformulant les phrases. Tout ne peut pas être traduit en restant proche du mot pour mot, surtout avec autant de termes spécifiques au TAS qui n'ont pas d'équivalent en français.
Pour moi, movie = fichier input car dans Helping onglet "encoding" on peux lire : "publishing encoded movies" que je traduit par : "publié des encodages de fichier d'input", et je considère que TAS = fichier d'input aussi car un TAS n'est qu'une suite de touche précisent à des moment précis.
Pour finir, je préfère "une run" car en trad je dis "une course".
[17:37:00]<TheCoreyBurton> It's N64 - it's ALWAYS bad news.
@Lapogne36, peux-tu remettre "encodes" à la place de "encodages" pour les deux derniers s'il te plait ? L'encodage est l'action de faire une encode donc le nom existe en fr
Je suis sur mobile et j'arrive pas à modifier
[17:37:00]<TheCoreyBurton> It's N64 - it's ALWAYS bad news.
Je viens de traduire helping, dites moi ce que vous en pensez :
https://pastebin.com/VFmSwHpC
Il y a des chose dont je ne suis pas sur dans la traduction ou même l'interprétation donc n'hésiter pas a commenter.
[17:37:00]<TheCoreyBurton> It's N64 - it's ALWAYS bad news.
It's a great project that I'd like to contribute to.
There would be a little problem that is, when someone add/remove content on a page, how to do it for all the others in different languages ?
It would require the editor to make a english translation of what he added and the translators could just translate it in its language and update the content, but some content would be really outdated for the pages that aren't well supported.
So this require a warning on top of the page that would redirect to the English one (or something like this) to be sure the visitor get all the missing content.
[17:37:00]<TheCoreyBurton> It's N64 - it's ALWAYS bad news.
I'm open to suggestions, and I'd prefer start with the easiest console to emulate, and I thought A2600 was a really easy one.
I'll take a look at these links.
About legal stuff, what is legal and what is not in creating an emulator ?
[17:37:00]<TheCoreyBurton> It's N64 - it's ALWAYS bad news.
Hello,
I'm interested in creating my own emulator to learn about the emu development itself, but the fact is I don't know how can I find the required informations about the console.
So how did you manage to get all these informations ?
I know there is everything about the CPU, the GUI shouldn't be the hardest part to do (In my opinion) but my main trouble is in the ROM stuff : how do you do to read the rom ?
Thanks for your answers !
Btw, the platform will be atari2600 to start with a small one.
[17:37:00]<TheCoreyBurton> It's N64 - it's ALWAYS bad news.
After a few researches, I know better this glitch :
To get rid of it, I need to change the direction 1 frame earlier, so this glitch occurs when you change the direction on the last available frame. This glitch is thus frame-perfect (1 visual frame, 2 VIs, the game have 30 visual frames/sec and 60 VIs/sec)
This can lead to some good things, like manipulating the armoured trains, they follows you depending on the path you follow. I haven't test it yet but can be usefull.
[17:37:00]<TheCoreyBurton> It's N64 - it's ALWAYS bad news.
So I just discovered a new glitch that I'd prefer it not to exist. Here is a video of it :
Link to video
What happen is in the lost wood, I follow the path that I should to go to the sanctuary, but when exiting the forest, the game consider that I didn't followed the right path, but I did.
It's really annoying and I currently don't know how to get rid of it
[17:37:00]<TheCoreyBurton> It's N64 - it's ALWAYS bad news.
Hi, I made an lua script that calculate my time, but this time is different compared to the one given by DeSmuME : it give me 18:57.10 when my script says 19:00.4 for 68028 frames.
I saw on this page that DeSmuME's framerate is 59.826098288081, so I made this script :
Publishers have a lot of work, they can't do everything in the same time. Even though I did the longest part, publish a movie still takes a certain amount of time.
[17:37:00]<TheCoreyBurton> It's N64 - it's ALWAYS bad news.
No idea, but the video from Stovent's post uses TASVideosChannel, so I thought he was doing it.
I'm only an encoder, not a publisher. My job is to do the encode so the publisher only have to take it and add a description and post it to archive.org
[17:37:00]<TheCoreyBurton> It's N64 - it's ALWAYS bad news.
Hi,
I'm making a DS TAS and I've changed the defaults firmware settings.
Can the run still be accepted with these new settings ?
The movie sync perfectly if you set the settings to mine but it don't sync with the defaults ones.
[17:37:00]<TheCoreyBurton> It's N64 - it's ALWAYS bad news.
So I miss-understood his question.
I'm considering that to reach the credits in the fastest way, you need to go to a point at which no further input is required to get to the credits as fast as possible
[17:37:00]<TheCoreyBurton> It's N64 - it's ALWAYS bad news.
b) WiiVC obsoletes N64. Now a user searching the site's movies by console is going to think "where the hell's SM64 1-key?"
As scrimpeh said, these movies will be published as wii games, so the can't obsolete movies from others platforms.
thatguy wrote:
but I don't want to see a profusion of pairs of movies which are basically the same on this site.
I agree with this.
But we can do it this way : because the site doesn't want too much categories per game, maybe the VC runs will do different categories.
By example, SM64 have "1 key", "70 stars no BLJ" and "120 stars" on N64, and we can have "16 stars" on VC
[17:37:00]<TheCoreyBurton> It's N64 - it's ALWAYS bad news.