Welcome to our community

Be a part of something great, join today!

  • 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 :)

FCP XML 10bit project shows up 8bit in Smoke

Allan Stallard

Well-known member
Joined
Aug 7, 2007
Messages
109
Reaction score
0
Points
0
Website
www.animalspots.com
We have a FCP project, sequence, and media that is 10bit. XML conforms fine to 10bit when brought back to FCP.

When opening XML in Smoke it's 8bits. Media that is shared gets imported @ 8bits too when using the XML module.

Media manually imported remains 10bit, but the XML will not link to that 10bit media.

Smoke 2009 ext1 sp1

XML shows up as 10bit in text editor
 
OK so after lengthy support calls here is the skinny:

Autodesk helps point to the culprit. Inside the XML is "colordepth=24" even though throughout the XML it lists the FCP project and media as "10bit"

So we discuss this at length with Apple support and the ignorant woman insists that "just because it says colordepth 24 does not mean it's not 10bits"

I am not impressed.

The workaround is to edit the XML where it says 24 to say 30 and save it. NOW it's 10bits.
 
Xml

Xml

Hi Allan,
Thanks for the post.
I am sure you sequence is set to 10-Bit in FCP via seq settings.
So basically, FCP XML export does not export the XML in 10-Bit.
That is the problem you found.
Was it a pro help desk at apple ?
 
Hey Snow, I don't know if it was "pro help desk" at Apple. Our editor had called in and we gave them our "code" and then we could discuss the problem with them. But yes on the other question. The editor and the support person tried every combination and resolution and never came up with a colordepth of 30. The XML read 10 bit throughout for things liek FCP SEQ 10bit, and the media, but the XML itself had a colordepth=24 imbedded and that was what Smoke was reading.

Now saying that, I will now quote someone else:

"Another thing to keep in perspective is that FCP costs less than my
iPhone bill for a year. While on the other hand Smoke costs more than
my house and it can't figure out for me that the XML file has a
conflict and then ask me if I want to it to stonify the clip at 8bit
(based on the colordepth) or 10bit (based on the clip bit setting)."

Makes you think.
 
Good point!
 
......................

Here is the proper way to deal with this in smoke/flame that was posted on another board. Thank you to the original poster:

"If you import the XML and then go to the Library BEFORE capturing, you will
have an empty sequence sitting in your library with no media. It will have
all the settings you are talking about including the incorrect 8 bit
setting.

At that point all you have to do is reformat the sequence under the
tools>Unlink/Relink>reformat menu to 10 bit. Then go to
tools>Unlink/Relink>recapture and it will put you back to the same capture
menu as you had when you first imported the XML, but at the correct 10 bits.

You can also now use this sequence to link to your manually imported 10 bit
media as well using the recapture from reel."
 
Back
Top