Premiere Pro CS5.5 to CS6 and save back to CS5.5

I was given project in Premiere Pro CS5.5 to work on in CS6, but have to save it back again in CS5.5.
Is this possible?
If so. how does one do it?

The license allows 2 activations... so just install/activate on your laptop... as long as you have only installed/activated once already

Similar Messages

My Premiere Pro won't open and keeps coming up with a 0xc000007b error message!! I have uninstalled

My Premiere Pro won't open and keeps coming up with a 0xc000007b error message!! I have uninstalled and reinstalled it but it will still not open.

It worked for me, any way we have to do following things now, I have seen this happens becasue of the corrupt dll for Visual C++ packages. if the following thing will not work, I am affraid we have to reinstall the windows 7
Good Luck
Try to remove all the Visual C++ 2010 Redistributable and Visual C++ 2008 Redistributable Packages (both x86 and x64) from the Control Panel
Download and install following Visual C++ Redistributable Packages
Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)
Microsoft Visual C++ 2010 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)

99 or 100% when it says Premiere Pro has stopped working and needs to close. What's going on?

I am using the premiere pro trial at the moment and have been trying to render a video for a solid week now. My computer is far more powerful then the recommended specs and yet it still takes 2 hours to attempt to export a 3 minute video (that isn't even heavily edited) and not only that but it will get to 99 or 100% when it says Premiere Pro has stopped working and needs to close. I have used earlier versions of the product before and never had such problems, even my 2 year old laptop could breeze exporting. What's going on?

Thanks, I'm a bit new to asking for help!
Version : Premiere Pro CC 2014.2 (8.2)
It is up to date
I'm using Windows 8.1 build 9600
My sources are contained in .mov, .mp4 and .png. The codec I'm trying to use is H.264
After I set the project to export I got this error message every time it gets to either '99' or '100%' completed. "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available"
I have never had such a problem with the program which makes me think it might have something to do with a recent update.
No other notable software was running during the export.
I don't have any third-party effects or codecs installed.
I have 64 bit OS and processor, Intel i5 - 4670K quad core clocked at 3.40 GHz. 12 GB of RAM. And a GTX 770 with 2GB of video RAM.
Unless it was installed in the trial, I do not have the Mercury Playback Engine.
And finally, it can be noticeably choppy during the preview when it gets to the part I don't have rendered but is fine again for a bit if I replay those parts. A part from being a bit slower then usual, I didn't actually run into a major problem until I started exporting.
Thank you for the help! Any suggestions?

I work with Premiere Pro on a mac and export quicktime movies to be played on pc's or mac's

I work with Premiere Pro on a mac and export quicktime movies to be played on pc's or mac's. When I export a qt from Premiere with audio it will not play on a pc only a mac. After extensive research I have narrowed down the problem to this: if you use the inspector in quicktime it looks like this
DV, 720 x 480 (640 x 480), Millions
16-bit Integer (Little Endian), Stereo (L R), 48.000 kHz
I have to run it thru AE to make it look like this....then it plays
DV, 720 x 480 (640 x 480), Millions
16-bit Integer (Big Endian), Stereo, 48.000 kHz
SOOOO the problem is the Little/Big Endian. I googled that and it looks like a file/bit structure....anyone know how/why to change it in Premiere? Because everytime I make a movie in Prem I have to drag the sequence into AE and render it there so the sounds works.....
thanks

Two questions:
1. What CODEC are you choosing when exporting on the Mac?
2. Do you have any Blackmagic hardware/software installed?
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

I have bought a single App Premiere Pro in creative cloud and installed and downloaded my app, but the App will not launch

I have bought a single App Premiere Pro in creative cloud and installed and downloaded Premiere Pro, but the App will not launch.

Hi There,
We would appreciate if you could provide us the below mentioned information so that we can assist you appropriately.
OS Version:
Have you used Premier Pro as trial before?:
Error message/screenshot<if any>:
Thanks,
Atul Saini

Why remove .flv export from Premiere Pro CC 2014? And what's a good workaround?

Why remove .flv export from Premiere Pro CC 2014? And what's a good workaround?

OK, so you want to put it on your own web page. That's fine as long as you know how to create a web page.
The next thing you have to decide is how big do you want the video to appear on the web page. Many people just post on YouTube and then embed the video into their web page. That way, the video can take advantage of all of the various sizes that YouTube provides.
In any case, I suggest that you use H.264. But the data rate depends on the size of the file. If you are going to display it in HD, then you probably want to start at about 20Mb/s and go up or down from there. The required data rate depends on what you find acceptable, and that depends on the amount of movement in the video. For example, a talking head next to a white board explaining something requires a lot less bits to represent the image because less changes are taking place from frame to frame. If you use 10Mb/s for that, you might find 20Mb/s or more is required to make you happy if you shot a football game from the sidelines.
I generally use settings that look like this image. If you have any questions as to why I choose these settings, feel free to ask.

I created a file in Photoshop CS5 (a photo) and another in Illustrator CS5 (a graph) to place in my InDesign CS5 brochure. When the Photoshop and Illustrator files are placed in InDesign, they look blurry - whether viewed in InDesign, printed, or saved as

I created a file in Photoshop CS5 (a photo) and another in Illustrator CS5 (a graph) to place in my InDesign CS5 brochure. When the Photoshop and Illustrator files are placed in InDesign, they look blurry - whether viewed in InDesign, printed, or saved as a PDF. Can anyone give me some tips on how to fix this? Thanks!

Ask in the program forums
This forum is about the Cloud as a delivery process, not about using individual programs
If you start at the Forums Index http://forums.adobe.com/index.jspa
You will be able to select a forum for the specific Adobe product(s) you use
Click the "down arrow" symbol on the right (where it says ALL FORUMS) to open the drop down list and scroll

Premiere pro / After Effects CS6 upgrade , render doesn't save ?

Hi, I have just upgraded CS5.5 to CS6.
I have opened and converted a previous project in CS6 which is linked to After Effects via the dynamic link. The media opened ok but even though it was fully rendered and saved from the previous version I had to re- render the entire sequence ..l. It's a 4 minute timeline and took over an hour to render in premiere CS6 .
Now I have come back to the project today , I have opened After Effects and then opened the project in premiere pro, all the media is connected but I have a red render line again and another hour to wait for rendering until I can start working.
Any tips on getting the render to save so I don't have to re- render each time I open the project.
Is this a problem with converting older CS5.5 projects in CS6 ?
My system is :
IMac 3.1 Ghz i5
12gb
OS10.7.4
Thanks
Mark

Ok thanks. What about this card?
Amazon.com: EVGA GeForce GTX 770 Superclocked with ACX Cooler 4 GB GDDR5 256-Bit Dual-Link DVI-I/DVI-D HDMI DP SLI Ready…
It's been recommended before.

Top 15 Issues/Fixes Needed in the next Premiere Pro release/update (CS6.5 or CS7)

I’m excited for what’s coming next in Premiere Pro CS6.5 or CS7 (whichever update is next). As a former FCP7 user myself, Premiere CS6 was a quick and necessary switch (especially after changing the main keyboard shortcuts back to what I was used to). I’ve since gone back to FCP7 on occasion for certain things and I can tell you that I’m so glad I’ve switched. For all the headaches and serious errors that I still get daily/weekly with Premiere Pro CS6, it’s still definitely a big step up. I'm encouraged by staff members like Mitch W. that have expressed confidence that many of these issues will be resolved in the next release. Here is my personal list of “Top 15 issues/fixes” needed in the current Premiere Pro CS6…
(Adobe STAFF...feel free to print this out and hand it to the engineers responsible for making changes )
1) The infamous multicam FLAW. Needing no introduction…when you are editing your video in the multicam window and you hit pause or stop Premiere has decided that’s a great time to make a cut on your timeline and also switch angles back to the original angle whether you like it or not. You cannot stop ever while editing multicam without Premiere making these unwanted cuts and angle changes. Awful. Multicam in PPro is otherwise pretty nice, but this issue is terribly counter-productive especially when you are editing longer complex multicam sequences. Imagine if every time you hit pause or stop in the regular timeline it made a cut there and switched clips. Ugh. You get my point.
2) The audio meters/levels do not work while in the multicam window. A staff member in the forums (I think it was you) said this was a bug. Hope it will get fixed. The audio levels work in every other window and its essential to be able to keep an eye on the levels while editing multicam.
3) Ticktime.cpp-207 error. Ugh. What a nightmare. I have confidence that it will be fixed soon. Mitch W. from the forums is my new hero for taking on this error. How to replicate it?…simply have 6 (or 7) or more clips with the warp stabilizer effect added on the same timeline as a nested multicam clip and you get this error upon reopening your project. The more warp stabilizers you use, the more times you’ll have to hit “continue” to get through the error before you can open your project or export it to AME. I deal with this every single day because all my projects use these two elements. Most of my projects I have to hit “continue” on the error message upwards of 350-450 times to open my projects. Gets old fast.
4) Icon View order control. When you display all your clips in icon view instead of a list view (In the project window), there is no metadata to allow you to put the clips in order somehow (or at least maintain the order that you have in the list). There are roundabout workarounds, but c’mon.
5) Warp Stabilizer fixes…it is an AMAZING tool (far, far, far better than smoothcam in FCP7) BUT…it has it’s issues. Since I use hundreds of times/week (no exaggeration) I know it’s functions/flaws really well. The issues with Warp Stabilizer:
a) #3 above
b) Toggle OFF the effect after it’s applied and then hit Analyze again and PPro crashes. (easy to avoid but annoying bug)
c) If a clip is in the middle of stabilizing (not just analyzing…but the final step labeled “analyzing”) when Auto-save comes up…most of the time PPro freezes and crashes.
d) The DEFAULT “method” (in the settings for Warp Stabilizer) should NOT be “Subspace Warp”…it should be “Position, Scale, Rotation”. Why? It’s FAAAAARRRR better and more efficient. 95 out of 100 times it causes MUCH less “wobble” in the final stabilized clips AND most importantly 95 out of 100 times it scales the video less. Way better method.
6) The ability to open multiple projects simultaneously. As simple as FCP7 had it…or even better…as cool and efficient as FCPX does it would be nice.
7) The ability to mark a clip and not just a point on a timeline (because if you move the clip, the marker doesn’t go with it). I know you can use “Clip Marker” but it's very limiting, can't be moved, can't add notes, can't advance to the next marker (as far as I know). Also a marker list like FCPX has would be nice so you can see your markers all in a list at a glance and adjust them as needed.
8) Ability to select a clip in the Project window and find out where it’s used in the timeline. I LOVE how you can do the reverse and take a clip in the timeline and “Reveal in Project Window” but it would really help to go the other way around. Dealing with several hundred clips for every project I’ve missed this feature from time to time (FCPX handles this really well).
9) Add a through-edit indicator in timeline and “re-join clips” option. If you cut a clip but keep both clips together it’s just one continuous clip. But I really hope Premiere adds the not only an indicator of some sort (like FCP7′s way of having two small red triangles facing each other on that cut) so you know it’s one continuous clip BUT ALSO the ability to right-click and “re-join” the two clips into one.
10) When clip is double-clicked in timeline, CTI position in source viewer should match location in timeline. This one is pretty annoying and a fix would be incredibly helpful. The way it is now is very counter-productive. Definitely hope this gets fixed ASAP.
11) Better border controls for images/videos. Can’t do much with images right now in PPro. At least allow to customize the color and size/strength of it’s borders and shadows.
12) Better support for Mac/Apple's top end computers/GPU's. I'm still surprised that 2011 top of the line iMac cards (AMD 6970M) that have 2gb of ram are not supported. I’m sure/I hope 2012 iMac’s will be supported with their new Nvidia GPU’s…but I’ll hold out hope that the top iMac (up until 3 months ago) is supported at least at it’s full power. All around better Mac support would be great considering the wave of new users coming over from FCP.
13) Opacity/Transparency issues with EXPORTED videos with Cross Dissolves, etc. For some odd reason videos exported from Premiere CS6 have issues with cross dissolves or minor transparency. I’ll try to explain…in the program window of PPro CS6 cross dissolves look fine. Also, if you take a clip and stack it on top of another clip and put the top clip at say 99% opacity instead of 100 it looks like it should in PPro. But, if you export the clips you’ll quickly see that there are issues. It’s almost like the exported videos dissolve from 5 to 95. They skip the subtle beginning (0-5%) and subtle end (95-100%) of any fade. A clip in PPro as described above that is on top of another but set at 99% will look more like 90-95% in the exported file ESPECIALLY if the two clips are contrasting (eg. top layer dark, bottom layer with bright elements). It’s like the opposit of ease-in/ease-out. I have to ease-in/ease-out of every dissolve to avoid this issue…and even then, it’s not THAT much of an “ease” as one would hope. Another user in a forum once posted a video that shows how abruptly exported videos end their transparency changes…see: THIS SAMPLE VIDEO Perhaps this is a GPU/processing issue with AME vs. Premiere Pro but whatever it is, it should be fixed so videos you export look like the videos you edited!
14) Better control in Creative Cloud over which devices are “activated/deactivated” We have 3 computers and it would be nice if one could log in to their Creative Cloud account and see a list of which devices they have and just toggle on/off which one’s are activated/deactivated. This is especially helpful when you are mobile and forget to deactivate one of your two home/office devices so you’re stuck now until you get back to the home/office to deactivate it. This is not a Premiere thing, but just a general wish.
15) Ability to sync multicam clips automatically using the audio. Plural eyes apparently does this well. Would be nice to have it built into Premiere like FCPX does. Select all the shots you want to sync, One button click, wait a few seconds, done.
That’s my top 15. Everything else is awesome in my opinion for what I do 10 hours a day 6-7 days a week. I’ve included bug reports/feature requests for all of these at one point but if you are someone else reading this go to the following link and ask for these issues to be fixed: FEATURE REQUEST/BUG REPORT
I wish Adobe did smaller updates more often. Because even if they were smaller updates, we’d at least know you are working on fixing some of these issues that have plagued this NLE for years. Holding off fixes for one or two big “updates” every year is tough to deal with in a world of the ever updating apps we live and play with daily on our phones. I realize Premiere is a much larger scale and far more professional than a phone app, but hopefully you get my point. Here’s to hoping the next release (NAB 2013?) resolves all my top 15 issues. Here’s to hoping that these issues will be resolved sooner than later so I can stop raising hell in various forums. I’m honestly ready to start praising and defending Premiere Pro instead of griping about it’s bugs and flaws. It’s a fantastic program “on the way” to being the best. I hope.

