Media Encoder adding RBG color casts on BW 16mm Footage

Hey Everyone,
I am really stumped by this one. I am working with FCP6 and Apple Pro Res HQ scans of 16mm B&W footage. I am trying to encode a self-contained .mov file (direct from FCP) in Adobe Media Encoder CC (for Blu-ray) and then burn to Blu-ray with Encore CS6.
I burned the first test Blu-ray last night and when I played it back on my Blu-ray player/TV, I was stunned by the fidelity and definition of the otherwise thick/complicated 16mm grain structure, even via what was only a 6GB .m4v render (compressed from 33.5GB .mov). Everything was perfect...EXCEPT...I got these horrible "color casts" of red, blue, green, magenta, across practically every shot in the footage. Particularly in the last shot of the drain pipe (see example clips 14 seconds long):
Original: https://vimeo.com/97456916 (pass: "original")
Blu-ray: https://vimeo.com/97453674 (pass: "colorcast")
Obviously the footage does not look this in either FCP6 or .mov in QT7. I just double checked and the color casts ARE visible when playing back the ME converted .m4v in Encore. I have also taken the .mov from FCP and brought that into Encore and NO COLORCASTS. I have also taken the .mov, reimported it to FCP and but a 3-Way Color Corrector on it and put the saturation at zero, exported that, and then ME>Encore and it still adds the color....So I am 99% positive this is a Media Encoder issue. Here are the settings I used:
Considering how long is has taken me to get satisfactory web compression results from 16mm footage in the past, I feel like I just hit a grand slam in the bottom of the 9th with the playback fidelity of the first test Blu-ray. The motion and definition are phenomenal, I mean we are talking Criterion quality--without X.264 or Blu Code--(even with all the modern "overcompensation" crap turned off on my TV). I AM SO SO CLOSE TO RENDERING/BURNING A PERFECT BLU-RAY IF I CAN JUST FIGURE THIS COLOR THING OUT!
Got a deadline to get this into the hands of a couple of prominent filmmakers.
Any help or ideas that anyone can provide will be most appreciated.
Thank so much!
Alec
MAC PRO // OSX 10.7.5 // 2 x 2.66Gmz 6-Core Intel Xeon // 32 GB 1333 MHz DDR3

***SOLUTION***
Well it seems silly that I had to do this at all, but here is the workflow that finally seemed to solve the issue without adding an extra level of encoding...
Save self-contained .mov of my timeline in FCP6 > bring that back in FCP as a separate sequence and apply the "Desaturate" filter (Image Control > Desaturate) to the entire film > save as self-contained .mov again > convert in AME > master and burn to Blu-ray with Encore > Presto!!! NO COLORCASTS on B&W 16mm footage in Encore and no colorcasts from the file on the burned Blu-ray disc.
I believe I stated it above, but in case I didn't, adjusting the chroma and/or "desaturating" via FCP's color corrector plugins did not work...even with the exact same workflow otherwise. I have no idea why, but if anyone ever runs into the same problem, this worked for me. Only took two weeks to do something that I guessed would take a day, maybe two. Geesh.
Thanks again guys for all the suggestions. Really really appreciate it.
-Alec

Similar Messages

Media Encoder adding flash frame

Using Media Encoder to create a .m2v for use in DVD Authoring. I import a QT, and in the encode, it is adding a random image that occurs about 32 minutes into the program at the 35 minute mark. I reran, with the same result. I have checked the original QT frame by frame and there is no such flash frame in it. Settings are 2-pass VBR, Target Bit Rate 4.2 for a file that is 1hr 43min long. Could Encoder be glitching, and are there any settings I can adjust to avoid it?

I, too, am experiencing Media Encoder throwing in a random flash frame occasionally on an output file. Output specs are typically Pro Res HQ 1920X1080 23.98P with 2 to 8 mono audio channels at 48k and 24bit. These are files for delivery to a client. It seems to be going to some random location within the episode and grabbing a frame and popping it in. Anybody have any ideas as to why this is happening?
We're also realizing this is a random occurrence. Output settings don't seem to matter, and redoing the export with identical settings will yield a file with no flash frame. Sometimes it's there, and sometimes it's not...

GoPro Hero 3 Black 4k and Adobe Media Encoder CS6

