Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Boris FX avid mc, boris red 3 – an external photoshop file – interlace jitter

  • avid mc, boris red 3 – an external photoshop file – interlace jitter

    Posted by Alius Sato on March 4, 2009 at 6:14 am

    i’m experiencing quite a weird interlace-jitter issue:

    a PSD, if imported straight to avid as a matte key, looks ok:
    avid matte key

    if i put a boris effect on the track, then import the same PSD as the content of a 3d track, i get garbage:
    same psd via boris red

    the problem only shows up if i use the “highest quality” video setting on avid (green button), but it DOES exist in exported quicktimes as well.

    i noticed the problem first on a 23.976pA dvcpro50 project (that on avid is 30i), but now that i’ve played with it it seems that the problem persists across different project types.

    i’m on a pc MC 3.0 – the images above are screen grabs of avid’s full-screen playback with the “prt sc” function. ignore the squares, they’re on the alpha channel that the two apps handle differently.

    i’d really like to use boris on this project as i need complex moving graphics, but…

    Alius Sato replied 17 years, 2 months ago 3 Members · 12 Replies
  • 12 Replies
  • Peter Mcauley

    March 4, 2009 at 3:43 pm

    Hi,

    It’s unclear to me whether you are pulling the media into RED from the desktop or from an Avid bin but either way, here’s something to try. Go to the RED 3 preferences window (edit>preferences) and click on the import media tab. Set the Interpret Field Order to “None” and see if that solves the problem for you.

    Cheers,

    Peter.

  • Alius Sato

    March 4, 2009 at 10:04 pm

    just to clarify – i’m pulling video tracks off of the avid timeline, but adding overlay graphics that come from the desktop as .psd files.

    no – the settings you refer to don’t seem to remedy this. i have played with them quite a bit, and they seem to have no effect.

    besides, the import setting is separate for still image files & movies – & the still image one doesn’t have interlacing / field interpretation options – yet the problem is most noticeable on imported graphics with text as per my sample images (that, when resized to this page don’t show it as clearly as they do in their native size).

  • William Busby

    March 5, 2009 at 3:17 am

    If I were you I wouldn’t be importing graphics with text, and I’d build the complete graphic in Red using to import the original media files PLUS use Vector Text in Boris for the titles. Much cleaner & wouldn’t have the problem I see here.

  • Alius Sato

    March 5, 2009 at 4:17 am

    william – i concur /w you in principle & would do so if the workflow/schedule with graphics coming from a 3rd party source would so permit.

    however, what i’m experiencing is not a matter of slight deterioration that would be caused by pixel-source-graphics/type, it’s severe wreack-havoc type of thing that is caused by something else. just to confirm, i just created a title in boris and tried that too – same exact problem persists.

    another thing that i’ve probably failed to mention earlier- the damage is only visible when the footage is actually playing. if the playhead is parked all appears good.

  • Alius Sato

    March 5, 2009 at 5:02 am

    hey william – i concur, that’s what i’d do if it wasn’t for the graphics templates coming as flat .TIF from a 3rd party graphics house.

    but that’s not even the point, the problem i’m experiencing is beyond slight deterioration of pixel-generated type.

    just for the kicks, i just did a version where the text came from borisRed’s vector type – i see the same exact issue.

    one thing that i may not have mentioned earlier – if the playhead is stopped, the type appears fine on the still frame – it only falls apart when playing the footage.

  • William Busby

    March 5, 2009 at 7:36 am

    Sounds like field reversal or something. Did you try what Peter suggested?

  • Alius Sato

    March 5, 2009 at 2:28 pm

    i did try what peter suggested. no jive.

    the other interesting thing i’ve found out now is that this problem does not appear on a PAL 25i project. which reminds me that most projects where i’ve used boris red extensively in the past were PAL, so i wouldn’t have necessarily ran into this before.

  • Peter Mcauley

    March 5, 2009 at 2:50 pm

    I just noticed that you mention using RED 3 … have you tried this with RED 4? It may be a problem with RED 3 and Avid MC 3 – sometimes Avid makes changes to the AVX code and when that happens sometimes we can wind up with field reversal problems. I’d like to suggest downloading the latest trial version of RED 4 to see if that helps remedy the situation.

    Cheers,

    Peter.

  • Alius Sato

    March 6, 2009 at 4:27 am

    oops – i misremembered, the boris red on the system is version 4.03.

  • Peter Mcauley

    March 6, 2009 at 12:26 pm

    And what happens if you render the file using the RED standalone render engine? Is it free of the jitter that you are seeing when using RED as a plug-in to the MC?

    Thanks,

    Peter.

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy