Parasol - User contributions [en]

Anfrage/Board

2018-09-27T08:12:17Z

Daul Preisen:

=Grundsätzlich=
Boards bzw. Neugeschäfts-Anfragen sind der Erste und damit wichtigste Eindruck den wir bei einem potentiellen Auftraggeber hinterlassen. Das Ziel ist, diesen Prozess so zu optimieren, das dieser erste Kontakt erstklassig gehandhabt wird und einen sehr guten Eindruck hinterlässt. Außerdem sollte das Kernteam von neuen Anfragen wissen, um intern und extern kompetent kommunizieren, und mit eigenem Wissen und Erfahrungen unterstützen zu können. Aber: E-Mails ersetzen nicht die persönliche Kommunikation.

==Rückmeldung==
'''Spätestens 4 Stunden nach der Anfrage sollte der Kunde von uns zurück hören''', das wir uns für die Anfrage bedanken, darüber informiert werden das wir an der Anfrage arbeiten, wer sein Ansprechpartner und was die nächsten Schritte sind. Bei Anfragen die Abends eingehen, entsprechend spätestens am nächsten Arbeitstag (Bsp. Eingang 16:30m, Rückmeldung bis spätestens 11:30). 

=How To=
Anfragen erreichen uns auf vielfältige Arten. Per Telefon, persönlich, eMail, manchmal per Post. Jede Anfrage wird per eMail an 
 
[mailto:boards@parasol-island.com?cc=geschaeftsleitung@parasol-island.com,bart.hendrikx@parasol-island.com&subject=Yeah%21%20A%20Board%20has%20come%20in%2E%20Let%27s%20win%20it!&body=Gibt%20es%20weiterfuehrende%20Informationen%2C%20Insbesondere%20Budget%20und%20Timing%3F%0A%0A%0A boards@parasol-island.com] 
 
gesendet und erreichen so das Kernteam. Bei Bedarf wird hier die Aufgabe evaluiert und eine zentrale Entscheidung wie die Anfrage weiter gehandhabt wird. Sofern es bereits weiterführende Informationen (Insbesondere Budget und Timing) gibt, so sollten diese in der Boards-eMail hinterlegt sein.

Auch über Nachrichten gewonnener und verlorener Projekte freut sich der Mailverteiler!

=Email Vorlage für den Mailverteiler=

 Zum weiterleiten der Emails hier eine Vorlage mit der jede Email an den Boards Verteiler anfangen soll.

 Projektname: Name in der Agentursoftware
 Producer: Name des aktuell verantwortlichen Producers.
 Status: Hier den aktuellen Status einfügen und bei erneutem senden aktuell halten.
 Shotgun: Link zum Shotgun Projekt.
 interne Info: Kurze Info über die nächsten Schritte bzw. was besprochen wurde.
 interne todo´s: Kurz und knapp was zu tun ist. Z.B. Anim Team soll Styleframes machen.
 Client Briefing: Briefing vom Kunden.

 Anbei noch eine Version ohne Erklärung zum kopieren in die Email.

 '''Projektname:'''
 Producer:
 '''Status:'''
 Shotgun:
 interne Info:
 '''interne todo´s:'''
 Client Briefing:

 Bitte benutzt diese Vorlage für eure Emails, sobald genug Leute damit angefangen haben wird es zur Routine.

ACES

2018-01-12T15:23:53Z

Daul Preisen: /* Workflow best case */

[[Animation Department]]

ACHTUNG WIP Seite, also echt WIP!

 In this document you will find all necessary information regarding the ACES color management workflows.
 Please read all information at least twice and follow the instructions carefully.
 If there are any questions concerning the documentation please contact Paul Dreisen for further information.

==Introduction==
 The Academy Color Encoding System (ACES) is a color image encoding system created by hundreds of industry professionals under the auspices of the Academy of Motion Picture Arts and Sciences. ACES allows for a fully encompassing color accurate workflow, with "seamless interchange of high quality motion picture images regardless of source"
 To make things short, it handles colors pretty well.
 From the technical side ACES is a huge color space which can handle very other color space without loosing any information.
 Do you want to know more?
 https://en.wikipedia.org/wiki/Academy_Color_Encoding_System
 http://opencolorio.org/
==ACES vs OCIO what?==
 Wtf is ACES and why do I find so many information about OCIO?
 ACES is the color space.
 OCIO is a set of tools designed to manage everything ACES is able to do with colors.
 If possible we are going to use one OCIO config for all our DCC tools.
 At the moment not every tool supports the use of a custom OCIO config!

==Important info on using ACES==
 
