Realtime Ram Preview Fail in Color Management is on

Hi. I m work with Ari Alexa footage as shown VIDEO: After Effects and Alexa - The Expurgated Version by ChrisZwar And I enebled mercury transmit in video preview preferences. When I want to ram preview After effects does not preview in real time. In info window appearce red text fps: 0,6/25 (NOT realtime) Note: project working color space is on
What should I do in this case

BeraT, if you disable Display Color Management (View menu > Use Display Color Management) and Mercury Transmit, do you get real-time playback during RAM preview?
Display color management and video preview in After Effects both impose a processing burden. As each frame is sent for display, additional work must be done to apply a color transformation or a dimensional transformation, respectively. If you have both color management and video preview enabled, both transformations are applied, plus an additional color transformation for the Mercury Transmit monitor. None of these transformations are cached, they are done live, on-the-fly and require additional processing at playback time.
The net result is that both color management and video preview require more processing power during playback. Larger frames, higher frame rates, and higher color bit depth increase the amount of processing power required, due to the increased memory requirements of the frames.
A faster processor would help give real-time playback more often, but you can also increase playback speed by lowering the memory requirements of the RAM preview frames: reduce the resolution in the Composition panel or the playback resolution in the Preview panel, reduce the project's color bit depth setting, or reduce the Frame Rate or increase the Skip rate in the Preview panel. Disabling the Use Display Color Management option will also help, as it removes one of the processing steps.
All of that aside, if you aren't able to achieve real-time playback when both Display Color Management and Mercury Transmit are disabled, that tells you the problem is coming from somewhere else. You'll need to provide more information about what's happening in your comp.

Similar Messages

Preview panel loses Color Management after Minimize Bridge CS5

Whenever I minimize the Bridge CS5 application window to the Windows taskbar, upon restoring or maximizing the Bridge application window the image(s) currently showing in the Preview panel no longer appear color managed (they look exactly as they would appear from a non-color-managed app.) In order to see them as color managed again, I have to either de/re-select their thumbnails or double click the Preview panel twice (once to minimize it, and once again to restore it.) Otherwise resizing the Preview panel has no impact on the color. The thumbnails in the Content panel are fine. This did NOT occur in CS4 or earlier versions of Bridge - otherwise the same environment.
I have a wide-gamut monitor, which causes many non-color-managed images to look super saturated, especially reds & greens, so it is probably much easier to notice this behavior in this environment than from a typical-gamut monitor.
Windows 7, x64, ATI Radeon HD 4850 graphics card, Bridge v4.0.3.9
Anyone else notice this annoyance?

Thanks Curt,
I doubt this is a video issue as no other versions of Bridge behave this way on this system. I have the same preference settings in Bridge CS5 as for Bridge CS4 - which works fine. Nor does Photoshop exhibit this behavior post-minimizing, & Photoshop behaves perfectly for all the OpenGL Drawing settings (which I have set to Advanced in PS.) Bridge just seems to poorly manage the Preview panel color post-minimizing the application window, but otherwise everything displays fine during operation. I'd be surprised if it was just me but if it is, it's an easy enough annoyance to work around. I'd imagine that this isn't too observable on a normal-gamut monitor.
I tried your suggestion of "use software rendering", just in case, but it made no difference. Appreciate the idea though...
One more observation:
While thumbnails are being generated for the first time on large images, they also have the non-color-managed appearance until they complete their generating, at which time they take the managed appearance - but I just consider that a processing-timing final step & it hasn't changed behavior from previous versions of Bridge.

HD RAM preview not playing in realtime through Blackmagic

I've recently upgraded one of my company's Blackmagic Multibridge Pro NLEs to CS5:
PROBLEM:
AE CS5 does not play realtime RAM preview of HD1080 video when displayed through the Blackmagic video output (even as low as 1/8 resolution).
INFO:
1.) Lowering resolution (even down to 1/8) does not help.
2.) Matching scale % to resolution % does not help.
3.) Doing #s 1-3 in combination gets very close to realtime, but CS4 did not require all of this.
4.) If I switch AE output to "computer monitor only" I get realtime.
5.) SD comps played through Blackmagic output achieve realtime.
In CS4, HD Blackmagic output WAS realtime. I have made all memory/multiprocessing settings match the CS4 configuration, but this has not helped.
Also, both AE and the Blackmagic driver are the most current version. I have no desire to revert to CS4... Anyone have any ideas?

