Cc 2014: rendering H.264 crashes

AfterFXcc 2014: rendering H.264 crashes at ~1 second. Even with a fresh project and no layers.
3DBOXX W8920Processor
Dual Xeon CPU E5-2670 0 @ 2.60GHz, 2601 Mhz, 8 Core(s), 16 Logical Processor(s)
Windows 7 Professional
Total Physical Memory 32.0 GB
NVIDIA Quadro K5000 / RAM 4.0GB

I know the setting is in there to render h264 out of AE, but it is very inefficient. After Effects renders a frame at a time and adds it to the end of a movie. h264 encoding looks at blocks of video an determines the areas that can be discarded. This helps the final product maintain a smaller file size. Rendering h.264 straight out of AE won't give you the smallest file size or the best results.
My recommendation is to either render out a high resolution movie and then encode it to h.264 using Adobe Media Encoder, Episode, or ffmpeg. If you are just looking to save a step, you might try rendering the the video using the h.264 settings in Adobe Media Encoder.

Similar Messages

Premiere Pro and Media Encoder crash while rendering H.264

Very recently, a problem's popped up where Premiere Pro and Media Encoder (CC) will crash while rendering H.264.
It's only while rendering H.264 - other formats seem to work fine.
And I don't mean that it returns an error, I mean it hard crashes with a Windows "Adobe Premiere Pro CC has stopped working" popup.
It doesn't crash at a consistent time during the render, even on the same project. Occasionally, it won't crash at all, but this is usually not the case.
I've tried disabling CUDA and my overclock to no avail. Please help!

On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
I cant even
If I find a way to fix either of these problems, I will post straight away.

Adobe Premiere Pro CC 2014 keeps lagging and crashing

My Adobe Premiere Pro CC 2014 keeps lagging and crashing to a point where I cannot do my job. When I open my premiere file, I can work on my timeline for maybe two or three minutes before it lags, freezes, and then finally crashes. I'm at a loss of what exactly is causing my problem because I edit primarily H.264 files and my sequences are not complex in any sense of the word. I've been dealing with this for days and I cannot seem to find a solution. If anyone has any advice please let me know because I am desperate. Thank you.
Specs:
Model Name: Mac Pro
Model Identifier: MacPro6,1
Processor Name: Quad-Core Intel Xeon E5
Processor Speed: 3.7 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 10 MB
Memory: 16 GB
Boot ROM Version: MP61.0116.B05
SMC Version (system): 2.20f18
Illumination Version: 1.4a6

Hi Dana,
Can you go to File-Project Settings-General and change the video renderer to Software Only Mode.
Check if that works or not.
Are you using any third party plug-in's for Premiere Pro?
Thank You
Arjun

Premire Pro CC 2014 and Media Encoder Crash During Launch

Premire Pro and Media Encoder crash during startup and are unusable. I am using Windows 7 Ultimate and already tried reinstalling Adobe Creative Cloud from scratch and it's still happening. I also tried following Adobes KB articles directions to rename the Adobe folder in my documents and appdata to no avail. When I try to launch either application, I get a generic windows crash message "Adobe Premire Pro CC 2014.0 has stopped working" and when I click problem details, it lists this:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Pro.exe
Application Version: 8.0.0.169
Application Timestamp: 536f4f89
Fault Module Name: ImageRenderer.dll
Fault Module Version: 8.0.0.169
Fault Module Timestamp: 536f2c18
Exception Code: c000001d
Exception Offset: 00000000001f5382
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 0b2d
Additional Information 2: 0b2df4702c3fc6489bf922fb8e966350
Additional Information 3: fa9f
Additional Information 4: fa9f59f642d335ee71c6667e52000d39

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

I am using 4K Footages for editing in Premiere pro CC 2014, but its getting crash in between at every 15 to 20 mins. Kindly suggest how can it be solved, does any plugins or settings needed to edit 4K footages? Also would like to mention that footages fra

I am using 4K Footages for editing in Premiere pro CC 2014, but its getting crash in between at every 15 to 20 mins. Kindly suggest how can it be solved, does any plugins or settings needed to edit 4K footages? Also would like to mention that footages frame rates are 29.97 and i have set timeline to 25 FPS is requirement by client. kindly revert. Thanks

Thanks Richarad ..It has solved the problem but still crashes some times .As the programme has the break (bumper)after every five minutes ,i hope it will not compress bumper time too after export.

