logo Sign In

GOUT image stabilization - Released — Page 42

Author
Time

@Chewtobacca

It's nice that the PAL ROTJ master was better, but some of us aren't in a position to obtain the PAL DVD and we have to "make do" with the NTSC release.  As such, has anyone even tried to take a crack at modifying this script for the NTSC version?

There are 10 types of people in this world: those who understand binary, and those who do not.
Author
Time
 (Edited)

rockin said:

Out of curiousity what is the average processing time for this script on a quadcore computer?

I'm currently looking at 32 hours.  I'm using an AMD Athlon II quadcore, 2.9 GHz, with 4GB RAM.  I also have an ATI Radeon 5770 graphics card which, under Windows 7, takes advantage of DirectCompute 11 (i.e., the graphics card takes on some of the processing tasks), which is supposed to be beneficial for such things as encoding.

Prior to this system, however, I was looking at a 6-7 day encode.

Edit: Oops, looks like I was only looking at the time for the first pass.  I guess that means I'm really looking at 64 hours :(

“It’s a lot of fun… it’s a lot of fun to watch Star Wars.” – Bill Moyers

Author
Time

Tip - render to an lossless AVI first (if you have the space), then use that as your source for your multipass encode.

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time

corellian77 said:

rockin said:

Out of curiousity what is the average processing time for this script on a quadcore computer?

I'm currently looking at 32 hours.  I'm using an AMD Athlon II quadcore, 2.9 GHz, with 4GB RAM.  I also have an ATI Radeon 5770 graphics card which, under Windows 7, takes advantage of DirectCompute 11 (i.e., the graphics card takes on some of the processing tasks), which is supposed to be beneficial for such things as encoding.

Prior to this system, however, I was looking at a 6-7 day encode.

Edit: Oops, looks like I was only looking at the time for the first pass.  I guess that means I'm really looking at 64 hours :(

Damn. That is pretty long. I have done renders before in both Premier and Vegas which took 15hrs for things but 32?!? Damn. Don't think I could cope with all my processing power being used for 32hrs on a render - need to use my comp for lots of other things as well.

Hmm, all the more excuse to upgrade I guess. This old thing has done me proud for a number of years. It's only logical I also get me something new that lasts me as long.

Has anybody tried this script on an Intel i7/i5/ or AMD Phenom X6? Would be interesting to know peoeple's processing time with those.

Author
Time

MJPollard said:  @Chewtobacca  It's nice that the PAL ROTJ master was better, but some of us aren't in a position to obtain the PAL DVD.

Why?  Can't you ship the PAL disc?  It wouldn't cost that much.  I'm not sure why that was addressed to me, but, to answer your question, to the best of my knowledge no one has modified the script to work with the NTSC version.

Author
Time

Moth3r said:

Tip - render to an lossless AVI first (if you have the space), then use that as your source for your multipass encode.

Thanks for the tip Moth3r.  I am following Oldschooljedi's instructions, so at what point in the process would I create a lossless AVI?  And how would that affect following the rest of the instructions as given?

“It’s a lot of fun… it’s a lot of fun to watch Star Wars.” – Bill Moyers

Author
Time

After you've created and saved the script, open the AVS file with VirtualDub. Using a lossless codec for video compression - I recommend Lagarith - save the video as an AVI file. This will take hours but you only have to do it once.

Now run your MPEG-2 encoder, and select this AVI file as your source. You'll find it speeds along for both passes, because the heavy AviSynth processing has already been done, the CPU is only being used for decoding/encoding.

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time

Cool, thank you.  I'll definitely try this out when doing ESB.

BTW, HCenc is currently on its second pass and is giving me the following error message: "WARNING, small source mismatch found in pass 2, count: 40181 frames."  I hate to ask (as I think I already know the answer), but is that bad?

“It’s a lot of fun… it’s a lot of fun to watch Star Wars.” – Bill Moyers

Author
Time

I don't use HCenc, but I assume you want no errors at all.

Author
Time

corellian77, check "Reload Avisynth" or "use lossless intermediate file" under Settings 3. It should help.

We want you to be aware that we have no plans—now or in the future—to restore the earlier versions. 

Sincerely, Lynne Hale publicity@lucasfilm.com

Author
Time

Well, I had a go with the script last night, and followed the instructions from that guide but HCenc keeps crashing when I go to add the AVS script.

I am using Windows 7 X64 by the way, not sure if that plays a role in why it's doing that.

Author
Time

rockin, did you install avisynth for 64-bit Windows?  I had trouble loading the AVS script too before upgrading.  From what I understand, you need to install the regular avisynth first, then install the upgrade.

That being said, you can see from my posts above that I'm not exactly having the best luck myself, so take my posts for what they're worth :)  I tried these just for the heck of it, but it looks like I might be better off waiting on dark_jedi's versions.

