Feb 09 /10-13:25/ Team Event
Feb 11 /10-13:35/ Team Event
Feb 12 /10-13:10/ Team Event
Feb 14 /10-13:25/ Pairs SP
Feb 15 /10-13:15/ Pairs FP
Feb 16 /10-14:30/ Men SP
Feb 17 /10-14:25/ Men FP
Feb 19 /10:13:45/ Ice Dance SD
Feb 20 /10-13:35/ Ice Dance FD
Feb 21 /10-14:30/ Ladies SP
Feb 23 /10-14:10/ Ladies FP
Feb 25 /9:30-12/ Gala
I see a lot of knew people trying to gif things recently and I wanted to help some people out ith somethings that may be confusing for people who are new to it.
You don’t need photoshop or to pay for anything for it. Of course the more money you put into it, the better the quality but the tools exist everywhere for little cost. All you need is access to the internet, some sort of screen recording program, and access to streams (you can use illegal streams but the quality usually sucks).
if your realizing your gifs are frozen when you actually post the gifset to tumblr that’s probably because the gifs are too big. and yes if it’s frozen on your end it’s going to be frozen for everyone else too it’s not your computer glitching. Gifs need to be under 2mb for tumblr. to achieve this i like to keep my gifs to about 2 seconds long sometimes more or less, but 2 seconds at 10 FPS and 500px wide is about average and may need a little cropping but will fit with tumblr.
During interviews i usually crop the hell out of gifs which will result in a smaller size gifs and i can usually get it up to 4 seconds, i do this for fights as well. Using a perfect square and fitting it around just the face of the interviewee or the around the players fighting will allow you to double the time. Esp. fights since they are so long i use this method because it’s hard to gif all of it in two second increments. This also allows for smaller dimensions because tumblr width is 500px and if you fit two gifs side by side it’s 250px.
going off of size actually i want to reiterate that. 500px wide is the ideal size for gifs on tumblr, you can go smaller i do that a lot but the bigger it is compared to the size tumblr shows the better the quality. Since you can put gifs next to each other you can cut this and half and get the same quality.
Putting wide gifs next to each other will make it harder for people to see your gifs. Tall gifs and thin gifs or square gifs tend to be easier for people to see when they’re next to each other. Obviously this doesn’t apply to everything as it’s your gif and you can do whatever you want to it.
Yellow or red text with a black border will show up best over hockey games. The contrast is usually really big on hockey rinks with the white ice and dark jerseys that you usually can’t use black or white text for it to come up over the whole image. I use green sometimes but i just think that looks a little goofier than yellow or red.
If you’re giffing a goal wait for the replay. Yeah the original goal will have the best shot of the celebration but if you’re getting the goal itself wait and record all of the replays if you can. There are going to be different angles and slowmos which are easier to gif. The original play of the goal will usually be too fast or unnoticable especially if it’s a tip. I tend to find that the last replay they show is the best. I will use the original celly though, because that’s usually the best one.
stylistic choices are all up to you and id on’t look down on anyone who’s gifs do not fit what i’ve said here. do you. your thing is your thing and i’m not going to judge you for the way you gif things. I just think this may be a good groundwork for people or maybe give other people the confidence or the know how if they’ve thought about giffing before but don’t think they can.
ok you know what would be a really creepy element in a horror game if done well? If during a scene, your movement slowed and the framerate dropped to like 10-15 fps but there was one enemy or element of the game that stayed going at full speed/fps.
Je veux que tu retourne parler à ta copine, d'accord ?
Je crois que ça servirait à rien, on est irréconciliables cette fois.
Nan attends arrête de fuir ! Arrête de fuir ! Essaie d'apprécier ce que t'as ici, avec elle, avec tes amis, des choses que, des choses qu'on pourrait jamais t'offrir. Et tâche de devenir un homme. Après tout ce que je viens d'entendre, je pense qu'elle a besoin de toi.
Before you start Here’s some supplies to have - a computer - a program capable of re-writing files internally —- in this case, a “hex editor” (either/both automatic/manual; prefer ROM Corrupter 5.99 by Dwedit for automatic, as it can render loseless AVI files, which are godly for pixel freaks and GIF perfectionists; Cygnus Hex Editor for manual, with ease of access and control) - a program capable of opening said file (if sound, Audacity can open and re-write internally with some practice; otherwise, for this segment, an NES emulator; I prefer Nestopia) - if graphics, a good painting program for final touches AKA resizing/animating (I prefer GIMP 2.6, NEVER GIMP 2.8; free, capable of exporting animated GIFs, and can scale without interpolation, even for JPEGs, for that crisp-ass quality) —- if you’re getting into animated files, and are using the AVI exportation route, pick up a program that can make animated GIFs out of AVI files (the freeware Movie To Animated GIF Converter by Evan Olds is perfect for this) - and of course, victim files (for this segment, ROMs; best to dupe them, and then edit the dupes; ROM Corrupter 5.99 exports dupes without affecting the original automatically; with manual, you gotta do it yourself)
Now that we have All our tools gathered Let’s begin by knowing Our GUI
The basics for Dwedit 5.99
1. Dwedit location 2. Emulator program (normally Nestopia; re-named it to piss off Steam friends) 3. Target file (doesn’t have to be a ROM; can corrupt anything really) 4. End corruption file (rename it to whatever is easy for you) 5. Start corruption range (for NES, all ROMs start at $10) 6. End corruption range (for NES, most ROMS end at $8000(2^X)+$10 [i.e. $20010 for Metroid] 7. Affected bytes 8. What bytes will become
For those that know Hexadecimals intimately We can converse about All what happens On a mathematical formula But for now Let’s just focus On the results
Not that hard To get somewhere Just requires patience And experimenting As you can see Had to change every 941th to 888th byte You’ll get CPU jammed at times If it continues to happen Just change the range Or which bytes to corrupt
Once you’re satisfied With your result You can either screenshot it Or save it as a movie file By naming the original capture file Recording And then exporting When you stop recording And just export it as loseless AVI Be mindful that sometimes What we saw And what the emulator saw Can be different Or even too broken To save as an AVI
We’ll cover what to do With the image nuggets later
While that covers automatic Perhaps you like a more “Pure” approach That’s dandy too I’ll go over manual editing too I would save this solely For picture files Or anything smaller than an NES ROM But hey, anything’s open season
The basics for Cygnus Hex Editor
1. Range 2. Current hexadecimal bytes 3. Current translated bytes
You can use either 2 or 3 For changing bytes in the file For 2 It has to be in 16base (0-9, and A-F, from 00 to FF) For 3 It’s any character that is recognized By the hexadecimal format AKA just keyboard smash
Boom Same idea, different paths After a while You get the hang for where Data for the file is stored Both for automatics and manuals For PNGs, it usually Right at the get-go JPEGs are after the File format itself (You’ll see a bunch of 01s 02s and the translations are in a nice pattern After that are the pixels themselves)
ROMs are trickier As one company can put all their Glossy title screens first Where others may have them last A good rule of thumb All the graphics/placement Are always clumped in their Respective group BUT, not always with the other group Ex. Samus’s projectile graphics Could be in $10010-$10040 And where they’re assigned on-screen In $14010-14040
To make a simple GIF We’ll use an even simplier program If you have an AVI file From using Nestopia Or any other emulator Capable of exporting AVI We can turn it into a GIF Right here and now
The basics of MTAGC by Evan Olds
1. Select as starting frame 2. Select as ending frame 3. Frame view slider
Little to go over here Once you selected What section you want animated Just export it Not only can you save An animated GIF right off the bat But also save the current frame separately For other design usage
Here’s what we got
Please note however That when we export as a loseless AVI It’s in real-time (~60 fps) So when being converted From MTAGC It will only capture the first frame Outta every 10 Becoming a 10 fps GIF If you wish for a 60 fps GIF You’ll have to use other means Even then At least you can export Every frame viewable with MTAGC
To finally cap On our tools I’ll go over GIMP 2.6 real quick
All you need to know about GIMP 2.6 For pixel-perfect export
Non-animated images 1. Scale image 2. Resize image that’s a ratio of the original aspect ([128x128] x N, where N is a whole integer)
Notice how “none” is selected For interpolation I can’t stress this enough Seriously This will solve every single problem With “fuzzy” images If it’s for video footage Of an awesome skateboarder That’s fine But for glitching This will save you From shitty quality
If you have a bunch of captured screenshots And want to compile them Into an animated image W can do that too easily
For animated image files
1. Place your image file here (if already animated through AVI, and proceed to 2) 1a. Your image will flip from lowest to highest in that order 1b. If you need to make an edit, select layer, and shut all eyes above that layer 2. When finished, open all eyes, and “Save As” 3. Enter the file name withextension (for now, “basic done.gif”) 4. Save as an animation (make it looped or not after you’ve chosen)
And here we have it
Do note again That all GIFs exported Will be animated at 10 FPS So even if you got every frame In GIMP 2.6 It will still be at the same speed As the one you made Right off of MTAGC Another program must be used To bump the cap for this
Here’s some tips and tricks I use
+ start at $10, end at $1010, change range by $1000, click on auto, and see what happens; rinse and repeat until you hit the end of the game; doing this will not only eventually yield a “sweet spot” (mostly the graphic storage/placement), but allow you to see where and what is located for future reference + if you made a good corruption file, make a new one, just in case you want to ever go back to that iteration + you can hex edit anything, but image files and NES ROMs are the smallest, which will also mean the easiest to start off with; later you can move onto Playstation ISOs or MP3s/WAVs + for NES ROMs, I recommend Metroid, Super Mario Bros., Wrecking Crew, Balloon, basically any old Nintendo game; they’re the first, so they’re the quickest to dissect, and quickest to create some really bizarre glitches from not being ironed out + back all your shit up; seriously; I can tell you this from experience; NES roms are tiny as hell; most are only 128/256 kilobytes, and the biggest, only a megabyte (1024 kilobytes)
Quick answers to future questions
“I keep getting a CPU jam!” Change the range/affected bytes Not everything corrupted are graphics
“I keep getting the AVI conversion error!” Hard reset and try again Chances are it captured invalid file-coding If it doesn’t work Make a new file and change the action a bit
“It rendered 30 seconds of [a still image / nothing / something else]!” Again What we see And the computer sees Are two different things Try screen capturing As it saves based on The current monitor display Rather than the hexadecimals themselves
“When I put a hex edited image into GIMP 2.6, it only partially loads!” GIMP 2.6 is fine It’s just the image that’s broken A quick fix is to Open it in paint.exe And just save It’ll change the hexadecimals Back to a displayable image While retaining the result
“My hex edited image won’t show up!” You probably borked it’s file-coding Instead of the pixels and their placement Reload and move further down the range
“Tumblr’s not allowing me to post my GIF!” Animated GIF files are huge Stick with around 400px - 600px And nothing past 100 frames Unless you’re feeling lucky punk
That should do it for ya If you have any further questions Hit me up