LabVIEW 2014 x64 AppCrash StackHash crash

Our application is crashing somewhat inconsistently in the x64 compile, but not the x32 compile. We are using LabVIEW 2014. When it crashes, LabVIEW stops responding and has to be closed from windows. The View Details feature says it's AppCrash and further says StackHash_someHEXnumber. Another member of the team analyzed dump files and seemed to think it's crashing in the LabVIEW run time.
Any known issues out there that would explain this?
It happens on the original release of LV2014x64 and SP1. It happens in LabVIEW and in a compiled executable. If is not consistent, if we open the software and start running tests, sometimes it will never crash, other times it will crash before 1500 test runs. Our way of testing this has been to run 1500 runs, then close it then reopen it, run again. If it doesn't crash within 3 times of doing 1500 runs, we say that the crash probably isn't going to happen in that version of the software. So we've been selectively disabling parts of the software trying to figure out which code is triggering the crash.

Some more information:
In addition to not happening in LV2014x86, it does not happen in LV 2014 MacOS x64. So this is specific to LV 2014 Windows x64. Furthermore, if we save our code to previous and open it in LV2013x64 there's no crash (there's some hickups with the downgrade so it's not 100% apples-apples though) .
We have narrowed the crash down to a specific changelist in source code control. In that changelist we changed the architecture of how we pass messages around in our program. We used to use User Events to pass messages and the vi listening would subscribe to the user event. However, we found this created a memory leak in LV2012. So we switched to a queued based messaging architecture in this changelist. We created a variant which held the queues as a variant attribute associated with the message enum. This was so that when a message is sent we could do a fast lookup by taking the message and getting a varriant attribute associated with it (thus giving us the queues subscribing to that message). When we introduced this in LV2012 we stressed tested it all and it worked great. Later we upgraded to LV2014 and that's when the crashing started, we have gone back to this specific changelist and tried it with LV2014 it crashes.
We have found other parts of our code which if we disable the crashing goes away. Our suspicion is that this occurs due to a perfect storm of calling vi's asyncronously (which call other vi's ascncronously), passing messages to them via queues, and maybe the variant's containing queues in attributes. Based on what various programmers have seen via a variety of observations, our suspicions are that some combination of those circumstances is triggering some sort of LV2014 windows x64 bug.

AME CC 2014 Rendering with only One Core

This seems to have just begun recently (within the past month) where AME CC 2014 is only using 1 core (out of 12) to render video. No, this is not the CPU Parking issue - I have made the regedit tweaks and also changed my Power option to Performance, all with no difference in AME. Premiere Pro CC 2014 renders the same video just fine using all 12 cores, so it seems this problem lies not with Windows software, nor Premiere Pro, but just AME CC 2014. Was there a recent AME update that might have included this bug?
Adobe, please look into this and resolve it ASAP. Not being able to queue up video renders is killing my productivity.

I just installed Premiere Pro CC 2014 this week and had the same problem, my media encoding time tripled (3 times longer).
The same sequence in Premiere Pro CC (Old Media Encoder ) still encoded at its normal fast speed.
Only one of my eight cores was running during encoding in Premiere Pro CC 2014.
After making the registry changes (below) all eight cores were running and Premiere Pro CC 2014 Encoder was back to normal speed.
Read Below:
I did a search and found this link below.
Go to this link below and read.
https://forums.adobe.com/thread/1506298
After you have read the Adobe Forum link above, go to this link below.
This registry change is for Windows 7, I'm not sure about Windows 8
The registry link may be different but you can still look.
Than call Adobe and have their tech go to this link below.
Than have them suggest what to do.
I did call Adobe back and told them it fixed my problem and they were appreciative and said they would pass it on to all their techs.
http://ultimatecomputers.net/forum/viewtopic.php?f=7&t=3644
Just a note,
I was in touch with Adobe earlier this week with this same problem.
I gave them control of my computer (from India) and after an hour the tech concluded it must be my video card causing the problem.
I am using a Nvidia GTX 560Ti, which is not a certified card. I preformed the card hack.
After getting off the phone with them I did some additional test and found that my old AME rendered my sequences with all eight cores.
The new AME CC 2014 was only using one core.
This registry change above keeps all the cores running.
After I made the change all the cores were running during encoding and the speed was back to normal.
Hope this helps,
The Video Guy

