Edius Double Vision Problem

[Mike Truly]

Edius5.01/NX HDV + exp

I have written about this problem before and it still plagues me. I am currently up against a deadline and will have to deliver with this flaw since there doesn't seem to be a fix that I can find... quickly.

I have some 1280x720 animation frames... we'll call this sampleA.

I make them into a 1280x720 29.97 HQ... we'll call this sampleB.

I bring this HQ into a 1280x720 29.97 over 59.94 project.


I place it on the timeline. I edit for days. At some point (not sure when or how), the HQ file starts playing back on the timeline with double vision.

(It happens that my current project is the perfect example in that there are telephone poles in the shot that move by rapidly and unfortunately... they show this flaw enormously).


If I take the SAME HQ clip and place it on the timeline down on the end beyond the edit... I can scrub through that clip and there is NO double vision. If I go back and scrub the clip where it lives in the edit... there IS double vision.

If I view the original animation frames... NO double vision.
If I view the resulting HQ... NO double vision.
Same HQ within the edit... DOUBLE VISION.

Naturally... when I go to render out the final delivery HQ from the edit... I get double vision in the resulting HQ.

I have some sample images to show but Edius kindly made JPGs that are somehow corrupt and I have to re-make them. Will upload in a bit.

Thanks!

[plasma_video]

Has the field order on that edited clip somehow been changed?

[Mike Truly]

Thanks for the ideas!

The field order on the clip within the edit (double vision) is Progressive and is the same as the same clip added beyond the end of the timeline which plays without double vision.

I have placed the good clip directly above the bad clip and it is playing without double vision. I am rendering out currently... we'll see.

Thanks again.

[GrassValley_BH]

Also check the position of any cuts/edits. Since you're not working in the native timebase of the clip, putting cuts "between" frames can sometimes cause issues.

[Mike Truly]

OK... the render came out fine so I can deliver without double vision. Whew!!!

[Mike Truly]

Brandon,

Thanks for the ideas!

I assume you mean that because it's a 29.97 clip over 59.94 that weird edits can cause problems.

My animations are rendered at 30fps originally and then output as 29.97 HQs. I am using the most appropriate Edius project setting aren't I? I have also used these 29.97 HQs in 59.94 projects (which I guess is kind of the same thing?).

When I render out my 30fps animations from my compositing app as 29.97... I could instead render out as 59.94. Would this avoid weird edits?

Thanks again.

[GrassValley_BH]

Though EDIUS should just be frame-doubling on import to the timeline, rendering out as 59.94 from your animation program should give the smoothest motion and reduce potential visual oddities.

However, if your intended output is 29.97p, and not 59.94p, then it might introduce visual oddities. Your situation is a bit of a tough cookie...

[Mike Truly]

Thanks for the info Brandon.

My animations are rendered at 30fps. I can render to 60fps but it adds a HUGE logistical hassle to the pipeline in the form of increased render time and frame storage. So I'll be sticking with 30fps for now.

My intended delivery is a digital file delivered via the web so basically 30fps. But since Edius doesn't have a 30fps project setting, 29.97 is the closest to 30fps. So for now... it sounds like I am using the best settings possible.

Thanks again.

[antonsvideo]

would 24p be an option?

[Mike Truly]

Anton,

Thanks for the ideas. It is possible... but I would probably rather stick with 30fps and have a few more frames of motion resolution for these technical animations. In the end... I may have to bite the bullet and move towards 60fps when the motion resolution is critical.

But I would definitely love a 30fps project setting.

Thanks again.

[Mike Truly]

This drives me Bonko. I am having this problem again and can't seem to make it stop.

See the attached images. The first image shows the clip as it's in the edit. The second image shows the SAME clip but further down on the timeline by itself. The first shows extreme double vision, the second shows the perfect clip with no double-vision.

Not sure why this is and in my notes as to how I solved this last time... well... there are no notes dangit!

[SRsupport]

It is not the same image . So it is hard to compare.

[Mike Truly]

Totally bizarre. I fixed it... not sure why this fixed it but here's what I did.

The edit is very simple and setup like this: There is a video clip on V2 and the problem clip is on V3 directly above it. Both clips are the same length and aligned and the V3 clip has it's IN POINT slid right so that you see the V2 clip for a while then dissolve to V3 clip.

I have an obnoxious hot pink TGA that I use for temporary filler. I copied the hot pink still and replaced the V3 clip with the hot pink. Then I copied the problem clip and replace the hot pink with the problem clip.

Now when I scroll the timeline through this area, the problem clip no longer displays with double vision and is now fine.

Weird.

[Mike Truly]

Well... I sort of fixed it. The V2 clip also exhibits the double vision problem and my replacement method does not stop the double vision happening there (but it is much less noticable because of the subject matter).

Steve, although the two samples I posted may be one or two frames off from one another... you can clearly see the double vision I'm talking about. They are the same clip in two different locations on the timeline. One shows severe double-vision and the other does not. The animation frames show no double-vision (like the second image) but Edius is introducing the double vision effect (even though there are no effects/speed changes added to the clip).

Edius shows the HQ clip properties as 30fps even though the clip was rendered out at 29.97fps. Changing the framerate to 29.97fps in the properties makes no difference.

[antonsvideo]

where are you seeing the double vision? external mon? edius preview mon?

is your pause field set to field or frame?

is your overlay method set to field or frame?