CC Crashes.... rendering too unstable

I work in TV News, and I started using Adobe Premiere Pro CC when it first became available. I was intrigued by the new features, as I felt they would be beneficial to the type of editing I do. I have to say I am extremely disappointed with how it's performed. From the start I was having compatibility issues with AVC-Intra 50 P2 video. Even after rendering and playing back at 1/2 resolution I was still having issues with dropped frames. That's assuming that rendering was even possible. Most of the time attempting to render would cause the program to crash. I should also mention that I edit on a top of the line MacBook Pro laptop that far exceeds Adobe's minimum system requirements. I found Adobe's Support system to be horrific. Posting on a forum and hoping someone will respond to your issue is a joke. I also tried to chat with a support specialist and that too was a waste of time. Attempting to get someone on the phone that understood my issue proved futile. I'm going to revert back to CS6, which is a shame because I do need some of the features that CC has. I've come to the conclusion that CC is far too unreliable for what I do. Hopefully someday this won't be the case.

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

K7N2G-ILSR: On-board video too unstable to use

Putting together a new computer for my son. Using K7N2G-ILSR and was really looking forward to the onboard video. Using Athlon XP 2100 (from my prior machine -- 100 percent solid CPU) and initially bought Corsair 2700 256MB with the new board. As an immediate downer, the board refused to work with the memory (nonstop beeping/D-LED stuff, etc.) at power up (tried all slots -- same result). Observation: this compares very unfavorably with my highly-favorable experience with Soyo boards, by the way. Swapped out that memory with Kingston 2700 256MB from my daughter's machine, which is running Soyo Dragon Lite.
Ok, so after some immediate (and unnecessary) memory hassle, got system to boot. CPU is running fine and cool at 50 deg C.
Next (BIG, BIG) problem: Onboard Video is WAY, WAY too unstable in Windows 2000 to be usable. At the outset, the video is showing random horizontal streaks (of trash) across the screen. The only time I've seen that before in my 15 years of PC use is in a Diamond video card a long time ago that was also defective. However, I can live with streaks. The problem is that the machine crashes every time, 100 percent of the time, within 15-90 seconds of booting into Windows 2000 (SP3). (Of course, used latest video driver from a web site, different settings, different refresh rates, and all the other usual stuff, etc., etc., etc.) By the way, I had the patience to try this with and without SP3, and tried a zillon different bios settings. Nothing worked -- same immediate crash problem. Also booted into safe mode and same deal -- but at least that confirms that the problem is probably underlying hardware-related problem, not software/driver problem. (If it can't run under generic Windows VGA driver, then it probably can't run under anything else.)
Only solution is to swap in an existing AGP card. That solves the problem 100 percent but I am not exactly happy camper since I paid for the on-board video (and for budget reasons the card that I am swapping in is not exactly cutting-edge.)
If anyone has a silver bullet fix for this, I would love to hear it. Otherwise, I will assume that the onboard AGP is defective and/or poorly designed, whereupon I would have been better off not spending the extra money for it. My best guess is that the memory and/or other video circuitry is defective.
Otherwise, happy with the underlying performance of the motherboard itself but the video fiasco is a BIG letdown. :O
Thanks.

