This repository contains the source code for the resolve.cafe website.
You can also find a list of DaVinci Resolve bug reports and feature requests in the Issues section.
Discussions about the website can also be found here.
The resolve.cafe website
Home Page: https://resolve.cafe
License: MIT License
This repository contains the source code for the resolve.cafe website.
You can also find a list of DaVinci Resolve bug reports and feature requests in the Issues section.
Discussions about the website can also be found here.
Version: 19beta6 not studio
GPU: quadro t1200, driver cuda 32.0.15
timeline setting original: ultra HD
timeline setting desired change to: vertical ultra HD
What format setting is not effected by the bug:
Bug:
Issue:
Symptoms:
Workaround:
Background:
Wasted all last night 5hrs to figure out banging my head to why the workspaces don't show the same size and shape aka aspect ratio setting in the project and timeline settings. Finally figured out why.
Overall Resolve Suggestions:
In DaVinci Resolve 18.6.2 and the public beta release 19: When you normalize an audio clip, the procedure is including the Effects Chain to assess the audio level.
You will find the clip gain much higher than before, roughly or exactly equivalent to the gain change in the effects chain.
The effects chain should not be included in the audio clip normalize function. The function should set audio levels relative to the audio clip before further processing. This is an industry standard.
To include the effects chain in assessing the level and then applying that back to the clip introduces mayhem.
Importing rec. 601 (ntsc) footage into rec. 709 timeline no longer properly converts the ycbcr values.
Below is a comparison graph
On the left is rec 601 footage when it is not being converted to 709 space correctly.
The right shows how the graph should look when 601 is being converted to 709 space correctly.
While the difference is minimal, it becomes far more obvious when you are working with limited colours on screen. Currently there is no way to properly import rec 601 footage into davinci resolve.
Davinci studio 18.6 incorrectly rendering tracks.
_[edit2] FOUND A WORKAROUND. Thanks @maximilian yuen.
copy the offending timeline
create a new project in same res as the offending one. Has to be a new project. Creating a new timeline in existing project doesn't affect this issue.
paste the timeline.
Save / Restart Resolve (this is the key)
Timeline now renders ok.
[edit] it seems to be a positioning/scaling bug. I changed my project settings to convert to horizontal format and you can see by the additional photo i've attached here that when it does the render, it's positioning the clip way off to the right. If you look close, it's also incorrectly scaling the crop. The crop should be a closeup of my right hand but if you look at the last photo, you can see that in addition to moving the image outside of the vertical frame, it's also cropped it incorrectly so that my hand is no longer framed but instead it's framing the guitar neck._
First image shows what it looks like in editor with annotations. V2 is completely missing from the render. V3 shows up in the render but the crop on the right side is incorrect.
2nd photo shows final render.
I have tried render in place, deleting cache as well as creating compound clip. No change in behavior. One interesting note is that if I render V2 in place, it immediately disappears in the edit view.
interestingly enough, if I set playback to disable all proxies, the v2 clip just disappears totally. I went through and deleted all proxies, all cached data too. The only way the clip reappears in the editor is if I re-enable caching and regen the proxy for the particular clip.
Machine is i13700k, 64gb memory, 3060ti, Nvme ssd with 1TB free space.
Video codec info:
H.2640x34363248 ('H264')
{34363248-0000-0010-8000-00AA00389B71} (MFVideoFormat_H264)MFMS
{34363248-0000-0010-8000-00AA00389B71} (MEDIASUBTYPE_H264)DSMS
H264V_MPEG4/ISO/AVC
DaVinci Resolve Version 18.1.4 Build 9
I noticed this behavior when attempting to select "Change Dynamic Attributes" after selecting keyframe(s) in the color panel that I wished to adjust. I would have to repeatedly re-select the keyframes I wished to adjust, but upon entering the context menu for "Change Dynamic Attributes", the keyframes would unselect themselves, rendering them incapable of being modified (when I click Okay).
It's almost like I'm in a race to complete the action before the software unselects the keyframes I've chosen. I don't remember it being this difficult to "Change Dynamic Attributes on keyframes on the color page.
See attached quicktime to see what I mean.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.