To answer my own question:
I lowered the project's color settings to 8 bits per channel--and now all HD RAM previewing (even at full resolution) seems to be playing back realtime!
Hope this thread can be helpful to anyone else experiencing the same issue.

My RAM is not fully in RAM Preview

Hi!
I have a problem with RAM Preview and rendering in AE cs5...when i finish a composition i click on RAM Preview and in task manager my CPU is going on 100% and my RAM is load just 1,8 Gb from the total of 4Gb...I looked over the Motherboard specs to see the RAM compatibility and is nothing wrong....my pc sistem is Athlon II x2 250, MotherBoard: Gigabyte MA770T-UD3, RAM: 4Gb Elixir DUal C, HDD: Seagate 500Gb 7200 RPM, Graphic Card: MSI Nvidia GT 240 on a Windows 7 Ultimate 64x. Is there a solution to unlock my RAM from AECS5 or WIndows?

Windows 7 Ultimate 64x
Ah, and where do you think that one runs along with tons of drivers, services and other tools? You never have full 4GB to begin with. Similarly, when AE loads, all its program components cann occupy another not so minor part of your RAM. None of that RAM is accessible to be used to cram footage in it once it is occupied, so what you see is perfectly normal. You need considerably more RAM to exploitz the benefits of 64bit applications. that's the only real and hard truth here. 4GB is really just the bare minimum.
Mylenium

Color management help - exporting JPEG

The attached image was shot in RAW (Nikon D70 NEF) and imported to Lightroom 1.3.1 for some contrast and toning tweaks. The image on the right is shown as LR displays it. When I export it as a JPG, however, and open the image in Photoshop or InDesign the image (as shown on the left) is much more red. I'm using sRGB as the exported colorspace and the same as the working space in PS and ID. I've also tried exporting using AdobeRGB and ProPhoto RGB with similar results. What's going on? I'm using a MacBook Pro with OS 10.4.11.

What are you using to calibrate your monitor? And how are you calibrating? Does the jpeg look wrong in preview.app (a color managed app that cannot be wrongly configured, contrary to Photoshop) too? We have seen some cases here of certain calibration devices creating bad monitor profiles. Sometimes it helps to simply select the default color profile (Color LCD on most Macs) to see if the difference disappears or to try another calibrator. Make sure your calibration software only creates a single rendering intent. Differences between Photoshop and Lightroom are usually caused by the calibration software creating a perceptual intent next to a relative rendering intent. Lightroom uses perceptual if available, while Photoshop uses relative. You can check whether this is your problem by softproofing in Photoshop to the monitor profile. Do not check preserve RGB numbers and select perceptual as the intent. If it looks the same as Lightroom, this is your problem.

Color Managment and CS3 Confusion - new LCD

Please help, I'm just learning about how Ps handles color and this is driving me nuts.
I'm using Ps CS3 in Vista 32-bit. Just got a new Dell 2408wfp LCD monitor. I'm using the default color profile it installed with monitor (specific to the monitor, not a "generic monitor" profile). Picture colors look great in Ps workspace. When go to "save for web" the images look way oversaturated (more orangish). In the save for web options, it's currently set to "uncompensated". If I change it to "Use document profile" or "standard windows color", it looks correct in "Save for web" preview. However, if I save it with either of these 2 settings and open it in IE, it looks bad again. In Ps, under "edit", my "color setting" is set to "North American General Purpose 2" with the workspace set to sRGV IEC61966-2.1. If I got to view -> proof setup -> and select "monitor RGB", the Ps workspace looks just like the "save for web" preview. My "Color Management" in the Vista Control Panel has the following settings:
Devices tab, ICC profile = Dell 240WFT color profile, D6500 default.
Advanced tab, device profile = system default (sRGB IEC61966-2.1)
Advanced tab, viewing conditions profile = WCS profile for sRGB viewing conditions.
What is going on here? From the forums it seems like either Ps is wrong or my monitor is. Which version is truly in the image? What I see in Ps workspace or in the "save for web" preview? In this scenario what version would my website visitors see (bad or good image color)? Could Ps be "correct" and saving without a color profile when "save for web" and then IE is using my monitor profile and therefore looking bad? How can I fix?
Thanks in advance!

