With the previous version of DaVinci Resolve I encountered issues where more complex EDLs (sessions) resulted in the timeline getting scrambled.Īfter losing hours of work, I decided to keep my use of DaVinci Resolve to more basic cut/splice/transition duties (no special effects, etc). The recommended RTX-3070 with 8GB RAM has been going for almost $800. It's when you're getting into Video EFX (nodes) that it can get pretty deep (need to watch tutorials, etc).īy itself (no 3rd-party plugins), DaVinci Resolve is probably the single most complete Editing/processing package. Not too drastically different from Vegas Pro. but those types of things can be annoying.ĭaVinci Resolve offers so many amazing features, it's almost overwhelming.īasic cuts/splices/transitions are actually very easy. Vegas often crashes due to some simple issue. That being said, for more advanced functions/processing (Chroma keying, etc), I find Vegas (at least previous versions) a bit dated/clunky. so for the very basics, it's easy for a typical DAW user to get up-and-running. Here's my experience/opinion on Vegas Pro, DaVinci Resolve, and Premier Pro: Thanks for mentioning the voice isolation problem, I'll be sure to keep that in mind since I'm working with voice overs right now.What version of Vegas Pro are you currently using? But like you said, becoming more aware of potential corrupted projects as well. ![]() I do like Resolve far better than Premiere, so I'm planning to stick to it. I was applying at the track level, so unless I'm unaware, I don't think caching is an option. I've had horrible performance with audio using the voice isolation features and it makes it almost unusable cutting if those are left on. I even tend to save out a fcp7 xml at the end of the day, in case I have to go back to Premiere. I regularly save out timeline and project back-ups throughout the day, as well as exporting at the end of the day or more frequently. Resolve projects seem to get corrupted way too easily something I can't remember ever happening in over a decade strictly in Premiere. My general rule of thumb is if it's a project that I'll be coloring, I try to do it in Resolve, if it's a strict cut, I do it in Premiere. I haven't abandoned Resolve, but I am way more weary of it than I ever was of Premiere and I go back and forth between them. I had more or less the same issue and lost 2 days of work on a project. Started using DaVinci cause it's way more stable than Premiere. If Resolve still does not launch, send another Resolve log.Īnd just to reemphasize, since people always get this wrong, the folder locations above are in the hidden /Users/tutor/Library folder, NOT the main /Library folder or the System/Library folder. Now launch Resolve, and it should start, with a fresh Local Database Local Project Library. Users/tutor/Library/Application Support/Blackmagic Design/DaVinci ResolveĪnd rename the Resolve Disk Database folder to Resolve Disk Database.orig Users/tutor/Library/Preferences/Blackmagic Design/DaVinci Resolve To see hidden folders, press the and and keys all at the same time. Note, some locations below are "hidden" folders. So, assuming you don't have any existing projects to worry about, do the following: The issue with 18.1.3 is some sort of database issue. Looks like the last time you had the system working was April of last year with Resolve 16.1.2.Īnd even then, I'm not sure it had a proper database, because I don't see that any projects were loaded. maybe it's the HDD and not the hardware?).įyi, the location for optimized media is in my documents where I created a folder called "DaVinci Cache". But I do need to have optimized media cause my laptop is not able to play the ProRes in realtime (Macbook Pro M1. I now cleared my cache and tried loading the project again, and it loads just fine! ![]() So it seems like generating optimized media for a clip might make it crash. Thinking back, I did clean my cache a couple days ago. Then I generated optimized media for a clip and shortly after. However, the project did load fine for a second. I've relocated the audio file from my downloads folder to my harddrive where the video files are located as well. And if that is the issue, the Downloads folder is probably not a good place to use Resolve media from. Might be worth moving any files in the Download folder other than the desired audio file to another folder to see if that's the issue. ![]() If there is some other file or files in the Downloads folder that Resolve doesn't like, that could cause it to crash when it looks in that folder for the audio file. The only other thought be that your audio file is located in your Downloads folder. I don't see anything going on in the project that should cause Resolve any issues. The timeline has 3 ungraded ProRes clips on it. Dwaine Maggart wrote:The project-that-crashes loads OK on my Windows system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |