Forum Replies Created

Page 2 of 6
  • Matthew Ross

    February 1, 2019 at 9:12 pm in reply to: Exporting Tall Videos

    Yeah, I’m seeing the iPad 4 not capable of H.264 above level 4.1. So it looks like that approach is a non-starter with that device:

    “H.264 video up to 1080p, 30 frames per second, High Profile level 4.1.”

  • Matthew Ross

    February 1, 2019 at 1:06 pm in reply to: Exporting Tall Videos

    If the file you want to export is 2048 pixels tall, then you need to set the H.264 Level to at least 5.1. Levels lower than that cannot support vertical resolutions at 2048. See this table:

    https://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Levels

    I don’t have CS6 handy, and I don’t remember what kind of control you have on H.264 exports, but in CC2019’s Media Encoder, the Levels setting is right below the Profile setting under the Basic Video Settings in the Video tab.

    I am able to export a H.264 file that is 1536 wide by 2048 tall with Profile set to Main and Level set to 5.1, but again, this is not CS6, and I can’t remember what settings CS6 exposed.

  • Matthew Ross

    October 22, 2018 at 12:04 pm in reply to: Compatibility with (only slightly) older OS’s

    [Steve Bentley] “To me the first two sentences are not compatible. Which is it?

    CC 2019 apps are available for Windows 7, Windows 10 or later, and macOS Sierra 10.12 or later. 2019 versions of Digital Video products require the newest versions of Windows 10 and macOS Sierra or later. Windows 8.1 or early Windows 10 versions are not supported.”

    I think they worded it that way because some of the apps are compatible with Win 7 while others aren’t. From what I’ve seen so far, Photoshop CC2019 is compatible, while the video apps (AE, Premiere) are not. So certainly not as clear as it should be. Maybe they should have worded it some CC 2019 apps are available for Windows 7…[ect.]”

  • Matthew Ross

    October 11, 2018 at 1:05 pm in reply to: FCP 7 to Premiere Pro CC 2018

    [Tudor Applen] “I DID try converting QT files to AVI, and to MP4, but the re-linking didn’t work. “

    Instead of transcoding to AVI or MP4, try keeping the files Quicktime, but instead of whatever the original codec is, convert to a codec that Premiere still supports. So you could have .MOV files with something like DNxHD/HR, Cineform, or ProRes (if you can still transcode on a Mac). There is a list of codecs that Premiere will still support inside of Quicktime here: https://helpx.adobe.com/x-productkb/multi/quicktime7-support-dropped.html

  • [Tero Ahlfors] “DNxHD/HR are completely different formats from what you’ve been asked.”

    All we know that Renee has been asked for is “Op1a, 25 fps interlaced, minimum data rate 50 Mbps.” DNxHD and DHxHR are perfectly valid formats to put into an MXF OP1a wrapper, so “completely different formats” doesn’t make sense. The broadcaster may not accept those codecs in the MXF OP1a, but that hasn’t been specified.

  • [Todd Perchert] “stick with a standard MXF to send the station. I wouldn’t bother with DNx??. “

    What do you mean by “standard MXF?” Renee has not said that the broadcaster has specified anything other than “Op1a, 25 fps interlaced, minimum data rate 50 Mbps.” MXF is just a wrapper, and it is perfectly valid to have DNxHD or DNxHR inside of that wrapper. The broadcaster may not accept that, but we don’t have that information.

  • DNx is a family of CODECS that you can put in an MXF OP1a wrapper. This is how it looks in my export menu.

  • Will the broadcaster accept DNx? We regularly export DNxHR/DNxHD MXF OP1a out of Premiere for masters. You’ll have no problem getting a minimum data rate 50 Mbps with DNx.

  • No, never did get any answer or figure out any fix (other than using a different program, like Resolve).

  • Matthew Ross

    May 22, 2018 at 1:01 pm in reply to: FCPX and After Effects

    [Simon Ubsdell] “…a corporation as clueless, as visionless and with as few actual products to offer and with even fewer ever likely to see the light of day, is still the most profitable ever.”

    Reminded me of some of the opinion I read in this Harvard Business Review article.

    Particularly this part:

    Tim Cook has now run Apple for five years, long enough for it to be his company rather than Jobs’s. […] Apple under Cook has doubled its revenues to $200 billion while doubling profit and tripling the amount of cash it has in the bank (now a quarter of a trillion dollars). The iPhone continues its annual upgrades of incremental improvements. Yet in five years the only new thing Apple managed to get out the door is the Watch.
    […]
    It’s not that Apple doesn’t have exciting things in conversational AI going on in their labs. Heck, Siri actually came first. Apple has autonomous car projects and AI-based speakers in the works. The problem is a supply chain CEO who lacks a passion for products and has yet to articulate a personal vision of where Apple will go. Without that, he is ill-equipped to make the right organizational, business model, and product bets to bring those innovations to market.

    It will be interesting to see how this all plays out and if any of that proves true.

Page 2 of 6

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