"What was confusing to me is ON MY MONITOR it looks good in Ps. "
What's confusing about this. Of course it looks good on your screen. Ps is using your monitor profile in conjunction with the workspace profile to display correctly. As soon as you view that sRGB image in Monitor RGB, which is what your other apps are doing, the on screen view goes to hell.
"If I then follow that logic, I should just ignore the SFW and final visualized output on my monitor in my workflow and hope my end users visiting my website don't have wide gamut monitors with goofy color profiles?"
Yes, that's about the best you can do. Actually embedding the profile and pushing for profile aware applications like Safari to become more widespread.
"Seems like this approach doesn't correct the problem for me or visitors to my website with a similar monitors. And if the issue is just my monitors color profile, why don't all images on the web also look color shifted on my monitor?"
How far off images look depends a lot on the image in question. Some types of images don't shift very much at all while others look hugely different. Also, if you're looking at images other than your own, you have no idea under what conditions (viewing and calibration) those images were adjusted. There are so many people, even professionals, who don't yet understand color spaces and calibration that you can't take anything for granted unless you do it yourself. For instance, I work with a lot of stock images from agencies like Getty and even though most of the files have embedded profiles, almost all of them were corrected by people who had no idea of how to properly do color and tonal correction, yet, somehow, you have to assume they thought the images looked great on their systems.

RAM Preview Playback Slow

I upgraded to AE CS4 and now the playback frame rate of my RAM previews will never play in realtime.
Even in the simplest comp (DV NTSC 29.97fps) my RAM previews playback at about 20fps.
On this same system in AE CS3 I could do HD Comps that were fairly complicated and get HD 24fps previews in realtime.
Any ideas on where to start looking for the problem? I've searched the forum for a similar issue, but the posts I have found don't relate to my issue.

