Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

An FCP XML to Redcine XML Script

flameop said:
no.. was a diff one.

I did another and it worked.

Unsure why 2nd xml failed.

codec prores in fcp seq settings rather than redcode?

25fps clips?

.. airplanes! anywhere interesting ?

s
Click to expand...

Nah just a bidnatz meeting.

25fps clips might do it, the problem is that FCP exports a 23.976 fps timeline as 24fps in XML. So I just hardcoded it because everything I do is 23.976. I'll make it selective for 25fps.

Prores downconverted proxy clips should work, how are they named? And where are they located?

IBloom
 
successful test!

successful test!

hey ibloom, just wanted to congratulate you on your great script! and since you said before, that you were the only one who got this to work so far, i wanted to give you a shout: it works here too!

only when i reconnect the re-encoded footage by RedCine in final cut, i get the following message:
error_message.png


it's not a big deal, when pressing okay it reconnects flawlessly. it might only be a problem when working with thousands of files (which we are planning to...) and having to confirm the dialogue hundreds of times. any thoughts?

so, well done! and if only RedCine would read the handles information, then your tool would already be a very clean and workable workflow. even for big productions like ours.

having seen your tool, i think the guys at RED should just work on RedCine to simply read the xml handle information first and foremost. it seems a quite simple and small thing compared to most other projects and suggestions in this forum.

then we could:
1. edit in fcp with the red proxies.
2. export the finecut with fcp xml.
3. translate the generated xml with your great tool and...
4. import the xml into RedCine.
5. in RedCine we export only the used shots in the finecut with their exact length to our preferred online codec & resolution (f.ex. ProRes HD).
6. then go back to final cut and media manage the proxy finecut sequence to the new ProRes resolution and...
7. reconnect this sequence with the ProRes footage exported from RedCine.
8. once reconnected, we are all set for nearly perfect (at least for broadcast) ProRes HD 16bit color grading in color.

these steps are quite easy and quick (apart from the lengthy conversion of the clips to ProRes) to do. and not much can go wrong. so this could be the first valid workflow for fcp & red for large scale projects.

so as i understand ibloom, there is nothing you can do right now, right?

and: hey guys at red: it can't be too hard to have RedCine read its own handles in its own xml file format? RedCine can export them, why not import them too? make the xml import work and i think many many people would stop complaining about a valid workflow!

or am i missing something?

thx again for a great tool, ibloom! we are getting closer...
cheers
tobeyonekenobi
 
tobeyonekenobi said:
hey ibloom, just wanted to congratulate you on your great script! and since you said before, that you were the only one who got this to work so far, i wanted to give you a shout: it works here too!
Click to expand...

It makes me happy that it's working for you.

tobeyonekenobi said:
only when i reconnect the re-encoded footage by RedCine in final cut, i get the following message:
error_message.png


it's not a big deal, when pressing okay it reconnects flawlessly. it might only be a problem when working with thousands of files (which we are planning to...) and having to confirm the dialogue hundreds of times. any thoughts?
Click to expand...
Not a big deal, but I'm working on round tripping, which will allow you to pull in a new XML that lets you skip the reconnect and the error message.
tobeyonekenobi said:
so, well done! and if only RedCine would read the handles information, then your tool would already be a very clean and workable workflow. even for big productions like ours.

having seen your tool, i think the guys at RED should just work on RedCine to simply read the xml handle information first and foremost. it seems a quite simple and small thing compared to most other projects and suggestions in this forum.

then we could:
1. edit in fcp with the red proxies.
2. export the finecut with fcp xml.
3. translate the generated xml with your great tool and...
4. import the xml into RedCine.
5. in RedCine we export only the used shots in the finecut with their exact length to our preferred online codec & resolution (f.ex. ProRes HD).
6. then go back to final cut and media manage the proxy finecut sequence to the new ProRes resolution and...
7. reconnect this sequence with the ProRes footage exported from RedCine.
8. once reconnected, we are all set for nearly perfect (at least for broadcast) ProRes HD 16bit color grading in color.

