![\"Creative](\"https:\/\/s3.amazonaws.com\/pbblogassets\/uploads\/2014\/06\/creative-cloud-header.jpg\" "\\"Creative")
<\/p>\n<\/p>\n
The latest release of Adobe’s Creative Cloud 2014 suite of applications<\/strong> is packed full of great new features, bug fixes and all the improvements you hope for in a major new update. If you have a Creative Cloud membership<\/strong> then these kind of large scale, regular updates are why you’re paying that monthly fee! But there are a few things you might want to know while you’re excitedly waiting for all your apps to update…<\/strong><\/p>\n One of the first things you’ll notice is that a lot more of your hard drive space has disappeared. That’s because the Adobe Creative Cloud 2014 update installs next to your currently installed Adobe Creative Cloud CC versions<\/strong>, rather than on top of them. It’s a whole new installation rather than a traditional cloud update. This is of course very useful if you’re in the middle of a project and want the security of knowing that everything will work as it was before. <\/strong>Note: You shouldn’t really be updating your software in the middle of a project<\/em>!\u00a0 The downside is that you’ll have twice the number of applications installed taking up twice the space. You will also need to drag the new 2014 icons to your dock.<\/strong><\/p>\n That said this way you can have the best of both worlds<\/strong> – the latest features, and the security of knowing your software will still work. The official Adobe blog has some useful advice <\/a>about making sure your custom plugins work in both installations.<\/strong><\/p>\n “fixing permissions problem on Mac OS that impedes start of Adobe applications”: http:\/\/t.co\/iaKFEMQsOL<\/a><\/p>\n \u2014 Todd Kopriva AE (@ToddKopriva_AE) June 22, 2014<\/a><\/p><\/blockquote>\n I noticed on Twitter a few people sharing a link to this Adobe blog post from Todd Kopriva<\/a> with a recent bug wherein some applications are taking a long time to start or are failing to launch at all<\/strong> because the permissions for the Adobe Preferences folder’s have not been set correctly. If you’re having this particular problem then it’s a simple fix of setting the entire folder to have both read and write permissions<\/strong>, which Todd takes you through here<\/a>.<\/p>\n If you’re frequently creating FLV files (Flash video) for your clients in Adobe Media Encoder, then you’ll soon notice that you are no longer able to export FLV or F4V files<\/strong> from Adobe Media Encoder CC 2014, Premiere Pro CC 2014 or After Effects CC 2014. In another blog post from Todd Kopriva<\/a> you can get the full story, which essentially boils down to FLV and F4V files being rather outdated:<\/p>\n We removed the exporters for FLV and F4V files from the Adobe video applications (Adobe Media Encoder, After Effects, and Premiere Pro) because maintaining these obsolete exporters was a large amount of work, and we could better spend that effort on developing new features and fixing bugs in areas that are used by more people.<\/em><\/p><\/blockquote>\n <\/em>So what are you supposed to do if you still need to supply FLV files to your clients?<\/strong> Well that’s why the side-by-side installation of the Creative Cloud apps is handy after all. Simply keep the Adobe Media Encoder CC version installed<\/strong> and you’ll be able to export FLV and F4V files as much as you need. Or you could tell your clients that the Adobe Flash Team recommend that they play video files in Flash as H.264 MP4<\/strong> files anyway…<\/p>\n If you’re not a fan of the new Adobe Premiere splash screen<\/strong> then thanks to this tweet from Bart Walczak you can change it to your hearts content. To find the particular .png file that Adobe uses when the program is loading<\/strong>, go to your Applications folder, right click on the Premiere Pro application and select ‘show package contents’, then navigate the following file path:<\/p>\n Applications> Adobe Premiere Pro CC 2014 > Adobe Premiere Pro CC 2014 [show package contents] > Contents > Frameworks > Frontend.framework > Versions > A > Resources > png > pr_splash.png<\/p>\n If you wanted to you could replace the pr_splash.png file used in the 2014 update with the one used in the CC version, but that might get confusing! Plus your loading text will be in the wrong place. But you could just Photoshop the top part of the new image<\/strong> and replace those crazy colours with something less ‘busy’.<\/p>\n Got ya! @MaciekKaliski<\/a> @JBowdacious<\/a> @AdobePremiere<\/a> pic.twitter.com\/9755Ow9kUT<\/a><\/p>\nCreative Cloud 2014 – A Whole New Installation<\/h2>\n
![\"installing](\"https:\/\/s3.amazonaws.com\/pbblogassets\/uploads\/2014\/06\/Screen-Shot-2014-06-26-at-15.26.53.png\")
<\/p>\nApplications Won’t Start?<\/h2>\n
FLV Presets Are Gone<\/h2>\n
![\"FLV](\"https:\/\/s3.amazonaws.com\/pbblogassets\/uploads\/2014\/07\/flv-adobe.jpg\" "\\"FLV")
<\/a><\/p>\nOne Last Thing…<\/h2>\n