As a current Creative Cloud member and a Premiere Pro user, I wanted to see if the Adobe Media Encoder can be used as an alternative to GoPro's Cineform Studio (free version), mainly as a batch encoder for use in Adobe Premiere Pro. The main issue with the GoPro footage in Adobe Premiere Pro is that its codec is not compatible with playback in Premiere, there's a conflicting codec that GoPro uses that unfortunately causes it to have choppy playback in Adobe Premiere Pro. Another issue is that the Adobe Cineform Studio (free version) is that one can only export one video at a time. And, finally I wanted to have more export options than what's available in the Cineform.
This is what I've come up with:
• 4Kcin and 4K show no preview footage in the encoder, and will export as black video - the encoder sees "no video"
• 2.7cin & 2.7k and below all show preview and export appropriately.
The main issue is that Adobe Media Encoder does not recognize the 4kcin or 4k footage from the GoPro camera. But it can encode 4k or above footage since it has a REDCODE plugin.
Any thoughts or suggestions?

Hello,
You may follow the instructions given in the link below and see if that helps
http://helpx.adobe.com/creative-cloud/kb/error-a12e5-installing-creative-cloud.html
If you still face any issues you may contact us directly through chat using Contact Customer Care or email us directly at [email protected]
Regards
Himanshu

Adobe Media Encoder "expands" my video from it's original size

When I export an XDCAM HD422 file (as an .mxf) that has scaled or aspected SD footage on the timeline using Media Encoder it changes the aspect or expands the footage so it's out of frame slightly. If I have a mask on the timeline, it gets shifted to the right. None of these problems arise if I don't use Media Encoder. Does anyone have a solution to this....or a workaround?

here are screen shots of my sequence and export settings. Thanks for helping with this.

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.

Is mp3 support going ot be added to Flash Media Encoder?