SILVER BULLET FOUND!!! (and it was free) BIG, BIG, BIG cigar to Bikeman for his above post, which focused my attention on the BIOS. Had considered it at the outset, but figured there was no way I was going to need to flash a brand spanking new board. But when you read the BIOS update notes, one of its fixes is with Kingston memory which is currently in the board. Recall from above, however, that Kingston was a fallback as board complained bitterly about the Corsair memory that I bought with the board. (My daugher's Dragon Lite is quite happy with either memory.)
So here's the rundown. Actually couldn't see what bios ver. I had at POST as text went by way too fast. So install live update software which confirmed that I had older v. 1.2 bios. (Interestingly, the live update itself was old enough that it itself had to self-update before I could use). Flashed BIOS to 1.3 using the Windows version of update, which I will report worked real smooth.
Rebooted and proceeded to install fresh nVidia driver from nVidia website. However, I can tell you that the BIOS was definitely the problem because before I wouldn't have been able to easily get to the point of installing video driver without 5-10 crash/reboot cycles -- so the new-found stability made it very clear that the BIOS update was the "silver bullet" I was looking for.
Postscript impressions: (1) MSI boards are VERY finiky about memory (which is a problem that I have never had with Soyo boards), and (2) this is the 2nd MSI board I have bought and the 2nd one that has had severe bios issues. The first board was a low-end A socket board with AMI bios that arrived faulty/trashed -- half way thru POST, bios would start spitting out garbage ASCII characters.
Again thanks again to Bikeman for saving me from spending any more money (on psu or other memory) and for letting my son's system now run 8X AGP.

How should I debug a PVM that is crashing & rebooting too fast ?

I have a newly created oel4u6 PVM that appears to be starting but then crashing & rebooting too fast and I don't know how to best debug it. The vm is a P2V'ed oel4u6 HP Blade that successfully boots as a HVM but I can't seem to get it to fully start as a PVM (I have several clones that I am working with to contrast/compare).
I can't seem to get the console to start fast enough to show me anything useful as the crash is within seconds.
I likely can flip the VM back to HVMPV mode or HVM and boot to the original kernel but if I boot to another kernel I am not sure what files in the VM (if any) may give any insight on the failed starts/crashed.*
Anyone have any ideas/recommendations on how to debug this?*
The message from xend.log is:
[2013-03-31 07:45:32 3273] WARNING (XendDomainInfo:2131) Domain has crashed: name=0004fb0000060000b0d58463f621a2a3 id=37.
[2013-03-31 07:45:32 3273] ERROR (XendDomainInfo:2265) VM 0004fb0000060000b0d58463f621a2a3 restarting too fast (Elapsed time: 1.654993 seconds). Refusing to restart to avoid loops.
[2013-03-31 07:45:32 3273] ...
More details as to the specific HVM kernel & PVM kernel & the process I used to get the PVM to at least get to load grub are in this thread looking for a good step-by-step guide on the recommended process:
Good guide to convert oel4 hvm to pvm on OVM 3.2.1 ?

Choose Utilities from the Finder's Go menu, open the AppleScript Editor, and run:
do shell script "mv '/System/Library/oldname' '/System/Library/newname'" with administrator privileges
(126015)

Firefox crashes when too many (3) tabs/windows open

Firefox crashes if too many tabs (3) are opened, if 2 browser windows are open, in Yahoo mail (deleting npYState.dll did not fix it) and does not give me a crash report. Internet explorer is not having problems like this.
== This happened ==
Every time Firefox opened
== After downloading 3.6.6

Go to the address '''about:crashes''' and tell us your latest crash IDs. We can then look at the data specific to your crash and have a better idea of what is causing the problem.
Or you can go to '''Start''' and type in the Vista search box '''%APPDATA%''' then click on '''Roaming''' then go to '''Mozilla>Firefox>Crash Reports>Submitted''' then open the .txt files and copy the Crash report ID that starts with '''bp-xxxxx-xxxx'''

Endless crashes rendering with After Effects CC

System:
Windows 7 Pro 64bit (all latest updates)
16gb RAM
i5-2200k processor
GTX780 video card
Latest version of After Effects CC
To preface this, I am a novice to After Effects but fairly experienced with other video editing software such as Sony Vegas.
I have been trying to render a simple downloaded audio visualizer/react template for the last 4 days and every time I get some kind of crash. The template has a few layers and particle effects which react to an audio layer.
First it was blue screens of death, usually with the "MEMORY MANAGEMENT" blue screen error about 10-20% into the render. Of course I ran a Windows memory diagnostic, which found no problems. I'm able to use + render from Vegas and Premiere no problem also, I might add, which would seem to indicate that it is not a hardware problem. The system is stable otherwise. I have AE set to use 12gb of RAM - multiprocessing I've tried both ways, on/off. Eventually I found a user suggestion to reduce voltage to my RAM via my BIOS, which I did, and that seemed to stop the blue screen problems.
Next, I would get errors such as "A crash occurred while invoking plugin..." anywhere from 50% to 80% through the render. The exact plugin varied. All are default AE plugins, no 3rd party stuff. For example, one crash occurred with the basic hue/saturation plugin, another with glow. These do not occur ion load or on normal playback. I have tried using the secret preferences to purge every 30 frames, turned off RAM preview, etc.
It's just insane how finicky and unstable this software is. The machine is practically brand new. Very clean installation, latest graphics card drivers, etc. NO problems with any other software including video software so again I find it unlikely to be a general hardware issue. Currently I am working on reinstalling EVERYTHING on the machine with a clean W7 pro install - nothing but W7, CC, and the graphics drivers.

OK, I've totally wiped my system and reinstalled with very little luck. Here is the full list of specs/info as per the FAQ.
After Effects version: 13.0.2.3, 2014.0.2 release (After Effects CC)
Have I installed recent updates: Yes
What OS: Windows 7 Home Premium 64bit. Version 6.1 (Build 7601: SP 1)
Error messages: Currently my system alternates between "MEMORY MANAGEMENT" BSODs, and a series of errors to the effect of "Crash occurred while invoking effect plugin" followed by a series of native AE plugins in my project, such as radial wipe, glow, hue/saturation, etc
What was I doing when problem occurred: In all cases, simply leaving a freshly-rebooted system to render in peace with no other applications open and caps lock ON
Has this ever worked before: I managed to render the project once, somehow, with no errors. I have not changed any settings, hardware, or software since then.
Computer hardware: CPU is i5-2500k @ 3.3ghz 4 cores, 16gb Corsair XMS2 RAM, GTX780 graphics card with LATEST DRIVERS, 20" LED monitor connected via HDMI, USB wireless LAN adapter, USB mouse, PS/2 keyboard, no other peripherals or hardware. OS + AE installed on a FRESH 250gb Samsung SSD. One other HD in the system (500gb normal HD)
Graphics driver version: GeForce 344.11 release date 9/8/2014, version 344.11
Third party i/o hardware: No
Source footage: You can download the exact template I'm using here. http://impactsoundworks.com/work/AudReactV2.rar
QuickTime installed: Yes version 7.7.5 (1680.95.13)
What other software am I running: While using After Effects, nothing except the Adobe CC application, Geforce control panel, and Samsung Magician for my SSD. No firewall no antivirus.
Third-party effects / codecs: None. This occurs with a 100% completely fresh installation of Windows 7 (with all windows updates) and AE CC, with no additions
OpenGL Features in AE: Not sure how to check.
RAM preview, final output?: The problem happens when rendering. Though if I try to play back the projects in real time, after about 5 seconds it says my RAM is maxed out @ 16gb
Using render multiple frames simultaneously? Happens with this feature on AND off, makes no difference.
Ray-traced 3D render: Not sure
Render settings: Occurs with H.264 AND uncompressed AVI, both set to 1920x1080 resolution, 8bit depth, 48khz audio, 24 fps
Please note for clarity, these problems were occurring on my previous installation of Windows with the same machine. So, I put in a 100% new hard drive, installed Windows 100% fresh, with nothing but Adobe CC and the same problems still happened. I then installed Premiere and Sony Vegas. I have been able to use and render from these with NO PROBLEMS at all.
I'm at my wit's end here...

Premiere exports and rendering too slow

I’m using Premier Pro CC on a 2012 MacPro (aluminum box) with 16gigs or RAM.
I have to say that being a long time Avid Media Composer editor I am very, very pleased with the UI and overall capability of Premiere. It’s loaded with tiny nuances that Avid should have incorporated a long time ago. I am in love with this software.
Or at least I was until I went to export my files. What a slog! I’m sorry but the exports are out to lunch. A six minute 1080p 23.976fps sequence with a few titles, a basic colour effect and two tracks of audio takes…. 3 hours?!?!?? What the heck? If I was rendering an equivalent sequence in the Avid I’d be done rendering any effects and exporting a source QT by the time I finished this sentence. And if I set that QT up to encode in Sorenson I’d have my MP4 done by the end of this email. And the Avid doesn’t need to use any external hardware to ramp things up. In addition, just typing this email while Media Encoder pushes through the output (even with Premiere closed) is causing my whole system to slow down to a point that I find my computer basically unusable for anything else. 16 gigs of RAM and 2x six core processors and it’s acting like it’s 1996 running OS7.
Now wait, I hear you say, you can do so much more in Premiere. Yes, I can. But the moment I drop, for example, an After Effect link in there…I can feel the system trying to race glaciers - and losing. What I don’t get is if I were to use the the equivalent clips in After Effects doing the equivalent type of effects the render would be way faster than Premiere --- and it’s the same company! And don’t get me started on Speedgrade. I’m better off doing an oil painting of each frame than using that Dynamic Link function. And teh dynamic links are what encouraged me to try all this in the first place.
Pre-rendering everything is not only awkward but appears to have no effect on the export time - or playback for that matter. In fact I find the rendering of effects rather confusing and horribly inaccurate - both in its estimate of time to go and the number of frames to process. And what is a 'video preview’ anyway -is that the number of clips? Effects? Effects and clips? Grains of sand on a beach? And why does it’s number keep going up too? It just keeps climbing for no reason I can see. C’mon Premiere…it’s basic math- you count how many frames and then that’s the total number of frames. Why are you recalculating? And did you borrow your time estimate code from Windows 98’s progress bar? One thing it does tell you accurately is how much time you’ve been waiting. That’s handy (not). Oh and I sooooo love the fact that if I quit the rendering process it keeps NOTHING from what it did before. So i have two choices: quit this seemingly endless render to try something else only to find it didn’t help ... or stay put and watch my life drip away into nothingness. Right now, on a second sequence, it says "ETA - 13 seconds left" for, like the LAST 2 hours.
I can’t help but think Premiere is too caught up on render-free editing and it’s glorious Mercury Engine when they should be making it faster & easier to render effects for smoother playback and much faster exports. In my Media Composer I may not have as much robust real time function as I would like but it doesn't choke on the basics (title, colour crrection, dissolves) and the renders are so fast I don't care that I even have to render.
Maybe I’m doing something wrong but I’ll be damned if I know what. And no one else is talking. As I skip around the Google-sphere I’m amazed how many people are posing about speed issues (very common Google search result) and so many other editors are retorting “seems pretty normal to me”. No it ain’t. This is NOT normal. This is painfully slow and in no way reflects the current state of speed for import & exports in NLEs.
I’ve watched every tutorial I could find, picked over every preference, closed every other application, tried different media types, purged every bit of cache and even restarted with no discernible difference. At this stage I’d be thrilled to find out if I’m doing something wrong. But until then I’m afraid this software will not be a regular part of my tool set. This is very disappointing from Premiere given how everything else seems to work so well. Such a shame. This software could kick some serious butt otherwise.
Maybe Premiere will announce that they have a new render engine at NAB?…crossing fingers? Don’t think so.
><({(º>

Thanks for the reply SAFEHARBOR11.
I agree, something isn't right. I've watched tutorials where the renders appear to happen in a "reasonable" amount of time and the numbers of frames and videos prviews never increases. So I don't know what is going on with me.
While I have researched into render/don't render workflow with Premiere I can say I tried both ways only out of desperation.
For my system, a MacPro from 2012, we got only one choice for a video card from Apple - ATI Radeon HD 5870. I tried to get a CUDA enabled card (3rd party) installed but despite tremendous research I could not find something that was authorized to work on my system. At the time I wanted the CUDA to accelerate by Sorenson encoding.
One 2011 post suggested that my issue was related to corrupt media. They had suggested that I try and isolate the timeline down by testing one section at a time with exports until the exports went from fast to excruciatingly slow. As I was working on multiple sequences without common media between them I had reasoned that the software may not have liked my Sony F5 native media (although it plays it just fine). So I took the time to transcode all my footage and use that instead— with absolutely no difference. Even if it did make a difference I’d be disappointed because working natively with my media in Premiere was a huge time saver, unlike the Avid which claims to work with native media but really it leaves the system and editing sow & unresponsive so I usually end up transcoding anyway.
My media encoder settings were the template h264 as a Youtube 720p, 23.976 file. Nothing remarkable there. (Although I did try other settings to see if that affected anything - it didn’t).
><({(º>

SQLDev 4 EA2 is too unstable

We were happily using 4 EA1, despite the obvious bugs it seemed stable enough and not so slow..
We have started using EA2 since it came out, and it seems much more buggy, very slow, and very unstable - crashing several times per day on Mac OSX and Win 7 environments. It is not obvious to reproduce these problems, and seems pretty random when it occurs.
Is there anywhere I could download EA1 from again - we cannot work with EA2, and don't really want to go back to 3.2 either.
FYI - we have been using SQL Dev since it was project raptor back in the end of 2005, but am ready to give up on this tool unless the stability / performance improves. So many nice features, but so frustrating at the same time....arrgghhh!!

cdroderick wrote:
... We don't backup beta software either - obviously. 3.2 is in our repo, but I don't want to go back to that.
And, just as obviously, 3.1 is NOT in your repository. But as a manager what you 'want' is irrevelant; you need to have a backup plan in case the original plan goes awry. Your backup plan is to ask a forum of strangers if anyone can bail you out of your problem.
You have to accept responsibility for the risks that you took:
1) using beta software as a key component of your development process
2) not performing adequate (or perhaps ANY) testing of that beta software before destroying your existing software
3) not having a suitable way to recover if the beta software turns out to be unsuitable
4) decreased productivity of the development team having to deal with issues due to that beta software
As an individual you are free to take any level of risk that you choose. It's great that you want to help beta test a new product. But you aren't talking like an individual. Most of the statements you make use 'we':
We were happily using 4 EA1, despite the obvious bugs it seemed stable enough and not so slow..
We have started using EA2 since it came out, and it seems much more buggy, very slow, and very unstable
we cannot work with EA2, and don't really want to go back to 3.2 either.
we have been using SQL Dev since it was project raptor back in the end of 2005 but am ready to give up on this tool
And then the last one:
We don't backup beta software either obviously. 3.2 is in our repo, but I don't want to go back to that.
You are ready to give up a tool you have been using for 8 YEARS because the latest early adopter beta release has bugs?
That isn't a rational decision that an experienced manager would make.
My comments aren't just for you but for everyone.
Make responsible decisions.
Take responsibility for those decisions.
Always have a backup/recovery plan.
Make backup copies of key software that you use.
Don't use untested or unreliable software as a key component of your infrastructure.

Firefox crashes when too many images are opened

Okay, so, a problem that appeared in 4.0 for me, and hasn't gone away ever since.
The problem is basically summarized in the short description - whenever too many heavy images are in the browser's tabs simultaneously, it slows down to a halt; then sometimes as I scroll it fails to redraw the page, with black non-redrawn area increasing as I scroll and disappearing as I change tabs back and forth.
After a dozen seconds of such sad behaviour, the browser crashes.
Sometimes, however, things go better. And it just crashes.
The problem can be easily replicated with Save Images extension, say, on any photo hosting, or by opening
http://danvolodar.livejournal.com/friends/big_picture
It should be noted that 3.6 never had that problem, and opened pages where I aggregated thousands of images, - slowly, of course, but it ''did'' work. 4 and 5 do ''not''.

Go to the address '''about:crashes''' and tell us your latest crash IDs. We can then look at the data specific to your crash and have a better idea of what is causing the problem.
Or you can go to '''Start''' and type in the Vista search box '''%APPDATA%''' then click on '''Roaming''' then go to '''Mozilla>Firefox>Crash Reports>Submitted''' then open the .txt files and copy the Crash report ID that starts with '''bp-xxxxx-xxxx'''

App Crash is too frequent in iOS 8.0 (iPhone 5 User)

Hey.
I am getting more and more annoyed by iOS 8.0.
Especially using Safari, there are too much App Crash (Sudden Shut-off the screen and go back to Home Screen).
I hope Apple should check this App Crash symptom and resolve it with patch or upgrade to iOS 8.1.

It may just not have been pushed out to your device yet. Just hook your device up to iTunes (which is the easiest way to upgrade anyhow) and then update. Make sure you back-up your device first. Enjoy!

Can't Use Safari Any Longer. Too Unstable......

I've tried everything. I've deleted, reloaded, gotten rid of preferences, deleted all extensions, stopped using Flash and all the other suggested "fixes" all to no avail. Safari continues to to extremely unstable and usually, right in the middle of doing something impolrtant. I've gone to using Firefox, which isn't my favorite either, but at least it doesn't crash during use. These problems seemed to increase/intensify with the latest update. I can't tell you how many times I reported a "bug" but obviously, it's not a priority even noting that there are many out there with the same issues. What's goin' on here? This is not typical Apple! C'mon guys and gals........let's get this fixed before there's an all out revolt and we all lose confidence with what used to be a great browser.

Please read this whole message before doing anything.
This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of this exercise is to determine whether the problem is localized to your user account, or is system-wide. Enable guest logins and log in as Guest. For instructions, launch the System Preferences application, select “Help” from the menu bar, and enter “Set up a guest account” (without the quotes) in the search box.
While logged in as Guest, you won’t have access to any of your personal files or settings. Any application you run will behave as if you were running it for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
As Guest, launch the application(s) and test. Same problem(s)?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.

Crash rendering sequence with titles, Premiere Pro CC

Just establishing fresh thread for CC from the reply I posted in the Premeire CS6 thread.
Summary with updates:
After adding titles from Premeire's bult in titler, on a 1080/24p sequence containing a mix of 4k R3D and 1080 ProRes 422 files, I received the following error when trying to render *some* of the clip previews with those title overlays:
"Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project."
Subsequently, Premeire wouldn't actually shut-down, but switch to a recovery file.
Disabling the title on the 2nd layer would result in the underlying video rendering without issue. Trashing media cache files did not remedy the problem.
Exporting video seems to function, though the render/export times have quadrupled from before adding the simple, text-over-video titles to the project. A 15 minute sequence containing 70% 4k raw/30% 1080 ProRes422 and with roughly 3 minutes of title overlays is about an 8 hour render vs. 2 hours without the titles.
System specs 2.53 GHz i5 Macbook Pro, 8GB RAM, OS 10.7.5

Well, certainly one of my sequences (let's call it "A") always causes a crash. Sequence B was NOT causing a crash last week. Today sequence B started crashing (in 7.0). So I updated to 7.01 and tried again. Still crashing (always, now). So I set out to create a new sequence C.
To create sequence C, I opened a successfully completed project from last week. I Saved As... "New Opening Sequences". Next, I cut away every sequence except for the sequence that holds the intro. I did a Project > Remove Unused to get rid of all the footage, titles, etc. Now I had a project that only contained Sequence C and it's linked media. Nothing is offline. Everything is in tact.
Finally, I open the project I need to finish today. I need to add the bumper to the front of the video. So I navigate within the Media Browser to find the "New Opening Sequences" project. I double click. I get the yellow, dynamic link-like loading bar. When the project media, bins and sequences appear, I double-click the sequence I want to impor.... KKKKKEHEHHE!!! Crash.
I'll restart to get you the exact error message...
WOW!!! I just left this window open to go get the exact error message for you. I went through the same steps above. It worked this time. So to answer your question, Sequence C is also hit or miss. This is the first successful attempt today (about 10 previous tries, restarts, etc).
Definitely seems like a bug. Can anyone else reproduce this crash?
P.S. - Perhaps it's significant, perhaps not: In all cases, A, B and C, these sequences have Dynamic Linked footage from After Effects (animations). While they do have some live-action, they are primarily AE animations. This may help you reproduce the crash.
I'm also not running anything unusual. Mainly the OS, a browser, Webroot SecureAnywhere (Anti-virus), Premiere.

Font rendering too thick

It seems that Firefox is rendering fonts a bit too thick. font-weight is set to the right values, the problem is partially solved when decreasing the weight 100 (from 300 to 200) but is then displayed too thin on the other browsers.
This image shows Safari 6, Chrome 25 and Firefox 19
http://palacz.at/exchange/comparison.png
You also can see clearly that the Font Awesome Icons I used are too thick and don't look good at all. Also the font-weight is set correctly and is displayed correctly in the Inspector of Firefox.

Hi dreerr, at first I got the same results you got, but then I noticed that the font download was being blocked by NoScript, so another font was being substituted. After I allowed the font download, Firefox lined up with IE9 and Chrome (on Windows 7 Pro 64-bit).

AE CS6 Renders too dark

After upgrading to CS6, the Quicktime Animation codec suddenly renders way too dark in After Effects.
Quicktime in Animation codec is my preferred render codec, as it is as good as lossless plus adding alpha is an option.
Is there a cure for this problem?
EDIT: Seems things can go wrong while saving custom presets. Sometimes they just don't work correctly after saving.The third made preset worked, even though everything was the same.

I tried to recreate your problem rendering Quicktimes to Animation + Alpha, ProRes 4444 + Alpha, and just plain H.264 and I didn't experience any darkening in all three renders.
The Quicktime animation codec is pretty ancient and hasn't been updated since Quicktime Pro 7. ProRes 4444 (AKA 4x4) is also as good as Lossless and has Alpha with a Depth option of Trillions of Colors +. I would suggest using that. In the Output Module box where it says Video Output choose Channels: RGB + Alpha, Depth: Trillions of Colors+, Color: Premultiplied (Matted) with Format Options set to ProPres 4x4.

Aperture crashing - Library too large?

It would be greatly appreciated if someone can give me a few suggestions. I've been editing a wedding in Aperture for about 4 hours when suddenly aperture crashed. Every time I reopen, it opens and looks like it is processing previews and then crashes within 5 seconds. I have run a consistency check and rebuilt the library to no avail.
I am afraid my library has gotten too large and could be contributing to the problem. The library currently weighs in at 139GB. I typically try to keep the library size below 50GB but have been too busy to clean up my system recently. Stupid me. Could this be the problem, and if so, how do I manage my files if I can't open aperture?
Thanks,
Ryan

Thanks to everyone for all the help. After speaking with someone at apple, I had to copy my library to an external drive, restore to a new library, check to make sure all the images were there, and then I was able to delete the backup copy. One issue I encountered was that a few thumbnails wouldn't load. After some exploration I found that these were referenced files that had been moved from there original locations and not reconnected with aperture. After relocating the original files, everything works perfectly.
Aside from this being a huge waist of time, everything worked out okay.

HDV preset disappear, always crash, file too big

I have several problem with premiere cs4 on my Mac Os x 10.5.8.
before unistall cs4 I'm trying to resolve the problems because I have a important project not exported yet and that I can't open anymore.
after found some plug in that make premiere crashing everytime and deleted them, now it opens but can't support anymore any file inside my project saying they're too big size! ( until last week it was working perfectly!)
now I just saw thet I don't have anymore the HDV preset , what's going on ?
shall I unistall it and start again?!
How can I open my project again with out lost anything??
many thanks

You can try removing the preferences and see if that helps you. user>documents>Adobe>Premiere Pro. Take the 4.0 folder to your desktop and start Premiere Pro. If that doesn't work, I would probably uninstall and reinstall just to be sure.
To uninstall on Mac go to the utilities folder and look at the ADobe Installers folder. There you should be able to uninstall (yes, you even have to do it on a Mac!)
Hope this helps,
Dennis

CC Crashes.... rendering too unstable

Similar Messages

Maybe you are looking for