Oh! Thanks guys! That's for sure a ticket from back in the days. =)
The path is 97 characters long.
On 2013-12-19 13:41, Peter Crossley wrote:
Hi Henrik and Deke,
I've looked into this, and it looks like it's caused by a conflict in
the keys used for metadata items. The dpx reader plugin correctly reads
the imageFileName field and sets it to input/filename tag. However the
base Read op then overwrites this entry with the actual path to the file.
It looks like imageFileName is being written to the wrong tag, and we
need a seperate dpx/imageFileName tag.
The bug 7114 - Some DPX header fields not coming in as MetaData has been
re-opened and updated with this issue.
Cheers,
Peter.
Deke Kincaid wrote:
Sorry, didn't realize ImageFileName was a existing metadata field. I
thought you we're just adding your own one with that name :)
One issue from researching this a little bit. It appears that Nuke
only sees the metadata field if it has less then 100 characters in the
ImageFileName metadata field. You can see this in the dpximage header
file from Nuke's SDK here:
http://docs.thefoundry.co.uk/nuke/80/ndkdevguide/examples/DPXimage.h
char imageFileName[100]; // image file name
is the file path longer then 100 characters?
--
Deke Kincaid
Creative Specialist
The Foundry
Skype: dekekincaid
Tel: (310) 399 4555 - Mobile: (310) 883 4313
Web: www.thefoundry.co.uk <http://www.thefoundry.co.uk/>
Email: [email protected] <mailto:[email protected]>
On Sun, Dec 15, 2013 at 9:48 PM, Henrik Cednert <[email protected]
<mailto:[email protected]>> wrote:
Thanks Deke and Chris.
Yes, that for sure fill my needs.
http://www.creativecrash.com/nuke/script/dpxinfo-tcl
Thanks a bunch
On 2013-12-15 22:42, Chris Noellert wrote:
I think Hakan, while he was still at Filgate, wrote a tcl dpx
parser called dpxinfo which reads the whole header and dumps
it. Check creativecrash. Might be what you need...
Sent from my iPhone
On Dec 14, 2013, at 3:29 AM, Henrik Cednert <[email protected]
<mailto:[email protected]>> wrote:
Hi
Nuke only accesses a predefined set of metadata headers.
How does people manage custom image metadata in their
pipe? I need to access 'DPX/ImageFileName' for a sh*tload
of shots but dunno how. =/ Need a point in the right
direction.
Anyone know why TF decided to go this way and only work
with a few predefined headers instead of reading all
metadata in the input? Is it limited in the read node or
in the 'ViewMetaData' node?
Thanks! =)
Cheers
--
Henrik Cednert
cto | td | compositor
Filmlance International
www.filmlance.se <http://www.filmlance.se>
_______________________________________________
Nuke-users mailing list
[email protected]
<mailto:[email protected]>,
http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected]
<mailto:[email protected]>,
http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
--
Henrik Cednert
cto | td | compositor
Filmlance International
www.filmlance.se <http://www.filmlance.se>
_______________________________________________
Nuke-users mailing list
[email protected]
<mailto:[email protected]>,
http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected],http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
--
Henrik Cednert
cto | td | compositor
Filmlance International
www.filmlance.se
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
