Marc Wielage
Forum Replies Created
-
[Robert Withers] “I don’t know who wrote this guide but I understood it and followed it and upgraded with no problems:
https://mixinglight.com/color-tutorial/guide-upgrade-davinci-resolve-15/“
That was written by Patrick Inhofer of MixingLight.com, with a little bit from me. -
High Sierra can work reasonably well. Mojave is a much bigger change as far as operating systems go, so it’s possible your 2015 machine would work better under the older OS.
-
I think massive projects can get unwieldly after awhile. My suggestion would be to cut your project up in such a way that it’s in (perhaps) 4 different pieces, each with 15 timelines, rather than a single project with 60 timelines. I also find that having a ton of media in the Media page can slow things down as well, so if you can pare away unused material, that might be a good idea.
Resolve 15 has the advantage of only loading 1 timeline into memory at a time (provided you choose that option), and that might help with low-memory issues.
-
[Daniel Parker] “I’d like to ask you what you meant by confirming the individual clips? When I began the project I confirmed all video files with different frame rates to match the time line. I’m working with video taken with a Sony a7 series camera.”
CONFORMING.DLSRs are often a nightmare to work with because you wind up with “fake” timecode starting at 00:00:00:00 per clip, meaning there are hundreds, potentially thousands of timecode conflicts in a project, and some cameras (like the A7) will create identical file names on different days like DSC0001, DSC0002, DSC0003, and so on. One mandatory issue of any proper workflow is to have different filenames for every file, so there are never any naming conflicts, and another is to avoid timecode conflicts when possible by using time-of-day. (Sequential timecode like Hour 1, Hour 2, Hour 3 and so on can also work in some cases.) Without that, it’ll all go to hell very quickly.
I see no solution except to go in and manually force conform shot by shot. Next time, don’t do this. I think a good tactic immediately after shooting is to append the shootday at the head of the file name, so it becomes 123118_DSC0001, 123118_DSC0002, and so on. If there’s more than one camera, consider a camera letter, like A123118_DSC0001, B123118_DSC0001, and so on. I also suggest avoiding Long-GOP H.264 compression entirely and transcode all the files to something benign like ProRes 422HQ or DNxHD (or DNxHR). All these things are part of good workflow practices, at least in my opinion. If you don’t do this, you’re in for a world of hurt.
-
BMD specifies Windows 10 for their System Configuration specs for Resolve 15. Some have reported it can work to a point with previous versions of Windows, but it’s technically not supported.
-
USB 3.1 hubs are out there, but not so much for Display Port or HDMI.
-
[Andi Winter] “please blackmagic, make us some christmas present and do the same for the pc and linux versions of resolve!!!”
Well, the Linux Advanced version of Resolve does do ProRes.ProRes licensing is up to Apple, not Blackmagic, so the ball is in their court. I think there are factors beyond money here.
-
What specific type of source files are they? Are they possibly from DSLRs that have no “real” embedded timecode, but instead start with 00:00:00:00?
If it’s only 24 shots, I would just conform those by hand. Note that this is not a Resolve-specific problem: XML has limitations in terms of clip names, reel numbers, timecode numbers, and issues like speed changes, reframing, and so on. Timecode conflicts within identical clip names is a particularly problem. If you were to try to transport a Premiere session to FCPX or Avid, similar problems will also happen.
-
Which version of Resolve? What OS? What hardware (CPU, GPU, RAM, I/O)? What type of camera & audio source files?
Using Dynamic Project Switching in the Project Menu should “in theory” let you have two open projects at one time and cut-and-paste some or all of the clips from different timelines into other timelines. The grades and tracking will come over automatically with the clips.
-
Which version of Resolve? What OS? What hardware (CPU, GPU, RAM, I/O)? What type of camera source files?