“It’s a lot of fun… it’s a lot of fun to watch Star Wars.” – Bill Moyers

Author
Time
 (Edited)

Thanks for the help guys.  Like I said earlier, I just followed Oldschooljedi's tutorial, adding filters here and there when HCenc obviously was looking for something that wasn't in my plugins folder yet.  I've only got a few hours left before the encode is done, so I'll just wait to see what it churns out.

Aside from OSJ's tutorial, is there another, perhaps more current, set of instructions for applying gforce's script to the GOUT?  I'm pretty green when it comes to programs like avisynth, virtualdub, and so on, and a nice step-by-step tutorial would be grand for me and others of my kind (i.e., encoding noobs).

“It’s a lot of fun… it’s a lot of fun to watch Star Wars.” – Bill Moyers

Author
Time

Avisynth works just fine on a Windows 7 PC, I am running Windows 7 Pro 64 bit and have no issues at all.

Author
Time

Chewtobacca said:

MJPollard said:  @Chewtobacca  It's nice that the PAL ROTJ master was better, but some of us aren't in a position to obtain the PAL DVD.

Why?  Can't you ship the PAL disc?  It wouldn't cost that much.  I'm not sure why that was addressed to me, but, to answer your question, to the best of my knowledge no one has modified the script to work with the NTSC version.

That's what I wanted to know, thanks.

And to decode between the lines of what I said: some of us only have the NTSC version and don't want to spend money on a DVD we otherwise can't use.  Hope that's clearer. :)

There are 10 types of people in this world: those who understand binary, and those who do not.
Author
Time

MJPollard said:And to decode between the lines of what I said: some of us only have the NTSC version and don't want to spend money on a DVD we otherwise can't use.  Hope that's clearer. :)

Yes; it's clearer. By the same token, people in PAL areas are importing NTSC discs that they wouldn't otherwise use to implement the scripts for SW and ESB, but if people don't want to spend money on that then of course that's their choice.

Author
Time

Moth3r said:

After you've created and saved the script, open the AVS file with VirtualDub. Using a lossless codec for video compression - I recommend Lagarith - save the video as an AVI file. This will take hours but you only have to do it once.

Quick question: I downloaded both VirtualDub and Lagarith.  I installed the Lagarith codec (I believe, anyway... it created a .dll file in a Windows sub-directory).  I then installed and ran Vdub, and started the conversion into a lossless AVI as you suggested.  My question is, is Vdub using Lagarith automatically?  Or did I have to instruct it to use it somehow?

“It’s a lot of fun… it’s a lot of fun to watch Star Wars.” – Bill Moyers

Author
Time
 (Edited)

Or did I have to instruct it to use it somehow?

Yes; you did.  Video-->Compression-->lagarith lossless codec

(After this I also select Configure-->Mode:YV12 to be sure but it might not necessary with Fast Recompress.)

Then make sure Fast Recompress is checked under the Video tab.  If you use full processing mode, you will trigger a conversion to RGB.

Author
Time

Thanks Chewtobacca.  So instead of telling VDub to use Lagarith, it was left defaulted to "Uncompressed RGB/YCbCr."  Is this better/worse than having used the lagarith codec?  "Uncompressed" sounds like it would be ideal, no?  (btw, the file size looks like it'll be around the 160-170GB mark by the time it's done).

“It’s a lot of fun… it’s a lot of fun to watch Star Wars.” – Bill Moyers

Author
Time

Uncompressed = no compression, huge files.

Lagarith = lossless compression, identical in quality, but smaller files (guessing around 60-80GB).

Guidelines for post content and general behaviour: read announcement here

Max. allowable image sizes in signatures: reminder here

Author
Time

Thanks for the info Moth3r.

“It’s a lot of fun… it’s a lot of fun to watch Star Wars.” – Bill Moyers

Author
Time
 (Edited)

Moth3r said:

Uncompressed = no compression, huge files.

Lagarith = lossless compression, identical in quality, but smaller files (guessing around 60-80GB).

When I encode to an avi file, will I have to split the encode into smaller files or can I make a single 80 GB file? I encoded the GOUT with one of g-force's older scipts and HCEnc last year, but encoding of one episode took about one week. I would make encodings with the newer script but only if encoding would not take so long. So I should encode the movies to avi but I'm not sure, how the HDD would handle so lage files without splitting.

Author
Time

How are you getting an 80 GB file? my Lag files range from 22-24 GB's.

Author
Time

You could tell it to only run the script for a certain number of frames, mpeg2 encode each segment individually and then join them afterwards with a program that can do that seamlessly.  Could save you a good deal of space that would otherwise be used up on the huge intermediate files, not to mention put less wear on the drive itself.