Sean Sartori
Forum Replies Created
-
Yup, I’m seeing it when playing out of the Blackmagic application. With normal pro res footage there is a crooked, flickering scanline. With SD footage playback is jittery and there are field artifacts all over the place.
I’ll swap the cable to eliminate that possibility, and then I guess its a call to BMD. The box is only a few months old.
-
They also had their projector doing a conversion from XYZ to 709 at 2.2, which made the image dim. So the projector wasn’t in p3 space, so I was just really seeing a blowup of rec 709. Not ideal.
After re running it, it seemed to match, but I don’t love the fact that I’m taking raw CinemaDNG down to 709 422.I intend to QC it in a theater with P3 space in future, as well as re creating the DCP from DPX. Live and learn.
-
Well it turned out the house creating the DCP had set the gamma incorrectly, and didn’t set the video levels at all, despite the fact that gamma and levels were stated in the slate.
-
Hey thanks for the flurry, I didn’t know people held such strong opinions!
I’m a resolve colorist, and there is a facility that would like to book me that is running an Autodesk shop.
I guess I was putting some feelers out there about the learning curve coming from resolve, and if its feasible to try to work it out myself on the training edition. Ill try the flame forum as there is no Lustre forum? -
Yes it could be connected to noise reduction, or it could be that the project is corrupted, as I brought it from Resolve 10. Its suspicious though, that all crashes are related to 4K.
I needed to export some 4K stills, and the workaround was to create a new project, bring in just those shots, and work in a 4K timeline. Even then, if I brought in a grade that had NR enabled, instant freeze. If i removed the NR and brought the grade over, all was fine.
So this begs the question, is it not possible to do ANYTHING in 4K with NR? I thought this new mac pro was a racecar and all….
-
yes, two AMD FirePro D700’s
-
ah, ok. We are looking into rolling back to 10.9.2 after this project is done. ugh.
-
I haven’t talked to support, i don’t have time at the moment I have to get this doc out the door. Yes it might be a bug, i can’t find any reason for it…..
-
I am having nightmarish problems with eucon and resolve. I am running eucon 2.7.1, and I just updated to resolve lite 9.1.5 Lite. I’m working on a retina MacBook for this job, perhaps that is the problem. Eucon will recognize the board but it simply will not work with resolve. I just used the board all day on another system with no problem, so I know it’s not the board. Any ideas? I’ve tried all configuration of static IP, DHCP, etc, no luck.
-
OK great thanks
I think its the field processing, you’re right. I’m working with a flat quicktime so there is no resizing, I will try it tomorrow with field processing off. It’s possible they reversed the fields in Avid somehow, will have to look into that.
I will see if they can upgrade the card, I’m sure they just went with the cheapest one that was listed as compatible.
Strangely enough, this is the first time I have encountered interlaced footage in Resolve, it seems to be dying out. Won’t miss it.