- Posts: 179
- Joined: Sat Mar 26, 2016 1:13 pm
Bugs (tested on Win10 Pro x64):
- big one: working in linear (1.0 gamma) timelines seems to break the render cache: uncached clips look correct, but the black level and shadow detail changes significantly when the clip is cached. this happens with all available render cache codecs, and looks like a bug with 1.0 gamma timelines. it seems like the below-video-levels shadow detail is clipped off incorrectly.
this means I can't use caching on my current project.
- on the same timeline, rendering a clip in-place also slightly changes its appearance. not as badly as above, but the colours still change (this might be a harmless colour management issue to do with rendered clip playback, but if so it is still undesireable as the whole point of rendering a clip with fx in-place is to see a correct final version).
- Edit clip render in-place to MP4 format (tested using Nvidia H265) produces MOV files?
- Clean Feed monitor window no longer automatically minimizes when you minimize the main window. this blocks everything on that monitor permanently (until Resolve is closed). it used to work prior to R17.
workaround: use ALT-Tab to bring a non-Resolve window hidden by the Clean Feed on top - but this only works when Resolve is _not_ minimized (otherwise the other window will not show).
- In Edit, dragging automation points on clips (in the non curve editor display) works with an incorrect X offset: dragging the point to the right works normally, but dragging left doesn't work unless you drag _two_ frames away, where it then moves the point only a _single_ frame. this is some kind of incorrect mouse X coordinate offset (tested with a Wacom graphics tablet).
However, when dragging the same points in the clip's curve editor it works correctly (so this only affects the non-curve view).
Graphics tablet issues:
- dragging the cursor to the timeline edges in the Edit page with the graphics tablet pen to scroll the timeline massively overshoots when the timeline zoom level is high, to the point of being totally unusable.
repro: zoom about half-way into the timeline. drag the cursor near the edge to auto scroll it a little. at this zoom level it works fairly well.
now zoom in all the way, and try again. result: massive uncontrollable overshoot, and then trying to correct it the other way, massive undershoot. unusable.
- clip edge/cut selection with my Wacom pen almost always moves the edge accidentally a frame or two. Graphics tablet pens are less accurate then mice when it comes to clicking precisely, they tend to wobble a pixel or two as you click. that makes clip edge selection v. annoying. a small 'dead zone' where the pen movement doesn't count during a click would avoid this.
- big one: working in linear (1.0 gamma) timelines seems to break the render cache: uncached clips look correct, but the black level and shadow detail changes significantly when the clip is cached. this happens with all available render cache codecs, and looks like a bug with 1.0 gamma timelines. it seems like the below-video-levels shadow detail is clipped off incorrectly.
this means I can't use caching on my current project.
- on the same timeline, rendering a clip in-place also slightly changes its appearance. not as badly as above, but the colours still change (this might be a harmless colour management issue to do with rendered clip playback, but if so it is still undesireable as the whole point of rendering a clip with fx in-place is to see a correct final version).
- Edit clip render in-place to MP4 format (tested using Nvidia H265) produces MOV files?
- Clean Feed monitor window no longer automatically minimizes when you minimize the main window. this blocks everything on that monitor permanently (until Resolve is closed). it used to work prior to R17.
workaround: use ALT-Tab to bring a non-Resolve window hidden by the Clean Feed on top - but this only works when Resolve is _not_ minimized (otherwise the other window will not show).
- In Edit, dragging automation points on clips (in the non curve editor display) works with an incorrect X offset: dragging the point to the right works normally, but dragging left doesn't work unless you drag _two_ frames away, where it then moves the point only a _single_ frame. this is some kind of incorrect mouse X coordinate offset (tested with a Wacom graphics tablet).
However, when dragging the same points in the clip's curve editor it works correctly (so this only affects the non-curve view).
Graphics tablet issues:
- dragging the cursor to the timeline edges in the Edit page with the graphics tablet pen to scroll the timeline massively overshoots when the timeline zoom level is high, to the point of being totally unusable.
repro: zoom about half-way into the timeline. drag the cursor near the edge to auto scroll it a little. at this zoom level it works fairly well.
now zoom in all the way, and try again. result: massive uncontrollable overshoot, and then trying to correct it the other way, massive undershoot. unusable.
- clip edge/cut selection with my Wacom pen almost always moves the edge accidentally a frame or two. Graphics tablet pens are less accurate then mice when it comes to clicking precisely, they tend to wobble a pixel or two as you click. that makes clip edge selection v. annoying. a small 'dead zone' where the pen movement doesn't count during a click would avoid this.