I'm on a Dual Core 2.66 machine with 2mbs of RAM.
I turned off the external preview option, and now I get realtime RAM previews. I had it going out of a Kone LHe card. That was never a problem in CS3, and I have the latest drivers for the Kona.
I'd like to be able to preview out to my external HD monitor. Any ideas on what I could tweak to do so? I've looked at the improve performance page. My issue is less about render times (I'm happy to wait), but I do want RT previews.
Thanks for the input so far.

No Real time Previews with color management on

Hi Everyone,
I use Color management all the time for correctly interpreting YUV footage in CS3, when I try the same techniques in CS4 I cannot get a realtime preview until I turn Color management off ... is any one else experiencing this ?
Thanks
Nic

I tried the same thing on my MacBook Pro and there was no issue. Here's my specs:
Processor 2.4 GHz Intel Core i7
Memory 8 GB 1333 MHz DDR3
Graphics AMD Radeon HD 6770M 1024 MB
Software Mac OS X Lion 10.7.4 (11E53)
I'd suggest:
Submit bugs to http://www.adobe.com/go/wish . More on how to give feedback: http://bit.ly/93d6NF

Color Space Ram Preview

Yet another problem seems to have arisen with the new CC 2014.
When I try to do a RAM Preview even of a small section at lower rez the RAM Preview will not play back in real time and the audio is way off.
I get a note saying that "Color Work Space is on" which indeed it is. If I go into Project settings and switch Color Workspace to "None" my RAM Previews play perfectly.
In previous versions of AE including CC this was never an issue. Playbacks were fine even with a Colorspace and Linear workspace chosen.
Has anyone else had this problem? Is there a solution other than having to manually turn off my Color Workspace every time I want to do a quick RAM Preview?
Thanks
TAK

Takasaurus, can you be more specific about the RAM preview playback speeds you're getting with Display Color Management enabled?
For example, on my MacBook Pro, RAM previewing a 23.976 5K R3D comp at 32bpc in full resolution with color management enabled, in either After Effects CC 2014 (13.0) or After Effects CC (12.2.1), I get the following results:
Display Color Management enabled, Color Management Quality set to Faster or More Accurate Except for RAM Preview (same meaning in this context): ~11fps
Display Color Management enabled, Color Management Quality set to More Accurate: ~5fps
Display Color Management disabled: 23.976fps (real-time)
Under the hood, when Display Color Management is enabled After Effects does an additional color transform of every frame at the time it is displayed. These frames are not cached, the transform happens live at display time. (Note that you can enabled or disable Display Color Management without affecting the state of the comp's image cache; ie., the green bar in the Timeline panel.) This live transformation of the comp is what is impacting the ability to play back the frames in real time. Granted, a 5K R3D in 32bpc frame is almost a worst-case scenario in terms of memory and performance, but it shows the limits of the machine.
You can compensate for the memory usage with the same techniques that you usually would: reducing the RAM preview resolution or frame rate in the Preview panel, or reducing the color depth. Sounds like you're already doing that.
When using Mercury Transmit for video preview, something similar happens: After Effects does a live transformation of the video frame for the Mercury Transmit device, which can be even more complex due to scaling and/or frame rate limitations. Add color management to that and you get a double-whammy.

No realtime playback during RAM preview

Ever since I upgraded to the newest MacPro, AE has been unable to play a RAM Preview in realtime. Even during the most simple of compesitions, RAM preview fluctuates between 20fps and 59.94fps and will never "lock in" to realtime. Resolution is set to full and zoom is set to 100%. We have compared all the settings to other, less powerful, machines in our studio and still cannot make it play realtime.
Mac Pro 2 x 2.66 Ghz - 6 Core intel Zeon
24 gb Ram
30 inch Apple Cinema Display
ATI Radeon HD 5870
OSX 10.6.6
Kona LHe 9.1
AE 10.5.0.253

I'm guessing the problem is with your Kona card. AJA has been having issues with CS5.5 and they just released updated drivers and have split the Adobe app plugins into their own installer now on the Windows side.
Unfortunately, you say you're already using the Kona 9.1 drivers so you're in the same boat as me with the poor playback in RAM previews.
Removing the Kona card instantly put my RAM previews back to normal, but it's not a proper solution.
Here are some tips I received from AJA support on this issue a few days ago:
OPTIMUM AE Settings for best performance:
Make sure the AJA video preview setting matches the sequence.
Use a RGBA video preview setting and not RGB 10-bit.
In AE preferences -> video preview set Output Quality to Faster.
Go to Project Settings -> set color settings -> depth and set to 8-bits per channel.
Make sure you are viewing at 100% during playback.
I just put the Kona 3G card in last week and CS5.5 instantly had playback issues in both AE and Premiere. I got the 9.1 drivers AJA released this week and everything was fine after that! Halfway through a project yesterday, my RAM previews started lagging again. I'm working with AJA to resolve and if I get it figured out, I will post the solution here.

Random Flashing Color Bars within Quicktime Files during RAM Preview Only

I have been getting random color bar flashes within quicktime files in AE CC during RAM previews using Multi Processor rendering. Files other than .mov seem to not have this issue (although I have seen it twice...though it may be due to quicktimes in the comp). The rendered output using MP rendering is completely fine. If I turn off MP rendering the ram preview is fine. The source material is coming off a RAID 5 at 600-800MBs, I have moved the footage to a local SSD and a standard spindle drive with the same results. I have tried everything.....disabling GPUS in preview, disabling Fast Adaptive Preview, Disabling Disk Cache, Adjusting MP settings and RAM usage per core, disabling hardware accelleration of interface, adjusting gpu memory useage, every codec under the quicktime wrapper including uncompressed codecs, updating Blackmagic drivers, updating quicktime, limiting how many processors Windows 7 64bit can see, resetting AE preferences. I even installed After Effects clean on my second boot drive for gaming with no plugins or other apps, same issues. Have discussed this heavily with tech support at Adobe and they are working on it for a few days before getting back to me. When I got off the phone the tech was of the mind that I have too many cores for the Quicktime codec to handle.
My system :
Windows 7 64bit
Dual Xeon E5-2687W: 16 Physical cores and 32 cores with Hyperthreading
32GB 1866 DDR3
3xNvidia GTX 680 4GB cards
SSD boot and seperate SSD media cache drives
8TB internal SAS RAID 5 using a ATTO card
Blackmagic Deckline Extreme 3D+ card
Any help or thoughts would be greatly appreciated as this is a huge boon to my workflow. Having purchased a $12K system for grading and rendering....not being able to use the ram preview in AE with multiple cores is a huge inconvenience.

Here is the requested taskmanager screenshot. As my test comp only has a single duplicated quicktime in it, it renders too fast to really catch the AE instances doing anything. So this is from a heavier comp. Settings are as pictured above with 3GB per core using 8 total cores of the 32. It did flash the bars.
Here is what I tried tonight:
- Followed the link on Quicktime having trouble with too many processors. Using MSCONFIG I dropped the recognized Processors to 21, 16, and 8 and tested all three settings. Each had the flashing bars issue. Again as usual, at random, sometimes 3 previews before showing up, sometimes the first preview run. I have noticed that the ram previews that take a little longer seem to be clean. Then sometimes it seems to fly through the preview, grabbing large chunks on the green progres bar above the timeline, or many little chunks very quickly....these are usually the preview runs that will show the flashing bars. I make a point of purging the cach between each one so it doesn't remember, plus I have disk media cache off, but sometimes I get the feeling it's remembering bits.
- I removed all the Quicktime Components from the QTComponents folder and tested it. Flashed the very first run without any quicktime components.
- Followed the Firewall or TCP instructions and made sure everything was allowed through ZoneAlarm. However I could not find the QT32 Server listed anywhere or figure out how to add it. No matter because I closed and force quit all of the firewall processes as well to make sure. Still flashed.
- I followed all the advice on the landing page for Quicktime-related problems
- I also tested out ram previews again thourougly with the same clip but converted to a Tiff sequence. No matter what I tried there was never any flashing in the ram preview with tiffs.
- I also re-tested the clean render output. Made a ram preview with the flashing bars, then without purging rendered it out to a quicktime file and there were no bars at all in the rendered output. I even tried duplicating this render output 6 times in the render queue and rendered them all at once. Not a single one had a flashing bar frame. I even played all 6 1080P uncompressed 4.2.2 YUV 10bit pieces off the RAID with no dropped frames or hichups.
- Killed every process in the taskmanager but for essential windows processes and the flashing bars were still present
- Set the priority to Real-time for every AE process including Adobe QT32 Server, Dynamiclinkmanager, and all the AE processes. Still flashed.
I am now considering disabling two of my GPUs in the device manager. However I'm a bit worried about disabling the wrong one and being locked out. Any thoughts? Is the computer to powerful for some process somewhere? Why only in RAM preview? Thanks again.

IE10 Consumer Preview Still Only Does Half Color-Management

The Internet Explorer version 10 Consumer Preview does not do full color-management - it ignores the monitor profile.
This is not a real surprise, as I have had it confirmed to me by someone inside Microsoft, but I thought I'd just pass along that in my Windows 8 CP testing I've verified this to actually be the case.
IE9 and IE10 do not manage the color of web page elements at all, and both interpret image color profiles in images if they're present, but they only convert the colors to sRGB, no matter what monitor profile you're actually using. For calibrated and profiled systems, this yields inaccuracy; for example, with wide gamut monitors the colors of images carrying a profile will always be oversaturated.
Sigh. Progress marches on EVER so slowly.
-Noel

Let me try to help you further:
1. In Illustrator's Swatch settings pallette, should the Spot Color Mode option be set to use:
a. CMYK
b. LAB
c. Book Color (not sure if this refers to the pantone swatchbook)
- I would use "c" - Book Color. This is the file going to the printer which will use Spot Color on press. For a copy of the file to be output by your Canon, use "a" - CMYK.
2. In the View menu should Overprint Preview be checked, and why, and would it differ based on the settings for #1.
- Only if the color was transparent ( which it isn't ) would overprint preview be of any use or you use a tint value of the Spot color and a black, but even then you may not be able to detect any change in the screen view. I typically do not use any overprint preview and I do not rely on the monitor for any color deisions. You could be different and that is OK. Let me know if you are able to detect any deviates using overprint preview.
I'm sorry for being a little short. There is a lot of confusion about these issues and Adobe and Pantone are not making things any easier.
The key is your Canon will not be able to print accurate Spot color without a RIP for the necessary color tables and conversions for that particular printer. In your case, it will be necessary to build a CMYK file to print a somewhat approximate representation of that specific Spot color. Another frustrating part of this matrix is CMYK cannot match all Pantone Spot Colors.

RAM Preview - Not in realtime

Hello
On my computer, whenever I try to playback somehting to see a preview, it plays at 17 frames per second, with red text saying, Not in realtime. Is there anyway that this can be remedied?

Make sure you are depressing the Zero key for ram preview. I bumped into this the other day because I had selected AJA Kona as my display option in Preferences. When I switched it back to Computer it played back in real time. The other reason might be a very complicated sequence on a computer with slow processers or not enough ram. You always need to share the details of your system when asking questions like this so folks know what you are using.

Preview Color Management broken? Profile not applied?

Hi all,
I've come upon an inconsistency and wondered if anyone else is having this issue?
I profiled my Xerox Color Laser Printer. When I print out of Photoshop CS 4 my prints look great.
If I print out of Preview (Mac OS X 7.5), the colors are not correct and the In Printer color management prints match the ColorSync Color Managed with my new custom profile selected prints? I tried turning on the soft proofing, and the screen image in Preview looks amazingly like my successful Photoshop Color Managed Print, but when I print, the image appears as if the printer profile is not being applied. FYI, this profile is an ICC v2 Profile.
As I noted prints out of Photoshop are accurate and just fine.
Any help would be appreciated.
Thanks, and so long for now, TOM

Thanks for the reply Richard. I indeed tried the latest driver, 91.31. The new control panel was quite confusing. I managed to get to the performance and quality place, but there was no way to set a color profile to a specific game, so keeping the same drivers, I went back to the classic control panel. Color profiles can't seem to be applied for game profiles, as the value in the profile switches to a "0" every time I hit apply (read that some other guy on the nZone forums had the same issues). So as of now, I just use the 84.21 drivers and set the color profile manually in the taskbar.
By the way, does anyone else here set color profiles in their game profiles? If so, how's the experience?

After Effects CC failed renders, RAM preview useless

Hi there,
I'm having some strange issues with After Effects, the sort that I've never experienced before.
I'm animating a 5-second sequence with nine layers, each with video copilot's "Twitch" effect plugin added. The comp is big, set to 4000 x 4000 px.
When I go to RAM preview on full resolution, I only get ten frames of the comp previewed before it loops from that point. Spacebar preview returns the same result (it freezes at ten frames). I tried exporting the comp, but it returns "Failed at 00:00:02." I created a new 1920x1080 comp and tried again with scaled down source material but the same effects occur, this time further down the timeline at about 3 seconds. Can't RAM preview, Spacebar preview or export beyond that point. If I trim the comp to just before the problem frames at 3 seconds, I can successfully export.
I'm running a brand new macbook pro (2.3 GHz, 16gb RAM, Nvidia Geforce GT 750M [CUDA enabled]) and the project is located on the internal SSD. OSX 10.9. After Effects is the latest update available 12.2.1.5.
Any ideas? I've not found anything in any forums dealing with this specifically. I think I have an OSX update due actually - I'll check to see if this does something interesting and report back!
Cheers!

Hi Todd and AlpineEdits,
I deleted Twitch from the plugins folder and ran a few tests - everything seems fine.
I reinstalled Twitch, but used perhaps an older version - I didn't use the 64-bit specific plugin provided as part of the download package. The same sequence now previews seamlessly and fast too.
Seems that Twitch causes strange little AE hiccups!
Thanks so much for the simple suggestions, worked a charm.

Realtime Ram Preview Fail in Color Management is on

Similar Messages

Maybe you are looking for