Re: Can't export to AME from AE

jmottle · ‎Aug 07, 2019

Posting here for the benefit of anyone else who runs into this. The issue was a recent change Adobe made in AE and how they handle scripting. The issue was a simple checkbox that needed to be enabled. Under Preferences -> Scripting & Expressions - check the box "allow scripts to write files and access network"

jmottle · ‎Aug 06, 2019

Thanks for the recommendation on RG. I'll take a closer look. However the issue is not the layers, effects etc. I can't even get these comps to load into AME. Even if they do, they won't even start rendering. There are no errors, just nothing happens.

jmottle · ‎Aug 05, 2019

I'm using AE 16.1.2 (Build 55) and AME 13.1.3 (Build 45) on a Late 2013 Mac Pro (32 GB RAM with 6 core 3.5GHz Intel Xeon E5). I am trying to export my comp to AME and 90% of the time it does nothing. Nothing shows up. I have tried the following: 1) reinstalling both AE and AME 2) Export direct to AME from File -> Export 3) Manually trying to open a comp from within AME 4) Using File -> Export to Render Queue and then Queue in AME About 10% of the time the comp will be added to AME, but when I press start it just hang trying to read the XMP file. I spent 3 hours on a live chat with Adobe where they got onto my machine and could still not figure out how to fix it. They re-installed everything again, wiped the adobe folders, made me create a new user login, messed with folder permissions, and nothing works. They have given up and escalated, but that process is so ridiculously flawed I am still waiting for a call back. I am able to render without issue inside of the AE Queue and have been able to render these same files in previous years on the exact same machine. The only difference is the version of these softwares. Meanwhile I have a deadline for a live event and am stuck rendering 1-2 hour comps one at a time. Of course I can't work on anything else in the process. Any ideas?

jmottle · ‎Mar 24, 2019

Well, I'm not sure I agree with this. Here is why. We took an image authored in an sRGB color space with an sRGB profile embedded. If we calibrate and profile the display, thus overriding the default sRGB setting in Windows CM and view it in the default Windows viewer (not color managed) it is very saturated. This is expected and indicates the color are being interpreted in the native gamut of the display. Being a native WG display this also is expected. If we open it in Photoshop, with CM turned on and set up correctly, the image as predicted looks as it should. However, this is where the confusion begins. We leave the calibration intact (D65/2.2 etc.) that was done with an i1 Pro, but default the Windows CM settings back to sRGB (rather than using the generated display profile). That image now looks correct both in the Windows viewer AND in PS. To me that suggests that for a Windows viewer, unable to read an embedded profile, and display the image correctly, is somehow clamping the gamut to sRGB, not just passing data through.

jmottle · ‎Mar 24, 2019

Windows OS (and most Windows apps) are either passing the RGB numbers straight to the monitor unaltered - or Assigning/Assuming sRGB then Converting to the monitor profile I'm a Mac user and don't have a PC, but because I'm trying to assist some colleagues in the industry, trying to get to the bottom of this for them. When he sets everything to the Windows default, it "seems" to be altering the LUTs so that the screen physically won't output anything more than sRGB, even though its a wide gamut display. I can't tell for sure as I am not there in front on the display and have only seen screenshot comparisons, but if that is true, it would appear to work the same as setting the gamut on the physical display (not all displays have this option, especially the higher end ones) It seems to be something found more on cheaper and low end WG displays.

jmottle · ‎Mar 24, 2019

Well all of that was the lead up to the real question at the bottom that so far has not been answered. some people I know are calibrating their displays, but abandoning the use of the generated display profile and instead leaving windows in its default sRGB color management settings. As I'm a Mac user and don't run into this, I was curious if doing this has the same effect as clamping the gamut at the hardware? Is this just a software version of this? Doing this basically throws out all color management, but basically converts everything to the same color space (sRGB) and then the outputs regardless of the application match. I'm unclear what window's CM system is actually doing if left unaltered vs actually setting up proper CM. I agree that M$ has no clue about color management and like most things tries to adopt their own standards, which is why if someone does chose to use it with the default settings (https://www.thewindowsclub.com/reset-display-color-settings-to-default?fbclid=IwAR0-AYIatdPtqOuNz7fyHyHpVG_nxe98jPZZA_4-… I am unclear from a technical perspective what Windows is doing and what impacts it has on the display output.

jmottle · ‎Mar 24, 2019

don't use applications without color management. Just don't. That's nice in theory, but 99% of the applications used in the 3D industry are not color managed and likely never will be for the foreseeable future due to legacy code that makes up the ones many use. The ones that do have it are only partially implemented. I've been lobbying for much of my 23 year career and it's simply not technically possible without a complete rewrite of major underlying systems.

jmottle · ‎Mar 24, 2019

With most higher end displays being wide gamut, if you work in almost any 3D apps, the output from the framebuffers are generally not color managed. Thus, color decisions you make are being done in the native gamut of the display, even if it's calibrated and profiled. I've only ever come up with a few options to deal with this: 1) Make larger color decisions in the non color managed environment and once you import into PS, you have to do some conversions and assignments of profiles to get it to match, but it's not an ideal solution. 2) If you have higher end displays, force your display into an sRGB or aRGB color space and then calibrate and profile. That way the framebuffer more closely matches a standard device independent color space and you can still use color management. 3) Don't buy high gamut displays. Which brings me to my question. Aside from has anyone else figured out a better workflow, some people I know are calibrating their displays, but abandoning the use of the generated display profile and instead leaving windows in its default sRGB color management settings. As I'm a Mac user and don't run into this, I was curious if doing this has the same effect as clamping the gamut at the hardware? Is this just a software version of this? Doing this basically throws out all color management, but basically converts everything to the same color space (sRGB) and then the outputs regardless of the application match. I'm unclear what window's CM system is actually doing if left unaltered vs actually setting up proper CM. Cheers, Jeff

jmottle · ‎Nov 23, 2007

I am putting together an image gallery but am not quite sure how to approach this using Dreamweaver. The main gallery page will simply connect to all of the images in the gallery and allow you to page through them. When you click on an image and go to the detail page I want the detail page to a larger version of the clicked image. So far easy. HOWEVER, I want that detail page to allow the user to page through all of the other images beloning to that same user. So when you arrive on the detail page, you are really viewing a recordset of all images by a particular artist and you are pushed directly to the image on the first master page. I hope that makes sense. How would I go about doing this? Cheers, Jeff

jmottle

jmottle

Activity

Re: Can't export to AME from AE

Re: Can't export to AME from AE

Can't export to AME from AE

Re: Working with Non Color Managed graphics apps b...

Re: Working with Non Color Managed graphics apps b...

Re: Working with Non Color Managed graphics apps b...

Re: Working with Non Color Managed graphics apps b...

Working with Non Color Managed graphics apps befor...

Image Gallery Paging