* Projects done in ACES can be easily saved into sRGB or Rec 709 color space.
* You will need to convert all used input files with the right mode into ACES, otherwise they will produce wrong colors.
* In case we do only a part time ACES workflow it is possible to write out into log files with the same look as the camera raw material (Nuke setup)
* Working with ACES means paying extra attention to color and color workflow rules!
* If a 3D rendered file is done using ACES it cannot be used with a sRGB comp workflow!
* In a perfect world we would preconvert all plates into ACES before we start working on the in VFX.
* You can find our OCIO configs here: X:\Pipeline\_Globals\LUTs

 

==Supported DCC tools and how they support ACES==
 Before we go into details here is a list of all our inhouse DCC´s we use to create our images and films.
 
{| class="wikitable"
|-
! Software !! ACES !! OCIO !! Plugin
|-
| Maya || 1.03 || Yes || included
|-
| Nuke || 1.03 || Yes || included
|-
| Fusion || no || Yes || included
|-
| AFX || Yes || Plugin || Yes
|-
| Flame || 1.0 || no || included
|-
| Resolve || 1.0 || no || included
|-
| Houdini || tba || tba || tba
|-
| Cinema || tba || tba || tba
|-
| Photoshop || no || ICC profile || no
|-
| Premiere || tba || tba || tba
|}
 As you can see most of our tools support the new ACES workflow.
 As there are severy things you need to take care of the setup process for each DCC will be explained a little lower on this page.

==Workflow best case==

 
* everything is running as planned ^^ (Never gonna happend but here is how it should be)
* To make our life easier we will only use ACES in parts of the Pipeline where it will help us the most.

# Editing, Flame and Davinci will stay in our typical REC709 world and we do not need to use OCIO or ACES.
# Backplates which are needed for adding effects or paintjobs going thru Nuke need to be exported as unclamped REC709 encoded EXR files (float 16/32bit)
# In Nuke we will then transform them into linear ACES files to comp them with our 3D files.
# Comp renderings need to be converted back into the same colorspace as they have been delivered. (90% of the time this will be REC709).
# At the end of the project we render out a sRGB/Rec709 converted Master for sendout and the client.
 

==File Formate and conversions==

 
* ACES supports every file format we know, but to make our life a little bit easier we should limit our selves to use only a few formats.
* Not every format can or should handle every ACES colorspace.
# There are the usual 8 bit formats which are there to store sRGB image data
* for example: jpg, png, tga, tif8, gif
* all these files need to be converted into linear files using the utility sRGB - texture conversion
 Log: DPX
 Linear: EXR

 

==Maya setup==

Setup your Maya like this.

[[File:MayaOcioSetup.JPG|1024x1024px]]

To avoid errors in RedShift you should setup your render settings like this.

[[File:MayaRedShiftGammaSettings.jpg|400px]]
 

==Nuke Setup==
 Nuke is best suited for a OCIO color management workflow. To setup Nuke in the right way you will need to do the following steps.
 [[File:Nuke_Setup.jpg|600px]]
* Press the hotkey "s" to load up your project settings
* select the "color" tab and switch from nuke to OCIO in the color management field.
* select "custom" again and enter this config location into the folder: x:/Pipeline/_Globals/LUTs/OCIO/aces_1.0.3/config.
* now everything is ready for working with ACES in Nuke

==Flame Setup==
 
==Resolve Setup==
 
==Digital Fusion Setup==
 
==After FX Setup==
 
 Since AFX version 2018 the Adobe guys did a first implementation to support ACES.
 You can switch it on when you click on the color mode change option in the "Projects" (See image for detailed info)
 In After Effects you can load the plugin "OpenColorIO" and put it onto an adjustment layer ontop of your comp or footage.
 Inside of the plugin window you will need to load our OCIO config file from here: X:\Pipeline\_Globals\LUTs\OCIO\aces_1.0.3
 [[File:AFX_Setup.jpg|800px]]
# Here you can load the OCIO file
# Next you can choose the source color space from your material or comp. Alexa log or ACEScg for example.
# At last you can choose the output color space which is normally sRGB(ACES)

 The setup in AFX is a bit tricky and complex, but at least you can work with ACEScg linear images if you get them from our 3D guys.

==Premiere Setup==
 Same as in AFX but at the moment the plugin is too slow to use it for editing :-(

==Substance Painter Setup==
 Substance Painter is not able to save/bake textures into the selected LUT Format, it is just possible to display it in the viewport of Painter.

The maps exported from SD and SP are in sRGB or gamma-encoded space. They are not exported as linear.

EXR Textures are also saved as sRGB not as Linear. <<< Pretty shitty!!
 
 How to activate?
 
 1. You need to import/copy the LUT Profile to Substance Painter.
 2. LUTS are located here. X:\Pipeline\_Globals\LUTs\OCIO\forSubstance 3. Drag/Drop the LUTS to your Color Profiles shelf in Substance Painter.
 [[File:SubstancePainter_Setup2.JPG|1800x1800px]]
 

4. Activate and select your desired Color Profile [[File:SubstancePainter_Setup1.JPG|724x724px]]

ACES

2018-01-12T15:16:51Z

Daul Preisen: /* After FX Setup */

[[Animation Department]]

ACHTUNG WIP Seite, also echt WIP!

 In this document you will find all necessary information regarding the ACES color management workflows.
 Please read all information at least twice and follow the instructions carefully.
 If there are any questions concerning the documentation please contact Paul Dreisen for further information.

==Introduction==
 The Academy Color Encoding System (ACES) is a color image encoding system created by hundreds of industry professionals under the auspices of the Academy of Motion Picture Arts and Sciences. ACES allows for a fully encompassing color accurate workflow, with "seamless interchange of high quality motion picture images regardless of source"
 To make things short, it handles colors pretty well.
 From the technical side ACES is a huge color space which can handle very other color space without loosing any information.
 Do you want to know more?
 https://en.wikipedia.org/wiki/Academy_Color_Encoding_System
 http://opencolorio.org/
==ACES vs OCIO what?==
 Wtf is ACES and why do I find so many information about OCIO?
 ACES is the color space.
 OCIO is a set of tools designed to manage everything ACES is able to do with colors.
 If possible we are going to use one OCIO config for all our DCC tools.
 At the moment not every tool supports the use of a custom OCIO config!

==Important info on using ACES==
 
* Projects done in ACES can be easily saved into sRGB or Rec 709 color space.
* You will need to convert all used input files with the right mode into ACES, otherwise they will produce wrong colors.
* In case we do only a part time ACES workflow it is possible to write out into log files with the same look as the camera raw material (Nuke setup)
* Working with ACES means paying extra attention to color and color workflow rules!
* If a 3D rendered file is done using ACES it cannot be used with a sRGB comp workflow!
* In a perfect world we would preconvert all plates into ACES before we start working on the in VFX.
* You can find our OCIO configs here: X:\Pipeline\_Globals\LUTs

 

==Supported DCC tools and how they support ACES==
 Before we go into details here is a list of all our inhouse DCC´s we use to create our images and films.
 
{| class="wikitable"
|-
! Software !! ACES !! OCIO !! Plugin
|-
| Maya || 1.03 || Yes || included
|-
| Nuke || 1.03 || Yes || included
|-
| Fusion || no || Yes || included
|-
| AFX || Yes || Plugin || Yes
|-
| Flame || 1.0 || no || included
|-
| Resolve || 1.0 || no || included
|-
| Houdini || tba || tba || tba
|-
| Cinema || tba || tba || tba
|-
| Photoshop || no || ICC profile || no
|-
| Premiere || tba || tba || tba
|}
 As you can see most of our tools support the new ACES workflow.
 As there are severy things you need to take care of the setup process for each DCC will be explained a little lower on this page.

==Workflow best case==

 
* everything is running as planned ^^ (Never gonna happend but here is how it should be)
* For editing most of the time we do use Premiere which does not support a ACES workflow at the moment, by the time it does... We will need to do a preconversion of all takes into ACES on set or before we go into editing.

# After editing we take all needed source materials and convert them via Resolve into linear ACES EXR files.
# In the next step we render all takes in the edit and create shots in Shotgun for each required VFX shot (backplates need to be sorted into the right folder structure).
# The linear ACES files are then conformed in Flame and Resolve for the next steps (grading and conforming)
# In the VFX pipeline we use those linear files to do all VFX work. For viewing the output we use the sRGB or Rec709 conversion.
# 3D and comp renderings are rendered out only into linear ACES.exr files. Only the latestJPG saver will have a preview conversion into sRGB or Rec709.
# At the end of the project we render out a sRGB/Rec709 converted Master for sendout and the client. Besides that we render a linear ACES Master for our archive.
 
 
 
# To sum it up. We try to keep all files in linear space during the whole project and not bake in any sRGB or whatever converion to it.

==File Formate and conversions==

 
* ACES supports every file format we know, but to make our life a little bit easier we should limit our selves to use only a few formats.
* Not every format can or should handle every ACES colorspace.
# There are the usual 8 bit formats which are there to store sRGB image data
* for example: jpg, png, tga, tif8, gif
* all these files need to be converted into linear files using the utility sRGB - texture conversion
 Log: DPX
 Linear: EXR

 

==Maya setup==

Setup your Maya like this.

[[File:MayaOcioSetup.JPG|1024x1024px]]

To avoid errors in RedShift you should setup your render settings like this.

[[File:MayaRedShiftGammaSettings.jpg|400px]]
 

==Nuke Setup==
 Nuke is best suited for a OCIO color management workflow. To setup Nuke in the right way you will need to do the following steps.
 [[File:Nuke_Setup.jpg|600px]]
* Press the hotkey "s" to load up your project settings
* select the "color" tab and switch from nuke to OCIO in the color management field.
* select "custom" again and enter this config location into the folder: x:/Pipeline/_Globals/LUTs/OCIO/aces_1.0.3/config.
* now everything is ready for working with ACES in Nuke

==Flame Setup==
 
==Resolve Setup==
 
==Digital Fusion Setup==
 
==After FX Setup==
 
 Since AFX version 2018 the Adobe guys did a first implementation to support ACES.
 You can switch it on when you click on the color mode change option in the "Projects" (See image for detailed info)
 In After Effects you can load the plugin "OpenColorIO" and put it onto an adjustment layer ontop of your comp or footage.
 Inside of the plugin window you will need to load our OCIO config file from here: X:\Pipeline\_Globals\LUTs\OCIO\aces_1.0.3
 [[File:AFX_Setup.jpg|800px]]
# Here you can load the OCIO file
# Next you can choose the source color space from your material or comp. Alexa log or ACEScg for example.
# At last you can choose the output color space which is normally sRGB(ACES)

 The setup in AFX is a bit tricky and complex, but at least you can work with ACEScg linear images if you get them from our 3D guys.

==Premiere Setup==
 Same as in AFX but at the moment the plugin is too slow to use it for editing :-(

==Substance Painter Setup==
 Substance Painter is not able to save/bake textures into the selected LUT Format, it is just possible to display it in the viewport of Painter.

The maps exported from SD and SP are in sRGB or gamma-encoded space. They are not exported as linear.

EXR Textures are also saved as sRGB not as Linear. <<< Pretty shitty!!
 
 How to activate?
 
 1. You need to import/copy the LUT Profile to Substance Painter.
 2. LUTS are located here. X:\Pipeline\_Globals\LUTs\OCIO\forSubstance 3. Drag/Drop the LUTS to your Color Profiles shelf in Substance Painter.
 [[File:SubstancePainter_Setup2.JPG|1800x1800px]]
 

4. Activate and select your desired Color Profile [[File:SubstancePainter_Setup1.JPG|724x724px]]

ACES

2018-01-12T15:10:03Z

Daul Preisen:

[[Animation Department]]

ACHTUNG WIP Seite, also echt WIP!

 In this document you will find all necessary information regarding the ACES color management workflows.
 Please read all information at least twice and follow the instructions carefully.
 If there are any questions concerning the documentation please contact Paul Dreisen for further information.

==Introduction==
 The Academy Color Encoding System (ACES) is a color image encoding system created by hundreds of industry professionals under the auspices of the Academy of Motion Picture Arts and Sciences. ACES allows for a fully encompassing color accurate workflow, with "seamless interchange of high quality motion picture images regardless of source"
 To make things short, it handles colors pretty well.
 From the technical side ACES is a huge color space which can handle very other color space without loosing any information.
 Do you want to know more?
 https://en.wikipedia.org/wiki/Academy_Color_Encoding_System
 http://opencolorio.org/
==ACES vs OCIO what?==
 Wtf is ACES and why do I find so many information about OCIO?
 ACES is the color space.
 OCIO is a set of tools designed to manage everything ACES is able to do with colors.
 If possible we are going to use one OCIO config for all our DCC tools.
 At the moment not every tool supports the use of a custom OCIO config!

==Important info on using ACES==
 
* Projects done in ACES can be easily saved into sRGB or Rec 709 color space.
* You will need to convert all used input files with the right mode into ACES, otherwise they will produce wrong colors.
* In case we do only a part time ACES workflow it is possible to write out into log files with the same look as the camera raw material (Nuke setup)
* Working with ACES means paying extra attention to color and color workflow rules!
* If a 3D rendered file is done using ACES it cannot be used with a sRGB comp workflow!
* In a perfect world we would preconvert all plates into ACES before we start working on the in VFX.
* You can find our OCIO configs here: X:\Pipeline\_Globals\LUTs

 

==Supported DCC tools and how they support ACES==
 Before we go into details here is a list of all our inhouse DCC´s we use to create our images and films.
 
{| class="wikitable"
|-
! Software !! ACES !! OCIO !! Plugin
|-
| Maya || 1.03 || Yes || included
|-
| Nuke || 1.03 || Yes || included
|-
| Fusion || no || Yes || included
|-
| AFX || Yes || Plugin || Yes
|-
| Flame || 1.0 || no || included
|-
| Resolve || 1.0 || no || included
|-
| Houdini || tba || tba || tba
|-
| Cinema || tba || tba || tba
|-
| Photoshop || no || ICC profile || no
|-
| Premiere || tba || tba || tba
|}
 As you can see most of our tools support the new ACES workflow.
 As there are severy things you need to take care of the setup process for each DCC will be explained a little lower on this page.

==Workflow best case==

 
* everything is running as planned ^^ (Never gonna happend but here is how it should be)
* For editing most of the time we do use Premiere which does not support a ACES workflow at the moment, by the time it does... We will need to do a preconversion of all takes into ACES on set or before we go into editing.

# After editing we take all needed source materials and convert them via Resolve into linear ACES EXR files.
# In the next step we render all takes in the edit and create shots in Shotgun for each required VFX shot (backplates need to be sorted into the right folder structure).
# The linear ACES files are then conformed in Flame and Resolve for the next steps (grading and conforming)
# In the VFX pipeline we use those linear files to do all VFX work. For viewing the output we use the sRGB or Rec709 conversion.
# 3D and comp renderings are rendered out only into linear ACES.exr files. Only the latestJPG saver will have a preview conversion into sRGB or Rec709.
# At the end of the project we render out a sRGB/Rec709 converted Master for sendout and the client. Besides that we render a linear ACES Master for our archive.
 
 
 
# To sum it up. We try to keep all files in linear space during the whole project and not bake in any sRGB or whatever converion to it.

==File Formate and conversions==

 
* ACES supports every file format we know, but to make our life a little bit easier we should limit our selves to use only a few formats.
* Not every format can or should handle every ACES colorspace.
# There are the usual 8 bit formats which are there to store sRGB image data
* for example: jpg, png, tga, tif8, gif
* all these files need to be converted into linear files using the utility sRGB - texture conversion
 Log: DPX
 Linear: EXR

 

==Maya setup==

Setup your Maya like this.

[[File:MayaOcioSetup.JPG|1024x1024px]]

To avoid errors in RedShift you should setup your render settings like this.

[[File:MayaRedShiftGammaSettings.jpg|400px]]
 

==Nuke Setup==
 Nuke is best suited for a OCIO color management workflow. To setup Nuke in the right way you will need to do the following steps.
 [[File:Nuke_Setup.jpg|600px]]
* Press the hotkey "s" to load up your project settings
* select the "color" tab and switch from nuke to OCIO in the color management field.
* select "custom" again and enter this config location into the folder: x:/Pipeline/_Globals/LUTs/OCIO/aces_1.0.3/config.
* now everything is ready for working with ACES in Nuke

==Flame Setup==
 
==Resolve Setup==
 
==Digital Fusion Setup==
 
==After FX Setup==
 
 In After Effects you can load the plugin "OpenColorIO" and put it onto an adjustment layer ontop of your comp or footage.
 Inside of the plugin window you will need to load our OCIO config file from here: X:\Pipeline\_Globals\LUTs\OCIO\aces_1.0.3
 [[File:AFX_Setup.jpg|800px]]
# Here you can load the OCIO file
# Next you can choose the source color space from your material or comp. Alexa log or ACEScg for example.
# At last you can choose the output color space which is normally sRGB(ACES)

 The setup in AFX is a bit tricky and complex, but at least you can work with ACEScg linear images if you get them from our 3D guys.

==Premiere Setup==
 Same as in AFX but at the moment the plugin is too slow to use it for editing :-(

==Substance Painter Setup==
 Substance Painter is not able to save/bake textures into the selected LUT Format, it is just possible to display it in the viewport of Painter.

The maps exported from SD and SP are in sRGB or gamma-encoded space. They are not exported as linear.

EXR Textures are also saved as sRGB not as Linear. <<< Pretty shitty!!
 
 How to activate?
 
 1. You need to import/copy the LUT Profile to Substance Painter.
 2. LUTS are located here. X:\Pipeline\_Globals\LUTs\OCIO\forSubstance 3. Drag/Drop the LUTS to your Color Profiles shelf in Substance Painter.
 [[File:SubstancePainter_Setup2.JPG|1800x1800px]]
 

4. Activate and select your desired Color Profile [[File:SubstancePainter_Setup1.JPG|724x724px]]