[Greg Knollmeyer]

Resolve takes FCPX XML natively and this thread is a few years old. I haven’t had issues with FCPX output and Resolve since that time. I have used X to 7 and 7 to X occasionally to get stuff in and out of Premiere. They are cheap and good solutions for that. Though generally I just try to stick to one editing program and tend to prefer FCPX as it is quicker, cheaper, and doesn’t have that darn software as service nonsense attached.

Anyway, editing the xml is easy. Getting the right syntax can be difficult. I’d recommend making a copy of the XML. Then open the copy in Text Edit or some other text editor. You can then look for inconsistent directories etc. and fix them as needed. It may or may not work for the issue you’re having.

[Greg Knollmeyer]

I’ve gotten resolve to open without the chassis error. I did have to set the Energy Saver preferences twice-once while plugged in and again while running on battery. However with restarts that error doesn’t come up in both cases.

I am having an issue with Creating a New Resolve Database. When I get through the splash screen, I encounter a message telling me I don’t have a database. Fair enough, but when I go to create one, I seem to only be able to do something with a preset host of 127.0.0.1. When I enter in information there to create a new DB, I get the error “could not connect to server:connection refused …is the server running and accepting connections”. When I installed on my last machine, I think it just defaulted to a new db or I created one without issues. Any idea what is off on my configuration here?

Thanks,
Greg

[Greg Knollmeyer]

Today I got a chance to run a couple more experiments. When I break apart compound clips and export XML from FCPX, I still get the “no valid sequences” error in Resolve. However, I am now getting reliable positive results when I change the version indication within the XML to 1.0. This works fine. So I’m able to get in and out of Resolve reliably now.

Also, I use Xto&7 from Intelligent Assistance to get FCPX stuff into Premiere etc. Running the FCPX XML through that and then taking that into Resolve works as well. It might be a decent $50 investment. I don’t get any kickback from them; but here is the link https://assistedediting.intelligentassistance.com/Xto7/.

[Greg Knollmeyer]

So I tried another few experiments. Earlier I tried editing the XML to no avail, both changing the XML version from 1.1 to 1.0 and fixing what seemed to be an incorrect path. At that time, I had reinstalled Resolve once and I was working on an external drive driven by an eSATA card.

Later today I agin uninstalled Resolve, then repaired permissions, reinstalled Resolve. I exported from a junk project on my internal HD. Got the same error. But when I opened the XML and edited that to indicate version 1.0 rather than 1.1, my simple sequence came up just fine in Resolve.

Sadly I don’t know what is causal or coincidental in this. Perhaps reinstalling, perhaps the local drive, perhaps the permission repair. I’ll give it another try, just changing the XML version working from one of my external drives when I’m back in my office and post whatever I find out. I’d be curious if anyone else has tried any of this.

[Greg Knollmeyer]

I have been running this round trip for a while and had no problems. For the first time in a month, I went back to do it again and go the no valid sequence error. I looked at the xml and noticed that there was a problem with the reference to one clip. The xml reported a file in the “original media” directory even though the source was the “transcoded media/high quality media” directory. So I fixed that but got no satisfaction…

I did run the Black Magic uninstaller from the dmg and then re-installed. Still no luck. I’m hoping someone finds a solution because I need this back.

[Greg Knollmeyer]

OK, so this may be silly typing to myself and all; but I had one more idea. I took the clip that was transcoded to pro-res in FCPX–the one that showed the super-whites in FCPX, and placed it on my timeline within Premiere Pro. No superwhites appear on the waveform, in PP and there isn’t any recovery for them

This makes me think that I’m still missing some setting or basic piece of info or CS4 has some problem recognizing superwhites if the clips are not in their native format. I welcome others to the conversation…

[Greg Knollmeyer]

Just a follow-up. I did a little more testing with all available settings including 10 bit in the Avid codec. Still no luck with the super-whites showing up. I do notice better results with Pro-Res (no gamma issues); but still no super whites. However with ProRes, I don’t have the codec options to work with. When I click on the codec options, nothing comes up as with the Avid codec.

Finally, I went into FCPX which I’ve been playing with. When I imported/transcoded from there, the superwhites show up and I can recover a little detail in the highlights.

So I’m beginning to wonder if there is an issue with Adobe Media Encoder’s ability to work with those codecs. I am using CS4, so that may make a difference. I’m waiting/hoping that in spring, CS6 will be out and I can pay for just one upgrade.

Anyway, I’m still wondering if there is any point to transcoding to an intermediate codec when working with footage from different cameras/sources in PP and Resolve. So far, I think not; but I keep reading the reverse. Any ideas/opinions?

[Greg Knollmeyer]

Thanks for the help. I didn’t know layer styles caused that sort of interaction. I pulled down the file as well. Obviously you’re right about the clip.

[Greg Knollmeyer]

That is a kind offer. If anyone has time/interest you can download the file at https://gregknollmeyer.com/files/ShadowNoShadow.zip. The archive has the aep plus a free clip that I was using within the water text. So it is 128 mb.

The project has a comp where shadows work fine, the precomped water text, and the problem comp. There’s nothing much going on in either of these, I was just beginning to set the stage when I ran into an issue.

Thanks

[Greg Knollmeyer]

Thanks to all for your suggestions. I am still looking for a solution

–I disabled openGL and saw no changes. I toggled it a few times during problem solving but saw no difference.
–I moved the light and objects around a bit and couldn’t find any shadows. I also added two other simple solids, a non-comped text solid & a rectangle (pictured below); but still can’t come up with any shadows.
–I toggled draft 3d, but that hadn’t been on.
–I also lowered the light intensity and played with settings between 80 & 150. I know it is high; but I thought more contrast might have come from more light.

So I remain confused about this one. I did up a new comp with what I think are the same settings and I get shadows on basic rectangles. Odd. Any other ideas.