When rendering IDVD just crashes.

Hello All.
I have been trying to put a few iphoto slideshows and trailers on idvd.
I have tried sharing my iphoto slideshows to idvd and while rendering it just crashes.
I have tried several different times. I'm using the newest idvd in ilife 11.
I have also created two different idvd projects and it still fails.
It tells me nothing just crashes.
Thanks
Al

That should be enough for small projects.
What do you mean by 'crashes'? Does it appear to freeze? What?
Rather than burning to writable media, make tour 'burn' to a disk image file (an option under FILE in iDVD). This separates the encoding process from the burning process. Try this and let us know if it works.

Rendering as MOV crashes photohsop (2014.2.1).

Hello,
When i try to render my file as MOV photoshop crashes/hangs and i have to use end task to close it. What causes this and how can i fix it? Thanks!
-ES

Hello Adobe, how can i make your product work?

Red 4k/Premiere CC 2014 Rendering Error

Hello,
So this has been an issue that has been plaguing me ever since I started working with Red Epic Dragon footage. (6k raw)
The native footage is 6k, but my sequence is 4k. So I just scale to fit. I have no issues editing the footage, or even previewing it in premiere. Even with effects applied, I'm able to watch it perfectly at 1/8 resolution, which is fine with me.
The only issue comes when I go to render out anything. I always get one out of a few error messages, and then it crashes. This has happened with every project I have done that involves the Red footage, so I don't think I have a corrupt project or whatnot. One example seen below.
Or, sometimes it just gives me the 'Premiere CC can't continue, sorry' error, and crashes.
I have tried this on two different computers, yielding the same results.
Specs on Computer 1 (Desktop)-
Alienware 17r / Windows 7 / Intel Core i7-3820 CPU @ 3.60Ghz / Nvidia GeForce GTX 660 / 16GB RAM
Specs on Computer 2 (Laptop)- Alienware 15 / Windows 7 / Intel Core i7-2670QM @ 2.20GHz / Nvidia GeForce GTX 680M (4gb) / 15GB Ram
This is frustrating because my laptop has such a powerful graphics card, and the effects I have applied are just basic RGB Curves, nothing that would require MASSIVE amounts of GPU.
Things I have tried so far, to no success.
Update drivers to latest version
Downgrade to older drivers
Upgrade PP CC 2014 to latest version
Try rendering in PP CC (not 2014)
Turn off/on 'Mercury Playback GPU Acceleration'
Clean cache
Bring entire sequence into a new sequence, and re-render
Bring entire sequence in AE Linked Comp, and render
Remove all the effects off the clips
If anyone has any tips or advice, it would be much appreciated. It's so frustrating because I have finished client video's that I need to show, but I can't.

A little more info:
This seems particularly likely to happen when I open a sequence on the timeline that has more than 5 audio tracks.
I'm using OS Mavericks 10.9.5. Video footage is .R3D. I have the crash report if that helps.

Premiere Pro CC (2014) - 8.0.0 crashes at every turn

Hello,
I am a long time Adobe user (both print and video production specialist). I was very excited to dive into the new Creative Cloud update. The only program I started to use since the 8.0.0 update is Premiere Pro. Since the update, I get a wide variety of crashes. The list below are examples of crashes I am encountering.
The entire (7.2.2) CC suite ran flawlessly before the (2014) update. I never had these problems before! I'm afraid to open the other (2014) programs to find out they wont work properly.
1) The open and close crash (Generic message telling you it has to close due to a problem).
2) I made three edit changes, then went to, 'render selection' and got a generic crash report with it closing the program.
3) When opening a project, it is never the way I left it, meaning the sequence I was working on needs to be re-opened and re-rendered from my sequence bin.
4) Crashes when watching a playback after timeline is rendered.
5) During a playback the viewer will freeze on its current frame but the playhead and audio keep moving as if nothing is wrong. Then a minute later it will show the correct frame the playhead is on and then you get the crash notice and it closes.
I have already un-installed and re-installed it.
My system Specs are:
iMac OS X
27-inch, Mid 2010
Processor 2.8 GHz Intel Core i5
Memory 16 GB 1333 MHz DDR3
Graphics ATI Radeon HD 5750 1024 MB
Software OS X 10.9.3 (13D65) Maverick
Dual Monitor display
Any suggestions!?!?! Help!Kevin Monahan

