Moving from CS6 to CC2014 messes up sequential clip references

I have a CS6 project I've brought into CC. The project media includes video clips (in Canon MXF format) that were split in-camera because of the file size.
In CS6 the clips were sequenced back together with no problems. In CC, the second clip appears to reference the first, so that any edits using clip 2 actually play back the content of clip 1. In the bin the clip name is as it should be.
I have tried all manner of workarounds, including reimporting the clip, replacing footage (both in the bin and clip-by-clip), importing the CS6 timeline, EDLs etc. but either the same thing happens or I get the grey stripes across the clip (which I believe indicates being out-of-timecode-range). The workaround I've had most success with involves duplicating the file, renaming it (strangely this only works if the start of the filename is different), importing the new clip and manually re-editing each one through laborious cut and paste of the edit points. It's a pain in the *undefined* and still isn't ideal; the replacement clips come in with stereo audio instead of dual monos as they should be so I have to fiddle even further.
Is this a bug? Am I being oblivious to some new (or old) feature? Would I be better off staying in CS6?
Cheers

Would I be better off staying in CS6?
For this project yes, then mov one to CC14.

Similar Messages

Moving from CS6 to CC (Question)

Hi everyone,
As the title explains, I'm moving forward to upgrade my Premiere cs6 to CC.
My question is: Can I open old projects from cs6 in the new CC? Can I fully work with them, like I did on CS6?
Thank you!

BEST PRACTICE: Complete current projects in THEIR version, and start new ones in the new version. Staffer Kevin Monahan (former life a major professional user/teacher of FCP before becoming an Adobe staffer) who frequents this forum preaches that as THE proper work-pattern in ANY NLE or video app for professional use. You gotta be able to get that work out, and though projects MAY transfer forward just fine, if they glitch up and you didn't keep the old project pristine ... you're screwed. Many people have up-graded projects without a hitch, but if you go through this forum you'll find a number that ... um ... it wasn't a happy moment. Or week. Or month.
His basic recommendation ...
- Any projects that will have a "final" state are worked to that state in the "old" version.
- The newer versions can be downloaded and installed separately from the older ones ... use them for any new projects and if something or some effect doesn't like the new version, you can still run the old one.
- Projects that are always on-going (like tv series) should be extensively tested with a COPY of you previous-version project and then ... when any issues that MAY pop up are resolved, move forward with the new version on its new project. NEVER allow the "main" copy of the old project to be modified past it's version.
- Keep past versions on your computer, perhaps renaming the icons so you know which programs "match with each other, across the PrPr, Ae, Sg, Audition, and AME set.
Neil

Porting issues with boost::regex when going from CS6 to CC2014 using Xcode

I have a working project in CS6 that uses the boost::regex framework that I'm having problems porting into CC2014.
I ported this project by using Dolly to create a new project, then coping the old source files across, finally updating the various out dated InDesign API calls that appeared when I compiled. For the use of regular expressions I added the debug and release builds of the boost_regex.framework to the respective targets.
Now, for the debug build the new CC2014 projects builds happily. But when I switch to the release build I get a few linker errors. They are all something like:
Undefined symbols for architecture x86_64:
"boost::re_detail::get_mem_block()", referenced from:
boost::re_details::perl_matcher<__gnu_cxx::__normal_iterator<char const *, std::string>, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const *, std::string> > >, boost::regex::regex_traits<char, boost::cpp_regex_traits<char> > >::find_imp() in SbRegex.o
etc.
I did a bit of reading through the boost header files. The odd thing is that the "get_mem_block()" appears to be defined for the pre-processor option BOOST_REGEX_NON_RECURSIVE, while in the project settings for BOOST_PREPROCESSOR_DEFINITIONS contains BOOST_REGEX_RECURSIVE. These two settings are mutually exclusive and there's pre-processor logic that blocks having both cases defined at once.
This recursive option is used to control how memory is used while processing a regular expression, so seeing a get_mem_block() call (other link errors involve a call to put_mem_block) sort of makes sense being calls that look like something to do with memory.
I'm trying to figure out why debug builds, but release build fails. Does this problem look familiar to anyone? Anyone have any suggestions to try to fix it?

