Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limited testing with Studio version #26

Open
zelikos opened this issue Oct 9, 2023 · 12 comments
Open

Limited testing with Studio version #26

zelikos opened this issue Oct 9, 2023 · 12 comments
Labels
help wanted Extra attention is needed

Comments

@zelikos
Copy link
Owner

zelikos commented Oct 9, 2023

I've only used the free version of DaVinci Resolve, as that has met my needs enough for my use cases, so using davincibox with the Studio version is another thing I'm unable to test.

Help would of course be appreciated here, but I have to urge caution in doing so. IIUC, the Studio version requires activation with an activation key?

  1. I don't know if running Resolve Studio in a container would interfere with that
  2. Care should be taken to not delete the container without first deactivating Resolve Studio, if possible; I don't know how trying to activate a different installation without first deactivating the previous is actually handled by Resolve Studio, but it's a potential headache that would be best to avoid

tl;dr: Help wanted on testing Resolve Studio, but be careful

@zelikos zelikos pinned this issue Oct 9, 2023
@zelikos zelikos added the help wanted Extra attention is needed label Oct 9, 2023
@rothgar
Copy link

rothgar commented Oct 10, 2023

I have davinci installed locally in /opt and also tried with davincibox and I was able to register my studio license.

image

It prompted me to put in my key again but so far it all appears to work fine.

@rothgar rothgar mentioned this issue Oct 11, 2023
@zelikos zelikos changed the title Untested with Studio version Limited testing with Studio version Nov 13, 2023
@not-a-dev-stein

This comment was marked as off-topic.

@zelikos

This comment was marked as off-topic.

@not-a-dev-stein

This comment was marked as off-topic.

@zelikos

This comment was marked as off-topic.

@not-a-dev-stein

This comment was marked as off-topic.

@zelikos

This comment was marked as off-topic.

@queequeg0925
Copy link

I've only used the free version of DaVinci Resolve, as that has met my needs enough for my use cases, so using davincibox with the Studio version is another thing I'm unable to test.

Help would of course be appreciated here, but I have to urge caution in doing so. IIUC, the Studio version requires activation with an activation key?

1. I don't know if running Resolve Studio in a container would interfere with that

2. Care should be taken to **not** delete the container without first deactivating Resolve Studio, if possible; I don't know how trying to activate a different installation without first deactivating the previous is actually handled by Resolve Studio, but it's a potential headache that would be best to avoid

tl;dr: Help wanted on testing Resolve Studio, but be careful

I'm going to give resolve studio a try on my arch system. Activation key should not be an issue. Resolve allows two activation. When you activate a third time, it clears the previous activation automatically.

@geewiz
Copy link

geewiz commented Jun 26, 2024

I've been running Resolve Studio in Distrobox for about two years. Since that Distrobox is so old that it started acting up recently with a known sudo issue, I decided to give davincibox a shot. It works nicely!

I'm grateful for your work, @zelikos! ❤️

@mtwb47
Copy link

mtwb47 commented Jul 20, 2024

Studio also works very well for me. The only issue I've found is that the text scaling is way off, but IDK that that's a Studio issue or not.

@marbub
Copy link

marbub commented Oct 14, 2024

I am running an older version of DaVinci Box with Studio. The only thing I noticed is that I had to remove libgobject, libmodule, etc. because there were linking errors. I think the origin is that DaVinci Box is based on Fedora instead of Rocky Linux, so the symbols do not match.

@zelikos
Copy link
Owner Author

zelikos commented Oct 14, 2024

I am running an older version of DaVinci Box with Studio. The only thing I noticed is that I had to remove libgobject, libmodule, etc. because there were linking errors. I think the origin is that DaVinci Box is based on Fedora instead of Rocky Linux, so the symbols do not match.

davincibox builds since June have had a fix for the issue with those packages

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

7 participants