Forum Replies Created
-
Sascha Haber
November 28, 2013 at 8:47 am in reply to: Resolve 10 on OSX 10.9 freezes system constantlyIf it happens on a cut, it might be the media..
I tend to convert everything to DPX after re-assembling my timeline.
If you have the possibility (RAID) try that..
There are so many “evil’ codecs out today…an internal RAW full res proxy would be kick-assA slice of color…
Resolve 10.0.0.073 , Smoke 2013 EXT
Colorist / VFX / Aerial footage nerd
https://vimeo.com/saschahaber -
If you read between the line, they dont want to use you anymore.
As common practice in VFX houses we offer “buy-outs” for flame reels and master tapes.
Its basically going into a car repair shop and asking them to give you the tools they use.
No go.
Not even presets.
Nada.
Only for a considerable amount of money.
Now you need to find a way to explain it 🙂A slice of color…
Resolve 10.0.0.073 , Smoke 2013 EXT
Colorist / VFX / Aerial footage nerd
https://vimeo.com/saschahaber -
Sascha Haber
November 13, 2013 at 6:42 pm in reply to: Methods for getting screening notes into resolve?Sure, just use audio..
People talk , TC is synced and you can jump to the points because you can see em.
Or extract the TC in AE.
Or even use Google for real time captions 🙂A slice of color…
Resolve 10.0.0.073 , Smoke 2013 EXT
Colorist / VFX / Aerial footage nerd
https://vimeo.com/saschahaber -
no 😉
Still not..
Even if the request is as old as Resolve by now.But you could render the whole thing using the “professional workflow” ad then create a playback timeline with the outputs.
We do this on systems that are to slow to work in RT from RED files or have no external GPUs.A slice of color…
Resolve 10.0.0.073 , Smoke 2013 EXT
Colorist / VFX / Aerial footage nerd
https://vimeo.com/saschahaber -
Sascha Haber
November 10, 2013 at 8:37 am in reply to: LightSpace CMS profiling PatchSize support in Resolve 10?Sweet 🙂
Because its a defacto-standardA slice of color…
Resolve 10.0.0.073 , Smoke 2013 EXT
Colorist / VFX / Aerial footage nerd
https://vimeo.com/saschahaber -
Sascha Haber
November 10, 2013 at 8:35 am in reply to: anyone having success with neat plugin and R10Thats what they said regarding Scratch for three years in a row 🙂
A slice of color…
Resolve 10.0.0.073 , Smoke 2013 EXT
Colorist / VFX / Aerial footage nerd
https://vimeo.com/saschahaber -
And if so, has Logickeybord to revise and issue a new keyboard again ?
https://www.logickeyboard.com/shop/davinci-resolve-1025c1.htmlA slice of color…
Resolve 10.0.0.073 , Smoke 2013 EXT
Colorist / VFX / Aerial footage nerd
https://vimeo.com/saschahaber -
I would say 10% of the advertising I see on TV is defiantly in the wrong color space.
With more and more people having access to video tools and digital broadcast, the quality dropped significantly.
I see a lot of mixed stuff too, where it clearly shows the production shot on video level and the poor AfterFX guy just slapped his super black graphics on…in RGB.When we were still working with LOG scans, 50% of the DPX files had been flagged as LIN 🙂
I actually graded one myself, unaware I had to compensate for it, and it turned out great…hehe.
But when “grading” is done in AVID or FCP using some plugs, all hell breaks lose.A slice of color…
Resolve 10.0.0.073 , Smoke 2013 EXT
Colorist / VFX / Aerial footage nerd
https://vimeo.com/saschahaber -
Sascha Haber
November 10, 2013 at 8:25 am in reply to: Is the 8 Bit Processing on Smart Scope Duo a limitation for Resolve?That is totally fine…
It doesnt have enough lines to show 1024 steps anyway 🙂
If the 256 are taken from your 1024 you are still getting the right ones, distributed across the whole range.A slice of color…
Resolve 10.0.0.073 , Smoke 2013 EXT
Colorist / VFX / Aerial footage nerd
https://vimeo.com/saschahaber -
Sounds like the classic video/data level problem, especially with 10b QT.
First thing you can check, are they just flagged false ?
Go into the clip properties and change em from Auto to video.
When they appear lighter it means they are in video level but will be interpreted as data which causes a lift.
Vice versa when you load in a false flag video level on being interpreted as data causing the image to appear hard in contrast with cut off blacks.
Both can be save by just switching the way.
Ok, lets say its not that, it could happen that THEY had that problem, did not fix it and then rendered the false interpretation into the new video.
In the film world this happens a lot when people are dealing with LOG files.
And the third place this wonderful thing happens is when people use different ways of reading RED.
For example rendering the first batch of ProRes to RedGamma3 and the next one to something else , because “its looked better”to them.
So you need to get into the drivers seat and find out where to fix the error.
Its 99% not Resolves fault 🙂A slice of color…
Resolve 10b3 , Smoke 2013 EXT
Colorist / VFX / Aerial footage nerd
https://vimeo.com/saschahaber