Thanks for the reply, Bartok, but those didn't seem to work for me. Maybe I applied them incorrectly as that thread was for the Win platform and not Xcode and I might have translated the solution poorly.
Basically I went to the "Release_Cocoa64" target, and scrolled down the "Build Settings" page. I then edited the BOOST_PREPROCESSOR_DEFINITIONS field.
First I tried just appending BOOST_SYSTEM_NO_DEPRECATED.
Second I thought that this might be a macro of some sort so I tried $(BOOST_SYSTEM_NO_DEPRECATED).
Finally, I deleted all the previous values and added "BOOST_ALL_DYN_LINK BOOST_REGEX_USE_CPP_LOCALE BOOST_REGEX_RECURSIVE BOOST_HAS_ICU=1 BOOST_ FILESYSTEM_VERSION=3 BOOST_CHRONO_HEADER_ONLY BOOST_SIGNALS_NO_DEPRECATION_WARNING".
As you might guess from the experimentation I got none of these to work. The error that I was getting has remained exactly the same.
One difference that I assumed between the Win and Xcode version is that Win separates the values with a semi-colon whereas Xcode separates with a space.
My only other thought is maybe I edited the wrong field. Is BOOST_PREPROCESSOR_DEFINITIONS the one?
As a final comment, the thread you gave me and my issue really comparable? I have other projects that don't use the boost::regex libraries and they build and run without issue. It's only when I try to use boost's regular expressions in a release build that I get problems when linking (debug build is still fine).
Also the link error looks different. The thread that you gave me points at "boost::system::error_category" as not being resolved, while I have problems resolving "boost::re_detail::get_mem_block".
I don't seem to have problems with basic boost - just the regular expression stuff.

Easily moving from CS6 to CC

Like most people, I'm really excited to see new versions of the software come out, and After Effects CC looks to be a great upgrade. That said, there is a moment of dread when installing the new software, when I realize I have to now migrate all my scripts, presets, and after market plugins into the new software, and is ultimately a block of time I'd love to avoid spending on that.
Apart from going through all the installers, which is not really any more efficient. Has anyone run across a streamlined way to do this? Written a handy script? or unlocked the secrets of the "migration" universe so that we can save some time?
To add... I'd love to see Adobe provide something to help facilitate this. Yes, I realize there could be some compatibliltiy issues that spring up, and they probably don't want to deal with that. At the risk of downplaying that possiblity... it would certainly help!
Thanks,
Stephen

