Skip to main content
Roadie Jesus
Participant
June 14, 2017
Answered

Updating to the new Update Version 11.1.2

  • June 14, 2017
  • 3 replies
  • 1652 views

I completely understand this is a critical update and also I'm very happy to see it because of the bugs in Version 11.1.1. We have projects in the works right now and need to clear these bugs from 11.1.1 and it looks as if 11.1.2 does clear those problems we have been having.

Question is to people that are using the new update, should we update????

This topic has been closed for replies.
Correct answer Kevin J. Monahan Jr.

Hi MarkP,

I completely understand this is a critical update and also I'm very happy to see it because of the bugs in Version 11.1.1. We have projects in the works right now and need to clear these bugs from 11.1.1 and it looks as if 11.1.2 does clear those problems we have been having.

Question is to people that are using the new update, should we update????

Whether or not to update is a great thing to be concerned about. Always look before you jump is a great stance. My feeling is that if you find the bug fixes too enticing, then you should update any short term project with one caveat—do so with a duplicate of your existing project. If anything should go wrong, you can always move back to the original. In the first couple of weeks on the updated project, continue to work the "

My feeling is that if you find the bug fixes too enticing, and you are not moving from one major version to the next—then you should update any short term project with one caveat—do so with a duplicate of your existing project. If anything should go wrong, you can always move back to the original.

In the first couple of weeks on the updated project, continue to work the "dupe process" for a good solid 2 weeks. Then, you're out of the woods and can proceed normally with regular back up procedures, Auto Saves, etc. If anything should go wrong, you can always move back to a working version.

If you have a large project, such as, a large doc, feature, or one with a lot of multi-camera sequences, etc. I would continue with the original version that you were working on for stability's sake.

Each person has their own threshold for whether or not to update a project, however, if you follow the above protocol, you should always be in a fairly safe position.

Thanks,
Kevin

3 replies

Kevin J. Monahan Jr.
Kevin J. Monahan Jr.Correct answer
Legend
June 15, 2017

Hi MarkP,

I completely understand this is a critical update and also I'm very happy to see it because of the bugs in Version 11.1.1. We have projects in the works right now and need to clear these bugs from 11.1.1 and it looks as if 11.1.2 does clear those problems we have been having.

Question is to people that are using the new update, should we update????

Whether or not to update is a great thing to be concerned about. Always look before you jump is a great stance. My feeling is that if you find the bug fixes too enticing, then you should update any short term project with one caveat—do so with a duplicate of your existing project. If anything should go wrong, you can always move back to the original. In the first couple of weeks on the updated project, continue to work the "

My feeling is that if you find the bug fixes too enticing, and you are not moving from one major version to the next—then you should update any short term project with one caveat—do so with a duplicate of your existing project. If anything should go wrong, you can always move back to the original.

In the first couple of weeks on the updated project, continue to work the "dupe process" for a good solid 2 weeks. Then, you're out of the woods and can proceed normally with regular back up procedures, Auto Saves, etc. If anything should go wrong, you can always move back to a working version.

If you have a large project, such as, a large doc, feature, or one with a lot of multi-camera sequences, etc. I would continue with the original version that you were working on for stability's sake.

Each person has their own threshold for whether or not to update a project, however, if you follow the above protocol, you should always be in a fairly safe position.

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Participating Frequently
June 15, 2017

I don't recommend that update for now. I had BIG problems with last one, had to import all sequences (more than 60 of them) again to new project to make it work. Now I trusted Adobe 'cause it was a 'critical update' and now when I open the project, it crashes after 1min. Cmon Adobe, why I have to waste 1 hour of my work every time you give an update?

I have 68mb project with more than 60 sequences, media is located on 8 hard drives. MacOs Sierra fully updated.

R Neil Haugen
Legend
June 14, 2017

From my personal experience, I'd say YES!

But that's one person on one PC.

So for your probably multiple-setup shop, I'd suggest trying on one machine ... if that works as you wish, move the rest up also.

Neil

Everyone's mileage always varies ...
Roadie Jesus
Participant
June 14, 2017

Thank you for your response and it helps greatly! I would really love some feedback from more individuals who have updated to 11.1.2. We have done tests on other computers but those computers do not carry the weight as the main editing station.

All in all thank you R Neil Haugen!!

We look forward to more responses!

Participant
June 14, 2017

Updated to 11.1.2 yesterday, and now Premiere is leaking memory like a champ. Red frames, and memory usage alert just by opening a tiny project. Crashes after a few minutes. Got 32 GB's so that should not be a problem... Especially when it ran smooth with 11.1.1....