Adobe Creative Cloud Video Production Suite updates for NAB 2019

So Adobe has updated it’s video suite in time for NAB 2019 with some exciting new features, and hopefully some stability improvements.

Obviously the most exciting new features is the content-aware fill for video in After Effects.

I am pretty excited to try this one out, as the results from the demos look impressive, but I think it will work best with moving footage so the pixels exist somewhere.

And the new expression engine in After Effects looks amazing.

I can’t wait to try that out.

For Premiere we get the Freeform view as a kind of visual storyboard.

This is pretty neat, though not a mind blower for me.

And the new rules and guides will make placing things much easier.

Pretty neat. And Faster Mask tracking will always be helpful.

Overall some cool new features, though I am hoping for more stability overall.

Adobe has released Premiere Rush for the iPad

The formerly only available through an invited beta, Adobe Rush has been released for the iPad and iPhone. It is an online editing system that converts everything to H.264 and can do simple edits, and they can even be exported to Premiere Pro though he desktop version requires 10.13 on the mac.

It seems to be a simple and quick editing program to upload web videos, and has to be better than the previous adobe clip, which was pretty basic.

I have downloaded to my ipad, but have not played with it yet.

Adobe released Premiere Pro 13 Today, also known as Premiere Pro 2019 October 15 Update

You can check out the full release notes at Adobe.

I am most excited about being able to access multiple lumetri effects from the Lumetri Panel, instead of only being able to access the last added one, and having to make changes in the effects panel.

Also looking forward to trying the Intelligent Audio Cleanup Tools.

I haven’t really played with Templates from After Effects, since I do my own graphics, and it just seems easier to make the graphics all the way in After Effects, but I will eventually play with it more.

No mention of having fixed the having to render audio to see audio in a multicam clip in the timeline. I am hoping that bug is fixed. I hate having to render every time I open the project, it is just frustrating and unnecessary.

Scott Simmons at PVC article on editing a complex feature in Premiere Pro with no crashes

Scott Simmons at ProVideo Coalition has a great article on how he edited a whole feature on Premiere Pro without any crashes.

It is certainly worth a read. Now I don’t see how he edits a whole doc with only one sequence, as I like to make stringouts of shots and use markers to mark them up, and he must subclips things, which I find slower.

And I already render at ProRES, but I have also started rendering everything over to ProRES before editing, because highly compressed formats cause too many issues (as do JPGs), though I have had to do it before import, because I have found that using the Ingest feature doens’t work, as it often crashes and loses it’s progress completely.

And I am going to start moving more sequences out of my project into archive projects as I go to see if that helps with stability.

Premiere Bro on the Adobe Premiere Pro CC 2018 (12.1) update

Premiere Bro has an in depth feature on the latest update to adobe Premiere Pro 2019 (12.1) and goes much more in depth than I have seen elsewhere.

Like I hadn’t realized that the comparison tool could be used for things besides color, such as Warp Stabilizer, Shot Resoration, Motion Graphics Template Chagnes and Fonts and Text placement. Or that it worked within Lumetri Color Scopes to help match shots with scopes! AWESOME!!

I also hadn’t realized about gradients in Essentials graphics with transparency.

Thanks, awesome look at the new features.

An awesome Mockup for a new Adobe Professional Color Tool Lumetri CC

So Bilal Alsurri at Nine Productions has created an awesome mockup of an upgraded SpeedGrade, which would obviously then be Adobe Lumetri CC.

This is a dream of mine, because I so miss SpeedGrade. Sure it isn’t DaVinci, but it was very powerful (and I love being able to control the contrast in different regions so easily) and I loved being able to have a grade come back into premiere as plug ins on clips instead of having to render out movies with the grade as currently has to be done. Especially since Lumetri within premiere is good, but not great, and certainly not a professional level color correction program.

It is so unfornunate that Adobe seems to have given up on a professional color app for a very begginer implementation and something like this would certainly go a long way to making color pro again in Creative Cloud.

If you are like me and like this idea, please go to Adobe User Voice and give it an upvote! It only has 19 right now!

Premiere Pro Essential Graphics Bug Canvas Goes black: UPDATED

So I am getting a totally reproducible bug in Premiere Pro CC 12.1.2 (Build 69).

I have a graphical bug to do with the Essential Graphics Text causing the Canvas Viewer to go black. Sometimes the entire timeline goes, and sometimes just the Essential Graphics Text, and it happens when I attempt to change the contents of the text.

