The MaskTools.dll is enough. But really, you can do this without HQDering. Smoothd2 should be enough. I was just listing good filters to deal with the issues in your source, but you didn't have to use them all in the same script.

I would suggest filtering the sections with bad blocking by themselves (to avoid causing extra detail loss in other parts of the video) with a stronger settings for smoothd2, it's a process of trial and error.

Dext3r wrote:It definitely isn't, unless that's what I was sold at an anime convention.

I know I got sold a bootleg at a con... so unless you bought it at the official licensor's booth, it could still be a bootleg.

But anyway, instead of upscaling it like there was no tomorrow, you could just edit at a lower resolution.Code Geass was released on Blu-ray disc, so if you really want to edit at 720p or 1080p you could get that, it'll look better to boot (and would also actually have some more detail).

Dext3r wrote:It definitely isn't, unless that's what I was sold at an anime convention.

I know I got sold a bootleg at a con... so unless you bought it at the official licensor's booth, it could still be a bootleg.

But anyway, instead of upscaling it like there was no tomorrow, you could just edit at a lower resolution.Code Geass was released on Blu-ray disc, so if you really want to edit at 720p or 1080p you could get that, it'll look better to boot (and would also actually have some more detail).

Wait what? I didn't upscale anything, I just fullscreened what I'm working with in premiere and took a screenshot.

In order to fullscreen, you are effectively resizing the footage to fit that screen. That's upscaling, if just for playback purposes and not in-source. Inflating the resolution is just going to make more obvious issues that can be less visible at a lower resolution. Ideally, if you're ok with that, you could downscale your footage to something like 768x432 or 704x396; it's pretty sad to do that in 2013, but when you downscale, you're going to blur and hide some of the artefacts, so it's an easy way out, though it won't suffice on its own. Assuming you can get the worst of it gone with smoothd2 and the rest with the downscale, it should looks somewhat decent even if small.

mirkosp wrote:In order to fullscreen, you are effectively resizing the footage to fit that screen. That's upscaling, if just for playback purposes and not in-source. Inflating the resolution is just going to make more obvious issues that can be less visible at a lower resolution. Ideally, if you're ok with that, you could downscale your footage to something like 768x432 or 704x396; it's pretty sad to do that in 2013, but when you downscale, you're going to blur and hide some of the artefacts, so it's an easy way out, though it won't suffice on its own. Assuming you can get the worst of it gone with smoothd2 and the rest with the downscale, it should looks somewhat decent even if small.

BasharOfTheAges wrote:

Dext3r wrote: I just fullscreened what I'm working with in premiere and took a screenshot.

lol wut?

You're confusing the issue by using a preview codec + forced upscale. Show us your filtered source before you put it in premiere at the normal resolution it's at.

My fault, I didn't realize that was using a different codec and screwing everything up.

I had a long conversation with L33twad, and actually tried exporting and discovered it was something in Premiere's codec and apparently not at all in the original source (to my knowledge).

I'm now using a version of mvtools' mdegrain (which is incredibly slow and going to take days to convert all the footage).