Videographer membership with Photoshop, Premiere, After Effects and Media Encoder

Hi,
I love Adobe's applications as much as a carpenter loves his toolbox, but I cannot justify the monthly cost of a toolbox full of stuff while I only use half of it.
My question is simple: could you please consider making more gradually selected membership plans, or please give us the opportunity to select a custom package with a more justifiable price?
Thanks,
Davey.

This is where you tell Adobe what you want Adobe - Feature Request/Bug Report Form

Similar Messages

Premiere, After Effects, Speedgrade, Media Encoder and... the dynamic link

My feeback after working with the dynamic link these days. Basic project. Editing, color correction, animated titles.
I'm using a 3.5Ghz iMac 24GB Ram and a GTX 780 4GB. (2014 versions & last updates).
Rendering the timeline in Premiere is sometimes extremly slow (with AE comps). Need to quit and reload the project to get a good speed.
Too long delay of refresh for the AE compositions inside Premiere (with the dynamic link). Need to go in AE then back to Premiere to get the refresh.
When i export to media encoder i need sometimes to save then send it 2 or 3 times to get the last edits in the export.
Even worse with the AE compositions. If i change something in AE then export from Premiere i need to quit and reload Media Encoder to get the last changes.
Really fast export from Premiere to Speedgrade and from Speedgrade to Premiere.
But !!! Lumetri fx is not compatible with AE. And Speedgrade doesn't support BlackMagic but only this nVidia Sdi thing.
And why we could not export h264 from AE anymore ???
Quiet disappointing :-(

Using Premiere Pro CC 2014.0.1 (build 21) and Media Encoder 2014.0.1 (build 8.0.1.48) on OS X 10.8.5
If I Export a video from Premiere, I can continue using Premiere, but if I Queue an export, returning to Premiere produces the beach ball of death. If I give it time, the beach ball goes away and the arrow returns, but trying to click anywhere in Premiere simply returns the beach ball. There is nothing to be done but Force Quit Premiere. I can leave Premiere and run any other application, but if I leave to execute the Media Encoder queue, I cannot return to Premiere and use Premiere. I can visit Media Encoder (call it to the foreground) and return to Premiere after the queue is done.
My current workaround is to use Export from Premiere and not use Queue from Premiere.

What is your Premiere, After Effects and SpeedGrade Workflow?

Hi Everyone,
I am an experienced editor who's switched to Adobe's CC barely a year ago. At the moment I'm in the midst of finishing up a corporate project and trying to think of the best workflow between Premiere, After Effects and SpeedGrade. I'm loving the Dynamic Link workflows, but at the some time I'm facing some obstacles, and am wondering how you guys do your work.
Let's say I finished the edit of the project and send the project via Dynamic Link to SG. I finish the grade and then decide to use the Dynamic Link to AE to add some titles with shapes and effects such as Fast Blur. This is where I'm facing the first problem. When I choose a clip to be 'Replaced with an AE Composition', the color correction is gone, and now if I grade in SG, it will naturally grade the titles I added. So, it seems as though my color grade is a waste of time and I have to do it the old school way of first absolutley completing the color grade, exporting, re-importing and then heading for titles and effects. That makes you lose quite a bit of "dynamics" in your work (and time aka money), if my clients want changes for example.
For simple animations with text, and shapes, this is not a big issue since you could easily add the titles to a second Video track. But when you use After Effects which changes the acutal image of a clip by adding effects, things don't work out too easily. But in any case, these might just be the limitations to the relativley new Dynamic Link workflow.
In my specific example, how would you go about it? What is your workflow? Maybe I'm missing out on some tips & tricks.
Be happy to hear from you guys and maybe get some expert knowledge.
Best,
fabian

Hey there,
I'm also looking for a solid workflow solution since adopting (and actually really liking) Speedgrade. So below is what I'm going to try which should work and will follow this thread to see if any other workflows pop up. Also typing this out here to help me with plan of attack
Project Specs - 3 minute corporate video with text animation, interviews, broll, and computer screen replacement
Edit in Premiere
Dynamic link to SpeedGrade for color correction
Open back up in Premiere, confirm all color corrections are applied, and then duplicate sequence to an AE Prep extension
In AE prep sequence, take all AE "base" shots (for computer screen composite or anything needing stabilization) up onto their own track (i.e. V5 & V6)
Add 10 frame handles to in & out, checkerboard clips as needed
Delete all other remaining content but keep blank spaces / no ripple deletes
Export this out to a ProRes4444 QT movie
Import ProRes4444 QT movie back into premiere, add over existing video layers in AE Prep extension sequence, and then there time out the screen shot replacement content to cover effect duration
Dynamic link AE Prep Premiere Pro sequence to AE
Do the AE work
Dynamic link back to Premiere
DoneHopefully
This was my similar work around back in the day before I had Automatic Duck in FCP to AE
Hope this helps anyone else - if there are any glaring "why would you do all that" points - please let me know I'll also report back if there are any horrible roadblocks throughout the process.
_Christina

Premiere Pro CS6 and Media Encoder CS6 Color shift on export

Hello,
I am working on an early 2008 Mac Pro with 2 X 3.2 GHz Quad Core Intel Xeon Processors 32 GB of RAM a NVIDIA GeForce 8800 GT 512 MB Graphics Card and I am running OS X 10.8.2.
I have the updated Version of Adobe Premiere Pro CS6 and Media Encoder CS6 through the awesome Subscription program that Adobe has started.
My footage is shot with the Canon 1D Mark IV shot 1920X1080 at 24 FPS
I am importing the camera files and then exporting them after I cut them up in to Quicktime Pro Res 422 HQ files
With the technical explination out of the way here is my problem. I have color right from the camera files that I like. and with out doing any thing to change the color I export the footage and get a dramatic color shift. The exported file looks desaturated and slightly green.
I have tried using Media Encoder CS6 to export my footage and that has the same result.
I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
I have attached three screen shots that show the color shift exactly. Now what I need is a solution. What I am not seeing is color settings for Premiere. I am totally open to any suggestions on what I might be doing incorrectly.
Ben

Benjamin Peterson wrote:
I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
I've been doing this for a few years now, and have come to some conclusions. Basically, the difference between still photography and video is like the difference between playing the trumpet and the sax. What you bring to the sax from playing trumpet is your ability to read music, what you know about composition, blending while playint with others, ect. But playing trumpet tells you nothing about how to physically play a sax. So it is with still photography and video.
For starters, your carefully calibrated computer monitor is just that, a computer monitor. It doesn't display the correct working space for video. What you need for WYSIWYG in video is a monitor that can show you the Rec.709 working space. Rec.709 has a different gamut, a different gamma, probably a different white point (D65), different phosphor colors, etc., etc., etc. Enought differences that it's difficult to make a computer monitor that can successfully display Rec.709. Yet there are a couple of computer monitors that can do this (a few Eizos, one HP). The vast majority of people doing serious color correction work in video use a production monitor for just this reason.
But a production monitor isn't enough. You also have to make sure that the signals you're sending the production monitor are correct. There's a sub-industry making signal converters for signals from NLE video cards (usually RGB based) -> signals for production monitors (usually YUV based).
That said, it is certainly possible to get a very good match between your NLE suite and a DVD / BD as displayed on an HDTV. But it's not as simple or easy as a calibrtated computer monitor for still photography use.
This is probably part of your problem. But Quicktime is probably the root of it. Quicktime is, well, I guess the polite way of saying it is that Quicktime is problematic. It gives all kinds of problems. Most people have abandoned it. You should too.

Both After Effects & Adobe Media Encode CC giving are not letting me export.

Dear All,
Both After Effects & Adobe Media Encode CC giving are not letting me export movies.
Some times they will, but after one file both programs give me the following error messages.
After effects:
“[file path and name].mov. An output module failed. The file may be damaged or corrupted. (-1610153464)"
AME:
"Can't read from source."
I've went through the forum and found threads & pages discussing the problem.
E.g.
http://blogs.adobe.com/aftereffects/2013/08/solutions-for-problems-with-quicktime-files-in -after-effects-cc-12-0-because-of-conflict-with-dvcprohdvideoout-quicktime-component.html
http://forums.adobe.com/thread/1252092
After following all the tips and suggestions (from deinstalling quicktime components & audio components to completely reinstalling CC) I'm still experiencing the problems.
Which leaves me in a bit of a squeeze. I need to export over 144 movies in the coming 2 days and the only way to do this is to quit and open media encoder (or AE) after each single export.
Not really an option.
Both problems have the process Adobe QT sever in common, I took this from the console:
9/26/13 1:02:44.517 PM com.apple.launchd.peruser.501[171]: ([0x0-0x42042].com.adobe.Adobe QT32 Server.application[331]) Job appears to have crashed: Segmentation fault: 11
9/26/13 1:02:44.672 PM ReportCrash[354]: Saved crash report for Adobe QT32 Server[331] version 7.0.1 (7.0.1.0) to /Users/martijn/Library/Logs/DiagnosticReports/Adobe QT32 Server_2013-09-26-130244_martijns-MacBook-Pro-2.crash
System information:
Retina MacBook Pro (Mid 2012) (16gb ram)
Mac OS X 10.8.5 (12F37)
Running Adobe CC (for teams), all apps are up-to-date.
I don't no why Adobe puts out such a buggy piece of software (I know it has to with Apple's poor 32bit quicktime implimentation, but hey, this was known information no?).
Upgrading to CC has given our office nothing but problems.
Hope someone can help to find a work around until Adobe realeases a proper update and solves this problem once and for all.
All help is much appreciated.
Kind regards,
Martijn