I wanted to let people know that this has helped very much. There are still slight issues here and there but not big enough to halt a project. There probably is something similar for Window users. Big Thank you to John T Smit and Kevin Monahan.
For MAC users do the following (posted by John T Smit above):
-next link says After Effects, but check YOUR permissions !!!
-http://blogs.adobe.com/aftereffects/2014/06/permissions-mac-os-start-adobe-applications.ht ml
-Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
-more Mac 10.9.3 https://forums.adobe.com/thread/1491469
-Enable Mac Root User https://forums.adobe.com/thread/1156604
-more Root User http://forums.adobe.com/thread/879931
-and more root user http://forums.adobe.com/thread/940869?tstart=0
John or Kevin, are there similar instructions for people on the Windows OS?
Thought it would be nice to have for Window users who come across this thread such as Life. Documentedencountered.

Premiere Pro CC 2014 freezes frequently and crashes

Since upgrading from Premiere Pro CC to Premiere Pro CC 2014 my projects crash in regular intervals, which didn't happen before.
All my settings and presets have been pulled across fine, but suddenly relatively slim projects get stuck during editing, rendering or exporting. The progress bar stops, the preview screen freezes and that's it. I can only radically crash the sucker. I did delete all preview files and it improved marginally... only that the time until it froze took a few minutes longer.
I'm on 64bit high-end Windows 7 machine and have never had this problem with previous versions of Premiere Pro.
Very frustrated.

@bendubb37: I'm not the least bit defensive about complaints regarding the stability and general quality of the program. As a quality engineer on the Premiere Pro development team (not a member of the technical support team), I'm quite familiar with many if not most of the problems--both those that are legitimate bugs in our code and those that result from conflicts with OSes, hardware, codecs, other programs, etc. I genuinely appreciate having customers come to this forum to report issues they're having. Such reports sometimes help us identify bugs that we weren't aware of, and they always help us to prioritize bugs to fix based on which issues are biting the most customers and having the greatest impact on their productivity and satisfaction. And naturally I understand the frustration and anger of customers who are wrestling with one problem or another in the program.
What I took issue with was cutco's derision of a perfectly valid troubleshooting step recommended by a technical support agent and his assertions that a) "This community is kind of useless" and b) "Adobe is absent." Cutco graciously acknowledged that he had let his frustration get the best of him.
As to the oft-repeated claim that CC2014 is buggier and less stable than prior versions, I submit that it's a problematic claim to substantiate, at least based on anecdotal personal experience or taking the pulse of this forum & others. There's no question that some customers who enjoyed smooth sailing with an earlier version are experiencing problems with CC2014. But I know for a fact that this release included fixes for a significant number of bugs, including crashers, so many other customers who were having problems with earlier versions are now cruising along without a hitch (or at least without those old, fixed hitches). Alas, those people are not frequenting the forum to sing the praises of CC2014.
My point here is simply that claims about the relative quality of one release versus others can be a distraction from the more important--and much more concrete--fact: a certain number of customers using CC2014 are having Problem X, which didn't happen in CC7.x. The more we can learn about Problem X--and the more clearly we can differentiate X from Y and Z, which may manifest similarly--the sooner we can nail down the cause.
Don't get me wrong: there is an objective trajectory of a product's quality. Unfortunately, even when you have a large pool of data in front of you, the trajectory doesn't lend itself to quantification. You can't simply count the number of deferred bugs, for instance, because not all bugs are equal. You can't even go by the number of known crashers because some are extreme edge cases while others lurk in the path of mainstream workflows. That said, for people like me who spend our working lives trying to deliver the highest quality possible, the trajectory our program's quality is a common topic of discussion.

CC 2014.1 error 5 crash on load, how to fix?