these steps are quite easy and quick (apart from the lengthy conversion of the clips to ProRes) to do. and not much can go wrong. so this could be the first valid workflow for fcp & red for large scale projects.

so as i understand ibloom, there is nothing you can do right now, right?
Click to expand...
I don't understand what your asking? We are bound by Redcine, yes, but I think this exporting of selects is a good workflow for many projects because it makes it possible to keep cutting with the footage even after you Redcine. Handles would be good in some situations but could be problematic.

tobeyonekenobi said:
and: hey guys at red: it can't be too hard to have RedCine read its own handles in its own xml file format? RedCine can export them, why not import them too? make the xml import work and i think many many people would stop complaining about a valid workflow!

or am i missing something?
Click to expand...
I think they are working on it.
tobeyonekenobi said:
thx again for a great tool, ibloom! we are getting closer...
cheers
tobeyonekenobi
Click to expand...
 
Handles work!!

Handles work!!

hey ibloom! thanx so much for your quick reply.
i have tried your droplet again with the new RedCine release 82 and guess what: it works perfectly now, even with handles!!!!

in my opinion this now makes your solution the first valid red workflow for big projects, where it would take too much time to re-encode the whole original footage in the beginning, and where even the final cut of a project is too big, to re-encode full takes.

with the working handles xml-import we can now re-encode and do a first light in RedCine, for only exactly the amount of frames that are used in the cut! this is absolutely great and crucial for large-scale project like ours! so congratulations! and thank you again.

since this is working so beautifully now, i was wondering if you are working on the mentioned 'roundtripping' feature. this would be awesome, because the error messages in final cut when reconnecting could get really annoying when reconnecting thousands of clips...

any other features and possibilities you are thinking about? we are glad to help and test for you!

cheers and keep up the great work.
tobias
 
Yep works for me too, well done IBloom!
 
Roundtripping feature is in debugging phase now. It's likely I will finish it tomorrow on the plane to L.A.

New website and lots more features coming up.

Let me know what features you need.
 
that sounds great ian! looking forward...

features:

- it would be great if we can get control over the 'format setting' in the project-tab in RedCine: i would like to have the frame-rate automatically set at 25fps, the format set at 4k 2:1, and the aspect ratio at 16:9. i imagine one would choose between the different settings when using the droplet and then save a default setting, which the droplet would use each time one uses it.

- similar thing in the output tab in RedCine: it would be great to be able to set a default output settings for the RedCine 'Output Settings', such as which Quicktime Codec to choose, which format and what output path. Right now, i have to choose that every time i do an import. maybe the xml file can set those settings automatically?

- is there any way around having to load ALL the original media into RedCine first, and then load the xml-file? right now, it is not a problem yet, but i fear with thousands of clips in a big project, that simply loading all the footage into RedCine first, will take a long time. it would be great to simply load the xml and the RedCine then finds only the shots it needs.

so far my ideas for more features. i have no idea if these are even possible to implement simply through xml or if this had to be done by RedCine developers. anyway, hope this helps.

cheers, tobias
 
ibloom,
With your updates, can you please post a simple list of instructions for those of us who have not yet tried it? Sounds like there may be a couple of hoops to jump through. And make sure we are going to the correct download location.

Also, does it deal with file names correctly? We are editing the "_H" QTs.

WELL DONE!!!
 
tobeyonekenobi said:
that sounds great ian! looking forward...

features:

- it would be great if we can get control over the 'format setting' in the project-tab in RedCine: i would like to have the frame-rate automatically set at 25fps, the format set at 4k 2:1, and the aspect ratio at 16:9. i imagine one would choose between the different settings when using the droplet and then save a default setting, which the droplet would use each time one uses it.
Click to expand...
My new build defaults to 4K 2:1 and supports all timebase frame rates from FCP including 25fps.
tobeyonekenobi said:
- similar thing in the output tab in RedCine: it would be great to be able to set a default output settings for the RedCine 'Output Settings', such as which Quicktime Codec to choose, which format and what output path. Right now, i have to choose that every time i do an import. maybe the xml file can set those settings automatically?
Click to expand...
Currenlty there is no way to access most of the output parameters of Redcine through XML. If and when Assimilate is able to include that in the build, I'm already ready to export it over from FCP.