Hello Tim,
Thanks for the really quick response!
Regarding the crash log: it doesn't reference com.apple.audio.CoreAudio (though it did before, so I followed all the steps in your blog post before I posted to this forum).
I've uploaded the crashlog to:
http://martijnlambada.com/TMP/AdobeQT32servercrash.zip
If you want to inspect it. It mentions the DXV codec (which I also uninstalled), but the crash keeps occuring. Also I need to export to DXV since it's the only codec the d3 media
server accepts (http://d3technologies.com).
I followed all the steps in the troubleshooting steps.
Codecs used: I've tried everything from animation to Apple ProRes (including: h264/motion jpeg/uncompressed). With all codecs the Adobe QT32 server keeps crashing (though I can't always reproduce).
Export destination: Internal SSD (same as where the OS is installed on) + External raid (via firewire & thunderbolt) + external HD via usb 3.0 (tried everything).
When does the problem start: Really hard to specify, sometimes a day without crashes, sometimes every export for days on end. Sometime after restarting (tried logging out, restarting, switching off and on the computer). With other programs running and with out. Now checking every process active when exporting, and comparing log files.
Can you export to other formats: See question 1, sometimes I can, sometimes not.
When you launch AE and/or AME, is QT32 Server running? At what point does it stop running? Still runing when I open the program. It crashes when exporting (ofter after finishing the first export).
What component files are in your Library/QuickTime folder?: Currently the folowing:
AppleAVCIntraCodec
AppleHDVCodec.component
AppleIntermediateCodec.component
AppleMPEG2Codec.component
AppleProResCodec.component
DesktopVideoOut.component
DVCPROHDCodec.component
DVCPROHDMuxer.component
DVCPROHDVideoDigitizer.component
DVCPROHDVideoOutput.component
DVCPROHDVideoOutputClock.component
FCP Uncompressed 422.component
iChatTheaterPreview.component
IMXCodec.component
LiveType.component
Hope this helps.
Cheers,
Martijn