Hi everyone,
I work at CNET in the Entertainment division and we recently
launched a full on Flash video player
Example:
http://www.gamespot.com/video/918428/6172011/fallout-3-official-trailer-1
On the side for the past few months we have been testing
On2's Live Flash encoder and Adobe's Flash Media Encoder with
Akamai. Because of features lacking (like de-interlace) in On2's
encode, we have no choice but to use Adobe's encoder.
While there are something I wish would be added like full on
multi-thread support (considering On2VP6 is so CPU intensive),
though that's more of an On2 thing (maybe Adobe can pressure them
since Dual-Core/Quad-Core systems are the norm these days and the
On2VP6 does little to utilize it), one thing that has really urked
us is the choice for the Nellymoser codec to be the only option for
audio in the Flash Media Encoder (and On 2's).
We want to migrate from webcasting in Windows Media to Flash,
but our audience feedback has been horrible with the Flash live
streaming because of the terrible audio codec we are forced to use.
Which leads me to my question --- is there going to be any
updates in the near future to allow us to use mp3 as the audio
codec? We have several machines on order just to handle Flash Live
streaming using Adobe's software and going by user feedback, we
simply cannot do it...so we are gonna have to be forced to have
Windows Media player within our Flash which is going to kill the
user experience.
Anyhow, just hoping to hear a good answer. Have the same
question into On2's support....
Dave

I recently read on one of the listservs (not sure which one
it was... maybe the flashcomguru.com list?) that the next version
of FME will use hardware acceleration, so that should alleviate
some of the processor load. Of course, this is third party info I'm
passing along, so take it with a grain of salt.
About MP3, I'm not so sure I'd hold my breath on that one.
Problem is, FME is a free product, so I don't know if Adobe will
see value in shelling out the cash for the licensing required to
support mp3 encoding (money that will never be directly recovered).
They already have the licensing for ASAO, and as I understand
things, that ASAO license is the reason you can only use FME if you
own FMS or have an active account with one of their partner CDN's
Incidentally, this is a user-end forum, and I don't see a
strong presence from the Adobe employees around here (some, but not
a whole lot). If you were using FMS (rather than a CDN) I'd suggest
contacting Adobe support directly, but I've heard that support
requests from non-purchasers tend to fall to the bottom of the pile
indefinitely.

Adding to Media Encoder Render Queue Failure

Hey guys,
So every time I attempt to add my composition to the render queue (media encoder) it always just results in my AE crashing and it does not get exported to Media Encoder. Any solutions to this?
Thanks!
Kel

No idea why because I don't know anything about your OS or your version of AE or your project. Try this. Create a new AE project that is 8 bit. Create a new standard HD comp that is 10 seconds long. Add a shape layer or a text layer or a solid to the project. Save your project and then see if you can add it to the AME. If you can, then there's something in your composition that is causing the problem and you need to give us a complete description of what is in the composition. The easiest way to do that is select all of the layers in your timeline and press the U key twice to reveal all changed properties or added effects. Then post a screenshot. If you project contains pre-comps then a flow chart and the timelines from he nested comps will also help.

AE not adding files to Media Encoder

Hello,
My After Effects CC is not adding files to the Media Encoder. I can render using the add to render queue option, but when I try to Add to Media Encoder, it will open Media Encoder but it doesn't add the file the the queue list.
I've updated AE and Media encoder and that didn't fix it. Running on Mac Yosemite 10.10.2 Does anyone have any suggestion?
Thanks for your help

See the known issue here about Adobe Media Encoder taking a very long time to open the first time on Mac OSX v10.10 (Yosemite):
After Effects with Mac OSX v10.10 (Yosemite)
Based on this, my suggestion is to open Adobe Media Encoder once, give it plenty of time to start because of this Mac OS bug, and then try again. My guess is that it'll work fine after that.

Media Encoder scrambles colors when encoding a warp stablilized clip

Hi. Anyone have this issue? Queing any clips into media enoder with warp stabilization applied result in and encoded clip with colors jumping all over the place within the said clip. Very strange, I tried to uninstall and re-install media encoder and did not solve the problem. Anyone have the expertise to help with this issue?

I've been trying everything now. With and without the Cuda Acceleration and both behave exactly the same, funny colors and jumbled video in the render.
Perhaps someone with skills in the Codec world can help? I wouldn't know where to start looking, and I don't wanna mess around with codecs without proper advise.
If someone knows if it may be a codec on my machine creating this problem?
I shoot in AVCHD, I get m2ts files from both my cameras (Sony). Could this problem be related only to this format when exporting with Warp Stabilizer? This problem only started after an update from Adobe for CC 2014 products.

RE: Media Encoder expected color levels (RGB or 601/709?)

Does Adobe Media Encoder (CS5) assume imported files have RGB or 601/709 color levels?
I'm using a quicktime reference file from Avid and I need to know if Media Encoder is expecting my file to be RGB or 709 color space.
I tried the encode with a QT reference that was 709 and the resulting encode looked identical (black levels looked similar on consumer monitors), but I need to be absolutely sure AME is interpreting my file correctly.
Thanks for any responses!
Andrew

Bad news....
It's always up to the Exporter plugin.
Very few (if any) get it right.
In general...
... if the input file is natively YUV (eg mpeg-4) then AME will open it as YUV 601. If there is a checkbox in the GUI it will change that default and open it as 709 if you select so. The range can be either 16-240 or 0-255 if opened in 8bit mode (ie not "Max Depth).
... if the input file is natively RGB then it's a complete mess.
To put it in perspective I spent 6 months ironing out every combination for my soon-to-be-released plugin.
A general rule is, if it's YUV source then it'll open it 601 unless it has the 709 flag set right. If it's RGB it'll almost always be 601.

Adobe Media Encoder CS5 hangs when adding files of varying HD resolutions.

I've seen questions similar to this related to CS4 but never explained very well, and my CS4 for mac worked fine. I am unsure if this is a new problem or a windows specific problem but here is the situation, if you need more information I will gladly provide it.
For the past week or so I have been encoding 1920x1080i mov files (h.264/aac) to 1280x720p (vp6/mp3) flvs. When I stick to that single HD format in the AMC processing que everything works great. However, when I add older HD content into the AMC que, content with non-standard presets, the program hangs. I tried to import about 15 files last night and the program just sat there all night in a '...NOT RESPONDING' state. The video's have different audio and video settings and it's little difficult to pinpoint exactly what they were. Some are 1440x1080, some are 1280x900, some have PCM audio some of mp3.
Now I temporarily resolved this issue by simply using cs4 master on my mac pro which worked great. However I have noticed a huge speed increase in CS5 64bit AMC. It takes 2-3 hours to encode 1 flash video on my mac pro (dual quad core xeon 2.9Ghz/32GB ram) with CS4. It takes ~20 minutes on my windows 7 station (single core 2 quad 3Ghz/8GB ram) with CS5.
How to replicate:
If I drop a single file into the AMC CS5 que, regardless of the resolution, frame rate, or sound codec; it will import. If I then add another file with a different resolution AMC will hang and become non-responsive. It never crashed but I can't wait 12+ hours to see if it accepted a job or not. As I said before this problem was not observed on CS4 for mac - it worked flawlessly, albeit a little slow.
Software used:
Adobe Media Encoder CS5 windows 64bit
Adobe Media Encoder CS4 mac 32bit
System specs:
Windows 7 home:
Core 2 quad 3Ghz
8GB ram
80GB SSD x25-m
nVidia Quadro 580
OSX 10.6.3:
Dual Xeon 2.99Ghz
32GB ram
4 7200 disks in 4TB raid 0
Radeon HD 2600
Matrox MAX h.264 compressor card
Any advice on this situation would be greatly appreciated. Thank you for your time
-Michael Emanuel

Hi Michael,
Sorry to hear you're having problems with Adobe Media Encoder. I'd like to get some more information about the problem so I can better understand your workflow, and potentially try to recreate the problem. For what it's worth, I often import files of different resolutions without any problem, so I want to find out what's different about how you're using AME.
Apologies for the long list of questions; the small details can be important.
-- After you import the first file, what else do you do in AME? Change the preset? Change the settings? Change the output destination?
-- What are the properties of the files that are causing the problem? You said it happens on "non-standard" files, but can you describe the specifications for one or more files that cause the problem? Please include file type, length, frame rate, frame dimensions, field order (if applicable), alpha mode (if applicable), and audio type and rate. If you know more the bitrate, both video and audio, that would be nice, too.
-- If any of the files are small enough, could you post a couple online that I could try on my machine?
-- How were these files generated? What application created them?
-- Where are the files stored? A local drive, a network drive, a removeable drive (USB or Firewire), etc.?
-- Which Adobe application or suite do you have installed? AME a limited set of options if you're using Flash or Web Premium compared to Master Collection, Production Premium, Premiere Pro, or After Effects.
-=TimK
-=Adobe Media Encoder QE

Adobe Media Encoder CS4 Suddenly Adding Black Bars To L & R

I think I may be going crazy.
Every video I have ever shot has been cropped to 720x340 in After Effects then exported as an uncompressed Quicktime movie file at 720x340. For the last year I have done this process exactly the same everytime.
On my website (www.stevenbogda.com) videos are either 360x170 or 480x226 FLV files, both variations of the original 720x340 Quicktime file. I would just bring a 720x340 file into Adobe Media Encoder CS4, adjust the dimensions and bitrate and export and it would work perfectly. Now all of the sudden, when I bring anything I shot and exported recently into AME CS4 to get it ready to go on my website, it adds BLACK BARS to the left and right side of my video (refer to image 2).
I thought it was just a visual problem in AME CS4 until I exported it as the FLV file that I planned on doing, just to find that the actual FLV file is in fact the dimensions I wanted, EXCEPT it has black bars on the right and the left...
I immediately blamed it on After Effects and started re exporting uncompressed Quicktime files with different settings and managed to get AME to work properly but it was random. Some videos were exported with "settings 1" and worked in AME but other videos with the same settings didn't work.
I went to my hard drive where I store my master Quicktime files that were used to make the videos on my site and brought some into AME CS4 and they acted the same way that the new videos I made do, with black bars on the left and right. These videos worked the way I wanted them to in AME CS4 last month, but now suddenly are doing what my more recent files do and I have no idea why.
I found out that by lowering the width of the video (refer to image 3) the black bars would dissapear slowly, but then the video would be a smaller width that it should be. I really think I am just missing something, or set some setting wrong by accident because this never used to happen and now is happening with files that once worked correctly.
Any help or ideas would be greatly appreciated because I am spending way too much time re exporting uncompressed files just to find out they don't work.
Thank you,
Steven

Stan,
I was using the on2VP6 codec at data rates from 275k to 400k with good results. -- with the new CS$ endcoder i am used h.264 at 500k to 700k, video quality looks good but the graphic overlays look like alised crap. In the encoder settings the edges of the graphics get jaged when I make the field order progresive...
I am starting with DV NTSC video at 720x480.
I am going to go back to my old work flow and test it. The settings are a bit different from premiere pro 1.5 to CS4 -- in 1.5 i could export out an unconpressed .mov with square px and then bring that large file to flash media encoder to create the .flv

Media Encoder gets stuck!!

I'm getting frustrated. I have a 1hr long project that i'm trying to export and been fighting with it for a week.
Media encoder starts its work, it goes on for hours and eventually, at some random point it just stops encoding. It doesn't freeze, it doesn't show any error, it doesn't physically "stop" but the output preview just freezes on a random frame (different each time) and the 'remaning' export time instead of getting shorter just gradually gets longer and keeps increasing to show that it's gonna take hundreds of hours to finish... I didn't trust the preview/remaining time so i kept it on and encoding for 48 hours - at that time it showed that it was gonna take 600 something hours to finish and was still increasing. ridiculous.
I'm on an HP elitebook workstation. Nvidia Quadro 2000, 8GB ram. Win7, Using Premiere CS6. My sequence is pretty heavy - 1hr long, 9 video tracks, 10 or so audio tracks. Most clips have MB Looks color correction on them, some clips have stabilization, few clips use MB MisFire effect. 95% of my footage are 1080p or 720p MOV files from the Canon 7D and from GoPro. Few other clips are different formats (flv/mp4) and i have some stills + tiff timelapses and imported photoshop graphics. Also, just a few AfterEffects clips imported into my timeline. It's pretty heavy but i exported my rough cuts of this project many times before - most recently with the 720p youtube HD preset - always took a while, but it always DID export.
Now I'm trying to export with the 1080p YoutubeHD preset (except i checked 'render in max quality') and I also tried exporting as 1080p H.264 - and it just will not export... It's been a week now, i tried many times, i deleted the cache, i started a new project and imported the old one into it, nothing makes any difference and i'm out of ideas...
*** Few potential clues i need to mention:
- For some time now I've been getting the [..\..\src\TickTime.cpp-207] error whenever opening the premiere project. There are several discussions on this error on the forums - so far no solution and no clear source of the problem (aparrently sth to do with stabilization). But after clicking 'ok' on the pop up error message continuously for a minute or so, the error goes away and the project doesn't seem affected in any way.
- a couple of my previous exports of this project had 1-2 clips that looked 'scrambled' in the finished exported file. It was mostly the stills. This only happened 2 times though, many other exports were just fine. not sure why...
i'd much appreciate any advice...

Sounds exactly like what is happening to me. This is frustrating because it was a 30 hour encoding process and the place where it is stuck is right at the very end of the sequence on the 2nd pass, although there is still about 12% of the progress bar remaining. I guess that this is where it takes all its work and puts the separate files into the single video file. I really don't want to go through this again. The final video file is showing up though and is shown having the size that I am expecting it to be.
Any workarounds to somehow get this unstuck? I am hesitant to just try and open the file. I am going to try a couple of things and if I am successful at getting this to finish without restarting then I will be sure to post it here.
Also, I don't know if this has anything to do with this problem, but I looked at my system Activity Monitor, and there is a CPU process highlighted in red, it states:
Adobe QT32 Server (not responding)
Thirty minutes later...
I was incorrect above as to the actual problem. I paused the queue encoding that was stuck, then opened up the project again in Premiere Pro only to discover that there was an offline still image which I stupidly had renamed during the day. So I renamed the file back to its original name, reconnected the picture, saved the PP project. Then I started the encoding back up and still no luck.
So I paused the encoding again, went back into the PP project and rendered just the area under question, saved it, and exported it into the queue. Then just to be safe I went to the paused item in AME, and duplicated it adding another version into the queue.
Then I unpaused the encoding and ... SUCCESS!! Not sure which of the final steps did the trick, but I am guessing that it was the rendering of the part of the sequence that it was stuck on. Hope this helps someone.

Linear workflow issues with Media Encoder CC 2014

I'm using After Effects CC 2014 and doesn't seem to be the option anymore to export via AE to H264. There used to be a button in the preferences to enable outdated codecs... not there anymore with CC 2014. So... I added my renders into Media Encoder. The problem is that it is not calculating my project working in Linear Workflow so all my renders are very dark & wrong colors.
Anyone find a work around for this? is there a button in Media Encoder that I need to switch on for linear workflow?

I've been validating in QT, but per your comment I opened up in VLC player as well. VLC player does playback the correct color. I attached SS of same lossless rendered video from AE open in AE, QT, VLC, and then the rendered H264 in QT & VLC from AME in one screen shot. You can see that the H264 file from AME is always just a little bit off when opened in QT or Preview mode (OSX) or uploaded to Vimeo. The rendered H264 file is just the lossless file being encoded into H264 via AME.
That's great that VLC player will playback the correct color, but when uploading to Vimeo, the color shifts as well during playback. I've never had this issue when rendering to H264 directly from AE before. I'm a little new to AME so I'm not sure if there is a setting I am missing or is there a limitation to the H264 codec where I've never noticed the slight color shift? Is there anyway to get a H264 file that will play back via Vimeo/QT without the color shift?

Media Encoder CS4 poor CPU use

A friend of mine made a 3 min video in Premiere CS4 and added some color corrections using Magic Bullet Looks, and when she try to export MPEG-2 with Media Encoder, the processor use in task manager is about 15 %, and RAM about 2 GB, after some time it goes to 50 % but soon drop to 1-2%
The rendering time for 3 min video is about 2:30 hrs, and it even fails sometimes.
Why is it using CPU only 15% ?
The CPU is i7 920 @ 2.66 (NO overclocking), 6GB RAM, and WinXP 32-bit

ImporterQT.bundle may be missing or corrupt
uninstall Media Encoder using the package in \Applications\Utilities\Adobe Installers
then reinstall.

Media Encoder adding RBG color casts on BW 16mm Footage

Similar Messages

Maybe you are looking for