July 2, 2021 at 8:26 pm
TL;DR ‘Studio vs. Free, project files not opening from Studio in Free ver? Any quick advice/links for Premiere < DaVinci transplants?
We have an interesting issue going on in our office ecosystem. We talked management in to getting us a Studio license to DaVinci, two of us use it most (I absolutely LOVE it so far, having been stuck in the Premiere world as long as I have..) So we have used our two licenses on two separate machines in the office.
We have one more editor on one more machine who has been color correcting his exports out of Premiere in DaVinci, bass-ackwards if you ask me so I’ve been trying to get him more in to the Edit and Cut windows to get him comfortable with the program, I’d like to completely replace our dependence on Adobe by the end of the year and am trying to get everyone on board.. At least in the video department!
There’s the set up!
Now the problem..
Since he’s stuck in the free version until I can talk management in to another license, he’s importing my Studio project file in to his free version. When he opens my project file he immediately gets a ‘You have reached a limitation with DaVinci Resolve’ dialogue box. It doesn’t say what the problem is just prompts to purchase, if he selects ‘Not now’, he gets another dialogue: ‘Unable to open project’. We made due with an XML file out of Premiere for this project but I’d like to be set up better for the next project. (amazing to me XML is STILL the go to file format for something like this all these years after FCP7!)
It was my understanding that you could still ‘open’ a project file from Studio in a free version.. was I wrong? The big question: ‘why the heck won’t Resolve open my file?!’
But another general question for the room: anyone have any good links for folks trying to, or ‘being forced to’, migrate over to DaVinci from Premiere?
July 2, 2021 at 9:56 pm
So, “TLDR”… ‘You have reached a limitation with DaVinci Resolve’
generally indicates that you have used a feature in the Studio version that the Free version does not support. Could be Noise Reduction, could be a premium plugin / transition/ grade, OFX or some other, including a UHD resolution limitation. You’ll probably have to weed it out…
July 3, 2021 at 2:38 pm
Would you say that the best quick solution for opening one of my Studio projects would be the XML file? (for something he needs to turn around quickly, I’m worried about management getting upset with the amount of time spent transferring projects between machines)
July 5, 2021 at 12:37 am
I don’t understand the false economy here. Best quick solution is to buy another license pronto. XML is not complete compared to importing a project. Try exporting just a timeline as there may be things within a project that won’t translate. Also I presume you are both on the same version (ie 17.2.2) even though one is Studio.
The price of a license is a couple of wasted hours and unlocks a whole lot of other goodies like NR and more OFX plugins.
July 6, 2021 at 4:47 pm
I’m going to back up Michael on this one. The time you spent (and will spend) on this is worth more than two Studio licenses… and you get a FREE DaVinci Resolve Speed Editor with each one. It is an astonishingly good deal… and such a simple solution to all of your problems.
July 9, 2021 at 8:21 am
Unfortunately, you are telling the guy who is not in charge of the purse strings to spend money, which he has said he us trying to get done…but that doesn’t help now.
If the project won’t open at all, I’d guess it is a project resolution issue…too big for the free version. Usually if its a plug in, you get the watermark on screen, but the project will open.
I’d try opening the project in studio, change it to HD, export the project, and see if it opens. I’m not sure what the limitation size is…if uhd is allowed in the free version, but I’d start there.
July 9, 2021 at 1:49 pm
Thanks so much Glenn for stating what I was getting ready to say again..
We do have some ‘larger than the free version can handle’ footage in that particular timeline.. I will try that sir thank you!
Log in to reply.