From: "Roei Tzoref" Received: from mail-it0-f47.google.com ([209.85.214.47] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 6397284 for AE-List@media-motion.tv; Wed, 31 Jan 2018 03:22:15 +0100 Received: by mail-it0-f47.google.com with SMTP id b5so3214450itc.3 for ; Tue, 30 Jan 2018 18:25:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=EUWOIvuhtEibjLj4EOnY7/TLveUulDjwtFrQSK5TsIs=; b=ezEbKZs0ygtgR0mCsP4YGzm5/uqAdqFw7UZVtxqMJ3gvZAfWtU7I0hgsevzKQFAR8N iI9A1GtvnP5KhE4sA3+QnfMsmVIsDC8l2gTAtMlaWFRH1RBS5MbCV3WCrIHn30nieY5o tuHJlEUYQ1lbyyas5o4ap5VbAeks0ft2+NYbsq+oZaD27Ci7NMnz2WeLDlO4Clh3I3l4 979z6gpc9PjhV91IB5jY2UvKSsvbQwrxa1OJtVyatLA5KB4gfoC7MOdVO9yMf7VttutQ 8vp3lchTCOM8OOcrv4gt2vCBFlZYawIH4vGDW19hYe9tXBZ/vzvFc80Hu74A7lCUsF2s WtIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=EUWOIvuhtEibjLj4EOnY7/TLveUulDjwtFrQSK5TsIs=; b=UT7NnsJ5t1Z48fKtlcRRCNHt7xcLMWg2RREDAie43tdKydQMgUwL2ku70gHUPA0ed+ oYsCm2gBdYTONL+rr9uNG8at88gVWSC3QcN+CymNRsVbsSKjZIB4DnDqb8w8F/C1cG0u PryfOK4Jg7/cxMtnqGEpsVqdmzRymM4F0/b2lEvrkpD+Ub5xsUs+65bPRBaPqJALLso3 YKcwJAD9YsEzwB4rowX+lSatweKpsHl5aONeDS7Yuumf+erbc9axh/mcnKODa6HrCPPK RDX3MTAfWKnVKH3k8hgHLHoVKR+0S4PKGL5qdP8RLk7vnk84mU/JAJhelpOMfJ1BXvSM b9vQ== X-Gm-Message-State: AKwxytfcQeyynw5tG//zVZy2RN3mgqO7ONsA9ozmXJ+NWZRS177+IVAu oqR33ernHy/LMWSzHkfAkyfPpLiH0UQi6rpDLaob0w== X-Google-Smtp-Source: AH8x224TT/yCihIZDjt1T5ptbtmHqqQVoOyrDDWBXeKYdcavrxfJXE/fA3mp7kxBsKd5NsXOjJNMCHMBAOzjEvc3Zis= X-Received: by 10.36.36.151 with SMTP id f145mr836351ita.103.1517365512631; Tue, 30 Jan 2018 18:25:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.155.250 with HTTP; Tue, 30 Jan 2018 18:24:32 -0800 (PST) Date: Wed, 31 Jan 2018 04:24:32 +0200 Message-ID: Subject: Greenscreen s-log2 workflow queries for the color spaced challenged To: After Effects Mail List Content-Type: multipart/alternative; boundary="001a1147b3e25ff9fb0564093095" --001a1147b3e25ff9fb0564093095 Content-Type: text/plain; charset="UTF-8" hey y'all. so I got a footage to key and roto. I have been told it's 444 so was pleased. it was an mxf file, imported to Ae and saw it was stated as RAW. I saw the color and contrast was good and immediately got to work. this is how it looked in Ae: https://imgur.com/a/ZkcQ0 on 200% it looked a bit funky but I just ignored it (WRONG!) and carried on. https://imgur.com/a/j7eyG about 80% into the project it started to bug me so I asked the cameraman and indeed something was off. so he told me I should download RAW viewer and export from there. so imported the file to the software, and now I was faced to decide which input parameters to enter. I obviously wanted the exact same color profile I had in Ae but how could I know which one is it. I was told the footage was shot in Sony f5, slog2, raw. but I already keyed the footage on what appears to be some sort of rec709 color space. so I entered those in the Raw app and exported a dpx 444 (the only option for 444) with these settings: https://imgur.com/a/wgewj and now it's about 90% what it was before, some keying had to be readjusted but I am in the clear for finishing the project now I know this is a mess of a workflow my questions is: 1. is there a reason the footage came distorted like this from the camera and I had to use the RAW viewer software to reexport it? 2. what was the color profile on this RAW footage? is there a way to tell? how can I know to match it if I get this type of scenario again? 3. what would be the right way to work? export from RAW viewere as s-log2, then in Ae convert to linear and key? I have looking into http://opencolorio.org/ but after converting from slog2 to ACES, the image looks too contrasty for keying. https://imgur.com/a/K0YYZ thanks --001a1147b3e25ff9fb0564093095 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
hey y'all.=C2=A0

so I got a footage= to key and roto. I have been told it's 444=C2=A0 so was pleased.
=

it was an mxf file, imported to Ae and saw it was state= d as RAW. I saw the color and contrast was good and immediately got to work= .

this is how it looked in Ae:
=
on 200% it looked a bit funky but I just ignored it (WRONG!)= and carried on.


about 80% i= nto the project it started to bug me so I asked the cameraman and indeed so= mething was off. so he told me I should download RAW viewer and export from= there. so imported the file to the software, and now I was faced to decide= which input parameters to enter. I obviously wanted the exact same color p= rofile I had in Ae but how could I know which one is it.=C2=A0 I was told t= he footage was shot in=C2=A0Sony f5, slog2, raw. but I already keyed the fo= otage on what appears to be some sort of rec709 color space. so I entered t= hose in the Raw app and exported a dpx 444 (the only option for 444) with t= hese settings:

and now it's about 90% w= hat it was before, some keying had to be readjusted but I am in the clear f= or finishing the project

now I know this is a mess= of a workflow my questions is:
1. is there a reason the footage = came distorted like this from the camera and I had to use the RAW viewer so= ftware to reexport it?
2. what was the color profile on this RAW = footage? is there a way to tell? how can I know to match it if I get this t= ype of scenario again?
3. what would be the right way to work? ex= port from RAW viewere as s-log2, then in Ae convert to linear and key? I ha= ve looking into http://opencolorio.org/= but after converting from slog2 to ACES, the image looks too contrasty= for keying.=C2=A0

thanks


--001a1147b3e25ff9fb0564093095--