I get this every time I try to load after effects:
Configuration error
Please uninstall and reinstall the product.
If this problem still occurs, please contact Adobe technical support for help, and mention the error code shown at the bottom of this screen.
Error: 5
http://www.adobe.com/support/
What you'll need to know:
The issue is only on my iMac 27-inch, Late 2013 3.4 GHz Intel Core i5 8GB 1600 MHz DDR3 NVIDIA GeForce GTX 775M 2048 MB running OSX Mavericks 10.9.5
I have a full creative cloud monthly subscription
Every other program I use (Photoshop, Premiere, Media Encoder, Bridge, etc) works just fine
I have removed / refreshed AE preferences by both cmd + alt + shift start and also by deleting directories
preferences folder has both read + write permission for my osx account which is admin
I have UNINSTALLED and reinstalled After Effects 5 or 6 times including using the Creative Cloud gear option next to AE as well as manually via the uninstall app in the program folder.
I have tried installing AE CC (pre 2014) and it does not work either
I have tried removing EVERY plugin from library media core and doing so does not fix the problem.
Mediacore DOES initialize every time I try load after effects,
I can get to the point that After Effects loads, I have just a couple of seconds to make a menu selection and open a dialog such as preferences, in which I have time to change any preference. When I hit okay... I get the error above I posted in the beginning of the post. If I have the preferences dialog box open and do not exit it I will not get the error, but of course I can't use AE when in that dialog box. If I let AE load and just wait and not touch anything... I will get the same error after a few seconds.
After Effects CC 2014 DID WORK on this machine before the CC2014.1 update.
How do I believe this happened?
During the AE CC2014.1 update CC app showed AE frozen at 99% of install for over 30 minutes... I had some other issues and had to shut down the computer...
when booting back up I had no need to run AE but since I had to shutdown at a 99% install I figure I better uninstall and reinstall.
CC had a hard time reinstalling AE, it took a couple of times but eventually it did a full install of AE... A few days later I needed to use AE, then I get this error.
I repeat... AE WORKED before this CC2014.1 update.. and even rolling back to CC2014 or CC no longer works either.
I need help resolving this Adobe Team...
AE works on my macbook pro with the exact same programs, setup, and plugins as the iMac.
I need help fixing this please.
P.S.
every time I reinstall AE, for whatever reason.. it takes nearly 30 minutes and gets hung up at 99% for at least 15 minutes before completing the install... just so you know.. this does not seem normal.. it shouldn't take that long to install.. same situation for uninstalling.. takes forever.
Disk Utility shows HDD is fine btw..
I have THOROUGHLY exhausting all the options I could fine online short of wiping Adobe off the iMAC completely which I am NOT wanting to do ... less the other apps that do work stop working or something crazy like that.

