Closed Lawrence58 closed 6 months ago
The hex value changes with each sequence.
No, it is a multiplier (x
, not 0x
) for the count of instances of the issue, looks like I need to find a better and more explicit way to display that. Here it happens in 17373 files.
Can you explain this situation to me please?
The DPX header has a total image file size
field e.g.:
0000000 Generic section header (1664 bytes)
0000000 File information (768 bytes)
0000000 Magic number: SDPX
0000004 Offset to image data: 8192 (0x00002000)
0000008 Version number of header format: V2.0
0000010 Total image file size: 18153472 (0x01150000)
[...]
(I used "mediainfo --Details=1 FileName.dpx)"
And we check that the value of this field matches the actual file size. Could you check that this is the case? If this is the case, please share a sample file so we can see why the warning is displayed.
MediaInfo
MacOS
Thanks. That explains it. And, the number of occurrences 17373 matches the number of files in the sequence.
So the DPX file is not conforming to the specs, and RAWcooked does its job by warning you about that. Depending on other file characteristic, it may be just the tool which is buggy by "forgetting" 4 KiB or maybe there is an extra (non conforming) content after the file not part of the DPX content.
You can disable the conformance checker if you prefer, with --no-conch
.
I am trying to troubleshoot something. I have a set of DPX sequences from a film scanning vendor. When I rawcooked them I get a warning. This is what it looks like for one of the sequences. The hex value changes with each sequence.
Warning: non-conforming DPX total image file size (x17373). At least 1 file is not conform to specifications.
Is the hex number the file size of the offending file or something else? I have checked the file size of some of the DPX files in the sequence referenced above but none of them are close to that. Can you explain this situation to me please? Thx.