Forum Replies Created

  • Wow. 2160p@59.94 is pretty exotic. Uncompressed and assuming you’re only at 8-bits-per channel…

    3840 [frame width] * 2160 [frame height] * 8 [bits per channel] * 3 [channels per pixel] * 59.94 [frames per second] = 11,931,992,064 bits per second. Divide by eight and you have 1,491,499,008 bytes per second. Even getting Premiere to play a single layer of uncompressed video at 1.5 gigabytes per second would be pretty impressive. After Effects? Forget it.

    Even if you’re using one of the many formats that run video at less than fully uncompressed rates, it’s still going to be a tall order for something like After Effects that wasn’t designed for realtime anything. And the raw brute speed of the storage subsystem and the amount of RAM you need on the graphic card for that is daunting, as is moving all that data across the system busses… it’s kind of dizzying to think about.

  • Mike Jennings

    April 27, 2011 at 7:31 am in reply to: templates and variable text fields

    I needed to do something similar. That was incredibly helpful, thank you for that suggestion.

  • Mike Jennings

    May 23, 2008 at 1:42 am in reply to: CS3 P2 Project Settings again

    Use the Premiere Pro settings now. They’ll process YUV and high bit depth when possible (some of the older filters force it to 8-bit (but who uses those anyway?) — the filters written expressly for Premiere Pro like the color correctors won’t degrade the image. (Note that your source is 8-bit, BTW.)Also, you’ll get realtime performance, dynamic link support and so on. At this point there’s no advantage to Raylight or anything else.

    If you’re really hell-bent on processing uncompressed, simply go into the Video Rendering panel of the Project Settings and set the codec to QuickTime (Mac) and choose your codec, or choose an uncompressed codec on Windows.

    Oh yeah — There’s a setting in the Render Panel of the project settings called “Use Maximum Bit Depth”. If you check that, and everything in the “signal path” supports it, it will do its processing in 32 bits, or at least the highest bit depth available given what’s in the timeline. It’s a bit slower and will hamper realtime previewing, but you wouldn’t get that anyway if you change the render codec.

    Finally, why render out to After Effects at all? Just import your Premiere Pro sequence to After Effects and you can drag the sequence in as a layer, unrendered.

    –Mike Jennings

  • Mike Jennings

    May 23, 2008 at 12:19 am in reply to: CS3 P2 Project Settings again

    Time base should be 29.97fps, not 30. And you might try emulating the frame sizes and aspect ratios from the default presets.

    But I have to ask — why in the world would you want to do it that way? It’s a terrible workflow. You have a crappy choice of codecs for preview renders (Well, at least on Windows), and the processing is 8-bit RGB so no YUV processing. And you’re scaling everything you bring in so it will take forever, you get no realtime performance, and consume tons of disk space.

    What’s the upside?

    –Mike Jennings

  • Something is messed up on the system. I don’t know why .prproj files would be associated with Encore. I can tell you firsthand that Premiere CANNOT write Encore files.

    Try opening them with File > Open from within Premiere.

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