Forum Replies Created

Page 1 of 59
  • Alan Lloyd

    December 13, 2016 at 11:39 pm in reply to: Transcoding to 3K for edit – is this dumb?

    Take a hike. A long one.

  • Alan Lloyd

    December 13, 2016 at 7:40 pm in reply to: Transcoding to 3K for edit – is this dumb?

    [Blaise Douros] “Why not proxy your footage in 1080p with something like ProRes LT”

    Most likely because a Z820 is an HP (Windows) machine.

  • Alan Lloyd

    December 13, 2016 at 7:36 pm in reply to: Shielded xlr cable/connector

    Have to agree, especially if there’s any dimmers involved. Audio interference and massive hum bars in the video signal to boot.

    Also, HD-SDI over non-spec cabling can cause interesting results with wireless audio. (Personal experience – it drove a couple of us, including a rental vendor, crazy tracking that source of interference down.)

  • Alan Lloyd

    December 12, 2016 at 11:19 pm in reply to: Jello Effect on backgrounds caused by Warp stabilizer

    Have you applied “Rolling shutter repair” to the clip in question?

  • Alan Lloyd

    December 11, 2016 at 9:31 pm in reply to: problems when using LED stage lights

    It’s the overly saturated blue. Or other color, for that matter. LED instruments are not continuous-spectrum, and while eyes see one thing, cameras see another.

    If you look at it on a vectorscope you’ll see the blue spiking, even to the point where the trace is outside the circle. (Illegal color.)

  • Alan Lloyd

    December 11, 2016 at 5:40 pm in reply to: Recording setup and editing advice.

    Unless all cameras will also be recording audio locally you might consider adding a single burst of a photographer’s strobe at the beginning as well. It will be on only one frame and make (visually) syncing up camera rolls rather simple.

  • Alan Lloyd

    December 7, 2016 at 12:11 am in reply to: Variable Frame Rate (VFR) Fix in CC2017?

    This is the second post (that I’ve seen this week) blaming Adobe for not fixing Apple’s shortcoming.

    The problem is not Premiere. The problem is Apple not making a fixed frame rate camera part of the iPhone.

  • By definition, a variable frame rate file is not professional quality.

    Apple could make their camera output fixed frame rate if they chose. Why blame Adobe for someone else’s inaction?

  • What is the footage from? Is it variable frame rate? (That is a known issue and has been for some time.)

    ETA: I reread your post. It’s from an iPhone, and yes, it’s variable frame rate. The problem is in your phone footage, not Premiere.

  • Alan Lloyd

    December 3, 2016 at 8:39 pm in reply to: Premiere Issues after a big upgrade

    CS6 is really dated. I know a lot of people don’t like the CC subscription model, which can get interesting at times, but 4K really would be a good reason to look into it.

    Bonus – you can upgrade both seats of Premiere (and Photoshop/Audition/After Effects/whatever else…) for the one subscription.

    The old boxes and CS6 are sunk costs. I’m guessing they’ve paid for themselves multiple times over at this point. HP Z-series workstations with RAID setups would be a nice upgrade path if you’re seriously considering such things.

    And refurbs of some of the Z-series an iteration older than current can be got for good price points. They’re extremely robust and will run just about forever. You can get them fairly bare-bones and kit them out with a lot of the components (new Quadro, etc.) from your current, older machines by some careful cannibalization.

    But do look at the CC option. CS6 is really not built for 4K material. That first, and I’d recommend the 2015.x version rather than the new 2017, which seems to still have a few issues.

Page 1 of 59

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