Using Interlace A Word of WARNING!

Grazie wrote on 5/30/2010, 12:16 AM

Just did a Lagarith Render. Used one of my existing Lagarith Templates in Render to New Track script. Noticed it was taking one helluva time to render an easy peasy slice. I tried this way and that . . no joy . . still dragging its feet . .hmmm???

I tried using the VEgas Render TO Track. Still sloooow.

Now I get real curious - I look at the final render and the field order had been switched - HAH!! Gotcha!!- Well I thought so . . .

I go through the Lagarith Template and all is as it should: LFF. This is wonkie . . .

OK, I'll start afresh with the UNCOMPRESSED Default and re-design it using the Lagarith CODEC using LFF and save. This time, it rapidly does its thing AND I retain the LFF.

Don't really need or wish to know why, but please check your Templates for any wayward interlace being having reversed field order . .

Recap: Template said LFF but rendered out as UFF. And before you ask, the Project is LFF, but still rendered out as UFF.
And the Media? Yup . . LFF too.

So everything was LFF until render.

Grazie

Comments

farss wrote on 5/30/2010, 1:16 AM

"please check your Templates for any wayward interlace being having reversed field order "

You checked the template yourself though and it said LFF but still rendered UFF.
Are you certain the script was using the correct template in the first place?

Bob.

Grazie wrote on 5/30/2010, 2:48 AM

. . and for that very same reason, Bob, I repeated the process twice to make entirely sure it WAS picking the exact same template.

Grazie

farss wrote on 5/30/2010, 4:23 AM

Then that's truly wierd. As I understand what you said in your original post the template said one thing but did another. So even checking the template itself is not enough, you have to check what it actually produces in the rendered output.

Either that or your change in source media made the difference.

Bob.

Sebaz wrote on 5/30/2010, 7:48 AM

Grazie, in doing some tests with Lagarith a few weeks ago I can tell that Lagarith has a bug for which it doesn't save what you check on uncheck every time. For example, multi-threading is unchecked by default, and I checked it when starting a new template in Vegas. Also I changed the default RGB to YV12. Then I saved that template as "Lagarith YV12". Later I wanted to make another template but with YUY2, so I opened a Render As dialog, chose AVI, selected the template I had done before and opened it, to find out that it was still on RGB and multi-threading was unchecked.

For what I've seen, the way to set Lagarith to what you want is not from Vegas, but to open VirtualDub in the same bit version that you will use it in Vegas (32 bit if you will use Vegas 32 bit) and set it from there to what you want. That's the only way it worked for me.

Grazie wrote on 5/30/2010, 8:11 AM

Interesting . . Thank you - g