Nice list, however it does seem a little bit like you may be hoping that Adobe provides the Final Cut 8 package that Apple never delivered on. Having edited primarily with P-Pro for the last decade, I hope Adobe focuses more on getting the next release to run as smooth as CS5x does, strangling and crucifying all the codec and playback bugs that arose in CS6. To me, it appeared that too many of the changes in CS6 were semantic or cosmetic, meant to give a FCP user more familiarity. Why change the name of an edit function from "overlay" to "overwrite" after 15 years? Because it enhances the product, or because that is what Apple called the function in FCP? If Adobe renames the Program Monitor to the "Canvas" with the next release, I think that I might be sick. There were nice additions to the Creative Suite as a whole, but I hope the next Premiere release reverses some missteps made in CS6, and focuses more on stability and enhanced functionality. I also really hope that they have an open ear towards criticism; Apple did not and their users ended up with FCP-X
It saddens me that the fixes I want most in a future release were purposeful changes between CS5x and CS6x.
1) Provide the options for transport controls in the source and program monitors. All of the users at my office hate that the jog and shuttle were removed in CS6. JKL was an option prior to CS6 and if we liked it we would have used it. I keep reading the justification that this change was meant to save space and streamline the UI. I can't express cordially how much this bothers me to look at the empty wasted space in my CS6 UI where the transport controls should be. The experiment has gone on long enough.
2) Restore the 3 Way Color Corrector to its previous functionality. The 3 way color corrector has been effectively neutered in CS6. Where in CS5x and earlier releases one could separately target the input/output levels of Highlights, Midtones, and Shadows, CS6 has only a master input/output level control. Why is less control better? Is it a 3-Way Color Corrector or a 1-Way Color Corrector?
3) Restore Clip and Timeline markers to their previous functionality. I don't even.... I can't. A user shouldn't have to do work arounds to create a modicum of functionality. This again was an attribute that wasn't broken in earlier releases.
4) Simplify the the task of pasting media into a targeted track. As it is now, pasted items will always go to the lowest activated track instead of the targeted track.
Lastly I would like the Adobe Premiere teams to consider what an amazing accomplishment Premiere CS5x was. Upon CS5's release, a good portion of competitor's workflows became obsolete. CS5.5 refined, stabilized, and expanded functionality.
CS6 changed the UI around, moving or deleting buttons, changed keyboard shortcuts, and renamed functions. Oh, and added hoverscrub, you know...like FCPX. In exchanged there was loss of functionality, stability issues and broken codecs.
I really hope the next release is more like CS5x and less like FCPX

