Forum Replies Created

Page 1 of 2
  • Nick Schlott

    April 18, 2016 at 6:55 pm in reply to: Uninstalling QuickTime/Windows

    Adobe has a blog post up about this. You can actually use some QuickTime features in Premiere/Win without having QuickTime installed, something Adobe has been working on for years and adding more support where possible over several versions.

    https://blogs.adobe.com/creativecloud/quicktime-on-windows/?segment=dva

  • Nick Schlott

    November 12, 2014 at 12:50 pm in reply to: Rendering in Rec 709 From Premiere Pro

    REC 709 color space is for HD sized material; SD sized material uses REC (formerly CCIR) 601 color space. https://en.wikipedia.org/wiki/Rec._709#Primary_chromaticities

    Premiere/AME will render anything larger than SD in REC 709 colors. ProRes supports 709 (as you’d expect) and Premiere will mark the color space in the QuickTime container with the correct primaries, so there’s nothing to set. Pretty much any container Premiere would export at HD size will be either explicitly or implicitly REC 709, although some older containers (e.g. MPEG-2) have export settings to allow you to change the color primaries in the export settings, though I can’t imagine why you would.

  • So on the same system, with the same footage, using CC 2014.0, ProRes imports just fine?

  • Nick Schlott

    September 24, 2014 at 12:00 am in reply to: bad fps export, no matter what

    Yes, it probably would explain the powerpoint case: if the powerpoint .mov has long duration frames at the start of the file, Premiere will probably not be able to determine the frame rate. That’s not a case I’ve heard of, though. And powerpoint exports .avi on Mac and .mov on Windows? That sounds backwards!

  • Nick Schlott

    September 23, 2014 at 10:57 pm in reply to: bad fps export, no matter what

    “Seems to” is the key here.

    What’s going on is that QuickTime doesn’t *have* a “frame rate” per se. Every frame in a QuickTime movie can have any duration. Premiere/AME take advantage of that when Optimize Stills is turned on. What this does is permit the QuickTime exporter to aggregate frames that do not change over some long period (stills, black video, etc) into one long-duration frame.

    Why is this useful? Bandwidth and export speed. If you have fewer frames in a file, the file size is smaller. And if you stuff fewer frames into a file, it exports more quickly. A useful example is to drop, oh, 100 1-second still images into a timeline. Export with Optimize Stills turned on, then turn it off and export again. The former file will contain 100 frames of the correct durations. The latter @ 23.976 fps will contain 2398 frames and will export more slowly and be a much larger file.

    The drawbacks of Optimize stills is as you saw some utilities will get confused about the frame rate (even Pr will in some cases, if the first few frames of the file are long-duration frames). The 100-still case above exported @ 23.976 will appear to QuickTime Player to be a 1fps file. And it actually is in some sense, but not in any very meaningful way: the video is all there and cut at exactly the times you chose. That said, some hardware players will get upset if you feed them files with a variable frame rate, so it can be important to turn off Optimize Stills for them, or if you really and truly want all those duplicate frames in your final file.

  • Nick Schlott

    September 23, 2014 at 9:03 pm in reply to: bad fps export, no matter what

    Turn off “Optimize stills”

  • ping me at nschlott at yahoo dot com and we’ll figure something out.

  • OK, I think I get what you’re doing. Let me think about this; I can’t promise anything because we really like not making illegal DV, I’ll consider some sort of workaround. Can you please send me a file that’s *exactly* what you want to use? It doesn’t have to be long, a few seconds will do.

  • Oh, wait: is the DV video not for visual reference, but actually the clock that ProTools wants to reference, either as timecode or just reference time? Is that why it’s there?

  • Hi, Chris. I guess you’re getting me on the right track, but I’m not there yet.

    So what is it you get from Hollywood? An already-i-process project of some sort, or some other pile of assets (in what formats?) ? That you then need to turn around and convert into something ProTools likes (meaning QuickTime DV 23.976 + I assume some audio, though maybe you’re adding all new audio yourself in ProTools).

    Then you do audio work in ProTools and while you’re doing it you need to monitor the video as DV. Right? (Why? Can’t you just look at the computer monitor? What am I missing?) I assume the DV is just throw-away reference video at this point that helps you refer to the video. It can’t be the final product.

    Thanks for your patience explaining this.

Page 1 of 2

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