Inspiring

Answered

Is CC 2019 ready for a full time post pro to commit to using it?

Forum|Forum|7 years ago
January 8, 2019
5 replies
1403 views

Are there any crippling bugs in either that are preventing you from completing projects? Or, anything forcing you to resort to draconian workarounds?

I'd love to hear from full-time post-production professionals, if possible.

I'm eager to be able to use the new Lumetri hue features, and Mocha as an effect in Ae CC19, but don't want to be taking two steps back in stability and reliability.

Thanks in advance for weighing in.

This topic has been closed for replies.

Correct answer Christian.Z

For me it's working fine. Some people were reporting stability bugs, but most of them were solved by the regular preferences/Cache trashing, Or by optimizing their systems and workflows.

What are the specs of your system? Are you using a different software? or an older version of PP?
If you are using a different software, you can try PP for 30 days.
If you are using an older version I suggest the following:
1- Do not update if you have pending projects. Finish your important projects before updating.

2- When you update it, try it daily for 2-4 weeks, report any issues you might have, and If you did not feel comfortable, you can roll back to the older version.

Let me know.

L

leandrog25948639

Participant

I am paying for the suite 43 dollars a month and I got to say I have never experienced so many problems in video editing.

I'm already searching for alternatives. Every time there's a new update it might work for a few days and boom again not working or become intolerable.

Im so disappointed with Premier pro it crashes all the time. Right now, I cant a decent chat person t help.

Gotta a major project for YouTube nut I guess my 200,000 subscribers can wait. Right?

R Neil Haugen

Legend

Have you posted here about the various issues you're having?

If not, please create a new thread and list your gear, media, and specific problems so we can try and sort it out.

Neil

Everyone's mileage always varies ...

Mo Moolla

Legend

Hi Jim

In a word "NO"..its not ready ...yet

Stay with CC2018 for just a little longer especially if u r on mission critical projects

Mo

J

Jim CurtisAuthor

Inspiring

https://forums.adobe.com/people/Mo+Moolla wrote
Hi Jim
In a word "NO"..its not ready ...yet
Stay with CC2018 for just a little longer especially if u r on mission critical projects
Mo

I'm inclined to agree with this, Mo, and am sticking with 2018 as you advise, but can you tell us why you have come to this conclusion?

I just finished a project that I inherited from another editor who started her project in 2019, and had no nail biting moments, but I wasn't stressing the combo of Ae, Pr, and AME that hard. Biggest issue I had was several crashes in Pr, but one thing I love about Pr is how it saves work on crashing that's rarely unusable or corrupt after a relaunch.

Mo Moolla

Legend

Hi Jim

As most pro users know (and this can be with any application, not just PP), when an update is released, no matter how tempting it may look, wait a few days before even thinking about looking into updating. You will get to hear about lots of issues and bugs. If u r fortunate to have a 2nd Mac or Pc that’s NOT mission critical to test on you will be able to experience them first hand.

To the point then: Why is PP not ready yet and how did I come to this conclusion.

I have been testing CC2019 alongside 2018 and have picked up a number of issues (which I won’t go into here). Adobe engineers have ironed out quite a few of these and CC2019 is running pretty stable now. However I have noticed a few “glitches” here and there and I will not do any mission critical work on it just yet. What I do to test is take a project I’m working on in 2018, open it in 2019 and see how far I get before anything goes wrong. In the first week of release I had at least 6 issues per week. I am now down to 1 so it’s ALMOST ready. I will give it a month or so more before I migrate over fully.

Also note that I like to use 3rd party plugins and lots of them weren’t yet ready for 2019 on launch. 99% are now compatible.

I trust this explains my comment about it not being ready. I am using 2019 daily now and it’s holding stable. The last and only bug I am seeing is the workspace won’t remember my settings and keeps reverting to default: small issue but one that annoys me.

Beside that it’s pretty stable, well for me anyway. U might read tons of feedback on instability on the forums but personally I’ve barely encountered any serious issues over the last 2 weeks.

So as a good rule of thumb, keep 2018 and 2019 next to one another. Work on 2018 and in your free time open up the project in 2019. See if anything goes wonky and if it doesn’t, well, you are then good to go.

Mo

Regards

Mo...

Sent from my iPhone

J

Jim CurtisAuthor

Inspiring

I thought I'd come back and report this. I inherited a project that was started by a bush league editor who did a bunch of work in Pr CC19 before her client realized she was over her head, and hired me to rescue the project. Downgrading to CC18 was going to take more work than I wanted, so I forged ahead with Pr CC19.