AE Warp Stabilizer (C5.5) Vs. Premiere Pro Warp Stabilizer(CS6)

Was wondering what folks experience was in CS6 with WS in Premiere Pro ?
Is it the same WS as in CS 5.5 in AE ? Has it been improved ?
My expereince with WS in CS5.5 (AE) has been very hit and miss. Some scenarios it works very well, others it tends to "warp" the footage so that it appears to be a disco scene on speed.
Any CS6 folks care to chime in ?
Thanks.

It seems that Premiere CS6 stabilizer is identical to AE CS5.5
Sometimes it helps to use Detailed Analysis, but in my case it did not work. I have a boat in the storm because stabilizer hooked to the moving object. I would like Adobe to add the ability to mark some key points, because full auto is not a professional style of work. However, even if I'll do a feature request it will not be implemented until CS12. I would be very surprised to see some improvements in CS6.5/CS7, but it is not Adobe style. This issue is known for 2 years from now and it is sad that they think about features quantity, but not feature quality (in terms of functions).
Sorry for being emotional, but 2 bugs for one project is too much for me for today.
However, I would like to thank them for adding Adjustment Layers. Saves time a lot.

Premiere Pro CC2014 suddenly slow and unusable

Last week I started a new project with PProCC2014 and thought nothing of the program's reliability because I've used it to this point without a problem. This new project is a big one with tight deadlines, and I've run into a major issue with what I believe is CC2014 as the culprit from the reading I've done thus far:
Premier Pro 2014 is very sluggish
Adobe QT 32 Server is Not Responding in Premiere CC
My problem is similar to the one described in the first link above. I noticed my QTServer was not responding either so I addressed it as they did in the second link. I started my project and imported about 1500 low-res stills to put together some assemblies. Initially, sfter a couple of hours building the project Premiere suddenly became unresponsive - or so incredibly sluggish that it is unusable. If I scrub the timeline I can hear audio,if I hit play I can hear audio, but nothing happens in the monitor. Clicking on other panels takes 10 second or longer for it to recognize. At first I thought it was a corrupt image so I cleared all of them out to import them one by one as required. But that approach eventually resulted in the same problem. That suddenly Premiere would freeze up and I would have to start a new project from scratch, doing something just a little differently. My third try began 24 hours ago and I was able to put a whole day in - I built three assemblies and was just about to export a screener when Premiere froze. I then figured the problem wasn't with me or my project so I did some reading and found the link above which describes best what I am experiencing. But the solutions in that post didn't help, not did fixing the QT32 Server so I'm at the point where I'm about to cancel my subscription to Adobe CC and fall back to CS6 (rebuilding it from and XML, which I was fortunately able to export with some patience). I've lost nearly a week of work due to this and can't afford any more false starts.
My system:
iMac late 2012 w/Yosemite 10.10.1
32GB RAM
Nvidia CUDA Drivers 6.5.14
Quicktime 7.6.6 installed
Help would be appreciated.
Greg

