[Rodrigo Lizana]

I follow you about Log and Transfer.

Yes, it´s pretty easy to create dailies with Resolve, even with 3D preview LUTS applied but it´s not something I´m not willing to do, it´s just this computer cannot run Resolve.

A new workflow comes to my mind. One is having Prores Proxies delivered by the Codex Vault we are using to clone and archive the footage (see we are not that obsolete 🙂 ). In that way we can keep the original Prores 444 files on the Resolve suite and have editors deliver just the 422 Proxy files. When finished they should be delivering the XML file and on the grading import the XML file into a new final 444 project. All this assuming the Codex Vault won´t create a “v” letter at the end of the proxy clip like FCP 7 does.

BTW, this “v” letter is really strange. The computer does not see those proxy files as quicktime, it has no .mov extension but FCP does indeed recognize them and I was able to edit them even with the original hard drive (the one with the 444 clips) ejected. Just weird.

Rodrigo Lizana
Pixine

[Rodrigo Lizana]

[Shane Ross] “Normally the offline/online workflow in FCP only works if you use Log and Transfer. But the media managing option has been used by a few, but it’s not as solid as Log and Transfer to Proxy, and then batch capture at full res.”

Do you know if there is a plug in available to add Log and Transfer support for Pro Res in FCP 7 ?

Thanks in advance

Rodrigo Lizana
Pixine

[Rodrigo Lizana]

Ok it works,…with a few bugs. This was my experience in case somebody else needs this rare workflow.

First the recompressed files adds a “v” at the end of the name so you have to reconnect each clip manually as the name differs from one another. Because of this the “reconnect all files in relative path” option to ease the connection does´t work.

You have to create a 444 project before importing the XML otherwise it will create a Proxy 422 sequence instead of 444.

What´s nice is that you can deselected the applied filters from the proxy sequence, as this project gets 2.39 mask but this has to be done at the end otherwise resolve will grade the black bars outside the 2.39 area.

thank you very much Shane for your help. If you want to add something else, please do it so as i only have done test so far. No real work.

Thanks again !!!!

Rodrigo Lizana
Pixine

[Rodrigo Lizana]

Thanks again Shane !!.

Ok, did it your way.

Now I have a new project (which I saved as online inside the internal HDD along with the recompressed proxy files). Created a Proxy sequence, did a few cuts and I´m ready to bring that back into a 444 project (from which I´ll be XML it into Resolve). But I´m lost there.

also I´m not able to eject the drive with the original files because it says FCP is using it, even if I close the 444 project and remain only with the proxy one.

Thanks again

Rodrigo Lizana
Pixine

[Rodrigo Lizana]

I shane, thanks for the answer.

No need to do the resolve test. Already know I can go back and forth with an XML from FCP 7 into Resolve.

My struggle is how to create a proxy sequence in FCP 7 in order to edit fast and light and then be able to transfer all those cuts into a new FCP 7 sequence, but this time in the original Prores 444 format.

I tried creating a 444 sequence, imported a few clips in it and then did a media manager offline which created a new proxy sequence but no proxy clips out of the 444 files. They all appeared like media offline.

Will keep testing. Anyadvice will be greatly appreciated.

BTW, I´m not that obsolete but this prom is a collaboration between many people and FCP 7 was the software chosen.

Thanks again

Rodrigo Lizana
Pixine

[Rodrigo Lizana]

While I haven

[Rodrigo Lizana]

I

[Rodrigo Lizana]

I

[Rodrigo Lizana]

Hope you get well soon. As an ex-motocross racer, I know the effort and pain it takes to come back to your regular life from a serious injury. Patience is a necessary virtue to go through this kind of test.

Best wishes for a good and fast recovery.

Rodrigo Lizana
PIXINE
http://www.pixine.cl
rlizana@pixine.cl

[Rodrigo Lizana]

Try capturing using the HD-SDI output of the 1200A. If the problem dissapears then probably there