Copy link to clipboard
It looks like Adobe has just pulled many of the primary installers that were available for previous major versions of Premiere Pro, Audition, Prelude, and Adobe Media Encoder (AME).
— Premiere Pro CC 2015.3 (versions 10.3 & 10.4 – June 2016)
— Premiere Pro CC 2015 (version 9.0 – June 2015)
— Premiere Pro CC 2014 (version 8.0 – June 2014)
— Audition CC 2015.2 (versions 9.2 & 9.2.1 – June 2016)
— Audition CC 2015 (version 8.0 – June 2015)
— Audition CC 2014 (version 7.0 – June 2014)
— Prelude CC 2015.4 (versions 5.0 & 5.0.1 – June 2016)
— Prelude CC 2015 (version 4.0 – June 2015)
— Prelude CC 2014 (version 3.0 – June 2014)
— Media Encoder CC 2015.3 (versions 10.3 & 10.4 – June 2016)
— Media Encoder CC 2015 (version 9.0 – June 2015)
— Media Encoder CC 2014 (version 8.0 – June 2014)
Note that this loss affects all revisions from these three years (2014, 2015, and 2016), because without the base installers available, none of the minor version updates can be installed either.
Can't say for sure why this happened, but it could possibly be related to the recent change in CC application support for the Dolby codec.
One of the great promises of Creative Cloud is the ability to use any version of the CC apps that you desire or require. This is especially important for video customers, who are urged by Adobe experts to install and maintain multiple CC versions and to always re-open their .prproj files with the exact same versions of Premiere with which they were created, no matter how new or old. This is for compatibility reasons.
The loss of these major releases could also be a big issue for customers who cannot upgrade, for example, due to changed system requirements or newer versions that their current hardware cannot support. They will not be able to access or reinstall older versions of their software.
Adobe also sometimes drops features or functionality between releases, and says that if you want to use the discontinued feature, then you need to go back and install/use the previous version.
If you would like to have these three years of CC releases restored, then the most likely path to having that happen is to let Adobe know how important these are to you (their customers) – so please share why you want or need them...
Please add your feedback below, and/or click "I have the same question" underneath this text.
This totally bit me today with a new machine install. AME 2017/2018 don't render my current film projects at all in MP4 or H.265 (well documented and reported but not fixed since 2017 release - plenty of threads about that here). So I use 2014 and 2015 AME to encode since I still have most of them in AE 2014 for render speed reasons.
But I have discovered to my horror I can't install these older versions - not officially and not hackable. This is terrible mistake on Adobe's part. Drop support, fine. But don't block installs - that's class action stuff.
It's apparently an issue with licensing concerning another companies trademarks. Even though the Dolby Laboratories patents on AC3 encoded audio has expired, it's been mentioned in other places that DL had some issue with anyone using their old patented codec and trademarks that were somehow ... I don't know, but embedded or something. As neither company (Adobe/DL) is saying one word, I'm guessing that people with gray suits and power ties are involved.
So ... it wasn't that Adobe cut off the ac3 on a whim, but it seems had to in order to comply with legal requirements of the licensing company. As the prior versions of PrPro had that built in, they were probably not in compliance with the current legal situation. So taken down.
I'm certainly hoping that they'll make the time to put out 'corrected' version of the old programs list ... but as it would seem that Adobe was acting so to comply with external legal requirements, filing an actionable suit against a licensee complying with legal requirements from another company would probably have difficulties of its own.
Again, this is speculation, as ain't noboby at Adobe breathing a word. But from actions and statements elsewhere by DL, and the changes in ac3 utilization that suddenly cropped up in the 2018 release, it seems a valid surmise.
Which is why it's good to always uncheck the 'advanced option' option of 'remove previous versions' in the CC App's installation process. Not a help for you in this moment, but something to be aware of.
I'm fully aware of the remove previous versions but that does not help on a clean build new machine. And blocking wholesale the install of old apps does not sound like a legal issue - that would just be an update with those encoding options not available. And for AME specifically, if the same renders actually ran in 2017/2018, it would be moot anyway.
But having the ONLY option on a new install in the broken 2017/2018 (for a number of people) as the option. But thankfully, After Codecs developer fixed that issue same day and I can now render MP4s and H265 straight out of AE 2014 again. Thank god for AE Scripts.
It's apparently an issue with licensing concerning another companies trademarks.
And that is why any half-competent lawyer makes sure that there's a workable sunset clause in the IP licensing agreement from a supplier, ensuring customers aren't dumped in a ditch. Protected legacy code, 90-day grace period to replace functionality, etc.
When Apple shut down Quicktime for Windows, many vendors that relied on those libraries just went out and hired as many people, and spent as much money, as necessary to get their code future-proofed as fast as possible. Costs were offset against customer retention. Adobe with Dolby seems to be taking a somewhat different stance, but NASDAQ:ADBE took a 20-point dive last month, maybe the beancounters will eventually take the hint. Subscription is a contract that requires both money and trust. If the terms and conditions began "We may, on instructions from a third party you've probably never heard of, reach inside your computer at any time and permanently remove things you need to do your job..." then I don't see quite as many people signing up.
All quite true. Sadly ...
Hopefully, Adobe will hear the outcries and restore access to these versions. But for now, we are stuck.
All the evidence suggests that these decisions are being made under orders from lawyers (Adobe's or Dolby's or both) and in that case nobody is going to bow to customer pressure and put the software back, nor are they going to explain what's going on. Let's be frank about this, a few lost subscriptions is nothing compared to the risk of being sued by a company with a billion-dollar turnover. Both Adobe and Dolby have record share prices, that's ultimately the only thing that public-listed corporations are allowed to care about.
Edited by Moderator: Warning. Please do not discuss legal issues on these forums. It is against our community guidelines.
The Creative Cloud subscription terms and conditions allow Adobe to terminate the supply of software to a subscriber at any time, including without warning, if they "are required to do so by law (for example, where the provision of the Services or Software to you is, or becomes, unlawful)" or "elect to discontinue the Services or Software, in whole or in part". You agreed to those T&Cs when you signed up. Trust me, if lawyers are driving this process, they will have made absolutely sure that what they're doing cannot come back and bite them.
A few weeks ago, Adobe took down the CC 2017 installers for the DVA apps, removed the Dolby codec, and then restored their availability online.
CC 2017 was gone for a few days while this happened, and then reappeared.
Having done that, there is no technical or legal reason why the company couldn't do the same for all of the CC 2015.x and 2014 versions which were pulled down a week ago.
A modest effort here would save countless customers a lot of grief going forward.
There are many valid reasons why the previous installers are needed, including:
– Need to work with collaborators or clients using those versions
– Third-party plug-in compatibility
– Need to use legacy features not available in newer releases
– Changed system requirements or newer versions that their current hardware cannot support
– General best practices for opening older projects created in those same versions
– Creative Cloud customers have been promised to be able to use, or continue to use, any CC version
– The complete version collection as a whole provides significant value and utility to customers
Bring them back!
CC 2017 was gone for a few days
It was a couple of weeks, actually. Which at least hints at the work necessary to fulfill your request. Time I would still prefer Adobe devoted to moving forward.
I'm not disputing that it's technically possible to re-write all the legacy versions without Dolby support, just that it's perfectly within the T&Cs for Adobe to remove them from availability without notice. They might well reappear in that state at some point but it's hardly top priority for the engineering team given the bug queue in the current build.
People who accidentally uninstalled a Dolby-enabled build and are hoping that they can somehow regain access to that build's installer package including the Dolby codecs are out of luck. I appreciate their frustration, after all it's affected me too - I'm stuck on CC2017.1 for the foreseeable future because I have clients who use those codecs. However that's the price to pay for software that you 'license' rather than buy outright. Even if it came in a box, it's never legally your property. It's not an Adobe thing; everyone has the same terms and conditions. Microsoft can remove Windows features anytime they want to (and with W10 you don't even get the chance to say no). Apple stopped support for Quicktime on Windows with no warning and left it with a published vulnerability -that messed up far more users than Dolby's actions.
Copy link to clipboard
Don't you agree with me that none of the two things happened?
Copy link to clipboard
It's sad Adobe removed access to 2015. One of our PCs got upgraded to 2018 in stealth mode it seems. Fortunately it is dual boot so the CC 2015 on the Win10 Partition is intact. CC 2018 is bloatware that does not play well with BCC 11. Maybe time to go back to AVID MC.
I have never understood why some Premiere users feel the need to upgrade or update as soon Adobe makes them available. Users should know by now that there are usually problems.
One of our PCs got upgraded to 2018 in stealth mode it seems.
That's just not possible. Updating/upgrading is always and only manually initiated by a user.
More likely, someone just doesn't want to admit they did it.
Copy link to clipboard
This is unacceptable! I am working on a feature film that has been in editing for almost a year now. We chose Premiere CC 2015 10.4 because it was the most stable version of the program at the time.
We do not want to upgrade an entire 130 minute film with incredible amounts of offline keyframing, filters, speed ramps, etc. Absolutely under no circumstances should we have to update to an entirely new version of the Premiere, as it literally has to translate the entire sequence and there is no guarantee something will not be changed (I know I had a lot of issues doing an upgrade with a smaller project from 2015 to 2017.)
Please fix this immediately!
Provided you have not updated then just ignore the "new version available" prompts and carry on using CC2015. Adobe had not (yet) remotely disabled that version.
If you need to "install" CC2015 on another computer then currently the only option is if you already have another computer running it - in which case you can do it the hard way by mirroring the operating system partition to the new PC and re-activating everything.
Absolutely under no circumstances should we have to update to an entirely new version of the Premiere
The only circumstance in which you'd have to is with a new or reinstall of PP. The version you currently use is simply no longer available.
I have the discs for Production Premium CC5, CC 5.5 and CS6 and guess I will have to stick with CS6 in this PC's Win7 partition. All the XAVC material is being transcoded to MXF. PPRO CC2018 does not play nicely with BCC11 and locks up all too frequently. I cannot rip DVDs customers give me as video source but Sony Vegas 13 does it no problem. Not being able to revert to CC 2015.4 really does p**s me off but thankfully I have CC 2015.4 on the other editing PC. It is a shame we lost access to the earlier versions but worst case scenario I reckon we can go back to AVID MC if somehow Adobe manages to disable CC 2015 for me. I called BorisFX about the BCC11 issue with Premiere Pro CC2018 and was told it is a known problem Adobe is working on. Right.
I have 2014.2, 2015.3 and 2018 all on the same two machines and under Windows 7. I have no issues with MXF media and so far, past projects from older versions open and play nicely in 2018. In a few years I believe that there will be much bigger changes coming as the entire PC paradigm yields to mobile devices and we go cloud based, entirely. My first PC was a dumb terminal connected to an IBM mainframe. We've come full circle. Imagine that.
Regarding your copies on disk. Those may no longer work either as the license servers were also taken down before all this. To Adobes defense, they do provide reconfigured version that will work off of a valid license. I have already done this using CS3 to resurrect a few cherished projects.
Guess we will be mighty careful with the editing PCs. Almost all our footage is shot with PDW 700 & PDW 800 XDCAM HD 50 422. CS6 always edited the MXF perfectly. It is the XAVC 4K and HD MXF that causes grief - CS6 won't ingest it.
Yes. CS3 and CS6 were good versions. I come from the old school (video toasters and avid) were software and hardware were proprietary. Configurations were simple. Upgrades were unheard of or performed by service techs. They were only used for production: no internet, games or office apps. Nothing else was installed on them.
These days, armed with an image file to fall back on, it's not as risky to try out updates. What is risky is leaving auto update checked and apply updates without reading up on the changes, etc. Then blaming the vendor.
Lots of folks like to blame Adobe. However, they have to create software that will run on a wide gamut of gear. With users whom really don't know the inner workings of their systems. That's not a fun place to be. When I dumped my last Video Toaster to switch to Adobe. I found out that they and many other vendors were using Dell Precisions with newly introduced Xeon processors. Bingo. Hardware problem solved. That was 15 years ago, I'm on my 5th machine now. I deviated only once to a BOXX 7400 with Opteron AMD, what mess that was. I dumped it for another Dell.
Personally, I own refurbished Dell Workstations that I configure for myself. These run surprising well and off lease units are dirt cheap. I had a 420 that wouldn't die, it ran for 12 years straight.
Sadly, I see the demise of the PC market itself. Mobile is coming into play. I wouldn't be surprised to see the likes of Verizon stocking Monitors and keyboards on their shelves. No more configuring or building custom units. Of course, we'll be back to proprietary hardware and software. Everything will be cloud based.
There is a shining light in all this: Modularity. On a whim I bought a Moto Z2 Force phone and many of the Mods. It's an awesome concept, if it catches on with other vendors with pro level tools and software. That would be a win.
Breaks over. Back to work.
This is absolutely unacceptable. I agree with you Kuddlesnot, how can you be expected to upgrade an entire feature film project to a new version. I agree with you, way too risky!
Adobe, please fix this ASAP. I'm now having to delay finishing off on a project.
Currently there are CS6, the first CC version, 2017.4 (after the removal of ac3 audio), and what, 2-3 versions of 2018 available.
You can have all of them simultaneously installed except only one version of the 12.x builds of 2018.
Any of the removed versions will work if already installed.
Which version are you needing?
I need AME 2015.3. I have PPCC 2015.3 but my AME 2015.3 that worked with it stopped working and I need to re-install it.