Hi raffaele mariotti,
Please mention some more information mentioned below.
1. Have you taken any backup through time machine for your user profile?
2. What are the media files that you are using in Premiere Pro CC 2014 ?
Regards,
Vinay

Premiere Pro 2014 is crashing and freezing and I have to use force quit to get it to shut down.

Premiere Pro 2014 is crashing every day. i am running Premiere Pro 2014 on a 2013 imac with 3.4 GHz Intel Core i5 with 16 GB RAM. Playback on premiere continually freezes and the program crashes. Or the playback will start to freeze and then I save and close the project file/program, but the program will not close and I have to force quit. This is extremely frustrating. Premiere Pro CC was super stable and I rarely if ever had a problem. I have changed my permissions to give myself read/write. I have created a new project file in 2014 and then imported all my sequences from my updated project file but none of these strategies have worked. I am considering creating a new project file and going back to working solely in CC because I am on a deadline and troubleshooting this issue is taking up so much time.

I have had to force quit PP CC four times today. The fourth was when it crashed while trying to reopen it. I have had exactly the same problems as described above. I have no solutions to offer. I will go through a week of constant Premiere Pro bugs and poor performance then experience a period that seems too good to be true only to end up having a day like today. I can't believe that they call this a professional editing suite. It just wastes so much of my time pissing around trying to fix things and managing all the extra render and preview files it makes each time I have to save a new copy of a project which usually results in renaming it. It gets confusing after a while. Really not happy with this and have begun to learn Avid so as soon as this project is done, PP will be history.

