Replies: 3 comments
-
Thanks for the insight/confirmation! I'm using a dongle so was never able to check. A couple quick thoughts from your write-up:
I haven't heard anyone complain about having to constantly re-register with every new Thanks again, |
Beta Was this translation helpful? Give feedback.
-
Oh I just found that there's a "convert to discussion" button, so I'm gonna convert this over if you have any further thoughts. |
Beta Was this translation helpful? Give feedback.
-
The MAC address thing is related to the host system. The certificate signing business is restricted to the container. I actually used Distrobox and Fedora, but a friend shared this repo and I had already done the testing. I'm working with some of the DaVinciBox people to get dGPUs sorted. I believe your script is also affected. |
Beta Was this translation helpful? Give feedback.
-
Hello,
I have run some extensive tests with DaVinci Resolve Studio and did a write up about it here and in a video essay: https://trafotin.com/v/davinci-resolve
I discovered by accident that Resolve requires a static MAC address in order to stay registered. Using a random MAC address will require you to re-register Resolve every time NetworkManager restarts or reconnects. There's probably a relationship with vendor OUIs so they can limit piracy, but not exactly sure. It's the only reliable reason why they require a static MAC.
As for machine-id, if you change your machine-id to something generic, it has no impact on Resolve at all.
Hope this helps.
Beta Was this translation helpful? Give feedback.
All reactions