YATTA

[19:40:50] <torque> btw, I heard that you have experience with YATTA
[19:41:15] <@Hale> I know some basics..
[19:42:46] <torque> hmm
[19:43:16] <torque> can you explain what pattern guidance is?
[19:43:25] <@Hale> there's really only a few poeple out there that completely know how to use it.. and 3 of them are mia
[19:43:40] <@Hale> I'll try
[19:45:35] <@Hale> assuming we're talking about a straight telecine without any vfr sections, there's two possible scenarios: 1# the whole ep was rendered in one run #2 parts of if were spliced together, screwing with the pattern
[19:46:29] <torque> so just 3:2 pulldown?
[19:47:06] <torque> ok, and you use it to find the pattern where there are scene changes.
[19:47:17] <@Hale> let's say you have your tfm metrics and the decimate for scenario 1 - you'll hit the pattern guidance and you'll get a new window with every frame, that was marked as out-of-pattern
[19:48:13] <torque> because you've already fixed all the problem frames?
[19:48:16] <@Hale> in case 1 this will result in a few ones that are either hard interlaced/have ridicilous v-metric values or couldn't be decimated correctly
[19:48:22] <@Hale> nah
[19:49:04] <torque> ah, ok
[19:49:13] <@Hale> you have your calculated metrics (gathered via ymc beforehand).. you hit said button and are presented frames that couldn't be processed correctly
[19:49:41] <@Hale> it's one of the cool auto-magic-functions that make yatta worth learning
[19:50:02] <torque> hmm
[19:50:31] <torque> so then how do you know if you're dealing with vfr footage?
[19:52:11] <@Hale> simple - scenes that couldn't be decimated correctly will be listed in the extra window from pattern guidance.. you work your way through them and if you spot that there's no decimated frame withn a range of 10 in both directions, you start investigating that particular scene more closely
[19:52:54] <@Hale> if you don't run into duplicates sooner or later, you're most likely dealing with a 30frame section and mark it as no-decimate
[19:53:47] <torque> hmm
[19:53:55] <torque> how long does it take to run pattern guidance?
[19:54:09] <@Hale> one click away..
[19:54:19] <@Hale> but you need all metrics first
[19:54:43] <torque> well, when I tried to do it, I got "Matching Failure at 0" and then it sits there.
[19:54:53] <@Hale> -.O
[19:55:00] <torque> I probably screwed up when I was collecting metrics with YMC
[19:55:03] <@Hale> and it doesn't list any others?
[19:55:08] <torque> no.
[19:55:21] <@Hale> then yeah - you most likely screwed up
[19:55:28] <@Hale> got your d2v ready?
[19:55:34] <torque> yep.
[19:55:46] <@Hale> ok, fire up ymc and drop it in there
[19:55:58] <torque> done.
[19:56:03] <@Hale> mom
[19:56:37] <@Hale> first make sure you tick either mpeg2dec3 or dgindex depending on what you used to index your source
[19:56:48] <torque> dgindex
[19:57:01] <@Hale> also - what mode did you run it in? (force film, honor or ignore pulldown)
[19:57:12] <torque> ignore pulldown
[19:57:17] <@Hale> uhm.. why?
[19:57:49] <torque> well when I was trying to do this straight through avisynth without YATTA, that worked a little better
[19:57:55] <torque> lemme go make one with honored pulldown
[19:58:03] <@Hale> *nod*
[19:58:19] <@Hale> 90% of the time that should be what you have to use
[19:58:43] <torque> thanks for helping me out with this
[19:58:46] <torque> I appreciate it.
[20:00:38] <@Hale> well it's really not of a big issue to run someone through the basics, but finding someone willing to is.. don't have anything better to do now, so why not =)
[20:00:39] <torque> ok, done and in YMC
[20:00:46] <@Hale> hayai >_>
[20:00:55] <torque> doesn't take long to index.
[20:01:13] <@Hale> ok, tick dgdecode and tdecimate for starters
[20:01:28] <torque> ok
[20:01:33] <@Hale> next tick tfm+telecinematrics and click configure
[20:02:03] <torque> ok
[20:02:14] <@Hale> now in this new window set pp to 0 for now and browse through your video looking at what the matches tell you
[20:02:49] <torque> c and p?
[20:02:55] <@Hale> if you run into ü matches instead of n matches, change "field from bottom to top" (or the other way around)
[20:02:57] <@Hale> exactly
[20:03:06] <@Hale> erm p
[20:03:20] <@Hale> so basically you just want c and n matches there
[20:03:56] <torque> hmm
[20:04:06] <torque> I'm getting cccpp for the most part
[20:04:14] <torque> no n matches so far
[20:04:32] <@Hale> change "field" then and browse the same section
[20:04:41] <@Hale> should switch to n normally
[20:05:00] <torque> ah
[20:05:03] <torque> yes
[20:05:27] <@Hale> ok .. now we figured out if it's tff or bff ..
[20:05:32] <torque> bff it seems.
[20:06:03] <@Hale> tick pp 7 again and see if you immidieatly run inta a frame that isn't marked as "clean frame"
[20:06:15] <@Hale> (by browsing through it again)
[20:06:30] <torque> ran into one
[20:06:40] <@Hale> how does it look like?
[20:07:31] <torque> it's combed if I set PP 0
[20:07:59] <@Hale> ok.. you either have to options now..
[20:08:54] <@Hale> first one: run it with pp0 and check for combed frames later via pattern guidance / search function, or set pp7 and hope for the best (that's the lazy-bum-version)
[20:09:08] <torque> hmm
[20:09:24] <@Hale> you can still override it even if you set pp7 now, so let's do that for now
[20:09:40] <torque> okey dokey
[20:09:42] <@Hale> sorta easier to explain with it
[20:09:58] <@Hale> hit ok, set the putput path for the yap file and fire it up
[20:10:00] <@Hale> or wait
[20:10:14] <@Hale> do you also have the scene-change plugin loaded in ymc?
[20:10:41] <torque> SclavC?
[20:10:58] <@Hale> forgot what it was called, but I think that's the one
[20:11:07] <@Hale> tick it too and fire it up
[20:11:11] <torque> yeah
[20:11:40] <torque> do I just leave it on the default configuration?
[20:11:51] <@Hale> I don't have the slightest idea ^^'
[20:12:03] <torque> fair enough.
[20:12:10] <@Hale> I usually collect scene-change information in another path via xvid
[20:12:27] <torque> ah.
[20:12:38] <@Hale> I can run you through that though..
[20:12:42] <torque> ok.
[20:12:50] <torque> Well YMC is running right now
[20:12:54] <torque> so might as well, I guess.
[20:13:08] <@Hale> we'll see what happens
[20:13:15] <torque> ok.
[20:13:59] <@Hale> brb
[20:17:02] <@Hale> what is it you've got there anyway?
[20:17:13] <torque> >___>
[20:17:15] <torque> futurama.
[20:17:30] <@Hale> I see..
[20:17:38] <torque> they're the messiest DVDs I have
[20:17:52] <torque> at least as far as I know
[20:18:00] <@Hale> no idea how this was produced.. we might run into some oddities here
[20:18:20] <torque> that's ok. I just want to get the basics down for now
[20:21:39] <@Hale> "getting colder during the night", my ass.. it's 2:20, I'm sitting here in a tanktop with the windows wide open and it doesn't feel any different from this afternoon >_>
[20:22:00] <torque> you in europe?
[20:22:06] <@Hale> *nod*
[20:22:09] <torque> hmm
[20:22:14] <torque> I went there last summer.
[20:22:18] <torque> it never got cold at night.
[20:22:25] <torque> Except in Britian.
[20:22:54] <@Hale> britain is odd.. I've been there 3 times now and never experienced any rain at all
[20:23:04] <torque> hmm
[20:23:10] <torque> I've been there twice
[20:23:18] <torque> gotten rained on once.
[20:24:36] <@Hale> first time I though I'd play the maniac at speakers corner while beeing drenched by the rain, but that didn't work ^^'
[20:25:16] <@Hale> ^-- the plan was to count the minutes until I'd get arrested by the local police xD
[20:25:29] <torque> haha
[20:25:39] <torque> always a good plan to get arrested
[20:26:24] <@Hale> nah - don't have the balls to pull something like that in south-east asia
[20:26:39] <@Hale> or russia >_>
[20:27:18] <torque> yeah.
[20:27:21] <torque> I don't really blame you
[20:28:37] <@Hale> status?
[20:30:36] <torque> oh it just finished
[20:30:36] <@Hale> sweet
[20:30:37] <@Hale> fire up yatta and move to the tools section first
[20:30:38] <torque> lots of sections.
[20:30:38] <@Hale> the "tools" button ^^'
[20:30:46] <@Hale> > avs genearation
[20:31:01] <torque> ok
[20:31:25] <torque> sorry, when I said lots of sections, I meant under the tools dialogue :P
[20:31:30] <torque> I'm not completely hopeless.
[20:31:37] <torque> ... I think.
[20:31:46] <@Hale> tick spline36, tdecimate, nnedi2 (or 3 whatever you have there) and untick both, resize and crop
[20:32:08] <torque> ok
[20:32:28] <@Hale> what about the scene-change thingie? did it provide you with different ones under the sections tab?
[20:32:36] <torque> yep.
[20:32:42] <torque> about 500 of them
[20:32:55] <@Hale> double click one randomly and check if it's correct
[20:33:05] <@Hale> (i.e. jump back one frame)
[20:33:24] <torque> it's correct if what happens when I jump back a frame?
[20:33:33] <@Hale> different scene?
[20:33:48] <@Hale> or at least something vastly different
[20:33:59] <torque> lol ok, so I am hopeless
[20:34:03] <torque> yeah, most of them work.
[20:34:08] <@Hale> k
[20:34:37] <@Hale> close that window and work your way thorugh right-click to the crop & resize windwo
[20:34:40] <@Hale> window
[20:34:57] <@Hale> (hidden under additional)
[20:35:15] <torque> ok
[20:35:46] <~TheProfosist> so torque ur essentailly encoding... care to encode for us?
[20:36:01] <@Hale> tick show resized and the source's aspect ratio (I'm assuming 16/9 ntsc here)
[20:36:26] <torque> 4:3 ntsc
[20:36:29] <@Hale> ok
[20:36:33] <torque> yep
[20:36:53] <@Hale> crop off the edge noise taking mod2 into account
[20:37:30] <torque> doesn't it have to be like mod4 for x264 or something?
[20:37:32] <@Hale> usually at least 4 on both sides vertically plus whatever the studio did to screw things up ^^'
[20:37:57] <@Hale> you might be right there
[20:38:07] <torque> Not a huge deal
[20:38:15] <torque> ok so I have it cropped
[20:38:33] <@Hale> copy the crop like, hit anamorphic and close the window
[20:38:57] <@Hale> open up tools again and navigate to the presets manager
[20:39:16] <torque> ok
[20:39:39] <@Hale> choose the "default" preset from the drop down menu, throw in your copied crop line and hit "update"
[20:40:06] <@Hale> also - save your progress once in a while =)
[20:40:16] <torque> good idea.
[20:40:33] <@Hale> right click > save all overrides
[20:41:16] <@Hale> now let's see if things works so far.. hit preview and check if your crop it recognized correctly
[20:41:46] <@Hale> should be about the frame size minus crop
[20:42:57] <torque> couldn't locate "telecide hints.dll" >___>
[20:43:02] <torque> guess I need to go find that.
[20:43:10] <@Hale> guess so oO
[20:43:39] <@Hale> grab nnedi2 while you're at it, if you haven't got it in your avs plugins folder yet
[20:43:46] <torque> I have it
[20:43:57] <torque> I think >_>
[20:44:00] <@Hale> not having telecinehints is weird then xD
[20:44:06] <torque> it was an available checkbox, at least.
09[20:46:47] * @Hale np: Shinzan Zeroshiki {Eternal Force Blizzard} - 04. Shining Justice (2009) @ 946 kbps
[20:46:55] <torque> ah, finally found it >__>
[20:47:55] <@Hale> decomb, fieldhint and tivtc are pretty essential too, check if those are present
[20:48:09] <torque> yeah, I got those when I was setting it up
[20:48:13] <@Hale> k
[20:48:18] <@Hale> try again then =)
[20:48:21] <torque> somehow I overlooked telecidehints
[20:49:39] <torque> ok
[20:50:04] <torque> the preview is cropped but not resized.
[20:50:27] <@Hale> that's exactly what we wanted so far.. seems everything woks then
[20:50:41] <@Hale> ok.. save once more and let's more on to the fun stuff
[20:50:54] <@Hale> right click > pattern guidance
[20:50:56] <@Hale> =D
[20:51:27] <@Hale> how many entries are you presented roughly?
[20:51:46] <torque> under pattern guidance?
[20:52:09] <torque> a lot
[20:52:10] <torque> uh
[20:52:11] <@Hale> no - in the new pop-up window
[20:52:20] <~TheProfosist> doesnt have to be mod4 for x264 we went over issue alot when setting our encoding specifications
[20:52:30] <torque> hmm
[20:52:36] <torque> does it have to be mod 4 for something?
[20:52:53] <torque> since avisynth usually flips out at me if I crop it non mod 4 or 16 or something
[20:52:54] <~TheProfosist> well i used to have to be mod4 like way in the beginning
[20:52:58] <@Hale> try mod2 for fun later on.. not really an issue right now
[20:53:14] <torque> I have a bunch of matching failures
[20:53:28] <torque> and a bunch of "too short sections"
[20:53:30] <@Hale> yeah.. but how many?
[20:53:58] <torque> do you want me to count them one by one?
[20:54:24] <@Hale> the too short sections usually aren't much of an issue.. you can check them, but 90% of the time it's just high vmetrics screwing with you
[20:54:31] <@Hale> nah, just a rough number
[20:54:43] <@Hale> 30, 50, 500?
[20:55:09] <torque> ~100
[20:55:23] <@Hale> ok.. that's within limits
[20:55:24] <torque> not including the too short section ones
[20:55:50] <@Hale> oh.. well.. a liitle high but that's to be expected form fucking american productions =P
[20:56:02] <torque> haha
[20:56:03] <torque> indeed.
[20:56:10] <@Hale> you remember what I told you about the 3 possibilites in this window?
[20:56:41] <@Hale> double click the first matching failure entry and check what's wrong with it
[20:57:33] <torque> most of them don't seem to have any problems
[20:57:38] <torque> at first glance.
[20:58:10] <@Hale> by now the overlayed info should've changed and one out of 5 frames should be chrossed through
[20:58:13] <torque> I assume by what's wrong you mean like combing or something along those lines?
[20:58:18] <@Hale> correct
[20:58:18] <torque> yep.
[20:58:28] <@Hale> see any combing?
[20:58:49] <torque> not so far.
[20:59:09] <@Hale> what about the decimate? one out of 5 in the near area marked?
[20:59:24] <torque> yeah.
[20:59:28] <@Hale> should usually be one of the n frames
[20:59:34] <torque> yep
[20:59:47] <@Hale> hmm.. ok.. what about the metrics?
[21:00:07] <torque> well, what about them?
[21:00:13] <@Hale> paste here
[21:00:28] <@Hale> might be it's just overshooting due to a high value
[21:00:45] <torque> MMetric DMetric and Vmetric?
[21:00:51] <@Hale> yep
[21:00:58] <torque> which frame do you want them for?
[21:01:00] <torque> all of them?
[21:01:19] <@Hale> nah.. the one you were presented when jumping from the guidance window
[21:01:41] <@Hale> maybe one before and one after, just to be sure
[21:01:54] <torque> ok
[21:02:21] <torque> MMetric: 246834, DMetric:186777 VMetric:82
[21:02:30] <@Hale> don't want to make it sound too easy after all ^^'
[21:03:28] <torque> frame before is MMetric: 347353, DMetric:845, VMetric: 22
[21:03:36] <torque> frame after is
[21:04:10] <torque> MMetric: 230459 DMetric: 4802 VMetric: 24
[21:04:27] <@Hale> content-wise.. are those duplicates? i.e. is the one with the extremely high dmetric the same as the one before or after?
[21:05:19] <torque> same as the one after, basically
[21:05:31] <@Hale> and is it the first frame after a scene-change or is it a high-motion scene?
[21:05:41] <torque> first frame after a scene change
[21:05:45] <@Hale> =P
[21:05:56] <@Hale> ok.. now on for some magic..
[21:06:19] <@Hale> navigate to the sucker frame, hit "f" , navigate to the following one and hit f again
[21:06:31] <@Hale> then check what happende to the frame before
[21:06:40] <torque> it looks prettier
[21:06:44] <torque> it doesn't have like
[21:06:48] <torque> weird colorblending
[21:07:00] <@Hale> got an idea what you just did?
[21:07:13] <torque> frame replacing
[21:07:18] <torque> :D
[21:07:21] <@Hale> correct.. =D
[21:07:32] <@Hale> the encoder will love you for this later
[21:07:55] <@Hale> ok.. first frame in the chain processed, double click the next one
[21:08:05] <@Hale> same scenario?
[21:08:52] <torque> not quite
[21:08:57] <torque> the next frame isn't the same
[21:09:13] <torque> and there isn't the colorblending in the problem frame
[21:09:25] <@Hale> no combing and just a high value?
[21:10:09] <torque> that's what it looks like
[21:10:31] <@Hale> replace in case you've got the same one somewhere near, otherwise move on to the next one
[21:11:27] <@Hale> tip: on low-motion scenes the dmetric can go as low as 5 or 6, so something within the millions is obviously out of order
[21:12:06] <torque> so if the maching failure frame is preceeded or followed by a frame with lower metrics, you want to replace it?
[21:12:19] <@Hale> that's the idea
[21:12:22] <@Hale> at least ..
[21:12:43] <@Hale> if you can't find any combing one or missing decimate
[21:13:14] <torque> well there are random combed frames here and there
[21:13:23] <@Hale> that's what we're looking for right now.. so click your way thorugh the list randomly for now and search for one of those
[21:13:26] <torque> but they weren't picked by the patter matching
[21:13:32] <torque> *pattern matching
[21:13:48] <@Hale> most of them should.. but a few slip though usually
[21:14:06] <@Hale> that's why you're presented this list to begin with ;)
[21:14:51] <@Hale> ok.. assuming you found a combed one: there's the "s" key to take care of that..
[21:15:09] <torque> ok, leeme try to find a combed one
[21:15:57] <@Hale> it switches the field for this single frame usually ending up in eigher a correct frame (remeber - if possible, we still only want c and n matches) or something blended
[21:16:16] <@Hale> in case of blending, that's where the tricky stuff starts
[21:16:24] <torque> ok, I found one.
[21:16:36] <~TheProfosist> wow i fell retarted
[21:16:43] <torque> hitting S makes a giant blended frame
[21:16:45] <~TheProfosist> it just hit me about the mod4 thing
[21:16:55] <~TheProfosist> i though i said mod16
[21:17:11] <~TheProfosist> yes it has to be mod4 width and mod 2 height
[21:17:15] <@Hale> prof: my bad.. doesn't matter now though
[21:17:26] <torque> lol now I know
[21:17:29] <torque> thanks for the info
[21:17:35] <@Hale> torgue - in each of the three cases?
[21:17:48] <@Hale> one combed, one blended and the other one combed I assume?
[21:18:29] <torque> well
[21:18:45] <torque> 2 of them are exactly the same
[21:19:39] <torque> one of them is interlaced with the previous frame.
[21:20:07] <@Hale> ok.. we have two options now.. first: freezeframe with a duplicate from the same area (chances are this won't work) or switch to n field again and hit "p"
[21:20:25] <@Hale> this really depends on the scene now
[21:20:30] <@Hale> is there any motion at all?
[21:21:20] <torque> uh
[21:21:30] <torque> moving mouth
[21:21:41] <torque> and actually it looks like I can freeze it with the next frame.
[21:21:54] <torque> oh wait, no
[21:22:14] <@Hale> ok.. switch to n field > hit p
[21:22:35] <@Hale> save your project and hit preview to check if it wokred
[21:23:21] <torque> yeah
[21:23:33] <torque> worked pretty well.
[21:23:33] <@Hale> if everything is set up correctly this single frame you just marked for post-processing should be fed into an external deinterlacer (the nnedi2 you ticked earlyer)
[21:23:39] <@Hale> sweet =)
[21:23:48] <torque> brb
[21:24:10] <@Hale> same here, dry mouth
[21:25:48] <@Hale> re
[21:25:54] <@Hale> so far this lessen worked like a charm..
09[21:26:57] * @Hale np: Ootsuki Kenji to Zetsubou Shoujotachi {Sayonara Zetsubou Sensei - Series Uta Mono Kessaku Senshuu} - 07. Kuusou Rumba (2008) @ 984 kbps
[21:27:08] <@Hale> assuming you run into the third scenarion while working your way through the list (the one with the choking decimate), it's time to use your eyes...
[21:27:47] <@Hale> basically you'll hate to manually inspect the scene and check if one out of 5 frames is a duplicate
[21:28:33] <torque> hmm
[21:28:54] <@Hale> this can get particualar tricky if its either static, a reaaaly slow pan/zoom/fade or a chrossfade
[21:29:27] <@Hale> in this case you should browse through it to the point where the decimate kicks in again and check how it differs
11[21:30:30] * Disconnected
[21:31:46] <@Hale> if it's just static stuff you can savely kick them out
[21:32:27] <@Hale> but if you don't run into any duplicats for at least 11 frames AND you have motion, that's 30frame stuff
[21:32:42] <torque> is it ok for there to be a fairly long sequence without any decimation?
[21:32:43] <torque> hmm
[21:32:58] <@Hale> openings, endings, some cg animations and so forth are the usual ones
[21:33:22] <@Hale> in this case you'll just leave the scene as is and mark it as "no decimate"
[21:34:15] <torque> hmm.
[21:34:32] <@Hale> later on, when you're done with everything you want to do, you'll override everything again and get a timecode file corresponding to those 30fps sections
[21:34:57] <@Hale> the avs scrips will automagically trim such sections, not applying the decimate here too
[21:35:24] <@Hale> understood the concept?
[21:35:38] <torque> I believe so
[21:36:04] <~TheProfosist> hey SinSiXX !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[21:36:10] <@Hale> well, you can always ask for a particular scene if uncertain, but that's the general idea
[21:36:20] <torque> thank you very much
[21:36:29] <torque> I appreciate the time you've spent explaining this to me
[21:36:34] <@Hale> hol on: two things are left..
00[21:37:01] <@SinSiXX> ive been following the Hale's session the entire time ^^
[21:37:11] <@Hale> when you worked your way though the list, you'll have to do at least 2 more runs manually
[21:37:46] <@Hale> one of them involves checking for post-processed frames (chances are a few were marked you didn't set yourself)
[21:37:52] <torque> ok
[21:37:59] <@Hale> there's .. a hotkey for that... lemme check which one
[21:38:58] <@Hale> "m"
[21:39:39] <@Hale> again.. checking for the ones that shouldn't be set and unmark those by hitting p again will do the job
[21:39:42] <torque> ah yes it jumps from one pp frame to the next
[21:40:00] <torque> so you don't want progressive frames to be post processed
[21:40:32] <@Hale> the other one is simple arrow up / down which corresponds to vmetric differences set unter tools > find
[21:41:02] <@Hale> here you'd want to tick "v from both sides" and set the value rather low, to not let any major ones slip through
[21:41:14] <@Hale> I've got "5" here
[21:41:56] <@Hale> this can take a while, but as soon as you did those 3 overall passes, there shouldn't be any major problems left
[21:42:12] <@Hale> or at least none, that could be fixed without filtering
[21:43:13] <@Hale> that's what's usually called a "match perfect" source and coming up with any filtering chains would only be worth on this =)
[21:44:11] <@Hale> when you've reached that stage, your video will already look vastly superior to what it would look like on any hardware player ^^''
[21:44:49] <@Hale> I think that sums it up..
[21:45:22] <@Hale> also - hi sin ;)
[21:45:40] <torque> so basically, it takes a while to make a nice encode.
[21:45:49] <@Hale> sure
[21:46:13] <@Hale> there's one-click solutions for ugly ones, if you prefer that
00[21:47:20] <@SinSiXX> hiya
[21:47:59] <@Hale> prof didn't see the benefits from manual inspection so far, or rather didn't feel like it.. resulting in a few rather ugly frames in his encodes which could've been avoided withough filtering the crap out of stuff, but meh..
[21:48:16] <torque> lol.
[21:56:01] <@Hale> torgue - one tip I can give you after figuring out some weird problem I've been having here with a vertain episode - importing hundreats of freezeframe lines inserted manually for improved compressability can screw things up big time >_<'
[21:56:41] <torque> >__>
[21:56:46] <torque> that's kind of lame
[21:57:01] <@Hale> what's lame?
[21:57:17] <@Hale> freezing whole sections? ^^'
[21:57:23] <@Hale> :effort:
[21:57:23] <@Hale> =P
[21:57:59] <torque> the fact that spamming freeze frames causes it to screw up is lame
[21:58:36] <@Hale> it was only screwed up because I imported the freezeframes from the wrong episode
[21:58:45] <torque> lol.
[21:59:01] <@Hale> replaced stuff within motion and such
[21:59:02] <@Hale> xD
[21:59:03] <torque> I can see how that might cause a few problems.
[22:00:11] <@Hale> anyway.. I think the rest is up to you.. call again, if you can't figure out how the preset manager is supposed to work
[22:00:19] <@Hale> I'll go to sleep now
[22:00:41] <@Hale> fucking birds are singing again already >_>
00[22:00:58] <@SinSiXX> night