MrSID Gen2 Encoding Problems
Greetings,
I have a client that requires Gen2 sid files. I have been attempting to encode for over a week now, and I'm getting a failure code of 9218 (memory allocation error). I'm running GE8 on a WinXP machine. I successfully encoded a Gen2 last week with a much greater input size, so I'm confused as to why this one is failing repeatedly. It will run until 94-97% completion, then fail with the above error. These are the settings I have.
MOS Width 125002 Height 180002. Input is TIF/TFW RGB 8 bit. The Mosaic Image size is 62.9GB and I'm encoding at 100:1 with a reported target file size of 643.7mb.
As I said, I encoded other imagery for this same project with output file sizes right at the 2GB limit, and they ran fine.
Is there a listing of error codes somewhere that I can reference? Im trying it again after changing my output directory and temp directory to an external dive with a terabyte of free space instead of the C drive with 500GB free hoping that it may be something to do with the network.
Any thoughts would be appreciated.
Thanks,
Brian
I have a client that requires Gen2 sid files. I have been attempting to encode for over a week now, and I'm getting a failure code of 9218 (memory allocation error). I'm running GE8 on a WinXP machine. I successfully encoded a Gen2 last week with a much greater input size, so I'm confused as to why this one is failing repeatedly. It will run until 94-97% completion, then fail with the above error. These are the settings I have.
MOS Width 125002 Height 180002. Input is TIF/TFW RGB 8 bit. The Mosaic Image size is 62.9GB and I'm encoding at 100:1 with a reported target file size of 643.7mb.
As I said, I encoded other imagery for this same project with output file sizes right at the 2GB limit, and they ran fine.
Is there a listing of error codes somewhere that I can reference? Im trying it again after changing my output directory and temp directory to an external dive with a terabyte of free space instead of the C drive with 500GB free hoping that it may be something to do with the network.
Any thoughts would be appreciated.
Thanks,
Brian