You local grades and use colortrace to copy grades from the other timeline when you load a new XML. Which could be quite annoying if my film would have been 90min longĭo you know how I could avoid this problem ? I saw a video once - cant remember who it was - that talked about changing the color space of a node in Davinci to HSV and utilizing the 'Gain' in the primaries to increase/decrease. So I had to manually reload the specific version I created for each clip. I'm not sure if that's the correct term, but I've noticed many modern tv shows/movies have 'denser' or 'thicker' looking colors but not necessarily more saturated.
So I created a new XMLv2 of my new FCP sequence, and imported it in resolveĪll the grades I did before were loaded automatically as they were remote ones, that's great.īut all the clips which were linked by the red arrow and for which I created new versions (version 1, version 2, version 3, etc.), they all have loaded the version 1 only. Then I had to do some corrections of my film in FCP, and add a few more clips. So for each of these clips I've created new remote versions (version 1, version 2, version 3, etc) in order to grade them separately. Some clips in my timeline were part of the same shot (so they were "linked" with the "red arrow" in resolve
I edited a mini doc on FCP, created XML v1 and imported the timeline in resolve. Is there anything similar that I can do in Resolve so that I don't have to play this version installation game if this happens again?īTW, before I grade the next episode of this particular series I'll convert the offending opening sequence do 29,97.I had a little problem when grading with remote versions and was wondering if someone had a solution.
Many programs on the Mac like Final Cut Pro allow the user to trash preferences and recover from this kind of fatal error. But having the 9.04 installation has been the best insurance I could possibly have.
After I finish this project, I'll install 9.1.1 again just because it is so much better, overall. It's just that 9.1.1 has been more stable than 9.1. So, what are the other factors involved? It's a FCP XML workflow. Better then losing a days work, especially when the episode airs in a couple of days. The only strange thing is that it stops at every single cut, giving me a black screen for a couple of seconds and then it renders the next one. Luckily I did the same thing I had done with the 9.1 crash.
Strangely, I've graded 5 other episodes of this same series since upgrading to 9.1.1 and, while another one crashed at the same spot, the project opened up just fine and I resumed the render from the opening sequence on. Forums DaVinci Resolve davinci resolve lite for pc keeps crashing after import davinci resolve lite for pc keeps crashing after import seb demeffe updated 2 years, 7 months ago 13 Members The crash occurred when the render got to this opening sequence. What this project has in common with the other one is that the program's opening sequence is in 23,976 while the rest of the show is in 29,97. You can still search for HEVC in the MS store and pay 0.99 though. There was simply no way to open it, no matter how many time I tried - even after restarting the computer. This is still valid info, however Microsoft put it behind an OEM Code.
Then the project crashed while opening, exactly like it happened in 9.1. I spent all day grading a TV series episode and when I started rendering resolve Lite 9.1.1 crashed.