In the meantime it is easy enough to rescale you image simply by selecting the ALL button in the Shot Framing dialog after you change your sequence settings in Redcine.

tobeyonekenobi said:
- is there any way around having to load ALL the original media into RedCine first, and then load the xml-file? right now, it is not a problem yet, but i fear with thousands of clips in a big project, that simply loading all the footage into RedCine first, will take a long time. it would be great to simply load the xml and the RedCine then finds only the shots it needs.

so far my ideas for more features. i have no idea if these are even possible to implement simply through xml or if this had to be done by RedCine developers. anyway, hope this helps.

cheers, tobias
Click to expand...

I think most of what you are asking for is limited by the current XML capabilities of Redcine. My understanding is that they plan to include more of these things in the future. In the meantime, I have a few work arounds I'm implementing and some detailed instructions in the works.

IBloom
 
Paulee said:
ibloom,
With your updates, can you please post a simple list of instructions for those of us who have not yet tried it? Sounds like there may be a couple of hoops to jump through. And make sure we are going to the correct download location.

Also, does it deal with file names correctly? We are editing the "_H" QTs.

WELL DONE!!!
Click to expand...

Currently any filename will work if it is formatted in this way:
{CameraReel}_{Shot Number}_{Date}_{Anything} will work. The script looks for the underscore seperators and ignores everything after the first three.

So:
A020_C011_071207_P.mov
A020_C011_071207_M.mov
A020_C011_071207_H.mov
A020_C011_071207_M_ProRes422.mov
etc. will all work. Just keep the begining of the filenames the same and keep them in the same folder as the .R3D
Downconversion of proxies through Compressor to ProRes is a great way to cut Redcode today. I'd suggest doing it this way. That is how both of the editors on the dramatic projects I currently have in post are working.

I'm considering ways to do it so that you can have your ProRes on a seperate volume for example, any suggestions are welcome.

IBloom
 
I can't seem to get it to work for some reason. Do you think it is a problem mixing 2k and 4k in the same timeline. I get the Failed to load construct error and nothing happens. I am using the new version of REDCINE and still no luck.
here is what i am doing,

1. Export .XML file from FCP.

2. Drag and drop onto the Script which opens terminal. I know something is happening but not sure what.

3. Open REDCINE. Load in all the clips that correspond to my FCP Timeline.

4. Take the XML file from FCP that i dropped onto the Script and try to open it in REDCINE.

5. I get Error, "Failed to Load Construct" Nothing else happens.

What am i doing wrong? Much appreciated.
 
mikeburton said:
I can't seem to get it to work for some reason. Do you think it is a problem mixing 2k and 4k in the same timeline. I get the Failed to load construct error and nothing happens. I am using the new version of REDCINE and still no luck.
here is what i am doing,

1. Export .XML file from FCP.

2. Drag and drop onto the Script which opens terminal. I know something is happening but not sure what.

3. Open REDCINE. Load in all the clips that correspond to my FCP Timeline.

4. Take the XML file from FCP that i dropped onto the Script and try to open it in REDCINE.

5. I get Error, "Failed to Load Construct" Nothing else happens.

What am i doing wrong? Much appreciated.
Click to expand...

If the script is working properly a new file .Redcine.xml will appear next to the FCP XML. That is the only file that will work in Redcine.

If you want, post your FCP XML and the output you get in terminal here as attachments.

Or you can wait for the new alpha version, tommorrow night hopefully, it's a complete rewrite, I just have some other work I'm doing today.

A GUI is two versions away.

IBloom
 
Yeah, it doesn't create a new file next to the final cut XML file like you said above. Maybe do i have to update python or something. if not i will wait for your new version tomorrow.
Thanks
 
You must log in or register to reply here.
Back
Top