DPX import

[beaker]

what version of shake are you using?

[Tob]

4

(wow, that must be the shortest reply in history; better add some more text here between these brackets...)

[beaker]

hmm, strange. Try reading it in as a cineon (dpx is just a cineon file with metadata).

[Tob]

nope, no luck.
(Also tried the add "sys.dumpHeaderInfo= 0;" to-startup.h-file-trick at Apple's recommendation, but no difference there. I'll post as soon as I hear anything new from them)

Thanks for the hint though

[beaker]

that blows. Well a temporary solution might be to try having xnview resave them. Xnview reads just about anything out there. Also it has a command-line version called "nconvert" so you can batch convert them.
www.xnview.com

I've had a few problems with dpx the other day, but going the other way. I exported some dpx files out of the flame and shake read them just fine, but then when I rendered the dpx file out of shake with the meta-data copied back into the header, neither flame nor inferno could read them. I ended up resaving them out with xnview and then Flame and Inferno had no issues reading it.

Just curious, what data is contained in your dpx files? 10 bit log, 10 bit lin, 12 bit lin, etc...?

[Tob]

cool. I'll check them out. Thanks.
The files are in 10bit linear with gamma.

Yeah, you never know when the machines are going to pull a stunt like that. Had the same problem with the Smoke and plain ordinary iff files a while ago. Maybe it just version 7 acting up again - a lot of weird stuff has been going on since the upgrade; no quicktime import for example. :curious:

[MrElmo]

Where can you find the colorspace information about your dpx file? I also have a sequence and I need to know.

[beaker]

Just look at them. In most instances a log space file looks quite different then a linear one.

Also you can easily tell if you know the source of them. Film Scan 2k file its most likely log, tape transfer/hd rez and it's linear.

[Aneks]

we are doing a lot of .dpx work at the moment. I know that our datacine process is almost identical to what you described ; a spirit attatched to a daVinci 2k+. We are having no problem with the i/o of the .dpx files.

Is it possible that something is being set incorrectly in the daVinci portion of the process ?

For the most part this should be a pretty rock solid pipeline. My only caveat with all this is the problems we are experiencing trying to export to our black magic hardware in order to do 2k 10bit playback. After all this time it still seems that shake and black magic codec quictimes are not seemless.

[beaker]

Aneks: Between FCP 4 and 5 the blackmagic guys worked with Apple on their 422 codecs. So as of FCP 5, all the kona/blackmagic cards are supposed to use Apple's 8/10 bit 422 codecs by default instead of their own (thought they are still availiable for the newer 444 cards, legacy support and their YUV codecs are are actually better quality but as you mentioned, buggier at times).

[stopmo]

How do you add the startup.h fix? Where is it located in the package? We've been having problems with the picture being offset as if it is out of frame to the left.

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.