I think that exit code is a Windows DWORD (unsigned int) converted to a
signed int. Converting the unsigned value (3221225477) to hex (which is
how Windows typically represents common exit codes) gives you
0xC0000005, which refers to an access violation (i.e. segfault).
On 6/25/2020 9:59 AM, Larry Gritz wrote:
So it writes no output image, but there is no specific error message,
nor does it crash?
Just out of curiosity, can you reproduce the *exact* command line for us?
Can you try with the extra flags at the beginning: --debug --runstats
--info
and tell us everything it prints?
On Jun 24, 2020, at 11:33 PM, Moe Myint Htet
<moe.technicalart...@gmail.com
<mailto:moe.technicalart...@gmail.com>> wrote:
Ther return code is -1073741819.
On Thu, Jun 25, 2020 at 3:03 PM Larry Gritz <l...@larrygritz.com
<mailto:l...@larrygritz.com>> wrote:
Off the top of my head, it looks correct...
What resolution are the r, g, b, a files to begin with?
What happens, how does it fail? Is it a crash? An error message?
Or does it complete but the output image is not what you think it
should be?
Is there anything unusual about the execution environment or
hardware, like a nonstandard OS or a very constrained amount of
memory?
Which version of OIIO are you using?
-- lg
On Jun 24, 2020, at 10:56 PM, Moe Myint Htet
<moe.technicalart...@gmail.com
<mailto:moe.technicalart...@gmail.com>> wrote:
Hi Larry,
This is Moe from Tokyo.
I couldn't convert 8K textures with oiiotool, and was wondering
if you could shed some light.
If I use the same command with 4K textures, it works without any
problem.
Here's the command line I'm using.
r = input jpeg texture path
g = input jpeg texture path
b = input jpeg texture path
a = input jpeg texture path, and I'm using its R channel for alpha
output = output tiff texture path
oiiotool r --ch R g --ch G --chappend b --ch B --chappend a --ch
R --chappend --chnames R,G,B,A --resize 8192x8192 --compression
lzw -d uint8 -o output
If there's no known limitation for converting large textures,
could it be that the command I'm using is wrong?
Thank you for your time.
Moe
--
Larry Gritz
l...@larrygritz.com <mailto:l...@larrygritz.com>
_______________________________________________
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
<mailto:Oiio-dev@lists.openimageio.org>
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
_______________________________________________
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org <mailto:Oiio-dev@lists.openimageio.org>
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--
Larry Gritz
l...@larrygritz.com <mailto:l...@larrygritz.com>
_______________________________________________
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
_______________________________________________
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
