Recently I was honored and excited to be invited to the new publicly funded (to help counter the energy transition woes for the regional – and the German as a whole – economy) and innovation project called Startup Village by Brainergy Park outside of Jülich, Germany to check out the second batch of their ZEBRA green tech and impact “accelerator”.
It’s a huge investment with the capital – and a huge area – already committed to building out a massive innovation campus, and I do enjoy experiencing new startup initiatives outside of the major cities in this area of the German state of North-Rhine-Westphalia first hand. So much is happening outside of Cologne and Düsseldorf that is often overlooked.
It’s still very early days (not many buildings completed yet), but keep an eye on this area and do visit if you have the chance – even getting there can be quite the adventure…
Recently I had the honor and pleasure to be invited for jury duty at the 17th batch of the Ignition+ program by DigiHub Düsseldorf and help decide who would get further funding.
And the winner was… Co-reactive “Correcting greenhouse gas emissions with CO2 reacting to solids”!
Full Disclosure: I’m not getting anything in return – Cullen’s work, both with educating us n00bs and creating incredibly useful and beautiful tools for us, is awesome and I just think he, Mr. Zambrano, and Mr. Smith – deserve all the good Karma they can get. (For some inexplicable reason, Cullen Kelly seems to have the most bizarrely convoluted web presence for his tools that I have ever come across – and I’ve been in the web dev biz for +30 years and seen some things – but that’s not the rant you came here for…)
</PSA>
A while back, I posted about my Live Streaming Studio V3.1 setup, because many people wanted to know what gear I’m using and how I get the “cinematic” look on a live Zoom call. And to achieve the look I was going for, one of the things I had to (well, more like “desired to”) learn from scratch – in addition to operating a digital cinema camera and properly use lighting – was how to color grade.
Reference: Non-graded image without look and effects applied, only BMD Film Gen 1 (camera log aka RAW) color space transform to rec709 / Gamma 2.2 (what a monitor can display) via a classic CST applied. (See results of using OpenDRT instead of CST below for comparison.)
Below, after some grading, applying a ton of stuff for the look, and even throwing in some effects to emulate anamorphic edge distortions and a fake film gate crop for too much good measures:
In this post, I’m sharing a bit about my further digging myself into a hole adventures into color grading with Blackmagic Design’s DaVinci Resolve Studio (free download of the non-studio version). It’s an incredible piece of software, by the way. If you’re thinking about ditching Adobe Premiere – just do it! It’s a joy to work with and I’ve never regretted it for a second.
This is not a primer on color grading. It’s just me dumping writing up and sharing what I’ve learned that works best for me so far. If you too wish to start (or continue) on a color grading learning journey with DaVinci Resolve, Cullen Kelly’s YouTube channel is probably the best place for that.
Getting somewhere… second pass / grade
The following assumes you’re already familiar some of the concepts of color grading – or at least have a faint interest in how to create a cinematic image with digital tools. If not, fair warning, this post will bore the living daylights out of you is probably not for you.
What started as a necessity during the lockdown era (aka building a professional-looking online tele-presence) turned into a path of rediscovery, reigniting my passion for the cinematic image. Little known fact: You might not know that I actually started out studying cinema with the goal to become a film director – but I dropped out after only two years as university as studying film wasn’t really my thing – and then the commercial Internet happened and the rest is history.
As a person most likely somewhere on a spectrum of some kind, of course I can’t, I won’t, and I don’t stop digging until I’m getting somewhere interesting, somewhere where I can feel a sense of mastery and understanding of the full stack (in this case lighting, lenses, physics, camera sensor, cinematography, color grading, look development – everything that goes into the sausage factory of a nice – to me – digital “cine” image), aka being able to make predictable outcomes and making those outcomes look cinematic and pleasing – to me. It’s become sort of a new time sinkobsession hobby of mine (in addition to still helping other startup founders go farther faster, don’t you worry).
And I’m still digging.. .
Read on below for this long non-startup (but hey – still full of tech & geekery) post.
A lot (aka way too much, time to roll back some) going on under the hood here.
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gid
ID used to identify users for 24 hours after last activity
24 hours
_ga_
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga
ID used to identify users
2 years
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utma
ID used to identify users and sessions
2 years after last activity
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
You can find more information in our Cookie Policy and .