Adobe Premiere Pro is constantly crashing and freezing

I'm a new user to adobe and I've used their free trials in the past for cs6, but this latest version of Premiere Pro keeps crashing while I'm in the middle of projects. I really don't know what the problem is. Is there something I need to update?

Macbook Pro 13" 2013
OS Mavericks
8gb RAM
Processor 2.5 GHz Intel Core i5
Graphics Intel HD Graphics 4000 1024 MB
I forget what it said specifically, but the error message said something along the lines of
"There was a serious problem with Premiere pro and it needs to shut down immediately. It will try to save your current session"

Premiere Pro is not responding and using 587% of CPU

My projects are going extrordinarily slow. and according to the activity monitor, Premiere Pro is using 587% of the CPU and the fan is going non-stop and the macbook is always very hot when I start this program. I feel this could physically damage my laptop if I left it running to render only 286 frames of a clip that takes over an hour to do at this high usage.
Only this program does this to the CPU When I turn it off Premiere Pro, the heat starts to cool off and the fan slows down, and it eventually goes quite again
What would be causing this?
I am using a new 15 inch macbook that is a few months old with 16 GB of RAM and 2.6 GHz processor.
I feel Premiere Pro could could almost be a fire hazzard to my home. What is wrong with my system? have there been previous lawsuites for CS6 for this issue?
Andy

