Blog

I have used this for years.  Here are some things I learnt and re-learnt today, about and around it:

• Deshaker’s main forum is http://forum.doom9.org/showthread.php?p=1418923
• Deshaker is used as a plugin to VirtualDub.
• VirtualDub can’t directly read XDCAM-EX files.
  • One way round this is to transcode to an AVI format.
    • I traditionally use Cineform (CFHD).  In Sony Vegas, when rendering-out to this from a 720p50 Project single XDCAM-EX .mxf file of 720p50 footage, the result when viewed in the original project has a weird effect where the image only advances every two frames.
      • This does not occur for larger Projects, reason unknown (need to experiment, but maybe ? it’s because because larger projects tend also to contain media in other formats?).
    • So instead on this occasion I render to HuffYuv.  Larger but lossless and no (obvious) issues.
    • After every such render, check for the “doubled-up frames” issue, e.g. in case accidentally rendered to unintended format.  Mistakes happen, especially when under pressure of long hours…
• The result, from VirtualDub, can be saved to AVI formats e.g. Cineform (CFHD).
  • If saving to CFHD then be sure to specify RGB mode (in the codec’s dialog), this preserves the levels in 0..255 (”Computer”) range, otherwise (default non-RGB) it scales to 16..235, giving a washed-out appearance when viewed back in Sony Vegas.

Using Boris RED 4.3.3.1502 on Windows, mostly as standalone (Red Engine).  Today, wanted to apply it as a stabilizer.  Have done this a long time in the past, for AVI files etc., but this is the first time I have seriously tried to apply it to to XDCAM-EX footage, of 720p50 (intended for a PAL DVD 576i50 deliverable).   Summary:

• Warnings:
  • Boris can’t be used in Sony Vegas for other than static effects, hence not for stabilization (a dynamic effect).
    • At least, not without a workaround of debatable overall advantage (explained under “More”).
  • Boris doesn’t recognize Sony XDCAM ClipBrowser’s “MXF for NLEs” format, but does recognize Cineform AVI (no need to be QT).
  • When altering any settings, Boris defaults to keyframing them.  Right-click the funny symbol and change it to Constant.
  • Have to double-check the compression settings, including the codec’s own dialog (their defaults are not always good and they can change “automatically”).
  • Boris can export 720p50 as QT-CFHD but, as far as I can tell, Sony Vegas cannot (it can only export such CFHD as AVI, though thankfully Boris can read that).
  • Boris doesn’t use multiple CPUs it seems.  Unlike DeShaker - of great advantage for such lengthy (CPU-heavy) processes.
• Instructions (in Boris):
  • Delete existing tracks, drag-in the source file, de-select its tracks (audio & video), Menu: [Filters > Time > BCC Optical Stabilizer], select the Stabilizer track.
  • In Controls change Mode from default [Setup region] to wanted [Smooth], twirl-open the Stabilizer track, drag video track onto its Input Layer.  Also increase Smoothing Range from default (30 frames) to 1 or 2 seconds-worth (in my case 100 since footage was 50 fps).
  • Click Preview’s [ >>| ] ”Go To End” button.  This causes motion analysis to begin.  Takes ages…  Likewise, don’t bother playing it…
  • [Menu: File > Export > Movie File].
    • Initially generate a quick draft to check the stabilization is as required:
      • Temporarily set 25fps, choose [Fast]
      • Select a limited region (I/O) for export.
    • Regardless, in compression dialog, if Cineform is used then select Quality = Medium (not Best or High which are overkill).
• Links:
  • Tutorial on YouTube: http://www.youtube.com/watch?v=q53YmSuz5uA
  • New (to me) forum: http://www.pigsfly.com/forums/index.php?s=48265a27e235c75b30ce35270c3935a6&showforum=70

(more…)

Problem:

• In Windows I export from Sony Vegas to AVI (CineForm).  In OS X I read the file into FCP and apply the SmoothCam effect, then export to ProRes.  In Windows, Sony Vegas, I replace the original file with the smoothed one.  The levels/gamma are wrong.

Solution (Search):

• Sony Vegas forum http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=718371
  • Use DNxHD
    •  Couple of tips re DNxHD:  709 color level assumes 16-235, and RGB assumes 0-255.
  • Force it back again: www.kenstone.net/fcp_homepage/gamma_mac_pc.html
    • But this presumably implies getting re-quantized twice (the roundtrip issue and the forcing), which for 8-bit footage I imagine could reduce the quality (banding).
• Uncertainties
  • Where and how does this gamma get applied?  In FCP I didn’t (knowingly) alter the levels (eg until it looked right), I just applied the SmoothCam filter.  So I guess it would look wrong on the (pre-SnowLeopard) Mac but I wouldn’t care.  Wouldn’t FCP then export back whatever it got but smoothed?  This one is really confusing.    Experiments needed (when I get time…) I guess.

Context:

• In FCP I imported [File>Import] a CineForm AVI file residing on an NTFS disk.   It showed up in FCP’s browser OK.  I dragged it to Viewer and it played there OK.  I dragged it to timeline and it displayed there as a clip i.e. as a long pale-green block.

Problem:

• When I tried to play teh timeline the Canvas screen remained blank.
• Also the timeline clip-block had no thumbnail (which, given my configuraton of FCP, I would normally expect)

Interpretation:

• Mac support for AVI is said to be half-hearted.  This is probably what is happening here.

Response:

• Try re-wrapping the Cineform AVI file as a CineForm MOV file.
• This can be done via Cineform’s bundled tools as follows:
  •  On the PC by using HDLink
  • On the Mac by using ReMaster
• (I have not yet tried this)

According to CineForm NEO HD FAQ [http://techblog.cineform.com/?cat=69] as of 2009-05-05:

“Color does NOT support QuickTime codecs. Instead, Color only allows
certain codecs that have been compiled into the code to be used.  Apple
is aware of this limitation, but they haven’t been to quick to solve
the problem.”

Whaaaaat!?!?!   If so then that’s astonishing(-ly uncool).

On the Mac, Cineform uses the QuickTime wrapper, hence:

“CineForm files currently do NOT work in Apple’s Color application.”