One Eye Resized/Scaled

Scenario:
When left and right clips are married, one side is displaying more zoomed or magnified than the other. The clips play fine on the time line separately and the quicktime files look identical when viewed outside of Final Cut Pro.

We’ve seen this behaviour before with interlaced sources in progressive sequences (or vise-versa), or when “Range Check” is turned on or H.264 codec quicktimes are used directly in Final Cut Pro.  This issue is restricted to Final Cut Pro 6 or 7. After Effects, Motion and FCP X are unaffected by this behaviour.

The issue originates with FCP passing only one field at a time from interlaced sources to the FxPlug filter via an image well when the filter expects all lines. It likely means that the source footage is interlace (upper or lower field first) and the sequence is progressive (“none” for field dominance) or vise-versa. This issue can also occur if you attempt to use a non-standard editing codec in your sequence such as H.264, or FCP’s “Range Check” feature is turned on.

Possible Solution #1: Make all clips and sequences process as progressive instead of interlace

For best results select your clips and your sequence and then change the field dominance to “none.”

Then re-apply any image well sources to remind the plugin that the source has changed. This will not affect the look of your interlaced source footage but simply trick FCP into handling each frame as a frame and not as separate fields.

Possible Solution #2: Transcode H.264 sources to ProRes 422 and use ProRes422 as the sequence codec

Ensure that you are using ProRes422 or another common FCP video editing codec in your sequence settings.
If you have imported H.264 quicktimes directly from a camera you should transcode them to ProRes422 (any variant) using Media Manager or Compressor.

Possible Solution #3: Turn off FCP’s Range Check feature

FCP’s “Range Check” will alert you when your luminance or chrominance levels exceed broadcast standards. This feature disrupts the normal operation of Stereo3D Toolbox and should be turned off from the VIEW menu.

Some have asked why we can’t just scale the interlaced source from within the plugin. We could easily do that, but it would be at the expense of processing speed and image clarity. It is much better to feed the plugin full frame sources so there is no scaling necessary.

Rate this Article 1 Star2 Stars3 Stars4 Stars5 Stars
There's been 6 Ratings so far
Support Ticket Banner

7 Comments for One Eye Resized/Scaled

  1. Tony says:

    When I do this, my video looks badly interlaced. If I set the clips and the sequence to upper(odd) things look great, but that annoying warning comes up constantly. I clicked the button saying “do not warn me of this” but it still pops up over and over again.

    Please help.

    Tony

    ADMIN NOTE: Please see this Knowledge Base article to download a temporary fix for this issue.

  2. Allynn says:

    Same problem as Tony.
    My video is ProRes 422. It comes in as upper field. If I change it to None, I get the error message. If I keep it as Upper, I get the error message. I’ve tried it with the Sequence set to None and to Upper. Either way I still get the error message.

    FCP seems to want to output the video but the error message won’t go away! I managed to successfully output a short piece at work yesterday but no luck at home today.

    ADMIN NOTE: Please see this Knowledge Base article to download a temporary fix for this issue.

  3. Tim Dashwood says:

    We have received multiple reports of the issue with the alerter message continuing to pop up in v3.0 of Stereo3D Toolbox LE, even when “Do Not Show Again” is checked. We are looking into the bug and I will post a comment here when we have fixed it.

    The FxFactory Alerter shouldn’t pop up at all if both your source footage and sequence field dominance are set to “none”. Please select all sequences and clips in your bin and try that first as shown in the screen grab in the article above.

  4. Tim Dashwood says:

    Also, please remember to re-apply any image well sources into the image well after changing its field dominance as FCP isn’t very good at propagating the update through the filter.
    We also highly recommend the nested sequence method when working with FCP 6 or 7. It will save you many headaches. The instructions for this method can be found about 17 minutes in to this tutorial video: http://www.dashwood3d.com/help/getting-started-with-stereoscopic-3d-material/

  5. Tim Dashwood says:

    Please see this Knowledge Base article to download a temporary fix for the continuous alerter issue discussed above.

  6. Allynn says:

    Tony (and Tim!)
    I managed to get it working yesterday by starting a new project, importing the original footage and IMMEDIATELY changing it from Upper to None. I think FCP got a bit confused on the original project and it or the plugin was just always going to see it as an interlaced problem! So… that’s my fix.

    Definitely going to try the nested sequences next time. I couldn’t quite figure out how to do it (and I was too impatient to watch the video!).

    How long should it take to export and uncompressed QuickTime for about 20 minutes of ProRes 422? It took me about 4 hours and the file was around 24 gig. I figured it was easier to export the whole thing and bring it back in to cut it into clips. I was shooting on two Canon Vixia’s and I didn’t want to stop and have to re-sync.

    Here’s my very first attempt:
    http://www.youtube.com/watch?v=0CxCeL43SeY

    And Tim, I’m loving this!

  7. Edwin says:

    I had a lot of problems myself with the stability of the plugin. Zoom on the right imagewell, none applied adjustments when standing still on your seqience and adjusting disperity.
    All the first suggestions were not my problem.
    Thanks to the dedicated help of Ryan Alexander who, even though we are 9 hours apart in timezone ( I am in Europe ), he found out that it is the Range Check that did the trick in Finsl Cut Pro 6.06. Shortcut Ctrl-Z.
    ( Running Snow Leopard on iMac i7 )
    Searching the internet I found out that other people have also trouble in FCP wirh other filters and/ or plugins. So I guess its a FCP bug. Nothing to do with Dashwoods plugin.
    Thank you Ryan.
    Regards
    Edwin

Leave a Comment on this Article

*