Update the GoPro firmware, shoot some footage, and then see if the new footage will work in Premiere Pro for you.

Premiere Pro CC 2014 Crashing and Bogging Down on Documentary Film Project

We have been working in Premiere on this documentary film for months.
As we reach completion it is beginning to really bog down and crash a lot.
Equipment is
iMac 27 inch 3.5 GHz Intel Core i7 Late 2013 Model
Apple Cinema HD Display
32 GB 1600 Mhz DDR3 RAM
NVIDIA GeForce GTX 780M 4096 MB Graphics Card
1TB internal SSD Drive
We are running Premiere Pro CC 2014.0.1 and have remained there because we don't want to upgrade the software in the middle of the project.
The media is all on the external drive. It's a USB 3.0 connection. There is quite a lot of footage that we are working with.
We do have some After Effects comps that are linked in the project and we have exported the ones that are complete as QuickTimes to try to stop that from bogging us down.
Any advice on how we can manage this crashing and freezing problem would be much appreciated.
We don't have the cash to upgrade the computer and it has been working pretty well for us so far.
Here are things we have done:
Made a smaller timeline because we were working on one that was the entire movie.
Turned off the secondary monitor and unplugged it.
We are looking at moving the render cache off the external drive to a thunderbolt drive, but I'm concerned that this may take a long time.
Any recommendations would be greatly appreciated.

Splitting up the read/write items is rather a key to getting smoother operation out of PrPro. Either that or putting things on a large RAID-0/5, this sort of thing is covered over on the
Tweaker's Page ...
http://ppbm7.com/index.php/tweakers-page
And I highly recommend you take a look. Their info isn't just "we think ... " ... but the results of many many carefully crafted test sequences run on many machines with all sorts of hardware bits & pieces. You can also register, download the PBM test and run it on your own machine. It takes only a little while to do so, and with the logger app that's included and posting the results back to them, you can get a very good breakdown on where your machine is doing ok ... and where any choke points are occurring.
I think this would be good for you right now ... you need to get stuff done, not guess & try things.
Neil

Premiere Pro CS5.5 to CS6 and save back to CS5.5

Similar Messages

Maybe you are looking for