I do have a bug with an alpha and an adjustment layer with a video limiter above the text layer, but with essential graphics I continue to get the whole screen going black.

The only way to get it back is to restart premiere, and it will happen again later, though not always.

This is on a MacPro 5,1 with 32 GB of RAM and a GTX 970 with 4GB of RAM.

It is especially frustrating when combined with having to render audio to see multicam audio every time I restart.

I have posted this at Adobe User Voice.

I got a response and they seem to think it is the video card, and graphics drivers. So they lay it at NVIDIA’s feet. And they had me try to see if it happened with render set to CPU, and I tried to see, but it was literally so slow that I could barely function so I gave up after an hour or so.

Adobe Premiere Pro 12.1.2 Update, July 2018, didn’t fix multicam audio render bug!

Eric Philpott at the Adobe Blog has listed the new features of this new point update of Adobe Premiere Pro to 12.1.2.

The new features are limited to Performance enhancements and format support including Hardware Accelerated H.264 and HEVC decoding on the new MacBook Pro and iMac Pro, and Accelerated Encoding on Windows 10 with seventh generation and later processors, as well as improved RED Decoding and Sony RAW/X-OCN formats. They have also added export to 8K H.264 and a few other formats, but mostly it is about bug fixes.

Already I have seen the Recent warnings about incompatible fonts having gone away.

This release did not fix the really f***ing annoying Multicam Audio bug, where to see the waveform in your multicam clips, you need to render the audio. This would be OK if it kept the render between restarts of the program (or crashes), but every damn time you have to re-render the audio to see the waveforms! COME ON ADOBE, THIS ISSUE HAS BEEN AROUND FOR WAY TOO LONG FOR YOU TO HAVE NOT FIXED IT!

Adobe Premiere Pro 2018 Multicam Audio Bug

So I am using Adobe Premiere Pro 2018 with multicam sequences of UHD ProRES clips and separate 24 bit audio. And to see the waveform in Premiere the Audio needs to be rendered. The bug is that Premiere Pro loses this render each time I open Premiere, so I once again need to render the audio to see the waveform.

And this has been going on for a long time, as you can see from this post at the Adobe Forums, they were going to fix this ASAP as of February 2017, but is July 2018, and the bug still persists.

I have also posted about it on the new feature and bug request page.

Premiere Pro Ingest is broken, Media Encoder keeps freezing and breaking the process

So I am running Premiere Pro CC 2018 12.1.1 and Adobe Media Encoder CC 2018 12.1.1.12 on a macOS Sierra 10.12.6 with a MacPro 5,1 dual 6 core 3.06 GHZ with 32 GB of RAM and and a GTX 97- 4096 MB mac flashed. I am running the latest CUDA 387.178 with NVIDIA Web Driver 378.06.25f03 and am using CUDA renderer. I am using UHD 29.97 footage from a Canon C300 in MXF format and converting it to ProRES on Ingest from Media Browser.

I am importing the footage from within Media Browser in premiere and it sends the footage to Media Encoder to convert it. The problem I am having is that Media Encoder keeps freezing and giving me the app “not responding” message. And if you force quit media encoder all the encodes are gone, and I have to delete the footage I imported and re-import all the footage into premiere to get the ingest going again. This is super frustrating. At least if I bring clips into media encoder myself and I have to force quit it, when I come back all the encodes are still in Media Encoder (sure some may have all compressed but that is an easy fix, just delete the encodes that already happened), it seems that Ingest can’t deal with any component breaking down, and it keeps breaking down for me.

It seems that the ingest only works if everything is working correctly, and it has not been working right, so as soon as you force media encoder to quit the Ingest is finished.

Honestly there should be a way to restart the conversions from within Premiere (not just creating proxys, but an actual ingest conversion). And it would be great if the ingest survived crashes, by leaving all the convertions within media encoder even after a crash so you could continue it later if something fails.

I know I can just do the conversion straight in Media Encoder (which I am doing now, but still getting not responding, but at least I can force quit and the conversions are still there and I can just delete the completed ones), but I was hoping to do the Ingest Process, but it does not seem to be working at all well for me.

And yes I know that Premiere can play back the MXF footage, but I have much better playback of the 4K footage once it is converted to ProRES.

I also posted this on the adobe forums, but don’t expect to get an answer that will fix the issue other than doing what I am doing and doing the conversions in Media Encoder directly. I just can’t believe how broken the ingest feature is that it can’t handle errors within Creative Cloud. It just expects that it will work, and it is not doing that for me.