Increment and Save a few times a day is also a good policy. ... View more

Start a new Project, and try importing your problem Project into it. ... View more

If you're on CC, you can nest the clips you want at 12 FPS and change the frame rate to 12 fps in the Sequence Settings.  In earlier versions, you'd have to create a new sequence of the same dimensions, because you can't change the frame rate after a sequence is created. Have you tried opening your Pr Sequence in Ae, and rendering it from there?  Ae doesn't have the same problems with large JPEGs that Pr has. ... View more

This is a possibility:  You have a or some corrupted footage items in your timeline.  Try exporting between in and out the first half of your sequence.  Then, export the second half.  If there's a substantial difference in export times, the slow export likely contains your problem footage.   Keep reducing the export ranges until you isolate the culprit.  Then, replace it or transcode to another codec. I've also seen corruption in my Preview files, and media caches.  When I have a "was working fine, but not any more" situation, I do a deep clean.  Trash Pr prefs, trash previews, trash caches.  And if that doesn't work, search and destroy corrupt media.  Final straw: uninstall and reinstall Pr. Since you're on Mac, you might try Digital Rebellion's Corrupt Clip Finder.  I've been given hundreds of corrupt JPEGs from clients. Converting them to TIF or PNG has allowed me to finish my projects. Good luck. Edited to add new info. ... View more

FYI, using the Adobe Cleaner Tool does NOT flush "all things Adobe" from your drive.  Last time I ran it, I ran EasyFind, searching for "Adobe," and it found over 300 files with Adobe in the name.  If you want to truly start fresh, you need to remove those items manually. ... View more

Does your project happen to have stabilization applied to any clips?  Or, lots of keyframe animation? ... View more

Tim, you're welcome.  I think you are correct about me neglecting to empty the trash on the list I made above.  I've been working with Ae CC for about four hours now since I last posted, and it's smooth sailing so far. And thank you again for your vigilance in getting this sussed for us. Jim ... View more

I'm adding my name to the list of victims of this heinous shortcoming in Ae CC. I can open some projects with ProRes footage, and see and hear it for about five minutes before I start getting that error message for each footage item in the project.  Other projects won't even let me get that far.  I get the errors as soon as Ae starts scanning the footage. I can Save As CS6, and work with the same footage with abandon there.  MacPro3,1 - 10.8.4 (10.7.5 before I upgraded, too) - 32G RAM - Quadro 4000 for Mac with fresh drivers reinstall - Ae 12.0 Here's what I've tried: Remove AJA Adobe driver Reinstall ProAppsQTCodecs1.0.2 Deleted DVCProHD component ran a suite of disk utilities, rebooted, etc. toggled audio hardware states: system default, and MOTU Traveler I just ran the Drive Genius 3 Repair Tool > Verify Preferences.  It found 4 corrupt prefs, that I deleted without making note of them.   Ae CC is working again, but I've now been trained not to signal an all clear.  I expect it will stop working again, as soon as I click the Post button here.  If it's still working tomorrow, I'll post back. ... View more

Joachim, I'm getting the same failure on the project you sent me via PM.  It looks like it's loading, until I get the screen that says, "This project could not be loaded, it may be damaged or contain outdated elements." Hopefully, since an Adobe team member has acknowledged this is a repeatable issue, a fix is around the corner. So, I take it you don't have an Autosaved version that preceded the time you applied the Warp Stabilizer? For future reference, I usually do and suggest a Save As every day, or with every significant change, and increment my Project name - sort of like a manual version of Increment and Save that Ae and other apps have.  That way, if I get in this kind of a bind, I have a working previous version. Sorry this didn't work for you. Jim ... View more

If you're on Mac, you can try Digital Rebellion's suite of tools that includes Project Repair, which can strip the Warp Stabilizer data from your project.  Keyframes too, which is another source of crashing/corruption, especially I've noticed on imported FCP7 projects. If you're on Windows, you could get somebody to run the tool for you, as Pr Projects are supposed to be cross-platform compatible. If you want to upload it and send me a link, I'll run it through Project Repair for you and send it back.  But, I don't hover on this list like some people. ... View more

No, but, like you, since I unlinked my clips, my crashing stopped, too. Except for one time when I tried to relink a couple of clips on the Timeline, which resulted in an instant crash.  So, that taught me that I'm going to have to live with unlinked clips until a fix is available. I've discovered a couple other bugs, which I've mentioned elsewhere.  So, I expect a 7.0.2 is forthcoming at some point.  ... View more

Pete, did you try my cut & paste workaround?  I haven't had a crash on this project since I did it, except for once when I tried relinking a double system video and audio clip.  So, I'm going to have to live with unlinked clips on this project until I finish.  But, I will be able to finish it, which I didn't think I could say with confidence a few days ago. Read up on this thread.  Adobe is aware of this, and working on a fix.  It probably won't help any existing projects, as Pr seems to be damaging the project on import. ... View more

