8 Replies Latest reply: Jun 23, 2014 1:54 PM by jyaroslow RSS

    Red Giant Plug-Ins and CC 2014

    jyaroslow

      I thought one of the main advantages to Adobe's subscription model was that new features would be added automatically?  Currently, I'm having issues with Red Giant software not being recognized by PP CC 2014 (i.e. Colorista & Magic Bullet Looks)--after uninstalling the older version of PP CC.  After all, why would I want 2 versions of all my apps?  Can someone help me understand this decision and how to fix my Red Giant issues?  Thanks.

       

      By the way, I was able to fix Red Giant Universe, by uninstalling and reinstalling the software, but I don't want to have to do that for Colorista and the others.  Does anyone have a better way?

       

      [Thread title changed for clarity.]

        • 1. Re: Why did Adobe release separate CC apps for 2014?  Now I have duplicates of everything...
          nw42 Community Member

          It's great to have new versions like the 2014 update as separate application!

          So we have a smooth transition if bugs or workflow problems occour - if anything goes wrong simply start the old version and wait until the new one get fixed...

          • 2. Re: Why did Adobe release separate CC apps for 2014?
            JSS1138 CommunityMVP

            Supposedly, Red Giant released new version compatible with CC 2014 last Thursday.

            • 4. Re: Why did Adobe release separate CC apps for 2014?
              jyaroslow Community Member

              Yes, I read about that too, but I don't think this is a Red Giant issue per se.  I think it's a flawed execution strategy on the part of Adobe.  In addition to plugins such as Red Giant not working properly, I also had to reset some settings in PP CC 2014.  Why add extra work for the end user?  Adobe's previous enhancements in CC releases didn't require all this work on the part of the end user.   I'm still looking for a good answer on why they decided to create a separate version for most of their applications.

              • 5. Re: Why did Adobe release separate CC apps for 2014?
                nw42 Community Member

                If they release small sub releases you just get an update for the current installation - but if you get a major update like the CC2014 release you get a new install to ensure that your current workflow don't break because of plugin issues and bugs...

                That is an important mechanism to protect your working Adobe CC environment and has to be done that way for security reasons.

                --> You can import your personal settings via cloud sync to the 2014 version...

                • 6. Re: Why did Adobe release separate CC apps for 2014?
                  jyaroslow Community Member

                  nw42 wrote:

                   

                  If they release small sub releases you just get an update for the current installation - but if you get a major update like the CC2014 release you get a new install to ensure that your current workflow don't break because of plugin issues and bugs...

                  That is an important mechanism to protect your working Adobe CC environment and has to be done that way for security reasons.

                  --> You can import your personal settings via cloud sync to the 2014 version...

                   

                  nw42,

                   

                  Thanks for the explanation and the cloud sync recommendation.  I understand the workflow argument very well; however, the irony with that rationale is that by proceeding with a separate app, Adobe did in fact break my workflow.  Also from a file management perspective, we now have 2 versions of the same app running in our post facilities, which creates added confusion.  The only way I was able to repair these issues for Red Giant users was to uninstall ALL my Red Giant apps and reinstall them with the CC 2014 version checked.  Previously, all I had to do to upgrade Red Giant was go to Red Giant Link and run an update--which was much simpler.  What changed in this release that required Adobe to change the game on how they released updates and required 3rd party plugins to have to create a new workflow as well?  Adobe had significant updates & changes in October 2013 and December 2013, but those didn't require a new app.  Why now?  Why create more headache for users with multiple plugins, etc? 

                  • 7. Re: Why did Adobe release separate CC apps for 2014?
                    nw42 Community Member

                    Adobe had significant updates & changes in October 2013 and December 2013, but those didn't require a new app.  Why now?

                    This update caused some major issues in our pipeline and we had to roll back and install previous versions of the apps during a tight deadline to get our deliverables out of the door... So I like the idea of "never touch a running system" and add the new version in parallel instead...

                    But as you write plugins also have to be considered here... By default the should work in the old version and you should be able to install them on teh new version to check if everything works fine...

                    If I think about Autodesk software there is the same situaltion: We install the new version 2013...2014...2015 in parallel and then adding all the plugins. If everything works as expected the next to last version can be deinstalled from the system.

                    So you have a stable sytem and a new system all the time...

                     

                    --> CC2014 Apps are in approval stage now. We test them with our leads and if there are no show stoppers we set the signal to switch all workstations at once company wide...

                    • 8. Re: Why did Adobe release separate CC apps for 2014?
                      jyaroslow Community Member

                      Thanks.  I think your approach makes sense.  I just feel like Adobe shifted the paradigm on us with this release--when compared to the 2013 CC releases.  I thought that once Adobe went to the CC model, there wouldn't be a need to have this testing & cutover period, like we did with when upgrading from CS4 to CS5, or CS5 to CS6.  I know now that that is to be expected every year or so--or whenever they have a "major" release.  Bummer.