This happens only in BETA version 8. i have 1 clip. I copy this clip over the first one, so i have 2 similar clips over each other. The playback works fine.
When i crop the clip above the playback bugs. The playback gets overexposed (extremly bright) and is starting to lag (no smooth playback anymore)
Is this only happening to me? Or is the issue reproducible at your systems?
- DaVinci Resolve Studio 17 - Windows 10 Pro 64bit - i7 4770k - GTX980Ti 6Gb - 16Gb RAM
There are definitely some bugs with cropping in 17.0b8. For me, cropping is ignored during playback. This makes all of my footage overlap in an additive manner. When stopped it is fine.
odd cropping behavior in 17.0b8
Screen Shot 2021-02-03 at 7.37.30 PM.png (876.41 KiB) Viewed 5963 times
I'm seeing a similar issue on a 2019 Mac Pro DR Studio 17 Beta 8. I placed a clip on top of an identical clip, the only difference being the top clip contains graphics. I key framed a reveal of the graphics using cropping and a thin white line appears at the cropped edge. When rendering the image flashes becoming overexposed. Reinstalling Beta 7 fixed the problem.
Been doing this since cameras went clickety, clickety, clickety, clickety . . .
Same issue - which coincided with updating to latest Beta. I rendered the video out earlier, all cropping is OK. After updating DaVinci Resolve, cropped videos now show a ghosted border of what was cropped. Condition is present during preview playback (Cut or Edit page) and after rendering.
Yeah, I searched the forums before starting a thread about this, didn't come up with anything, then wrote a whole post about it. Now, I see that this thread is about a week old, so deleted mine, and am putting my +1 here.
Changing composite mode to alpha doesn't seem to work for Color managed projects.
Also, is the "Retain Image Position" checkbox new? I never noticed it before, but it doesn't seem to do anything.
Jason Conrad wrote:is the "Retain Image Position" checkbox new?
In 17, yes. Under Help>Reference Manual a New Features guide will open explaining all the new stuff.
The new features guide does not cover this topic, but I figured it out. It doesn't do anything unless you've adjusted the images position coordinates. In such a case, it works like "pan behind" in Adobe products. I was expecting it to work more like Fusion's Crop node. Handy little addition, though.
(1) If you change the crop dimensions, some dimensions will look fine, and other will not (either black or white border showing). Changing by 1 pixel will change, and some will look fine.
(2) If you have rotation applied, then you will inevitably hit some of the "bad" at some point in the edge line.
See the slightly angled image bottom border where you see black jagged and on the side you see white jagged :
Resolve Studio - Ryzen 5800X3D - AMD RX6600 / NVidia RTX 4070 (switching between the 2) - Linux
I was hopeful that Beta 9 would fix this, but I still experience issues with Softness. The softer you make it, the more it "smears" for me, but even at 1 I get a black bar.
This is a freeze frame of Prorez 422 on top of the clip with color correction applied ... though, when I removed the color correction, the smearing still existed:
SoftnessSmear.png (150.51 KiB) Viewed 5480 times
Hope that helps as the team works to address it.
~Luke
Studio 19.1.3b7 | Windows 10 Pro | Driver 566.36 Studio
WORK 1. 2080Ti; Ryzen 9 3900X; 32GB 2. 3080; Ryzen 9 5950X; 64GB Blackmagic Cloud; Media NAS; M.2 Boot
HOME 1080Ti; Threadripper 1950X; 32GB Media 7200; M.2 Boot
It's fine until I apply softness, then I get a white line at the edge of the crop. Even if I reset it to zero softness, the white line remains. Much better than it was but still not completely fixed.
Been doing this since cameras went clickety, clickety, clickety, clickety . . .
I'm getting a white 1 pixel line around the crop without softening. With softening, it is like before with a light overlay-like appearance at the crop. Hoping beta 10 will address
I'm on beta 9 and still getting strange result with crop.
I made window in Colour, add alpha output and fed the window to the alpha out. On the Edit Page the crop only crops the RGB not the alpha so I'm left with black where it's cropped but the same alpha from the window. I can make this into a Compound clip, the alpha carries through and the crop behaves as you'd expect.
Windows 11 Pro, Core i9 13900K, 96GB RAM, RTX 4080 Super
17 is out of beta and they seem to have fixed the cropping issue. Great work on this release!
I realised that my complaint (above) about the crop not cropping an alpha made on the colour page is slightly different issue and probably to do with the order of operations edit page > colour page. Still not working in an ideal way though. It's either the alpha from edit, modified with the crop, OR the alpha from the color page, it should be AND I guess?
Windows 11 Pro, Core i9 13900K, 96GB RAM, RTX 4080 Super
I still had the "old" work around of having the alpha output added in the color page and with that active, it's still buggy same behavior as before (which AFAICT it should work, so that's also an issue ...)
If I remove the alpha output in the color page, then the only issue I can see that remains is that if an edge is not cropped (so it goes right to the edge of that image), then there is a thin black border on that side, and if you apply a rotation, it becomes very visible and jagged. (just like the pic in my post above on the lowest edge)
It's also dependent on the resize I apply to the image.
Resolve Studio - Ryzen 5800X3D - AMD RX6600 / NVidia RTX 4070 (switching between the 2) - Linux