So I used to Clean Tool to completely wipe After Effects,
Then I thought.... screw the cloud app! why not do direct download/manual updating...
So I downloaded AE CC 2014 directly:
http://trials3.adobe.com/AdobeProducts/AEFT/13/osx10-64/AfterEffects_13_LS20.dmg
and I double checked for any individual updates:
Adobe - After Effects : For Macintosh
which the only update I saw was 13.2... seems to be no 13.1
Installing AE 13 took less than 5 minutes with the install file!
Installing the 13.2 patch got really slow starting from 40% installed and then these popped up again in the console:
1/15/15 5:49:48.272 AM mdworker[9939]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 8. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
1/15/15 5:50:38.785 AM mdworker[9892]: zip importer encountered an error (2) scanning "/Applications/Adobe/AdobePatchFiles/{AA97C46A-23AF-4B1A-BF1C-681522994961}.zip".
1/15/15 5:50:40.505 AM mdworker[9939]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 8. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
1/15/15 5:53:09.026 AM mdworker[9976]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 8. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
1/15/15 5:53:09.131 AM mdworker[9976]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 8. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
The update reported it successfully installed... I had my doubts..
And SURE ENOUGH! Error 5 crash!
1/15/15 5:54:21.612 AM After Effects[10001]: objc[10001]: Class NSSoundDeleter is implemented in both /Applications/Adobe After Effects CC 2014/Adobe After Effects CC 2014.app/Contents/Frameworks/dvaui.framework/Versions/A/dvaui and /Applications/Adobe After Effects CC 2014/Adobe After Effects CC 2014.app/Contents/Frameworks/AfterFXLib.framework/Versions/A/AfterFXLib. One of the two will be used. Which one is undefined.
1/15/15 5:54:26.274 AM After Effects[10001]: There was an error parsing the Info.plist for the bundle at URL Contents/Info.plist -- file:///Applications/Adobe%20After%20Effects%20CC%202014/Plug-ins/Effects/Keylight/Keylig htPro.plugin/
The data couldn’t be read because it isn’t in the correct format.
<CFBasicHash 0x6000006771c0 [0x7fff702ddf00]>{type = immutable dict, count = 2,
entries =>
0 : <CFString 0x7fff702c0e00 [0x7fff702ddf00]>{contents = "NSDebugDescription"} = <CFString 0x600000677200 [0x7fff702ddf00]>{contents = "Found non-key inside <dict> at line 23"}
1 : <CFString 0x7fff702c33a0 [0x7fff702ddf00]>{contents = "kCFPropertyListOldStyleParsingError"} = Error Domain=NSCocoaErrorDomain Code=3840 "The data couldn’t be read because it isn’t in the correct format." (Malformed data byte group at line 1; invalid hex) UserInfo=0x600000678d80 {NSDebugDescription=Malformed data byte group at line 1; invalid hex}
1/15/15 5:54:30.555 AM After Effects[10001]: -[NSMenu menuID]: unrecognized selector sent to instance 0x60000007e400
1/15/15 5:54:30.634 AM After Effects[10001]: invalid drawable
1/15/15 5:54:30.647 AM After Effects[10001]: invalid drawable
1/15/15 5:54:30.650 AM After Effects[10001]: invalid drawable
1/15/15 5:54:31.210 AM After Effects[10001]: .sdef warning for argument 'FileType' of command 'save' in suite 'Standard Suite': 'saveable file format' is not a valid type name.
1/15/15 5:54:31.452 AM After Effects[10001]: CFUserNotificationDisplayAlert: called from main application thread, will block waiting for a response.
1/15/15 5:54:32.771 AM After Effects[10001]: -[NSMenu menuID]: unrecognized selector sent to instance 0x60800007fdc0
1/15/15 5:54:32.772 AM After Effects[10001]: -[NSMenu menuID]: unrecognized selector sent to instance 0x60800007fdc0
So then I thought... why not just try the AE 13 straight install without the 13.2 update....
I reused the Adobe Creative Cloud Cleaner Tool to remove all traces of AE again.
Here's the console log while installing:
1/15/15 5:57:12.000 AM kernel[0]: hfs: mounted Aftr Efcts CC 2014 on device disk4s2
1/15/15 5:57:12.310 AM mds[43]: (Normal) Volume: volume:0x7f81b10c7e00 ********** Bootstrapped Creating a default store:1 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/Aftr Efcts CC 2014
1/15/15 5:57:12.313 AM coreservicesd[76]: SFLEntryBase::ListHasChanged mach_msg returned 10000004d
1/15/15 5:57:13.515 AM DiskImages UI Agent[10060]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid
1/15/15 5:57:18.205 AM CoreServicesUIAgent[10057]: Error: qtn_file_apply_to_path error: Read-only file system
1/15/15 5:57:26.578 AM PDApp[10074]: CoreText performance note: Client called CTFontCreateWithName() using name "Times Roman" and got font with PostScript name "Times-Roman". For best performance, only use PostScript names when calling this API.
1/15/15 5:57:26.578 AM PDApp[10074]: CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.
1/15/15 5:57:29.613 AM PDApp[10074]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
1/15/15 5:57:43.747 AM launchservicesd[59]: Application App:"Adobe Application Manager" asn:0x0-2da2da pid:10074 refs=7 @ 0x7fb69977b740 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x2db2db pid=10080 "SecurityAgent"")), so denying. : LASSession.cp #1481 SetFrontApplication() q=LSSession 100005/0x186a5 queue
1/15/15 5:57:43.747 AM WindowServer[95]: [cps/setfront] Failed setting the front application to Adobe Application Manager, psn 0x0-0x2da2da, securitySessionID=0x186a5, err=-13066
1/15/15 5:57:43.759 AM authexec[10082]: executing /Users/davidlevy/Applications/Adobe/OOBE/PDApp/DECore/Setup.app/Contents/MacOS/Setup
1/15/15 5:57:55.000 AM kernel[0]: hfs: mounted 101685137D9D81FD on device disk7s2
1/15/15 5:58:06.000 AM kernel[0]: hfs: unmount initiated on 101685137D9D81FD on device disk7s2
1/15/15 5:58:07.000 AM kernel[0]: hfs: mounted 459A876A8DE8CEFD on device disk7s2
1/15/15 5:58:19.000 AM kernel[0]: hfs: unmount initiated on 459A876A8DE8CEFD on device disk7s2
1/15/15 5:59:00.000 AM kernel[0]: hfs: unmount initiated on Aftr Efcts CC 2014 on device disk4s2
1/15/15 5:59:00.506 AM coreservicesd[76]: SFLEntryBase::ListHasChanged mach_msg returned 10000004d
Hopefull... I thought maybe it would finally work....
NOPE!
1/15/15 6:00:09.763 AM After Effects[10190]: objc[10190]: Class NSSoundDeleter is implemented in both /Applications/Adobe After Effects CC 2014/Adobe After Effects CC 2014.app/Contents/Frameworks/dvaui.framework/Versions/A/dvaui and /Applications/Adobe After Effects CC 2014/Adobe After Effects CC 2014.app/Contents/Frameworks/AfterFXLib.framework/Versions/A/AfterFXLib. One of the two will be used. Which one is undefined.
1/15/15 6:00:10.473 AM PDApp[10194]: CoreText performance note: Client called CTFontCreateWithName() using name "Times Roman" and got font with PostScript name "Times-Roman". For best performance, only use PostScript names when calling this API.
1/15/15 6:00:10.474 AM PDApp[10194]: CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.
1/15/15 6:00:15.352 AM After Effects[10198]: objc[10198]: Class NSSoundDeleter is implemented in both /Applications/Adobe After Effects CC 2014/Adobe After Effects CC 2014.app/Contents/Frameworks/dvaui.framework/Versions/A/dvaui and /Applications/Adobe After Effects CC 2014/Adobe After Effects CC 2014.app/Contents/Frameworks/AfterFXLib.framework/Versions/A/AfterFXLib. One of the two will be used. Which one is undefined.
1/15/15 6:00:19.918 AM After Effects[10198]: There was an error parsing the Info.plist for the bundle at URL Contents/Info.plist -- file:///Applications/Adobe%20After%20Effects%20CC%202014/Plug-ins/Effects/Keylight/Keylig htPro.plugin/
The data couldn’t be read because it isn’t in the correct format.
<CFBasicHash 0x618000a6bbc0 [0x7fff702ddf00]>{type = immutable dict, count = 2,
entries =>
0 : <CFString 0x7fff702c0e00 [0x7fff702ddf00]>{contents = "NSDebugDescription"} = <CFString 0x618000a6b6c0 [0x7fff702ddf00]>{contents = "Found non-key inside <dict> at line 23"}
1 : <CFString 0x7fff702c33a0 [0x7fff702ddf00]>{contents = "kCFPropertyListOldStyleParsingError"} = Error Domain=NSCocoaErrorDomain Code=3840 "The data couldn’t be read because it isn’t in the correct format." (Malformed data byte group at line 1; invalid hex) UserInfo=0x618000a608c0 {NSDebugDescription=Malformed data byte group at line 1; invalid hex}
1/15/15 6:00:23.942 AM After Effects[10198]: -[NSMenu menuID]: unrecognized selector sent to instance 0x610000265980
1/15/15 6:00:24.034 AM After Effects[10198]: invalid drawable
1/15/15 6:00:24.051 AM After Effects[10198]: invalid drawable
1/15/15 6:00:24.054 AM After Effects[10198]: invalid drawable
1/15/15 6:00:24.597 AM After Effects[10198]: .sdef warning for argument 'FileType' of command 'save' in suite 'Standard Suite': 'saveable file format' is not a valid type name.
1/15/15 6:00:24.837 AM After Effects[10198]: CFUserNotificationDisplayAlert: called from main application thread, will block waiting for a response.
1/15/15 6:00:26.392 AM After Effects[10198]: -[NSMenu menuID]: unrecognized selector sent to instance 0x600000262b40
1/15/15 6:00:26.393 AM After Effects[10198]: -[NSMenu menuID]: unrecognized selector sent to instance 0x600000262b40
Same crap over...and over... and over again.

Illustrator CC (2014) update now instantly crashes application?

Hello,
I updated my CC (2014) - Illustrator, Bridge and Photoshop Apps via the Creative Cloud App this morning.
Upon restarting the app, any file I try to open has an "not enough memory" error message.
I've tricked it a few times, by creating a new document, then trying again to reopen an existing file... it opens and crashes instantly with the below error message.
Please help?!
Process:         Adobe Illustrator [17275]
Path:            /Applications/Adobe Illustrator CC 2014/Adobe Illustrator.app/Contents/MacOS/Adobe Illustrator
Identifier:      com.adobe.illustrator
Version:         18.1.1 (18.1.1)
Code Type:       X86-64 (Native)
Parent Process: launchd [16592]
Responsible:     Adobe Illustrator [17275]
User ID:         791228434
Date/Time:       2015-01-07 14:04:19.055 +1100
OS Version:      Mac OS X 10.9.5 (13F34)
Report Version: 11
Anonymous UUID: 872479C9-03BB-7AF6-3DDC-76A2AE54D072
Crashed Thread: 33
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

HP,
You could try to reinstall using the full three step way:
Uninstall, run the Cleaner Tool, and reinstall.
http://www.adobe.com/support/contact/cscleanertool.html

Photoshop CC 2014 for Mac Keeps Crashing on Startup!

Running latest version of OS X Mavericks 10.9.3, PS CC 2014, all plugins are updated as of TODAY and all worked FINE after installation.
Program seems very hit or miss with successive bouts of starting fine then crashing, etc.
Here is the crash log:
Process:         Adobe Photoshop CC 2014 [4712]
Path:            /Applications/Adobe Photoshop CC 2014/Adobe Photoshop CC 2014.app/Contents/MacOS/Adobe Photoshop CC 2014
Identifier:      com.adobe.Photoshop
Version:         15.0.0 (15.0.0.58)
Code Type:       X86-64 (Native)
Parent Process: launchd [146]
Responsible:     Adobe Photoshop CC 2014 [4712]
User ID:         501
Date/Time:       2014-07-10 22:54:17.765 -0600
OS Version:      Mac OS X 10.9.4 (13E28)
Report Version: 11
Anonymous UUID: 8FF68BF1-84C3-0D4C-C725-CD1B1308CA7E
Sleep/Wake UUID: 38D7BDB6-790C-4316-B832-6DF2503543EE
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000010
VM Regions Near 0x10:
-->
    __TEXT                 000000010bb7a000-0000000110655000 [ 74.9M] r-x/rwx SM=COW /Applications/Adobe Photoshop CC 2014/Adobe Photoshop CC 2014.app/Contents/MacOS/Adobe Photoshop CC 2014
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_pthread.dylib       0x00007fff93ccc9a4 _pthread_mutex_check_init + 14
1   libsystem_pthread.dylib       0x00007fff93ccc621 _pthread_mutex_lock + 28
2   com.apple.CoreFoundation       0x00007fff9363edbf CFRunLoopRemoveObserver + 79
3   com.adobe.PSAutomate           0x00000001bdb1d185 0x1bdb1c000 + 4485
4   com.apple.CoreFoundation       0x00007fff9363ed67 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
5   com.apple.CoreFoundation       0x00007fff9363ecd7 __CFRunLoopDoObservers + 391
6   com.apple.CoreFoundation       0x00007fff936303b8 __CFRunLoopRun + 776
7   com.apple.CoreFoundation       0x00007fff9362fe75 CFRunLoopRunSpecific + 309
8   com.apple.HIToolbox           0x00007fff895c1a0d RunCurrentEventLoopInMode + 226
9   com.apple.HIToolbox           0x00007fff895c1685 ReceiveNextEventCommon + 173
10 com.apple.HIToolbox           0x00007fff895c15bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
11 com.apple.AppKit               0x00007fff8e66824e _DPSNextEvent + 1434
12 com.apple.AppKit               0x00007fff8e66789b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
13 com.adobe.Photoshop           0x000000010bc1a2d0 0x10bb7a000 + 656080
14 com.adobe.Photoshop           0x000000010c651b38 0x10bb7a000 + 11369272
15 com.adobe.Photoshop           0x000000010c6535b7 0x10bb7a000 + 11376055
16 com.adobe.Photoshop           0x000000010c4e13c8 0x10bb7a000 + 9860040
17 com.adobe.Photoshop           0x000000010be84c7b 0x10bb7a000 + 3189883
18 com.adobe.Photoshop           0x000000010be85299 0x10bb7a000 + 3191449
19 com.adobe.Photoshop           0x000000010bb7c434 0x10bb7a000 + 9268
Can someone identify what this could be?
Thanks
Mike

It's the same with my EA everything updated I even have a fresh OS system with CC 2014 freshly installed. SVG crashing it as far as I have been using CC 2014 version.
Can you point me to some best practice for bringing in SVG or exporting from illustrator.

Cc 2014: rendering H.264 crashes

Similar Messages

Maybe you are looking for