Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Imf::OutputFile Produce binary different files #230

Closed
haotj opened this issue Apr 20, 2017 · 3 comments
Closed

Imf::OutputFile Produce binary different files #230

haotj opened this issue Apr 20, 2017 · 3 comments
Assignees
Labels
Question A question or a request for help.

Comments

@haotj
Copy link

haotj commented Apr 20, 2017

I use both
OutputFile (const char fileName[], const Header &header, int numThreads = globalThreadCount());
OutputFile (OPENEXR_IMF_INTERNAL_NAMESPACE::OStream &os, const Header &header, int numThreads = globalThreadCount());

I have a implemented pure virtual functions of OStream with a big buffer(memset to 0). Once it's finished, I write the buffer to disk which produces identical image to the const char* fileName[] version. However, when I tried to do a binary diff, I see from 0x00000130 to 0x0000230, they are different.
diff

Now, both images "look" the same, and have same pixel values, I'm not sure why the data is different. The output file using the fileName ctor, actually produces identical binaries, so I don't think it's caused by un-initialized memory.

@oleksiivorobiov
Copy link

Make sure you dump file on disk after OutputFile destructor call. It writes this values inside destructor

@cary-ilm
Copy link
Member

Looking into the OpenEXR issue backlog. Is this still an issue? Does the suggestion resolve it?

@cary-ilm cary-ilm added the Question A question or a request for help. label Jun 29, 2019
@cary-ilm cary-ilm added this to the Needs Attention milestone Jun 29, 2019
@cary-ilm cary-ilm self-assigned this Jul 4, 2019
@cary-ilm
Copy link
Member

cary-ilm commented Jul 8, 2019

Closing the issue for now, feel free to re-open or file a new issue if you need further help.

@cary-ilm cary-ilm closed this as completed Jul 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question A question or a request for help.
Projects
None yet
Development

No branches or pull requests

3 participants