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.

Similar Messages

  • Color space and preview mode for mobile devices?

    I want to create artwork that will be exported directly for mobile devices such as Androids and also that will be imported into Flash to create interactive content.
    1. Is sRGB the best workspace for mobile devices?
    2. I can use view > pixel preview to see what artwork will look like in a browser, though what about for a mobile device such as an Android?
    Thanks.

    anyone on this one?
    Thanks.

  • Change Aperture previews color space from Adobe98 to sRgb

    Hi,
    I'd like to change the default color space for the jpg previews that Aperture generates from the masters of my library.
    I now have all my jpegs saved as Adobe98 but it's important for me to have them saved as sRGB because when third party apps and devices go to read them, they can't reproduce the right colors if they find the wrong color profile.
    Thanks in advance for your help!

    I don't know how many different ways to say that you cannot change the color space for previews. The files themselves have specific image data that corresponds to a specific color profile that is Adobe 1998 you cannot change the way Aperture generates these. Changing your system has nothing to do with it.
    As for work-flow - If you need this to work and it doesn't then it never has so I really don't see how it is changing your work-flow that never existed?
    RB
    Ps. External devices like projectors work fine as long as your presentation software respects the source profile and has an output device profile - what kind of "device" are you using?
    Message was edited by: rwboyer

  • Quick develop and color space ...

    Ok, I know that library module previews are in Adobe RGB.
    So, we view files which are in Adobe RGB.
    But what about editing?
    What color space we use when adjusting in quick develop in library module?

    Armut12 wrote:
    Thank you for such a clear summary.
    Do you know why does Adobe not use Melissa RGB in library mode previews?
    As far as I can see, assigning an Adobe RGB profile to a JPG file and assigning a ProPhoto RGB profile to a JPG file does not create any difference in file sizes.
    Is there a disadvantage of using Melissa RGB in library views?
    Melissa RGB isn't really a supported RGB working space. That is, it's not something you'll find anywhere outside of LR unlike say sRGB, Adobe RGB (1998), ProPhoto etc. It isn't installed or used by any other Adobe app. It's kind of a strange beast too: ProPhoto RGB with the sRGB gamma TRC. We'd have to ping the original LR architect (Mark Hamburg) to find out why he decided to use this odd space solely for RGB values and Histogram but I suspect the main reason is that viewing a linear encoded Histogram would confuse most users (it would look 'odd'). I can't say why he didn't just use the ProPhoto 1.8 TRC instead but that's water under the bridge. This space is not ProPhoto RGB due to the gamma encoding and it isn't used for processing! Only the RGB values and Histogram.
    The actual color space used for processing has no name. It IS ProPhoto RGB primaries with a 1.0 TRC.
    I suspect that using Melissa RGB or a similar huge gamut is unnecessary in any preview mode because:
    1. Being so big, you'd want high bit (16-bit) data to reduce banding and that's overkill.
    2. There isn't and never will be a display capable of previewing ProPhoto gamut.
    3. There are a few displays that get close to Adobe RGB gamut, we may see that grow in the future. So might as well use that large gamut color space for previews. IOW, ProPhoto is way, way too big, sRGB is too small considering we have wide gamut displays.
    IF you have Photoshop, you can build Melissa RGB and save that out as a profile. Only useful if you want to play around but has no practical use. In Photoshop's color settings, select ProPhoto RGB as your working space. In the same menu, now select "Custom RGB". The dialog shows you the "DNA" of ProPhoto RGB (white point, chromaticity values, gamma). Change the gamma to 2.2, save as an ICC profile. You now have Melissa RGB. You don't get the true sRGB TRC but a simplified one, but close enough.

  • 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.

  • Safari and Preview have color space recognition bugs

    I found that both Safari and Preview have problems when viewing photos taken by a Canon DC. By default, the Canon cameras use sRGB for their digital still images. But Preview cannot recognize it and would report "ColorSync profile" as "-" in "Tools/Get Info". I guess that Generic RGB profile is applied in such a condition. If the file is opened by iPhoto or Photoshop, the color space information is recognized correctly. And if sRGB profile is manually assigned to the image using ColorSync Utility, Preview/Safari will give the same vivid color representation as iPhoto/PS do.
    The image below can be used to do the experiment.
    http://dpreview-img.fotki.com/gallery/canoneos5dsamples/originals/img9742.jpg
      Mac OS X (10.4.10)  

    See
    http://www.macintouch.com/readerreports/safari3/index.html
    http://www.macintouch.com/readerreports/safari/topic2922.html and http://www.macintouch.com/readerreports/macosx10_4tiger/topic3051.html#16may2007
    Also, search MIT for color. There's been a lot of traffic about profile calibration the past few weeks.

  • 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.

  • How to set PS for the most reliable image previews and how to make sure the color spaces are the same across plateforms

    I've been having an ongoing problem with some of my images changing color/luminance values after merging or flattening an image. This seems to most often happen if I use one of the filters (like crosshatch or notepaper, not sharpen or blur). I can make a copy using command/option/shift + E which most often will look exactly like what's on screen.
    Some people have suggested that it's to do with resolution, PS showing me a low resolution image but I don't think so because the histogram changes -- sometimes in a big way, but most often those spikes in the luminance levels are shaved off. Also, when I have the image open at 100% and effect a merge/flatten, the color changes.
    I'd like to know if there's a way to have PS show me one for one what I'm working on while I'm working on it, or if there is a way to control the color profiles when I'm saving. My best guess at this point is that there is a color profile mismatch going on somewhere. I just don't know where to look for it.
    Typically I work in 16 bit, so my color space is set to ProPhoto RGB; my camera is set to the Adobe color space;
    color management policies are set to preserve color profiles;
    conversion options --> intent is set to relative colorimetric.

    But it is calibrated. I use Xrite 1 and update it every month (on the first).
    The colors can be really off. Here's an example.
    https://flic.kr/p/r6A1Zd (what I want) https://flic.kr/p/qc5QTD (not what I want)
    Also, I can't see how the bit depth will have any effect since the change in color happens in PS when I merge or flatten. It's 8 bit through the editing and 8 bit when I flatten it.
    Have you any suggestions on what I can do on the computer side?

  • Asking the Bridge Team:  Bridge "working color space" setting when one does not have the Suite?

    Common sense tells me there is really no such thing as a
    "working color space" in Bridge, because
    Bridge is not an image editor, just a browser
    Therefore, this may turn out to be a purely academic question; but that doesn't keep my curiosity from forcing me to ask it anyway. ;)
    Is there a way to set the Bridge
    "color settings" when one does not have the suite?
    The only Adobe program I keep up to date is Photoshop, so I've never had the suite. My version of Photoshop is 11 (CS4) and I run updated
    (not upgraded) versions of Adobe Acrobat 7.x, Illustrator 10.x and InDesign 2.x. Consequently, the Synchronize color settings command is not available to me.
    It seems to me that Bridge is behaving like a proper color-managed browser (e.g. Firefox with color management enabled), in that it displays tagged image files correctly and assumes sRGB for untagged image files. This normally works fine.
    But what if I wanted Bridge to assume my
    Photoshop color working space for untagged images
    so that it behaves the same as Photoshop? I'm just curious, as I deal with a minuscule, practically negligible amount of untagged files.
    My reason for bringing it up now is that I don't recall this being explicitly mentioned in forum replies when users inquire about color settings in Bridge. A recent post regarding Version Cue in the Photoshop Macintosh forum got me thinking about this. Just wanting to make sure that I'm right in my assumption that
    there is really no such thing as a
    "working color space" in Bridge, because Bridge is not an image editor, just a browser.
    Thanks in advance.

    Hi Ramón,
    Thanks for sharing the outcome of your tests. However, I may have found a bug/exception to Bridge's colour management policy!
    It appears that CMYK EPS photoshop files are not colour managed in Adobe Bridge, even if they contain an embedded ICC profile.
    I've tried every combination in the EPS 'Save As' dialogue box, so it doesn't seem to be an issue with file encoding. Also, Bridge doesn't rely on the low-res preview that is held within the EPS itself.
    My guess is that Bridge is previewing the CMYK EPS with a Bridge-generated RGB image, but it's being displayed as monitor RGB (assigned) rather than colour managed (converted to monitor RGB). For most users the difference will be barely perceptible, but the problem became very noticeable when using Bridge to preview Newsprint CMYK images on a wide-gamut monitor (images that should have appeared muted really leapt off the screen!).
    How do I report this to the Colour Police at Adobe?!?

  • After Effects Ram Preview Drops Frames , Using Strangely Too Much Ram

    System Specs :
         CPU : Core i7 4770k
         Memory : 16 GB DDRIII
         Graphic Card : GTX 770 4GB RAM
         Storage : 256 GB SSD + 2 TB HDD
         OS : Windows 7 SP1
         Using After Effects CC 12.2.1.5
    NOTE : NOT ANY ADDITIONAL HARDWARE IS ATTACHED TO MY PC . NO SOUND RELATED EQUIPMENT NOR CAPTURE CARD NOR ANY THING ELSE
    Hi there
    As you Already Don't know I'm an After effects Specialist Using it for quite long time . There is an Ancient Problem with CS6 CC versions . I have a short Small size 1080p Video , about 8 MB , I drag it into project panel and then put it into timeline hence it creates a sequence . There are no Effects and nothing added to timeline , just a small simple video . The Strange Problem is when I click "0" for ram preview , The video starts playing and the green bar above timeline starts to fill . When Ram preview Finishes and plays the video from beginning I See there are several frames Between which are not being loaded to Ram ! The video plays RGB color bar instead of main video and when I check the Green bar above Timeline I see that those frames are being dropped and there is no Green bar above them !
    I have had this problem several times before but this time it is too important and the problem should be solved . What is obvious is that some frames are not being rendered or are being deleted after render !
    Another Strange problem is that when I open Task manager , It shows AE uses around 10 GB ! of RAM when I press "0" for Ram previewing this video !
    So there is a Logical explanation here , Somehow when I do ram preview this video it uses extra ordinary too much ram so AE is unable to load the full video (8 MB) into Ram and hence deletes some of frames .
    most of my videos have not this problem and use acceptable amount of ram .I've had this issue with some of my videos till now .
    Listen carefully : "This has nothing to do with AE preferences or low memory or plugins . because there is nothing wrong with any individual components of may hardware or software . I have far more than enough RAM for a 8MB video . My Memory has no hardware or software problem . I tested them and if there was any problem with memory or other hardware that should have affected other applications . I have the most recent AE version . I have the most Recent windows updates and drivers . I have a Clean virus free system , and as a computer engineer this strange AE problem is rarely caused by viruses , trust me . I have not any hardware instead of ones a normal PC has . I have not any problem with my whole entire system configuration because I have benchmarked my PC with several up to date softwares . I have tested my PC with almost any STRESS TESTING solutions available for really long period of time , 3 days by IDA64 . Not any driver conflict , dll missing , registry problem have been discovered , as I know perfectly how to solve them ."
    I asked some of my friend whom are expert in AE . I handed them my videos and Watched ALL OF THEM HAD THE SAME ISSUE ! So the problem isn't related to my Local PC . What i believe is that there is some malfunctioning or miss coded part in AE source code that decides to reserve such a huge strange amount of ram for such a tiny 8MB video . The point is that the AE works fine , no crash or any problem report . So the AE it Self decides to allocate such huge amount of ram and thinks it is correct ! So I think this is a work around that AE developers in adobe are using to bypass a problem or conflict ! by Using more amount of RAM . I think that there might be some miss understanding between the AE and my installed codec . I installed MEGA CODEC PACK on my PC to enable some new codec supports , and so are some of Windows default de/encoders changed to new ones . I think there shouldn't be any problem But there is something wrong between AE and de/encoder modules !
    Please any one with any suggestion , I really appreciate your advices .

    ###UPDATED###
    Well thank you guys for your patience ...
    as you considered I forgot to mention the codec itself and other stuff ...
    The video is in 1080p , 35 sec long , it is a green screen shot , this video is directly downloaded from YouTube and plays perfectly on all tested PCs . here are detailed info :
    Format                                   : MPEG-4
    Format profile                          : Base Media
    File size                                 : 8.55 MiB
    Duration                                 : 34s 993ms
    Overall bit rate mode                : Variable
    Overall bit rate                         : 2 050 Kbps
    VideoFormat                            : AVC
    Format/Info                              : Advanced Video Codec
    Format profile                           : [email protected]
    Codec ID                                 : avc1
    Codec ID/Info                            : Advanced Video Coding
    Bit rate                                    : 1 927 Kbps
    Width                                      : 1 920 pixels
    Height                                     : 1 080 pixels
    Frame rate mode                      : Constant
    Frame rate                               : 30.000 fps
    Color space                              : YUV
    Chroma subsampling                 : 4:2:0
    Bit depth                                  : 8 bits
    Scan type                                 : Progressive
    NOTICE : This video is just for testing the lighting and etc , and so the Sampling and other specs are not considered for broadcast .
    I think you hit the point ! Thats K-lite codec pack installed on every machine which the video is tested on ! The point is whats wrong with it ?! I have had never ever any problem with this codec pack !!!
    The deadly question : So what are the alternative ways to work with codecs that AE doesn't support ?! because installing codec looks simple and sufficient !

  • Colors in print preview not matching colors in soft proofing

    Hi There,
    Just wanted to print a new photo and realized that the colors in print preview do not match the colors in soft proofing. In both cases I selected the same icc profile and rendering method. The print colors matched the colors in print preview. I never had a problem so far. All new prints will be checked with soft proofing and adjusted when necessary. I never paid attention to the color rendition in print preview and all prints perfectly matched the colors from the soft proofing. I was surprised when my print came out of the printer and the colors weren't matching the soft proofing colors, but that of the print preview.
    I don't understand why Photoshop renders the colors differently in the first place. Please see attached screenshot for the difference in the blue/cyan colors.
    I would appreciate if anybody could point me in the right direction in what is causing this difference. I don't care if the print view colors will match the print, but I do care when soft proofing is not working.
    Thank you.
    Best regards,
    D.

    Here are some addtional details:
    PS 13.1.2
    Mac OS X 10.8.4
    12 GB Ram
    60 GB free disk space
    I printed the same photo from two other computers (MacBook and iMac) with different PS versions (CS4 and CS5). The prints turned out identical to the first one which matches the print preview color rendition on my main computer (MacPro) running CS6. Strangely the colors in print preview of CS5 on the iMac renders the colors identical to the soft proofing colors.

  • After Effects CC not saving ram preview when switching to different tab.

    Okay so just recently upgraded to CC and have been experiencing some ram preview problems.
    What happens is I will do a ram preview, watch it, then switch to a different window (Chrome, word, etc)
    and when I go back to AE and do a ram preview it does it all over again even though i haven't changed anything in the comp.
    I dont believe this was a problem in CS5.
    Any help on what settings i should check or if its a coding problem would be appreciated.
    Some specs:
    16gb ddr3 ram
    AMD FX-6300
    Radeon R7 250
    Everything Program/Cache is on SSD and the project file/video files are on Ext HDD

    Okay it's kind of fixed. (it isnt deleting it like it used too)
    i cleared my cache which was about 30gb, but I still had about 20gb of free space when i cleared it
    but Now I am getting some crashes and other stuff (colored bars, i already read thats getting fixed though)
    Do you think lowering the CPUs used to 3 will help?
    Ill update if it does it again when the cache is getting close to full

  • CS4 RAM preview slow

    Ever since I installed CS4 nothing will RAM preview over 8 frames a second.
    I am running on a Mac Pro 2x2.8 quad core Intel, 8gig Ram, files are on a Raid 5 XSAN storage with 31 terabytes of space...
    I've tried everything I can think of. I even imported in SD footage and tried playing back at 1/20th of the resolution. Tried unchecking color management, open gl previews, proxy renders into motion jpegs...nothing is working.
    Any suggestions?

    Hmmm..interesting.. thanks for the responses.
    Cameron - CS4 is laid out a little different in the "memory/multiprocessing" tab but yeah I've tweaked every possible setting in this with no luck.
    Mylenium - Doesn't feel right but XSAN may be the issue. Even when I run the project file and source files on the local machine I still get the same RAM playback problem. I run a MAC lab with 18 other stations like mine and I don't seem to have a problem from any of the other computers. The only real difference is that I have XSAN administrator installed on my machine while the others only have the client and I did not uninstall CS3 (for troubleshooting purposes). Perhaps the CS3 copy is interfering? I don't really want to toss this as every once in awhile I'll find that I need the older version laying around.
    I'll do some more troubleshooting ...thanks.

  • Multiprocessing color space render issue

    After installing the newest update of After Effects CC 2014 I am having troubles with my renders while using multiprocessing.
    The color space I'm working in is a linearized 32bpc sRGB IEC61966-2.1  When I render without multiprocessing turned on, the render turns out fine, but with it turned on the resulting render is way too bright, as though the gamma has been lifted way too high. I would really like to be able to use multi-processing, since it cuts my render times down to a fifth of what they would be otherwise. Any advice would be much appreciated.
    Also, just for fun I took my file back into After Effects CC (12.2)  and tried rendering it with multiprocessing without changing any settings and the render turned out just fine, making me think that this is specifically a CC 2014 problem.

    This is a bug that was introduced in After Effects CC 2014.1 (13.1). My apologies about this.
    First things first: to work around this bug you will need to disable multiprocessing in order to get a color-accurate render, via either RAM preview or via the Render Queue. Alternately, you can use multiprocessing but to get expected colors you must disable color management (set the project's working space to None), or if using Rec. 709 or sRGB you can leave the working space enabled and disable only the Linearize Working Space option.
    If you choose to leave multiprocessing enabled and disable color management, you can create the same color transform by applying the Color Profile Converter effect. For example, before rendering via the render queue, pre-compose your final comp and apply the effect to the pre-comp.
    We will evaluate a fix for this bug for a future update to After Effects CC 2014. An update is scheduled to release soon (this week or next), but a fix for this bug won't be included; this will have to wait for the next update.
    Under the hood, here's what happened to cause this bug:
    In After Effects CC 2014.1 (13.1), a color transform to Rec. 709 is automatically added to frames delivered via Dynamic Link when color management is enabled in the project. This is a new behavior in this version, which solved a problem with gamma and/or color shifts when sending frames to Premiere Pro or Adobe Media Encoder, which assume that all incoming Dynamic Link frames are Rec. 709.
    When multiprocessing is enabled in After Effects, it uses Dynamic Link to communicate with the subprocesses. In this case, After Effects knows what color profile is being used; no additional color correction is necessary.
    Combining these two behaviors we get this bug: an unnecessary color transform to Rec. 709 is being applied to frames rendered when multiprocessing is enabled. We failed to take the multiprocessing case into account when we added the new behavior.
    If your project's working space is already Rec. 709 or sRGB (which are functionally the same), you wouldn't notice a difference, since the additional color transform results in no change. Using any other profile would cause a color shift. Enabling the Linearize Working Space option with any profile will introduce a gamma shift.
    Again, my apologies about this bug.

  • RAM Preview Optimization

    I know there are a bunch of threads about Ram preview and how to make it render faster on the forum already.  However, I have read through a lot of them and tried most everything suggested that I could do or understand how to do and nothing has changed my current dilemma.
    I am using a 15" MacBook Pro (2012)  750GB HD, 16GB RAM
    OS X 10.9.5
    2.4GHz Intel Core i7
    After Effects CC 13.0.2.3
    I am working on a Lyric Video right now in After Effects with no outside footage, everything in the video has been created inside of AE or drawn in Illustrator or Photoshop and then brought into AE.
    I did everything suggested at this link for optimization in AE
    optimizing for performance: Adobe Premiere Pro and After Effects | After Effects region of interest
    The only thing I didn't do yet is get an external drive.  I used to have one that I put all my projects on for After Effect, Photoshop, Illustrator and even Logic Pro
    (My main use for My MacBook is Logic Pro/Recording Audio/Music Production.  But I have been using After Effects, Photoshop and Illustrator to make visual media to go along with the music I make)
    But I recently found out my 1TB "WD My Passport Studio" external drive was only 5200rpms,  So for this video I am making and the couple before it I have been only using the internal 750GB HD on my MacBook Pro (which has 5400rpm) to save my AE projects to.
    I know it's not the best case scenario but I had just upgraded my MacBook to 16GB RAM and I still have 440GB of available space on my 750GB HD so I'd figured I would see how much the RAM upgrade alone really did. Until it became necessary to get an external drive (and make sure I purchased the RIGHT one for me.
    ...With the 16GB RAM upgrade everything was much better, I can now have multiple applications such as After Effects, Illustrator and FireFox all running at the same time (I didn't have a chance of pulling that off before 16GB RAM).  Also what improved is while I'm playing videos using RAM Preview they usually do not lag anymore.  But the problem is now when I want to RAM preview it is taking forever to render, about 4-5seconds per frame, so trying to edit even a 15 second portion of my video can become seriously dull and really kill workflow.
    Like I said before I tried most optimization settings within After Effects that, that link I posted will suggest to do. But nothing has changed.  I'm basically posting this to see if anyone thinks I might have overlooked something within my After Effects or MacBookPro settings that will help my dilemma or if they think I just need an external drive to save all my After Effects projects onto. And if that is the problem, which external drive do they suggest?

    Once transform (Position, Scale, Rotation, Opacity) keyframes are set I seldom if ever touch them again in the process of building a scene. I already know they work so the only thing left is ink and color or Lights, Effects, Styling and final color grading. After the motion is good, and motion is the biggest part of Kinetic Typography projects is the motion, I seldom do a ram preview that is longer than 30 frames because I'm confident of the action in the scene.
    But that's the thing. Most of my animations are simply using motion such as Position, Scale, Rotation and Opacity. And that's all I have done to them so far...Yes some Text I use animation presets on, but most of my layers (whether they be Text, Shape, or Vector Image layers) only have motion key frames done to them and nothing else. I have not even messed with the lighting, color grading or shadows of the composition yet.  So that's why I am a bit frustrated that these previews are taking so long especially when my composition is not even at that complex of a point yet.
    What are your thoughts on the "fast previews" button? With "Adaptive Resolution" vs. "Draft" mode.  And why do you think my "Draft" mode is greyed out?  But all my other options (Adaptive Resolution, Fast Draft, Wire Frame, and Full Quality) are not?
    I ought to do a tutorial on KT or info graphic animations because they are very popular and most folks work way too hard at putting them together. I actually usually spend more time in Illustrator creating the starting graphics and editing the sound track than I spend animating. I create a huge Illustrator comp that has all of the elements in their final positions, import that as a comp, then resize the comp from the bottom left to HD, add a camera and camera dolly null and begin.
    If you did a tutorial from start to finish on how to make a kinetic typography video and optimize workflow as much as possible that would be AMAZING! and if you do definitely let me know! haha
    Here's a free animation preset for 3D layers that moves the layer into it's final position from a defined starting point and fades it in and out if the Setup check box is unchecked. Enjoy: 3DSlideshow.ffx
    I appreciate you giving me a free 3D animation preset but when I downloaded it from safari and clicked on it it just came up as code.  I tried to drag and drop it into my "effects & presets" panel in AE but that didn't work either.  I'm sure there is a specific folder I am supposed to save the the 3D animation file to, I just don't know what folder that is or where i can find it on my HD
    While I'm thinking about sound tracks, if you load a narration track into Premiere Pro and analyze the audio you can create markers that will show up on the audio track in AE that have the words as marker labels. This speeds up animating about 500% because you don't have to do any audio scrubbing to figure out the timing. Here's how to do that from Adobe TV:
    Accelerated Editing with Enhanced Speech Analysis in Premiere Pro CS5 | Adobe Story CS5 Feature Tour | Adobe TV
    Import the audio track into AE and yo'll be amazed.
    That sounds like an awesome way to save time! But I simply do not have Premiere Pro .  I have After Effects, Adobe Bridge and Media Encoder CC... and then Adobe Illustrator, Photoshop, InDesign CS6 and Adobe Acrobat XPro

Maybe you are looking for