You're welcome. And thank you for watching over and being responsive to your customers.  Four days after my original post and we have both an acknowledgement that a problem exists, and a fix is in the pipeline.  This is encouraging and most appreciated. Stay with us, Pete.  I too, have been a volunteer evangelist for Pr, but only since CS6 when Adobe improved their external monitor support.  I've gotten a few diehard FCP7 users at least on the fence and considering a defection.  I got handed off a FCP7 project last week, and it was frustrating going back. Regards, Jim ... View more

That didn't help me, Pete, but maybe you'll have better luck.  Fingers crossed. ... View more

Thanks for the explanation, Charles. I did open this project into 7.0.1, which I started in 7.0, but I haven't tried re-importing the XML, since I've already done a fair amount of work on the project since bringing it into 7.0.  I did try just importing the XML into a clean install of Pr 7.0 (The installer doesn't install the current version.), and no crashes!!!  Weird.  But, all my clips came in unlinked, too. And I updated Pr to 7.0.1, and got the same thing: no crashes, but no linked clips either.  It's possible I did a Select-All and Command-L and linked the clips after I imported the XML the first time, but I'm not sure about that.  Now, I'm really confused. Anyway, thanks for staying with me on this, Charles.  I hope this has been of some help. Here's a link to the XML in question: https://jpc.exavault.com/share/view/1lfq-g5ngeq69-h1db4ilu ... View more

This is also barfing on trying to work with a clip that doesn't exist.  So it is the clip itself that is the issue.  Are you coming in from FCP XML as well? Yes, Charles.  Both of the error messages I posted were from the same project.  When you say "a clip that doesn't exist," what does that mean?  Is Pr trying to link to the camera's audio track, but not finding it?  Clearly, the separate double system audio and video clips exist, because I'm seeing and hearing them, and they're the cause of the crashing. I tried Saving As, and that didn't help.  I moved my media and reopened a project copy, and Pr found the video, but the audio was off-line.  I clicked an off-line audio clip in the timeline, and Pr crashed. I then reopened the project, and relinked the off-line audio.  Clicked a clip, and Pr crashed. So, I still have my fallback off unlinking all my clips, as I described earlier.  But, perhaps now that you've tracked down the issue to a problem in the XML translation from FCP, that Adobe can work on a fix. I'll repeat that I can import the same XML into Pr CS6 and not have the same crashing issue.  So, hopefully that's enough information for the software engineers to fix this. BTW, I tried reporting this bug on the Adobe bug link, but the site gave me an error message after i clicked the Submit button.  I'm cursed. ... View more

I think I may have figured a way to stop the endless crashes in one of this type of problem Sequence.  Set an in and out on the clip or clips that clicking on causes a crash (or all the clips in the Sequence).  Goto the Mark In point on the Timeline.  Lift the clip, and then paste it right back in.  This unlinks all the clips, but I don't get the crashing now when I click on a clip. Trying to relink a video and audio clip causes a crash.  So, it appears that Linking is definitely causing the crashes for me, and perhaps you as well, Pete. ... View more

I'm also noticing, in the Events tab, numerous (40-ish) instances of this: "Couldn't load kPFColorParamSuite." Might be related. ... View more

Pete, I agree this needs to be fixed pronto.  Since one of the selling points Adobe is employing is bragging that that we can bring older Pr projects and projects from MC and FCP into Pr CC, it's going to frustrate a lot of editors if this functionality is a minefield. Fortunately, this sequence that's killing me is an indy film I'm cutting on my own time.  I think if I had clients present, it wouldn't take long for word to get around that Pr CC isn't ready for prime time. Thanks for trying my unlink gambit.  Reinstalling the app didn't fix it either for me. ... View more

On a positive note, PlannedR, if more than one person is having this issue, it suggests that operator error or corrupt media may be implicated slightly less.  I take it, you weren't having this happen on the same project in CS6? I'll add to my list of things that make Pr crash (in this FCP7>PrCC Sequence): Adding an audio effect to a clip Adding a transition (which triggers a similar error message): Premiere Pro has encountered an error. [/siree64/releases/2013.02/shared/adobe/ MediaCore/Backend/Make/Mac/../../Src/Sequence/ Action/SecuenceAddTransitionAction.cpp-57] BTW, I've tried Removing Effects>Volume (previous automation), which I suspected was the offending state.  That worked fine on a few clips.  I was encouraged.  But, then I encountered some clips that even crashed Pr with no effects at all.  You've given me an idea to Unlink my clips, and see if that helps.  I'll let you know. ... View more

If anybody speaks Crash Report, here are the lines up to the end of the Adobe citations. Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0   libsystem_kernel.dylib                  0x00007fff87dfdce2 __pthread_kill + 10 1   libsystem_c.dylib                       0x00007fff93fcb7d2 pthread_kill + 95 2   libsystem_c.dylib                       0x00007fff93fbcb4a __abort + 159 3   libsystem_c.dylib                       0x00007fff93fbcaab abort + 192 4   com.adobe.Frontend.framework            0x000000010006728a FE::ApplicationErrorManager::ThrowError(dvacore::config::ErrorLevel, char const*, unsigned int, int, bool, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&) const + 202 5   com.adobe.dvacore.framework             0x00000001002a1962 dvacore::config::ThrowError(dvacore::config::ErrorLevel, char const*, unsigned int, int, bool, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&) + 226 6   com.adobe.Mezzanine.framework           0x0000000105e30a9d MZ::Utilities::GetAudioClipFrameRate(ASL::InterfaceRef<BE::IAudioClip, BE::IAudioClip>) + 189 7   com.adobe.Mezzanine.framework           0x0000000105a85290 MZ::CreateAudioInfoString(ASL::InterfaceRef<BE::IMasterClip, BE::IMasterClip>) + 304 8   com.adobe.HandlerInfo.framework          0x000000010a8ba5b7 HandlerInfo::AudioContextLineRender::AsString() const + 39 9   com.adobe.HandlerInfo.framework          0x000000010a8b9a28 HandlerInfo::ContextLineRender<HandlerInfo::AudioContextLineRender>::DrawLineItem(UIF::DC&, unsigned int, unsigned int&, int, bool) + 72 10  com.adobe.HandlerInfo.framework          0x000000010a8bb1a9 HandlerInfo::AVClipInfoContext::PaintSelf(UIF::DC&, int) + 105 11  com.adobe.HandlerInfo.framework          0x000000010a8b374c HandlerInfo::InfoView::PaintSelf(UIF::DC&) + 748 12  com.adobe.UIFramework.framework          0x0000000104671499 UIF::TabViewImpl::UI_Draw(dvaui::drawbot::Drawbot*) const + 489 13  com.adobe.dvaui.framework               0x0000000103df42c6 void dvaui::drawbot::InvokeDrawbotFromRegionT<dvaui::ui::OS_View, std::const_mem_fun1_ref_t<void, dvaui::ui::OS_View, dvaui::drawbot::Drawbot*>, NSView*>(dvaui::ui::OS_View const&, std::const_mem_fun1_ref_t<void, dvaui::ui::OS_View, dvaui::drawbot::Drawbot*> const&, dvaui::drawbot::SupplierInterface const&, NSView*, __HIShape const*, dvaui::drawbot::SurfaceInterface*, bool) + 198 14  com.adobe.dvaui.framework               0x0000000103df0a71 void dvaui::drawbot::InvokeDrawbot<dvaui::ui::OS_View, std::const_mem_fun1_ref_t<void, dvaui::ui::OS_View, dvaui::drawbot::Drawbot*>, NSView*>(dvaui::ui::OS_View const&, std::const_mem_fun1_ref_t<void, dvaui::ui::OS_View, dvaui::drawbot::Drawbot*> const&, dvaui::drawbot::SupplierInterface const&, NSView*, __HIShape const*, dvaui::drawbot::SurfaceInterface*, std::vector<dvacore::geom::RectT<int>, std::allocator<dvacore::geom::RectT<int> > >*, bool) + 577 15  com.adobe.dvaui.framework               0x0000000103de07d2 dvaui::ui::OS_View::UI_HandlePlatformDrawEvent(dvaui::drawbot::SurfaceInterface*) + 402 16  com.adobe.dvacore.framework             0x00000001002a1a24 int dvacore::config::ErrorManager::ExecuteFunction<void>(boost::function0<void>*, void*) + 68 17  com.adobe.Frontend.framework            0x000000010006713c FE::ApplicationErrorManager::ExecuteFunctionWithTopLevelExceptionHandler(boost::function0<int>) + 76 18  com.adobe.dvacore.framework             0x00000001002a1abc void dvacore::config::ErrorManager::ExecuteFunctionWithTopLevelExceptionHandler<void>(boost::function0<void>, bool*) + 140 19  com.adobe.dvacore.framework             0x00000001002a362d void dvacore::config::ExecuteTopLevelFunction<void>(boost::function0<void>, bool*) + 125 20  com.adobe.dvaui.framework               0x0000000103deaba6 -[DVAMacContainerView drawRect:] + 118 21  com.apple.AppKit                        0x00007fff8dd903bb -[NSView _drawRect:clip:] + 3995 ... View more

FWIW, I couldn't get Ae CC to import any ProRes or PhotoJPEG movie files.  On the advice of a colleague, I deleted the AJA Adobe driver, and that put me back in business, but without ability to use my AJA with Ae.  I suspect a fix is around the corner. The AJA Adobe driver for CC works fine with Pr, though. YMMV. ... View more

Wee Rock wrote: Encoding to another codec means some data is definitely loss along the way. Unless you are recording directly into a field recorder (which makes your footage uncompressed), there is no point encoding a compressed format into another compress format. Most of the time, your first sentence is true, but the exception being that encoding to an uncompressed or a lossless compression will not mean data loss.  Many field recorders capture to codecs that suffer slight data loss.  This includes ProRes, DNxHD and R3D.  The only way to not lose data is to record to an uncompressed format or one with lossless compression.  Encoding from one compressed format to another is standard operating procedure in production and post production. Most distro formats such as web, Blu-Ray, DVD, etc. are pretty highly compressed.  The challenge in post production is to keep the amount of compression and the number of compression stages to a minimum, if you care about quality in the end product.  But, avoiding recompression is difficult, if not impossible in real-world situtations. ... View more

Very kind of you to share.  I've posted your link for my Windows colleagues on the Media-Motion Ae list. ... View more