Resolve was just not able to write the license data to disk due to a filesystem error (in my case I had made the Resolve dir read-only after installation.) My problem turned out to be on my own computer and nothing to do with the license key or license server or network connection. I don't understand why BM license system is so messy. I have to go on windows, activate, then disable licences, then reboot on linux and activate. Same issue here, I am on linux and it is all a mess, I activate then the next day it tells me to activate again and I can't. I have to rely on the automatic deactivate, which doesn't seem to work on Linux. This time I can't do that because I no longer have access to the system. What I have done in the past is go to MacOS and select "Deactivate" without any issues so that I can then install on Linux. However, on Linux, it doesn't seem to do that part properly as it always fails. It looks like when you attempt to activate on Windows or Mac, it contacts Blackmagic DB servers to deactivate the oldest installation. On Windows or MacOS, this doesn't seem to be an issue. This is terrible that I have to go through this every time. ![]() Reinstalling 17.1.1 and having the activation issue again. Unix4linux wrote:I'm back on this thread. If anyone has any idea on how to solve this issue, your help would be greatly appreciated! Here's the link to the Logs that result after attempting to activate the software as well as my system NFO file. My PC is custom-built, so there's no official brand on it (if it helps, I'm running off an Intel i5-9600K. My OS is Windows 10, and I installed the most current version of DaVinci Resolve Studio 15. For any Blackmagic Support folks, my ticket number is LPI-999-61972. Every time I enter in the activation key, it tells me that "there was an error when attempting to perform the activation." I've contacted BMD Support about this and have opened a ticket with them, but their response time has been. I haven't tried that with Fusion 16 yet, but I saw a user reporting an issue with that in the Linux version of v16.Īnyway, I think your questions have a better chance of being answered if directed to the Fusion forum, here.Hello! I've recently purchased the Studio version of DaVinci Resolve and was excited to get it up and running, but unfortunately, I've hit a snag in trying to activate the software. In addition, Fusion 9 can use FFmpeg for reading unsupported file formats/codecs, but it requires the user to install and configure it. With its heritage as a high end compositor, Fusion likes image sequences, but it does have support for DNxHR/ProRes and other codecs too. Not sure why your Loader node isn't working, but be aware that Fusion doesn't have exactly the same codec support that Resolve has. Most of the scripts available online for Fusion is created in Lua which Fusion runs natively without installing anything. That's usually done in VFX houses that use more automated/complicated VFX pipelines. You don't have to install any version of Python at all, unless you specifically want to run Python scripts. It does that for all applications that use certain API:s in the GPU driver. One more question: should I actually install both the 2.7 AND 3.6 versions of Python? And, where the "Script Editor" option in the Script page of Global and Default Settings should be pointing to - is this a correct value of this field: C:\Python27\python.exe (assuming I have Python 2.7 installed with all defaults)? compared to Resolve's Fusion page version) rendering, where only one of my 2x Titan Xp GPUs is used at up to 10% load at the maxĬan anyone suggest some most obvious errors in my stand-alone Fusion 16 Beta installation? TIA Inability to find and read video clips on a local driveĢ. So, to summarize, my installation of SA Fusion 16 Beta suffers from some rudimentary configuration problems, manifesting in:ġ. ![]() After rendering, the Spaceship shoots across in the viewer window. In this contents, it seems even stranger than Render actually (though very slowly) does work on the downloaded example project from the Fusion 16 product page ( ) with the link. This is so simple that I cannot imagine any other reason for actually not playing the script back and the Render button action failing and returning error, other than some very basic yet important configuration error of the Fusion SA application itself. Fusion console errors.JPG (71.26 KiB) Viewed 268592 times
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |