Limited testing with Studio version

[zelikos]

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

[rothgar]

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

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

[not-a-dev-stein]

18.6 Studio is working for me but one issue I'm facing (which I don't even know where to start looking into to solve) is that the program doesn't seem to be handling audio sources well, where I'm unable to play videos on YouTube or other videos while Resolve is open, and that it doesn't recognize my bluetooth earbuds and keeps playing sound through my laptop speakers.

Likely unrelated to this issue, but sharing the experience anyway.

EDIT: Installing the pipewire-alsa package in the davincibox toolbox fixes it, might be something you'd like to look into doing by default.

[zelikos]

EDIT: Installing the pipewire-alsa package in the davincibox toolbox fixes it, might be something you'd like to look into doing by default.

pipewire-alsa is already included by default as of #29, two months ago.

In a fresh davincibox container:

akzel@davincibox:~$ sudo dnf install pipewire-alsa
Copr repo for distrobox-utils owned by kylegospo                                                                                                                                                                                                                                               10 kB/s | 1.5 kB     00:00    
Fedora 39 - x86_64 - Updates                                                                                                                                                                                                                                                                  107 kB/s |  23 kB     00:00    
Fedora 39 - x86_64 - Updates                                                                                                                                                                                                                                                                  3.1 MB/s | 8.3 MB     00:02    
RPM Fusion for Fedora 39 - Free - Updates                                    7.7 kB/s | 2.9 kB     00:00    
RPM Fusion for Fedora 39 - Free - Updates                                    184 kB/s | 142 kB     00:00    
RPM Fusion for Fedora 39 - Nonfree - Updates                                  23 kB/s | 5.8 kB     00:00    
RPM Fusion for Fedora 39 - Nonfree - Updates                                 142 kB/s |  67 kB     00:00    
Package pipewire-alsa-1.0.0-1.fc39.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!

[not-a-dev-stein]

EDIT: Installing the pipewire-alsa package in the davincibox toolbox fixes it, might be something you'd like to look into doing by default.

pipewire-alsa is already included by default as of #29, two months ago.

In a fresh davincibox container:

akzel@davincibox:~$ sudo dnf install pipewire-alsa
Copr repo for distrobox-utils owned by kylegospo                                                                                                                                                                                                                                               10 kB/s | 1.5 kB     00:00    
Fedora 39 - x86_64 - Updates                                                                                                                                                                                                                                                                  107 kB/s |  23 kB     00:00    
Fedora 39 - x86_64 - Updates                                                                                                                                                                                                                                                                  3.1 MB/s | 8.3 MB     00:02    
RPM Fusion for Fedora 39 - Free - Updates                                    7.7 kB/s | 2.9 kB     00:00    
RPM Fusion for Fedora 39 - Free - Updates                                    184 kB/s | 142 kB     00:00    
RPM Fusion for Fedora 39 - Nonfree - Updates                                  23 kB/s | 5.8 kB     00:00    
RPM Fusion for Fedora 39 - Nonfree - Updates                                 142 kB/s |  67 kB     00:00    
Package pipewire-alsa-1.0.0-1.fc39.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!

Weird, I just git clone'd the repo a couple of days ago and used the setup.sh script. Maybe that's got something to do with it? Highly doubt it though.

[zelikos]

Weird, I just git clone'd the repo a couple of days ago and used the setup.sh script. Maybe that's got something to do with it? Highly doubt it though.

The script should pull in the latest container image, assuming a couple days ago was the very first time you had set up davincibox. (if not, #41 is on the ToDo list)

I'll double-check things in a fresh VM too

[not-a-dev-stein]

Oh shoot, it might have something to do with it, as I had tried davincibox a couple of months back but it didn't work for me at the time.

[zelikos]

Oh shoot, it might have something to do with it, as I had tried davincibox a couple of months back but it didn't work for me at the time.

Yeah, that would be it. Distrobox doesn't automatically pull new versions of a container image unless explicitly configured to, so if you already had the image, any new containers would be using that same old version.

You can run podman image pull ghcr.io/zelikos/davincibox:latest, then run setup.sh again to have the latest version

[queequeg0925]

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]

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! :heart:

[mtwb47]

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]

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]

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