I've gotten several crashes, but not an inordinate number considering the project has all kinds of codecs and 2TB of source media. Luckily, over 1TB of that is ProRes footage from an BMD Ursa in 4K, and ProRes hasn't presented any real issues for me, so far.

The prior editor did her graphics entirely from Envato templates for the Pr Essential Graphics feature. This was my first dive into Essential Graphics, and consider me unimpressed. Kerning is a nightmare. I get far better control in Ae, and learned a trick from a colleague about converting Essential Graphics .aegraphic files to Ae projects. I created all my new GFX in Ae and used Dynamic Link. As with Pr18, DL-ed clips don't always reconnect when reopening the Pr project, and renders on DL-ed clips are gone and have to be re-rendered. DL is great when it works. I wish it was more reliable.

Otherwise, Ae CC19 has been crashing on quit fairly regularly; so I save first, and just force quit to save myself a little aggravation.

At this point, I'm still a little hesitant to say Pr CC19 is ready for prime time, although I'm feeling fairly confident I'll be able to deliver this project on time, and that's the most important thing I can ask of any software. The app takes almost twice as long to launch that Pr CC 18 does. Since I'm switching back and forth between versions (I'm still relying on CC18 to finish projects I started weeks or months ago.), that's become annoying, but I've taken to use the opportunity to answer emails or refill my coffee.

R Neil Haugen

Legend

The mogrts thing is for many things quite a good tool ... and by design, there's more you can do in AfterEffects than Pr. In fact, the concept is advanced graphics are to be made in Ae, with only the things the designer chooses or wants the Pr editor to be able to mess with included in the controls moved to the EGP panel in Ae, therefore changeable in Pr.

At your level of work, it is assumed the main mogrt would be created in Ae. And don't use a DL for mogrts ... export them in to a Library, they pop up in your account's library in Pr ready to use. And to share with the Pr editors on staff in a larger shop or even 'remote', use a shared library accessible to whoever needs access. Anyone on that 'share' gets the mogrt as soon as you export from Ae.

This way you save all the DL hassles on a Pr sequence.

Neil

Everyone's mileage always varies ...

J

Jim CurtisAuthor

Inspiring

Thanks, Neil, but I'm a one-man shop. And since I'm old, and accustomed to doing things "the hard way," I'm not impressed with Essential Graphics or Essential Sound (although I'd like to use audio ducking, but was unsuccessful making it work as I'd like it to the one time I tried to use it).

A huge problem I see in Essential Graphics is that kerning is incredibly stupid. You have to select characters, then use the tracking or kerning tool in the Effects Controls. Leading affects the whole text block; not per line. It's like it was made by somebody outside of Adobe. Adobe was built more or less on handling type. I don't see why they don't unify formatting behavior across all their apps: place cursor, and option-arrow left or right.

Plenty of editors never kern anything. They've probably never worked with agency people. When I spent two sad years with DDB, they had a "creative" come in to my edits just to look at kerning and leading. No kidding. But, it taught me how to format text, and everything I do that involves text ever since is formatted beautifully, if I say so myself.

I downloaded this free guide to .mogrts, and searched for the word, "kern." NO matches.

Free eBook on Making MOGRTs - PremierePro.net

R Neil Haugen

Legend

Christian has it spot-on.

There are thousands of users around the world working away in 2019 without issue. So ... it may very well work fine for you.

However ... that's never a reason to simply dive into the pool, is it? Not if you want to keep all your nice paying clients at least ... so ...

You can install 2019 and leave earlier "major" versions installed and in use. Keep working in 2017 or 2018 as you are, and test new projects in 2019. When it's proven workable on your machine, start using it.

And ... never 'migrate' a project forward a version by opening it in the new version. Always make a new project in the new version, then navigate to and select the previous project file in Pr's Media Browser panel ... right-click/Import.

Much more stable way to move a project forward ... and you always still have the older version project file as a fall-back.

Neil

Everyone's mileage always varies ...

Christian.Z

Correct answer

Community Expert

For me it's working fine. Some people were reporting stability bugs, but most of them were solved by the regular preferences/Cache trashing, Or by optimizing their systems and workflows.

What are the specs of your system? Are you using a different software? or an older version of PP?
If you are using a different software, you can try PP for 30 days.
If you are using an older version I suggest the following:
1- Do not update if you have pending projects. Finish your important projects before updating.

2- When you update it, try it daily for 2-4 weeks, report any issues you might have, and If you did not feel comfortable, you can roll back to the older version.

Let me know.