From: "Timothy Sassoon" Received: from mail-pl0-f46.google.com ([209.85.160.46] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 7134211 for AE-List@media-motion.tv; Wed, 15 Aug 2018 20:26:18 +0200 Received: by mail-pl0-f46.google.com with SMTP id w14-v6so819108plp.6 for ; Wed, 15 Aug 2018 11:35:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version; bh=FHNKkemYbswdZu/qGhkAB3uA5X7MkpDM8FGh9o/2QNg=; b=QQqOfBdc2HxKiNQckHmKmo9tnmzYxlXxYJnmkAHKLrt9zfyckju4n2iHf9J+mieMCW n2g1kEU424GYk2apDxIBgTea8DHdFeTAxMWDdE1UyyNQphfQd0UIweRse9WSiyeVNFPU 3mK9wB5vivR937E9u7wB1uAldGsyXi/gqmUHQ8md2ElwT8cemZolIouBmMTEaL2OPabQ FHAcyVwVCyOxsMVD6niQj09PG1vv3rrKF3mg3mpTKWE+qF1YUqT5C5SSj7Frl1O3G4OY PD/OI+qGyuP7dP4Xj0QI9XVBGJ3zkfSRcyQejKnkWnUXaOe0jLL2D00ukD1uISTujfS5 EPYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=FHNKkemYbswdZu/qGhkAB3uA5X7MkpDM8FGh9o/2QNg=; b=rD+MRBZ4XP+39LugQi6bxxCnDRkkbrwCLXDWNQl7PB3yEngKusHhUtlw8IvVifBx/q Cr42wKdR02mveRZRCUWE39nisq22xUzwJZA/KbWOZLVI9gV9Z1D00m45W+0Epcozr6/z 9GYfpVyfsUYY1e67n6A+L5OfsHRkMGPEVWnw7Usg8K+ahlJiDMo+g+nmJP9RAx+XTeLm ZwiZbjRwNC27UcU2STAOm3n07TzjESJivkZOTeogLDQ6OdqFqIJDKdWltgvttoYlcEBf uukftYwKRrx/0CXLwerb9DVGVMPz0aZUXXMfrLJJpIYrn8nV10VpIt/i6w3BiKEyt/Of l8hw== X-Gm-Message-State: AOUpUlEkI8R1ApLwuMl0q+w+xQy6css8nhduL6K6f+cK2414lkc8mOpi ZeA3nCRq7tj3JtI2/5TI8Ti0MIsA X-Google-Smtp-Source: AA+uWPzY7ZvOtOgX5jx38U+TI+lTJBCZaxfiuLnTLhxlJpYc5IfWaBY04la8weyGf3oh+y0zFtF0VQ== X-Received: by 2002:a17:902:8601:: with SMTP id f1-v6mr25706674plo.61.1534358155162; Wed, 15 Aug 2018 11:35:55 -0700 (PDT) Return-Path: Received: from [2605:e000:1520:76c:88ce:f2b6:100::] ([2605:e000:1520:76c:38f1:15e2:36f1:194e]) by smtp.gmail.com with ESMTPSA id p64-v6sm42752631pfa.47.2018.08.15.11.35.54 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Aug 2018 11:35:54 -0700 (PDT) Date: Wed, 15 Aug 2018 11:35:26 -0700 To: After Effects Mail List Message-ID: <718bffe8-5ed2-4e36-af5d-540fdc76ed3c@Spark> In-Reply-To: References: Subject: Re: [AE] Urgent Cineon export questions X-Readdle-Message-ID: 718bffe8-5ed2-4e36-af5d-540fdc76ed3c@Spark MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="5b747289_4db127f8_271" --5b747289_4db127f8_271 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Stephen, Gamma is meant to match your display target, so that the files look the s= ame on any display. Black point should be 95, and the 90% white point to taste - 685 is spec,= but I usually went to 710 or so. Do you have over-whites you want to def= ine=3F Yes, you should be going Lin to log. BTW, check your settings by adding another AL with Cineon set to a interp= ret from log to Lin, display gamma whatever your display is set at, 95 an= d 685, as a print predictor. Tim Sassoon Sassoon =46ilm Design 350 Sunset Avenue Suite =231 Venice, CA 90291 W 310.664.9115 M 310.266.8630 On Aug 15, 2018, 11:27 AM -0700, Stephen van Vuuren , wrote: > It's been years since I delivered log cineon file and sleep deprived br= ain is not working. Client is asking for: > > =22 DPX (Cineon) format, 10 bit color, P3-D65 color space=22 > > I confirmed they want log not linear. My project is 16-bit, I've set it= to P3- D65 color space. Export will be CC 2014 (for speed). I assume Cin= eon export still does conversion linear to log since there is checkbox st= ill for =22logarithmic conversion=22 which I've check and set unit to 16-= bit. > > However, unclear on if anything else from =22full range preset=22 needs= to be adjusted e.g. ' current gamma is 1=22 - should that not be 2.4 (wh= ich was my calibration target)=3F > > Googling shows people doing all sorts of thing. > > Stephen > > -----Original Message----- > =46rom: After Effects Mail List > Sent: Wednesday, August 15, 2018 12:56 PM > To: After Effects Mail List > Subject: Re: =5BAE=5D Major Ae project corruption - and how I fixed it.= > > Importing troublesome projects has saved me many times. > > > On 8/15/2018 12:25 PM, Jim Curtis wrote: > > After working on this project for a week, my iStat menus are reportin= g that all 12 cores are at 100% when I just have Ae running and no comps = even open. Computer is correspondingly very sluggish and beach-bally (OSX= ). > > > > I deleted prefs and un- and re-installed Ae and it persisted. > > > > It only happens with one project that=E2=80=99s gotten pretty large -= lots of tracking and 3D camera solves. Keyframes galore. Each save takes= around 30 seconds. > > > > I think I fixed it. It was laborious: > > > > > > I have 10 comps in the corrupt Project. > > Select Comp 01, Reduce Project, Save As =E2=80=9CComp 01-100=E2=80=9D= (100 is for my > > CPUs pegging at 100%) Create New Project. > > Import Comp 01-100 - CPU levels go back to normal: what I expect for = an idling Ae Project. > > Save as =22Comp 01 only.=E2=80=9D > > > > Repeat process after opening original 10-com corrupt project for all = 10 Comps. > > > > I might import all 10 Comps into a master Project again, but only aft= er I start feeling lucky again. > > > > Posting this in case anybody else runs into a similar issue. > > > > > > > > Epilog / PS. This didn=E2=80=99t work on one Comp. So, I opened the C= omp. Select all Layers. Copy. Create New Project and Comp. Paste. Relink = footage. I got an error message telling my footage was tracked on a 360 x= 180 layer (=3F=3F=3F - Not true), but my tracking data was fine. I just = deleted the Mocha Pro plug-in that created the data, and all is well. Sav= e. > > > > > > > > . > > > > > > > > > > +---End of message---+ > > To unsubscribe send any message to > > > +---End of message---+ > To unsubscribe send any message to > > +---End of message---+ > To unsubscribe send any message to --5b747289_4db127f8_271 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Stephen,

Gamma is meant to match your display target, so that the files look the s= ame on any display.

Black point should be 95, and the 90% white point to taste - 685 is spec,= but I usually went to 710 or so. Do you have over-whites you want to def= ine=3F

Yes, you should be going Lin to log.

BTW, check your settings by adding another AL with Cineon set to a interp= ret from log to Lin, display gamma whatever your display is set at, 95 an= d 685, as a print predictor.

Tim Sassoon
Sassoon =46ilm Design
350 Sunset Avenue
Suite =231
Venice, CA 90291

W 310.664.9115
M 310.266.8630
On Aug 15, 2018, 11:27 AM -0700, St= ephen van Vuuren <AE-List=40media-motion.tv>, wrote:
It's been years since I delivered log cineo= n file and sleep deprived brain is not working. Client is asking for:

=22 DPX (Cineon) format, 10 bit color, P3-D65 color space=22

I confirmed they want log not linear. My project is 16-bit, I've set it t= o P3- D65 color space. Export will be CC 2014 (for speed). I assume Cineo= n export still does conversion linear to log since there is checkbox stil= l for =22logarithmic conversion=22 which I've check and set unit to 16-bi= t.

However, unclear on if anything else from =22full range preset=22 needs t= o be adjusted e.g. ' current gamma is 1=22 - should that not be 2.4 (whic= h was my calibration target)=3F

Googling shows people doing all sorts of thing.

Stephen

-----Original Message-----
=46rom: After Effects Mail List <AE-List=40media-motion.tv>
Sent: Wednesday, August 15, 2018 12:56 PM
To: After Effects Mail List <AE-List=40media-motion.tv>
Subject: Re: =5BAE=5D Major Ae project corruption - and how I fixed it.
Importing troublesome projects has saved me many times.


On 8/15/2018 12:25 PM, Jim Curtis wrote:
After working on this project for a week, m= y iStat menus are reporting that all 12 cores are at 100% when I just hav= e Ae running and no comps even open. Computer is correspondingly very slu= ggish and beach-bally (OSX).

I deleted prefs and un- and re-installed Ae and it persisted.

It only happens with one project that=E2=80=99s gotten pretty large - lot= s of tracking and 3D camera solves. Keyframes galore. Each save takes aro= und 30 seconds.

I think I fixed it. It was laborious:


I have 10 comps in the corrupt Project.
Select Comp 01, Reduce Project, Save As =E2=80=9CComp 01-100=E2=80=9D (10= 0 is for my
CPUs pegging at 100%) Create New Project.
Import Comp 01-100 - CPU levels go back to normal: what I expect for an i= dling Ae Project.
Save as =22Comp 01 only.=E2=80=9D

Repeat process after opening original 10-com corrupt project for all 10 C= omps.

I might import all 10 Comps into a master Project again, but only after I= start feeling lucky again.

Posting this in case anybody else runs into a similar issue.



Epilog / PS. This didn=E2=80=99t work on one Comp. So, I opened the Comp.= Select all Layers. Copy. Create New Project and Comp. Paste. Relink foot= age. I got an error message telling my footage was tracked on a 360 x 180= layer (=3F=3F=3F - Not true), but my tracking data was fine. I just dele= ted the Mocha Pro plug-in that created the data, and all is well. Save.


.




+---End of message---+
To unsubscribe send any message to <ae-list-off=40media-motion.tv><= br />


+---End of message---+
To unsubscribe send any message to <ae-list-off=40media-motion.tv><= br />
+---End of message---+
To unsubscribe send any message to <ae-list-off=40media-motion.tv><= br />
--5b747289_4db127f8_271--