Code Monkey home page Code Monkey logo

resolvecafe's Introduction

Resolve Cafe

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.

resolvecafe's People

Contributors

actions-user avatar blackworm27 avatar bobbydp avatar clueluzz avatar latenitefilms avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

resolvecafe's Issues

Aspect ratio & vertical settings disconnected between workspaces

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:

  • square vs cinemascope
  • mismatched resolution

Bug:

  1. Switching between workspaces the playback window doesn't equally match ratio and rotation between all workspaces per the project or timeline override manual settings.
  2. No way to see what aspect is really applied to all workspace playback players based on settings saved.
  3. Transform FX is also broken between cut/edit/fusion and color mode. Doesn't match. 3a. When enabling and adjusting setting in edit workspace its separate from and adds to a color grading node in color view workspace.
    For example I have no transform node ON, the zoom is the same throughout workspaces playback views. When I enable/ON a zoom from the edit/cut/fusion view, then go to color WS it shows both as added zoom together; thereby, double zooming or double rotating the clip.

Issue:

  1. How am I suppose to know as a beginner in resolve this is a bug or a setting?
  2. How am I suppose to trust v19 or beta given beta only fixes new features not basic old function and base function of resolve workflow of workspaces?
  3. How am I suppose to really know/see if changing ratio or vert/horiz is applied or not to all workspaces?
  4. What if I didn't change vertical and only resolution to higher or lower, how am I supposed to know it changed in 1 or all playback workspaces when there's no indicator of the setting after set? If I switched from HD to ultra HD but not the vertical, how would I know if it took effect or not? I lost faith in resolve.
  5. (Using non-studio version), I tried to set 4k or 6k and it switched back. No error or popup to say its not enabled for non-studio version. I had to do research after banging my head with frustration.

Symptoms:

  1. Timeline or project settings don't matter. issue persists to not effect the workspace not selected/currently viewed.
  2. the only correct workspace is media or cut, the other workspaces show a square or 16:9 aspect ratio. Basically vertical and ratio is ignored in other workspaces for playback.
  3. quitting and restarting resolve doesn't fix it.
  4. resetting UI doesn't fix it and shouldn't be needed to hit that.
  5. checking output or format tab inside project settings doesn't fix it. But when it's checked then it matches the setting after I fixed the bug using my workaround.

Workaround:

  1. Not use project settings and use manual timeline settings ONLY when set when viewing workspace: color
  2. Only after that is set when viewing color workspace then switching workspaces shows the correct setting across all workspaces. If I set the aspect or to vert inside any other view, its still broken.

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:

  1. Aside from fixing the bug. Give an additional UI reset to: reset with last preset chosen.
  2. Have a preview of all chosen aspect ratios and resolutions in the settings window.
  3. Or have a reset button or apply button or reset and apply last layout preset used button inside timeline settings or project settings. This will bypass confusion for anyone experiencing the bug for not changing the vertical setting.
  4. There is no way to copy or import node grading files from a clip to a timeline. applying clip can only apply to clip. applying to timeline or pasting between clip and timeline isn't possible. I want to export grading from clip still then import to a timeline or vice versa. Given the grading was created in clip and still created in clip theres no way to switch to timeline node grading view (via 2 dots at the top) and then apply the copy or the grade to not the clip but the view I'm looking at. So there should be an option drop down or right click to "apply grade to timeline" and "apply grade to clip" or apply to both "timeline & clip."
  5. Don't ask me to test this further doing your engineers jobs and not get paid. This is a huge bug and disappointed. I'll uninstall and try v19 non-beta and see if issue persists.

Audio Clip Normalize Including Effects Chain

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.

  1. Firstly, normalize the clip without any effects - note the audio levels and the peak display.
  2. Place a gain-changing plugin, such as a compressor, into the effects chain.
  3. Set the plugin up to significantly reduce the gain.
  4. Run the normalize function again.
  5. Disable the plugin.
  6. Compare the audio clip levels now to before.

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.

Problems with ycbcr conversion in latest version (18.6) (may have existed in previous versions)

Importing rec. 601 (ntsc) footage into rec. 709 timeline no longer properly converts the ycbcr values.

Below is a comparison graph

601 not properly converting to 709 color space

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.

Bug in rendering track which is scaled, offset and cropped

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

image
image

Keyframe Editor in Color Page Repeatedly and Unintentionally Deselecting Selection

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.

resolve-keyframe-bug.mov

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.