Ok guys... I'm totally stuck.
Found my old Plug-ins (the ones that aren't in the Application folder), in ~/Library/Application Support/Adobe/Common/Plug-ins/CS6/MediaCore/
This is where the core Trapcode plugins exist, for instance.
Unfortunately, that folder doesn't exist for CC. Where should I move them too?
Thanks!

CS6 to CC2014 after effects video edits getting moved around

Hi,
We are having a weird problem after moving our whole department to CC2014 from CS6. Once we bring open a CS6 project in After Effects CC2014 all the video edits get thrown off by anywhere from 300 to 18000 frames in the actual edit layer window (in the composition the edit cuts are still in the same place). We are shooting on Canon 305XF's using the 50 mbps .MXF format.
When I open the same project in CS6 and CC2014 and look at the footage setting in CS6 the clip says 9403 total frames in the interrupt footage dialog. But when I open the exact same project in CC2014 it says 83160 frames. If anyone has seen this issue can you point me in the right direction.
I really need to have an easy fix for this issue as it is going to effect about 100 large older projects.
Thank you
Keith

Yeah it is looking like a footage interpretation to me as well but wish there was some kind of auto fix.
The broken process is opening the CS6 .aep with CC2014 .aep.
What will work is opening the original footage edits that I made in Premiere Pro CS6 in Premiere Pro CC2014. Then I save the Premiere Pro CC2014 and import into the .aep CC2014 that was had all the edits that went funky. Since the composition were still the same I was able to replace the old broken edit compositions with the new CC2014 saved versions and now all the footage is correctly imported.
The main problem with this process is how many projects I would have to do this to would make it a total pain. As well I am very worried about such a manual process mistakes being made.

Trouble moving from lightroom to Photoshop CS6 raw editor

I am having trouble moving from my lightroom 4 to Photoshop camera raw. I can move directly to Photoshop but would like to use the raw editor in photoshop CS6 and not the lightroom editor

Hi,
You could use Photo>Edit In>Open as Smart Object in Photoshop
(or right click on the photo and Edit In>Open as Smart Object in Photoshop)
Then double click on the smart object thumbnail in the layers panel to open camera raw.

I need Encore CS6 and it is not available on Creative Cloud. Neither is Premier Pro CS6 which supposedly installs Encore CS6. I need to burn a DVD from my mpeg4 output from Premier Pro CC2014. What should I do?

I need Encore CS6 and it is not available on Creative Cloud. Neither is Premier Pro CS6 which supposedly installs Encore CS6. I need to burn a DVD from my mpeg4 output from Premier Pro CC2014. What should I do?

You should probably post your question about burning a DVD from Premiere Pro in the Premiere Pro forum
Here is a link to info regrding getting CS6 applicarions thru the Cloud with a full subscription...
Get CS6 Apps from Cloud Subscription:
Download previous versions of Adobe Creative applications -
http://helpx.adobe.com/creative-cloud/kb/download-previous-versions-creative-applications. html

About "Append mode" of cs6, cc & cc2014 project file in order to insert xml sequence which is sent from 3rd-party tool

let me ask you all something about “Append mode” of cs6, cc & cc2014 project file in order to insert multiple xml sequence which is sent from 3rd-party tool into specific project file .
Finalcut pro 7 & x was supported this , but i am not sure will support this on cs6, cc & cc2014 .
is this possible ??
could someone let me know about this - append mode possible or not ??

let me ask you all something about “Append mode” of cs6, cc & cc2014 project file in order to insert multiple xml sequence which is sent from 3rd-party tool into specific project file .
Finalcut pro 7 & x was supported this , but i am not sure will support this on cs6, cc & cc2014 .
is this possible ??
could someone let me know about this - append mode possible or not ??

I want to migrate my custom new doc sizes from cs6 to cc/cc2014

I want to migrate my custom new doc sizes from cs6 to cc/cc2014 where can i find that file to copy to new versions of Photoshop?

Yes it look like Adobe migrate presets misses your new document size presets. I was able to copy my "New Doc Sizes.psp" preference file from CC preferences to CC 2014 preferences a manual migrate at best.

How do I transfer all my plug-in filters, etc. from CS6 to PS-CC?

How do I transfer all my plug-in filters, etc. from CS6 to PS-CC?

Read this article - http://www.myfirstmac.com/index.php/mac/articles/how-do-i-move-my-itunes-library -from-pc-to-mac-and-keep-my-settings-intact
Your .wma (proprietary to Windows format) will not play or convert in iTunes Mac so convert them in iTunes Windows to .mp3 before moving your library. There are other converters on the Internet - do a search.
MJ

Best practice for moving from a G5 to a new Mac with SL

I am receiving my new iMac today (27") and am very excited
However I want to move over using the best practices to assure that I remain excited and not frustrated
My initial thoughts are to boot it up and doe the initial set up - to move my iPhoto library over and to use migration assistance to move the rest of my data files
Then to install all of the extra software that I can find the packages for from the original installation disks
And then finally to use migration assistant again to move over any software that I can not find original disks for (I've moved from Mac to Mac to Mac over and over and some of the software goes back to OS 9 (and won't run anymore I guess)
Is this a good way
OR
will I mess up doing it this way
OR
am I spending far too much time worrying about moving old problems over and would be better off to just turn MA loose and let it do its thing form the beginning?
BTW - mail crashes a lot on my existing system - pretty much everything else seems ok - except iPhoto is slow - hoping that the new Intel dual core will help that
LN

Migration Assistant is not a general file moving tool. MA will migrate your Applications and Home folders transferring only your third-party applications. MA will transfer any application support folders required by your applications, your preferences, and network setup. You do not have a choice of what will be migrated other than the above. MA cannot determine whether anything transferred is compatible with Snow Leopard. I recommend you look at the following:
A Basic Guide for Migrating to Intel-Macs
If you are migrating a PowerPC system (G3, G4, or G5) to an Intel-Mac be careful what you migrate. Keep in mind that some items that may get transferred will not work on Intel machines and may end up causing your computer's operating system to malfunction.
Rosetta supports "software that runs on the PowerPC G3, G4, or G5 processor that are built for Mac OS X". This excludes the items that are not universal binaries or simply will not work in Rosetta:
Classic Environment, and subsequently any Mac OS 9 or earlier applications
Screensavers written for the PowerPC
System Preference add-ons
All Unsanity Haxies
Browser and other plug-ins
Contextual Menu Items
Applications which specifically require the PowerPC G5
Kernel extensions
Java applications with JNI (PowerPC) libraries
See also What Can Be Translated by Rosetta.
In addition to the above you could also have problems with migrated cache files and/or cache files containing code that is incompatible.
If you migrate a user folder that contains any of these items, you may find that your Intel-Mac is malfunctioning. It would be wise to take care when migrating your systems from a PowerPC platform to an Intel-Mac platform to assure that you do not migrate these incompatible items.
If you have problems with applications not working, then completely uninstall said application and reinstall it from scratch. Take great care with Java applications and Java-based Peer-to-Peer applications. Many Java apps will not work on Intel-Macs as they are currently compiled. As of this time Limewire, Cabos, and Acquisition are available as universal binaries. Do not install browser plug-ins such as Flash or Shockwave from downloaded installers unless they are universal binaries. The version of OS X installed on your Intel-Mac comes with special compatible versions of Flash and Shockwave plug-ins for use with your browser.
The same problem will exist for any hardware drivers such as mouse software unless the drivers have been compiled as universal binaries. For third-party mice the current choices are USB Overdrive or SteerMouse. Contact the developer or manufacturer of your third-party mouse software to find out when a universal binary version will be available.
Also be careful with some backup utilities and third-party disk repair utilities. Disk Warrior 4.1, TechTool Pro 4.6.1, SuperDuper 2.5, and Drive Genius 2.0.2 work properly on Intel-Macs with Leopard. The same caution may apply to the many "maintenance" utilities that have not yet been converted to universal binaries. Leopard Cache Cleaner, Onyx, TinkerTool System, and Cocktail are now compatible with Leopard.
Before migrating or installing software on your Intel-Mac check MacFixit's Rosetta Compatibility Index.
Additional links that will be helpful to new Intel-Mac users:
Intel In Macs
Apple Guide to Universal Applications
MacInTouch List of Compatible Universal Binaries
MacInTouch List of Rosetta Compatible Applications
MacUpdate List of Intel-Compatible Software
Transferring data with Setup Assistant - Migration Assistant FAQ
Because Migration Assistant isn't the ideal way to migrate from PowerPC to Intel Macs, using Target Disk Mode, copying the critical contents to CD and DVD, an external hard drive, or networking
will work better when moving from PowerPC to Intel Macs. The initial section below discusses Target Disk Mode. It is then followed by a section which discusses networking with Macs that lack Firewire.
If both computers support the use of Firewire then you can use the following instructions:
1. Repair the hard drive and permissions using Disk Utility.
2. Backup your data. This is vitally important in case you make a mistake or there's some other problem.
3. Connect a Firewire cable between your old Mac and your new Intel Mac.
4. Startup your old Mac in Target Disk Mode.
5. Startup your new Mac for the first time, go through the setup and registration screens, but do NOT migrate data over. Get to your desktop on the new Mac without migrating any new data over.
If you are not able to use a Firewire connection (for example you have a Late 2008 MacBook that only supports USB:)
1. Set up a local home network: Creating a small Ethernet Network.
2. If you have a MacBook Air or Late 2008 MacBook see the following:
MacBook (13-inch, Aluminum, Late 2008) and MacBook Pro (15-inch, Late 2008)- Migration Tips and Tricks;
MacBook (13-inch, Aluminum, Late 2008) and MacBook Pro (15-inch, Late 2008)- What to do if migration is unsuccessful;
MacBook Air- Migration Tips and Tricks;
MacBook Air- Remote Disc, Migration, or Remote Install Mac OS X and wireless 802.11n networks.
Copy the following items from your old Mac to the new Mac:
In your /Home/ folder: Documents, Movies, Music, Pictures, and Sites folders.
In your /Home/Library/ folder:
/Home/Library/Application Support/AddressBook (copy the whole folder)
/Home/Library/Application Support/iCal (copy the whole folder)
Also in /Home/Library/Application Support (copy whatever else you need including folders for any third-party applications)
/Home/Library/Keychains (copy the whole folder)
/Home/Library/Mail (copy the whole folder)
/Home/Library/Preferences/ (copy the whole folder)
/Home /Library/Calendars (copy the whole folder)
/Home /Library/iTunes (copy the whole folder)
/Home /Library/Safari (copy the whole folder)
If you want cookies:
/Home/Library/Cookies/Cookies.plist
/Home/Library/Application Support/WebFoundation/HTTPCookies.plist
For Entourage users:
Entourage is in /Home/Documents/Microsoft User Data
Also in /Home/Library/Preferences/Microsoft
Credit goes to Macjack for this information.
If you need to transfer data for other applications please ask the vendor or ask in the Discussions where specific applications store their data.
5. Once you have transferred what you need restart the new Mac and test to make sure the contents are there for each of the applications.
Written by Kappy with additional contributions from a brody.
Revised 1/6/2009
In general you are better off reinstalling any third-party software that is PPC-only. Otherwise update your software so it's compatible with Snow Leopard.
Do not transfer any OS 9 software because it's unsupported. You can transfer documents you want to keep.
Buy an external hard drive to use for backup.

Moving from Gmail to MobileMe/.Mac, in relation to an iTunes Store Account

I'm moving from Gmail to MobileMe since I got my iPhone, and as with every email change, a whole mess of online accounts follow. The process is simple enough for third parties like social networks, but Apple wants my life to super convenient and easy, and in the process made it even more confusing. My MobileMe account apparently already has an attached iTunes Store/Apple account, so I can't change my old account to log in with the @me instead of my @gmail. While I could simply stop using the Gmail, I receive iTunes allowances which would need to be re-set up and would lose store credit. What would be best is to simply merge the two accounts. Is this in any way possible?

HI,
can you still update your UAE purchased apps after this change?
Thx

Opening CS3 files from CS6 InDesign

We are looking to upgrade the office from CS3 to CS6 Creative Suite. Can InDesign files from CS3 be opened in straight into CS6? If not, what is the best way to access the CS3 files from CS6?

Can they be opened directly? Yes.
Should they be? Harder to answer.
I've never had a problem with any file I created moving from an old to anew version, but we've seen reports here from other users who found converting CS3 or CS4 files to CS5 or CS5.5 seemed to be OK right up until they failed, often after extensive editing and while trying to export PDF. In general, exporting these same files from the earlier version as .inx or .idml, and opening that in the new version did not fail.
CS6 is too new to have had many similar reports, and I want to stress that these problems are probably isolated and indicate, I suspect, some underlying corruption in the original file (which might have caused failure in the original version at some point, too), but I've persaonally adopted a policy of export from the original for any file that is going to get converted. It isn't worth the risk compared to the short amount of time involved in taking precautions.

Moving from mask to image.

I've just moved from CS3 to CS6. Previously, when working on a layer mask I could make the image active by Command – ~ . This doesn't work now - is there another keyboard shortcut for this? I can't find any references to this anywhere. I use a Mac, OS 10.7.4.

From CS4 onwards, you have to 'Option + click' on the layer mask to reveal toggle between image and mask.
However, there is an option CS6 has for seasoned legacy users, like you!
Photoshop > Edit > Keyboard Shortcuts.
Enable checkmark on highlighted read area in the image - Use Legacy Channel Shortcuts. You'll be able to revive the legacy shortcuts for channels/ layers.
Do note that CS6 has a lot of improvements in shortcut commands for other layer/ channel options and tools within PS. You will be sacrificing these if you choose to use Legacy Channel Shortcuts.
Nevertheless, trust this helps

How to get keyboard preferences from cs6 to cc

Does anyone know how I can get my keyboard preferences and workspaces from CS6 apps over to the new CC apps? Most importantly Premiere's prefrences?

On a mac, these files were moved from the user library folder to the documents folder
Copy keyboard shortcuts - (not all keyboard shortcuts made it)
from
/Users/[your-user-name]/Library/Application Support/Adobe/Premiere Pro/6.0/[name].kys
to
/Users/[your-user-name]/Documents/Adobe/Premiere Pro/7.0/Profile-[your-user-name]/Mac/[name].kys
Copy Effect Presets
from
/Users/[your-user-name]/Library/Application Support/Adobe/Premiere Pro/6.0/Effect Presets and Custom Items.prfpset
to
/Users/[your-user-name]/Documents/Adobe/Premiere Pro/7.0/Profile-[your-user-name]/Effect Presets and Custom Items.prfpset
Preference Settings
from
/Users/[your-user-name]/Library/Application Support/Adobe/Premiere Pro/6.0/Adobe Premiere Pro Prefs
to
/Users/[your-user-name]/Documents/Adobe/Premiere Pro/7.0/Profile-[your-user-name]/Adobe Premiere Pro Prefs

Moving from CS6 to CC2014 messes up sequential clip references

Similar Messages

Maybe you are looking for