Forum Replies Created

Page 1 of 3
  • Bjørn Holmgren

    January 7, 2011 at 9:51 am in reply to: Faster/More Responsive Jog Device

    You could try the logitech revolution mouse – the mousewheel is free-running and works very well as a jog controller. Just place the mouse pointer over the canvas or viewer.

  • Bjørn Holmgren

    April 18, 2009 at 8:12 pm in reply to: Nesting FX FCP

    There is several ways to do this. One is to create a white color solid, place it on the track below the pip fill, crop it to the size of your pip. Then modify the composite mode of the pip fill to travel matte – luma.
    Resize to your favored zoom level.

  • Bjørn Holmgren

    March 6, 2009 at 5:36 pm in reply to: Image changes when play head is stopped

    This might be FCP misinterpreting the gamma of the material. It might be a codec conflict between AJA or Black magic and the Apple uncompressed codec. I haven’t seen this in a long time, though. If you have one of these capture cards, try removing the codec you don’t use temporarily and see if that solves it.

  • Bjørn Holmgren

    January 16, 2009 at 11:17 pm in reply to: system for working with 3/4″ tapes

    I would try to get my hands on a TBC (Time Base Corrector) for the 3/4″ player. Both Digibeta and capture cards can be unforgiving about horizotal timing in the video signal, resulting in wavy vertical lines in captures from analog tape.

  • Bjørn Holmgren

    November 17, 2008 at 9:24 pm in reply to: XML Unicode problem

    The problem is probably either the encoding or the line endings. Windows uses CRLF, Classic Mac uses CR and unix uses LF. Get yourself a better text editor for your mac (TextWrangler, Smultron and SubEthaEdit are all good), open the files and save them as Unicode (UTF-8) and with Unix line endings.

  • Bjørn Holmgren

    November 12, 2008 at 9:44 pm in reply to: Preserving Superwhites, 100-108 range

    16 bit image sequences are fine, which leads me to believe that the cause is incompatibility between later versions of QuickTime/FCP and Shake. This trouble started with FCP Studio 2.
    You can still fix the FileIn with Force8bit, but of course you loose the extra 2 bits of precision that way.
    Or use a G5 🙂

  • Bjørn Holmgren

    November 12, 2008 at 8:28 pm in reply to: Preserving Superwhites, 100-108 range

    At first it was only output, you could fix it with a Bytes node set to 8 before output. But now input is also broken.
    This image shows a PAL 10 bit colorbar:

  • Bjørn Holmgren

    November 11, 2008 at 4:14 pm in reply to: Preserving Superwhites, 100-108 range

    What you’re experiencing is the conversion from Y’u’v’ to RGB in QuickTime. The standard codecs have no options for level mapping, so your superwhites will get clipped when you import to Shake.
    You could try the SheerVideo codec from Bitjazz, it has options for how the mapping should be done.
    I just hope you still have a G5 for Shake, as 10 bit is currently broken in Shake on Intel.

  • Bjørn Holmgren

    January 24, 2008 at 5:27 pm in reply to: Quicktime 7.4: Install at your peril.

    The quality control at Apple is quite bad at the moment. 10-bit rendering in Shake is still broken after nearly a year, and now this issue…
    iTunes/iPhone/Movie rentals is probably more important to Apple than the Pro community.

Page 1 of 3

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