You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: