Show us some code so we do not have to guess what you are trying to do. Also you could try posting the image you are attempting to load so we can look at it. Does the image load with LoadFromFile(AFilename)?
The file you sent me does not open in any program including commercial apps. When the file is loaded it is reported as corrupt. ImageEn loads the file with LoadFromFile but it is blank.
When Fabrizio looks at the file I assume he will advise you what the problem is. You can fix the file so it loads into ImageEn with LoadFromFile by using SaveAs in ACDSee.
This file cannot be open using current version of ImageEn (this is a gray scale with four channels). Next version will be able to read it: however only 64 bit version will be able load it (or using the external ielib.dll library for 32 bit).
quote:Next version will be able to read it: however only 64 bit version will be able load it (or using the external ielib.dll library for 32 bit).
The code of yet another 32bit feature becoming unavailable because it's moved to the closed-source 32bit ielib.dll? Really? Why am I paying for the (as advertised!) full source code version once again ... ?
You sent me a link to a 64bit version because you insisted that the code of the 32bit version of ielib.dll is not part of the full source distribution we all paid for. Do I really have to link in the thread where you stated that publicly?
Sorry Uwe, but I don't understand what you mean. 32 and 64 bit versions of ielib share the same source code (it is just a parameter of Visual Studio project). I really don't know what you need more.
At the time we had the original discussion, we considered the use of IELib32 as purely optional, but we then realized that there may be situations like this (where it is not possible or practical to add the feature to the native release) so decided to make the source for both versions available.
The native source of ImageEn has always been the priority in our development and the use of DLL's is not expected to change that. We initially only expected to use a DLL for the 64bit version (required for compatibility), but it was hard to ignore the performance benefits offered by IELib in the 32bit version too (which we could not have achieved compiling under Delphi)
Also, use of the DLL does not mean a reduction in native code as it generally only replaces code that is supported by obj files anyway.
Search
Problem with loading J2K (jpeg2000)
Topic Locked
Posted - Mar 09 2013 : 12:44:30