Dual-core or Quad-core for Premiere, After Effects, and Photoshop CS4?

We are planning to purchase around 25 computers for a computer lab for working with CS4 Production Premium at the high school level. Mainly Premiere Pro, After Effects, and Photoshop. Our budget is, unfortunately, a mere $550-$625 per machine (just the tower though, we have monitors). I've already established that a 64-bit operating system makes a significant difference in the performance, even though Photoshop is the only 64-bit application, and I'm now hung up on whether or not it's worth the cost of a quad-core processor over a dual-core.
I'm discovering the different hardware needs for each application, so I'm trying to find an economic balance that will give me the best performance per buck. It seems that Premiere benefits significantly from more cores (we're editing 1440x1080 AVCHD), and this article over at Tom's Hardware has convinced me that I don't want to compromise with a hyperthreaded dual-core for After Effects.
I'm also struggling with what part the graphics card plays in the mix. Which applications lean on the graphics card, and will it make much difference as long as I meet the requirements (OpenGL 2.0, Shader Model 3.0, Direct3D 10, and 256 Mb Ram)?
I understand I will need to settle for less-than-awesome with my budget, but I'm already making sacrifices to get the number to $625. I would like to make sure that those sacrifices will be worth it for a quad-core system.

I think I may have answered my own question by looking at these charts over at Tom's Hardware:
http://www.tomshardware.com/charts/2009-desktop-cpu-charts-update-1/Adobe-Premiere-Pro-CS4 ,1404.html
http://www.tomshardware.com/charts/2009-desktop-cpu-charts-update-1/Adobe-Photoshop-CS-4,1 387.html
http://www.tomshardware.com/charts/desktop-cpu-charts-2010/Video-Editing-Adobe-After-Effec ts-CS5,2427.html
I think that the jump to the quad core in Premiere Pro is worth it, even if I don't see as large of an improvement in Photoshop or After Effects. I am still interested in the role of the graphics card in the mix if anyone can shed some light on that. Will an integrated graphics card (like an Intel GMA x4500 or Radeon HD4200) suffice or will I need an actual graphics card to realize the benefits?
Thanks

Laptop for editing with Adobe Premiere & After Effects CS6

Hi, I'm just started a company working with young people, and I need a laptop for editing some videos (short films/music videos).
I was looking at a cheap laptop to be able to run Adobe Premiere and After Effects smoothly. I was told that this laptop would run smoothly:
http://www.pcworld.co.uk/gbuk/hp-envy-m6-1178sa-15-6-laptop-17419990-pdt.html
Can anyone confirm this? The graphics card is not listed on the Adobe's website but I was told it's compatible?
Im new to this stuff so please help, thank you.

How realistic are the system requirements Adobe posts on their site?
System requirements
Windows
Intel® Pentium® 4 or AMD Athlon® 64 processor with 64-bit support; Intel Core®2 Duo or AMD Phenom® II processor required for Adobe® Premiere® Pro, After Effects®, and Encore®; Intel Core i7 processor required for Adobe SpeedGrade™
Microsoft® Windows® 7 with Service Pack 1 (64 bit) and Windows® 8. Refer to the CS6 FAQ for more information about Windows 8 support.*
2GB of RAM (4GB recommended) for 32 bit; 4GB of RAM (8GB recommended) for 64 bit
14.5GB of available hard-disk space for installation; additional free space required during installation (cannot install on removable flash storage devices)
Additional disk space required for disk cache, preview files, and other working files (10GB recommended)
1280x900 display with 16-bit color and 512MB of VRAM; 1680x1050 display required, and second professionally calibrated viewing display recommended for SpeedGrade
OpenGL 2.0–capable system
Sound card compatible with ASIO protocol or Microsoft WDM/MME
DVD-ROM drive compatible with dual-layer DVDs (DVD+-R burner for burning DVDs; Blu-ray burner for creating Blu-ray Disc media)
Java™ Runtime Environment 1.6 (included)
Eclipse™ 3.7 (for plug-in installation of Adobe Flash® Builder®); the following distributions are supported: Eclipse IDE for Java EE and Java Developers, Eclipse Classic, Eclipse for PHP Developers
QuickTime 7.6.6 software required for QuickTime features, multimedia, and HTML5 media playback
Dedicated GPU card required for SpeedGrade (for optimal performance in SpeedGrade and for GPU-accelerated features in Adobe Premiere Pro and After Effects: NVIDIA Quadro 4000, 5000, or 6000 or other Adobe-certified GPU card with at least 1GB of VRAM recommended); visit www.adobe.com/products/premiere/extend.html for supported cards
Optional: Tangent CP200 family or Tangent Wave control surface for SpeedGrade
Optional: For SDI output, NVIDIA Quadro SDI Output card required for SpeedGrade
Optional: 7200 RPM hard drive (multiple fast disk drives, preferably RAID 0 configured, recommended) for video products
This software will not operate without activation. Broadband Internet connection and registration are required for software activation, validation of subscriptions, and access to online services.† Phone activation is not available.
You have to be from another world to believe these requirements. Note the last optional statement. Up to and including CS4 this stated:
Dedicated 7200 RPM hard drive (multiple fast disk drives, preferably RAID 0 configured) for video products.
Nobody in his right mind believes that system requirements get lower over time. It is purely a marketing lie to artificially lure prospective buyers.
The requirement to have two physical disks for CS6 is bogus.
If anything is bogus, it is the system requirements from Adobe and only fools would try to use a system with these minimum requirements, like this:
Pentium 4 with 4 GB of RAM, 24.5 GB of hard disk space is enough according to them.
Harm is confusing editing with getting high PPBM scores, I am afraid - again. Not all projects have 10 layers of H.264 stacked with heavy effects for two hours straight. The vast majority of editing is simple transitions and effects with 10 minutes of YouTube encoding twice a week.
Wrong assumption. I was thinking of a simple DV timeline with one single track. And however much you dislike the PPBM benchmark, it is the only available tool to show how well a system is setup and in balance. Question: Is your dislike of the benchmark based on the fact that your favorite HP Z820 does not do well?

CS5 Premiere, After Effects, and Encore hang on splash screen - Solution

I just installed Production Premium CS5 on a Windows 7 64 bit system. The install went without a hitch, but when I attempted to start Premiere, After Effects or Encore, they would all hang at some place with the splash screen showing. I spent 2 hours on the phone with Adobe and they never solved the problem. They had me uninstall iTunes and Quicktime, upgrade my nVidea driver and upgrade to a newer version of Quicktime. None of this made a difference and at that point I realized they were not going to fix my problem. The first woman was an idiot and the guy I spoke to next was a lot better, but no solution. Premiere was hanging when loading the Quicktime plug-ins.
Then I had an Aha! moment. I shut off User Account Control, rebooted and then everything worked. I could also get the programs to work with UAC on if I changed the shortcut to "Run as Administrator" but then there would be a UAC prompt. By the way, I was running as a user with full administrator privileges.
I am astounded that Adobe has never encountered this problem before and did not have an immediate solution. Once again, Adobe Tech Support has continued to provide pathetic tech support.
Steve

The plug-ins that were involved in the hang on the splash screen were:
ExporterQuickTimeHost.prm
ImporterQuickTime.prm
The splash screen would hang for 5 minutes on each of these and then if PPro started it would only be a plain white window with the Menu Bar and then there would be no further response.

Help with Premiere, After Effects and Davinci workflow

Hi
I'm scratching my head wondering how I'm going to solve this workflow issue that I have, but hopefully it isn't that much of an issue.
We have shot a short film with an A-cam that delivers CinemaDNG files. I converted these files into Apple ProRes 422 Proxy with Davinci Resolve 9 Lite
and then I imported the proxy files into Adobe Premiere CC. The idea is to then to > edit the film in Premiere > import it to After Effects CC via Dynamic Link (to make the effects we're after) > send it back to Premiere > export as XML to Davinci > relink to the original CinemaDNG-files and perform the color grading, and then finally export the film (either back to premiere to export it with audio or export it directly from Davinci in some way?)
I'm new to all this and I would really appreciate help!
Thanks in advance
Regards
Patrik

Hi guys and thanks for your replies!
Well I thought I had a good post prod plan, but now I realized it maybe wasn't that good when AE gets involved.
My initial idea was to follow this workflow tutorial > http://www.youtube.com/watch?v=Kpg0k3aD088#t=327 (He have now made this tutorial private and I'm having a hard time remembering my YouTube password so at the moment I can't watch it... great)
CC may not specifically support A-CAM's CinemaDNG files, but it will do for a rough cut, even though it looks purple and horrible
What do you think about this? I import the cinemadng folders into premiere and make a rough cut out of it, then I'll export the sequence as a XML file and bring it into Davinci where I relink to the cinemadng files and perform the color grading and then export it as 422 HQ (for example?) and then bring it back to Premiere to make my final edit and also use Dynamic Link with After Effects? Any possible failures with that technique?
Regards
Patrik
Ps: Reason why I'd like to perform color grading in Davinci and not Speed Grade is because of the purple tint I get in SG and PP!

Error when exporting from After Effects into Media Encoder

Hi there. I am using After Effects CC and am trying to export>add to Adobe Media Encoder CC. Upon doing so, instead of the file being placed into Media Encoder CC, I get an error message
I just updated to most recent update of After Effects via the Cloud today but no difference. Instead, After Effects just creates a folder on my system to house a duplicate composition file with "tmpAEtoAMEProject" at the beginning of file name. I can use the render queue out of After Effects just fine.
Can someone give me a solution to how I can export out to Media Encoder CC? Probably something simple I am just missing. I don't know much/can't find much about how to know if Adobe Dynamic Link components are installed. Oh, and I have also tried to just drag the files into Adobe Media Encoder too but I still get this warning. If it helps, I am on an imac OSX 10.8.5. Thanks!

Hey there. Yes, I have uninstalled AE, restarted, and reinstalled. Still get the same error shown in screenshot in my original question posted.

After Effects & Adobe Media Encoder Rendering Issue

Hi,
First of all, just to give a background, I am running Windows 8 and Adobe After Effects CC. We had purchased the computer 2 weeks ago and I was working on a video and everything was fine in After Effects. I then went to render it using Adobe Media Encoder to get the H.264 file type that AE CC doesn't have anymore. AME rendered the first time but I had to make more changes. I went to render it a second time and AME crashed and my computer blue screened. Now when I go to Add compsition to media encoder the program shows the splash screen but then it crashes every time. So after some research I found that there were output settings that you can check to allow AE to render H.264. I rendered my video the first time and it worked fine. I had some mismatched audio so I had to make some changes to it again. I went to render it a second time this morning and I got an error message that said " After Effects Error: Rendering error while writing file...unable to delete existing file." This also crashed and blue screened my computer, now it won't let me render at all in either program. Are there any fixes to this problem?
Thank You!
Frank

Did you re-boot? Did you try re-booting in safe mode? Did you add anything to your computer or run any updates between the first render and the time this problem started?
Did you try creating a new comp, adding a single solid, and then rendering? If that works tell us about your source files including type and compression.
If that fails then make sure that you have run all the updates. Then, make sure you have not installed any 3rd party codec packs. Then, dig up the error log and look for anything you can find that starts with "unable" or "crash" and that may give you a hint.

After Effects + Adobe Media Encoder + Flash = Most Random File Sizes Ever

Asking this question in this AE forum because I think more would have knowledge on the topic here than the Flash Forum.
I've heard that video compression is more of an art than a science... Could someone provide me some insight on the following?
-Created a 12 second, 30 FPS, 300x250 banner animation inside of After Effects
-Exported for FLV/Flash to be placed inside of a 300x250 .FLA
-Comps rendered directly from Adobe Media Encoder standalone instead of Render Queue in AE (for 2 pass .FLV's, and heard from various that .FLV's from render queue are not the prettiest at times).
I've always been under the impression that I would get smaller file sizes with SWF's externally linking to an FLV. If I do it this way, I end up with:
41 KB .SWF + 668 KB .FLV = 709 KB
However, if I EMBED the same 668 KB .FLV to the FLA's timeline (not using the flvPlayback component) I end up with a 381 KB file size!
I am just confused on the logic here, could someone explain the reasons for this? I always thought my file size would be bigger if it was embedded to the timeline.

Actually I think it's the tons of extra AS code that make linked players fatter. Never could make sense of the why and how myself, but you can find enough alternate free players/ skins (nonverblaster for instance, which I use) that are a lot leaner.
Mylenium

Adobe QT32 Server.exe Premiere CS6 Pro and Media Encoder

Hi,
Been having intermittent issues with this. I'll be trying to render, or even just scrubbing through a clip in the timeline and Adobe Media Core CS6 has stopped working pops up:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Adobe QT32 Server.exe
Application Version: 6.0.5.0
Application Timestamp: 5211c5c2
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521ea8e7
Exception Code: c0000029
Exception Offset: 00090892
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Information 1: e8ad
Additional Information 2: e8adce1c2b9e7be834b4063ac3c53863
Additional Information 3: e8ad
Additional Information 4: e8adce1c2b9e7be834b4063ac3c53863
Doesn't always do it, but now I've found an instance where it's reliably repeatable. As I scrub through a certain part of the footage, it crashes. Or it crashes at the same point during rendering.
I've succesfully edited and rendered clips made from the same cameras, recorder (Tricaster 410) - even from the same actual media file. I've tried updating QuickTime, uninstalling, reinstalling QuickTime, doing windows updates, updating GPU drivers from Nvidia, clearing media cache DB, launching Premiere while holding shift. Nothing makes a difference.
System is an 2 CPU Intel Xeon E5-2687W 3.1 GHz, 64GB RAM running Win7 Pro 64.
Anyone have any suggestions that don't involve reinstalling CS6?

...BE AWARE.....the newest versions of PPro CC 2014 contain a "fix" for your problems with the .MOV 32 bit codec. Somehow, .MOVs are NOW handled in a 64 bit environment by PPro which REMOVES the CRIPPLING use of the 32 bit Quirktime process, and ALLOWS much greater memory to be used than the old 4 GB limit.......I've seen the DRASTIC improvement myself on my Haswell laptop. I am not sure about Media Encoder, however, it would be STUPID if the same improvement was not also made with THAT program. CS6 does NOT have this improvement.....and WILL not updated to get it. If I return to PPro 5.5....the "old" crappy performance returns with Canon MOVs......even on a TWICE as powerful machine !!!!.....UGH !!!
....Better to submit to the "subscription model" and its pecadillos that try to edit with a QUIRKTIME hobbled workflow !!!!

Problems exporting mpeg 2 videos using Premiere Pro CS6 and Media Encoder

Using a Mac, I'm trying to exporting an mpeg 2 video from Premiere Pro CS6 using the queue process that opens the Media Encoder but when the process begins, it freezes and doesn't end.

Using a Mac, I'm trying to exporting an mpeg 2 video from Premiere Pro CS6 using the queue process that opens the Media Encoder but when the process begins, it freezes and doesn't end.

Premiere Pro CC and Media Encoder won't start

Hey everyone,
I have a huge problem: My Adobe Premiere CC won't start. I've tried all the solutions I've found in the internet, but nothing seems to work for me
I am using OS X 10.9.3.
Here is a part of my report:
Process:         Adobe Premiere Pro CC 2014 [1153]
Path:            /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Identifier:      com.adobe.AdobePremierePro
Version:         8.1.0 (8.1.0)
Code Type:       X86-64 (Native)
Parent Process: launchd [235]
Responsible:     Adobe Premiere Pro CC 2014 [1153]
User ID:         501
Date/Time:       2014-12-10 23:51:37.341 +0100
OS Version:      Mac OS X 10.9.3 (13D65)
Report Version: 11
Anonymous UUID: 5BE9B722-1F73-691F-5EEF-9775088356E8
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000001650
VM Regions Near 0x1650:
-->
    __TEXT                 0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_platform.dylib       0x00007fff9195abe6 OSAtomicAdd32Barrier$VARIANT$mp + 2
1   libclh.dylib                   0x00007fff9076859f 0x7fff90765000 + 13727
2   libclh.dylib                   0x00007fff90875305 clhCtxCreate + 101
3   libGPUSupportMercury.dylib     0x00007fff94e2daab gldCreateQueue + 651
4   com.apple.opencl               0x00007fff8f68e8ad 0x7fff8f688000 + 26797
5   com.apple.opencl               0x00007fff8f68d32b 0x7fff8f688000 + 21291
6   com.apple.opencl               0x00007fff8f68d211 0x7fff8f688000 + 21009
7   com.apple.opencl               0x00007fff8f6a9fbe clCreateCommandQueue + 150
8   com.adobe.GPUFoundation.framework 0x0000000109afbeb1 GF::CreateOpenCLCommandQueue(_cl_device_id*, _cl_context*, bool) + 65
9   com.adobe.GPUFoundation.framework 0x0000000109ad521f GF::Device::InitializeContextImpl() + 2479
10 com.adobe.GPUFoundation.framework 0x0000000109ad76ae GF::Device::InitializeContext(bool, void*, void*) + 622
11 com.adobe.GPUFoundation.framework 0x0000000109af141a GF::Initialize(bool, bool, bool, void*, void*) + 2154
12 com.adobe.DisplaySurface.framework 0x0000000111bb7f84 DS::Initialize() + 228
13 com.adobe.Mezzanine.framework 0x000000010636c3cd MZ::(anonymous namespace)::FullInitializer::FullInitializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool, bool) + 6173
14 com.adobe.Mezzanine.framework 0x0000000106369874 MZ::Initializer::Initializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool, bool) + 84
15 com.adobe.Frontend.framework   0x00000001000abe97 FE::Initializer::PrivateImpl::PrivateImpl(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 1479
16 com.adobe.Frontend.framework   0x00000001000aadc8 FE::Initializer::Initializer(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 40
17 com.adobe.Frontend.framework   0x00000001000cdc32 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 226
18 com.adobe.Frontend.framework   0x00000001000d4ea5 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
19 com.adobe.AdobePremierePro     0x00000001000018ac main + 508
20 com.adobe.AdobePremierePro     0x00000001000016a4 start + 52

AND Media Encoder won't start as well!!
Process:         Adobe Media Encoder CC 2014 [1284]
Path:            /Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/Adobe Media Encoder CC 2014
Identifier:      com.adobe.ame.application
Version:         8.1.0.122 (8.1.0)
Code Type:       X86-64 (Native)
Parent Process: launchd [235]
Responsible:     Adobe Media Encoder CC 2014 [1284]
User ID:         501
Date/Time:       2014-12-10 23:59:55.226 +0100
OS Version:      Mac OS X 10.9.3 (13D65)
Report Version: 11
Anonymous UUID: 5BE9B722-1F73-691F-5EEF-9775088356E8
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000001650
VM Regions Near 0x1650:
-->
    __TEXT                 0000000100000000-0000000100088000 [ 544K] r-x/rwx SM=COW /Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/Adobe Media Encoder CC 2014
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib         0x00007fff93a9a292 __kill + 10
1   com.adobe.dvacore.framework   0x00000001003a28ea (anonymous namespace)::SignalHandler(int, __siginfo*, void*) + 410
2   libsystem_platform.dylib       0x00007fff9195b5aa _sigtramp + 26
3   libsystem_platform.dylib       0x00007fff9195abe6 OSAtomicAdd32Barrier$VARIANT$mp + 2
4   libclh.dylib                   0x00007fff9076859f 0x7fff90765000 + 13727
5   libclh.dylib                   0x00007fff90875305 clhCtxCreate + 101
6   libGPUSupportMercury.dylib     0x00007fff94e2daab gldCreateQueue + 651
7   com.apple.opencl               0x00007fff8f68e8ad 0x7fff8f688000 + 26797
8   com.apple.opencl               0x00007fff8f68d32b 0x7fff8f688000 + 21291
9   com.apple.opencl               0x00007fff8f68d211 0x7fff8f688000 + 21009
10 com.apple.opencl               0x00007fff8f6a9fbe clCreateCommandQueue + 150
11 com.adobe.GPUFoundation.framework 0x0000000109ef7b01 GF::CreateOpenCLCommandQueue(_cl_device_id*, _cl_context*, bool) + 65
12 com.adobe.GPUFoundation.framework 0x0000000109ed0e6f GF::Device::InitializeContextImpl() + 2479
13 com.adobe.GPUFoundation.framework 0x0000000109ed32fe GF::Device::InitializeContext(bool, void*, void*) + 622
14 com.adobe.GPUFoundation.framework 0x0000000109eed06a GF::Initialize(bool, bool, bool, void*, void*) + 2154
15 com.adobe.DisplaySurface.framework 0x0000000107845f74 DS::Initialize() + 228
16 com.adobe.ame.application     0x00000001000376e7 AME::app::MCInitializer::MCInitializer() + 12039
17 com.adobe.ame.application     0x000000010002323a AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 250
18 com.adobe.ame.application     0x000000010000d2ba AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 1802
19 com.adobe.exo.framework       0x00000001057d2bd5 exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1141
20 com.adobe.ame.application     0x00000001000167e6 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 3270
21 com.adobe.ame.application     0x0000000100047828 main + 440
22 com.adobe.ame.application     0x00000001000032f4 start + 52

Videographer membership with Photoshop, Premiere, After Effects and Media Encoder

Similar Messages

Maybe you are looking for