| Author |
 Topic  |
|
|
klausdoege
Germany
389 Posts |
 Posted - Sep 20 2015 : 04:44:09
|
Hello, after installing version 6.2.0 I can not watch RAW files more. What is to do ? ielib32.dll is in the same directory as the program.
Previously with dcraw.dll everything worked out great.
Klaus
www.klausdoege.de |
|
|
xequte
39056 Posts |
Posted - Sep 21 2015 : 00:16:43
|
Hi Klaus
Is this the latest version of IELib32.dll?
Test the Camera Raw demo in the Demos\InputOutput\ folder to compare.
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
 |
|
|
klausdoege
Germany
389 Posts |
Posted - Sep 21 2015 : 14:33:05
|
Hi Nigel,
yes it's the latest Version.
The camera RAW Demo itīs running.
My question must i remove the DCRAW.dll from program Directory ?
Klaus
www.klausdoege.de |
|
|
|
xequte
39056 Posts |
Posted - Sep 22 2015 : 00:11:22
|
No, DCRAW is just ignored by ImageEn now (i.e. whether it is there or not will not affect ImageEn).
You do not need to call anything to initialize IELib.
So the demo is working but not your program? Look for differences between your code and the demo.
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
|
|
|
Uwe
284 Posts |
Posted - Sep 22 2015 : 14:13:32
|
Nigel,
Is there any chance that you'll take a step backwards and make ImageEN support a stand-alone 64bit dcrawlib.dll?
I'm asking because my customers are only interested in the support of camera RAW files under 64bit. I don't need a DLL that wraps ievision.dll or the Boost library to speed up loading. I don't need ImageMagick, and I also don't need interprocess COM trickery to run 32bit DLL's in a 64bit process. All I need is a simple 64bit dcrawlib.dll that works with ImageEN and that I can compile myself once a new version of DCRAW is released. Unfortunately, the latest ImageEN seems to make this completely impossible from now on, which is why I haven't installed it yet. HELP!
Thanks
-Uwe |
|
|
|
xequte
39056 Posts |
Posted - Sep 23 2015 : 21:36:05
|
Hi Uwe
To clarify, ielib is just a standard DLL and not a COM DLL, and no "interprocess COM trickery" is involved.
This is the same as the old DCRAW. Were you compiling the DCRAW yourself to create a 64bit DLL. You can still add support for your formats to ImageEn as a "Plug-in" format (i.e. plug-in your RAW format support with your own DLL, rather than using ImageEn's RAW support).
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
|
|
|
Uwe
284 Posts |
Posted - Sep 24 2015 : 13:49:36
|
Hi Nigel,
To clarify, ielib is just a standard DLL and not a COM DLL, and no "interprocess COM trickery" is involved.
Hmmm, last time I looked at the source, ielib was a wrapper DLL containing (amongst others) imagemagick.dll and dcrawlib.dll, which are both 32 bit. How do you get them to work under 64 bit? Please correct me if I'm wrong, but the only way I know of is interprocess COM.
...plug-in your RAW format support with your own DLL, rather than using ImageEn's RAW support
I've never used the internal camera RAW support of ImageEN - always dcrawlib.dll under 32 bit. Simple and quick, which is why I was hoping for a direct support of a 64 bit version of DCRAW in ImageEn instead of having to jump through a ton of hoops or use a (for my purposes) bloated DLL of which I only need a fraction of the functionality.
-Uwe
|
|
|
|
xequte
39056 Posts |
Posted - Sep 25 2015 : 05:40:55
|
Hi Uwe
Ielib contains DCRAW, it does not contain ImageMagick.
Ielib64 is pure 64bit, so using ielib64 allows you to get 64bit raw support, which was not available by using the DCRAW.DLL previously.
For 32bit apps you could argue that the ielib.DLL is larger than DCRAW.DLL, but with the ubiquitousness of broadband these days, I don't know that its much of an issue.
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
|
|
|
Uwe
284 Posts |
Posted - Sep 25 2015 : 09:49:19
|
Hi Nigel
You were right - Imagemagick wasn't part of the DLL. I just checked the source from 2013 that is available to me. Sorry for the mix up. Still don't understand though why you guys are making things so complicated for your customers. Well, I can think of at least one reason, but that would be somewhat off topic here.
One final question: is ielib64.dll source code included in the VCS Access, or only the 32 bit version?
Thanks
-Uwe
|
|
|
|
xequte
39056 Posts |
Posted - Sep 25 2015 : 18:16:53
|
Hi Uwe
Both 64 and 32bit source are available on VCS.
I'm not sure why you are saying it is complicated. Moving away from separated DCRAW and IELIB DLL's makes it less complicated. Users need only worry about updating and shipping one DLL and it is updated automatically with each new release.
If your argument is that we should not have a DLL at all and all our code should be native then that is not really practical. All the time we would spend implementing and maintaining the code would be taken from development of other features, all for a change than 99% of users would not appreciate. Plus, because the DLL is more highly optimized by the IDE used, it has significantly better performance over native Delphi code.
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
|
|
|
Uwe
284 Posts |
Posted - Sep 25 2015 : 21:22:23
|
Hi Nigel,
...one DLL and it is updated automatically with each new release.
That's exactly the problem. In the past, when Dave Coffin updated his code, I simply took the new DCRAW version and compiled it myself the same day it came out. Now I do not have access to the ielib32/ielib64 code (unless I pay for VCS access, it seems), and I have to wait several months before the next ImageEN update is released. That's too long, and too complicated. Even with source code, the compilation of ielib32/64 is confusing, to say the least, as I found out a few years ago. On top of all this: what happens if you guys decide to call it quits and shut down Xequte?
My apologies should the ielib32/64 code be available on demand, but I hope that you understand my concerns. I got burnt once before with ImageLib by Skyline Tools. They went down the same path with their closed-source DLL.
-Uwe
|
|
|
|
klausdoege
Germany
389 Posts |
Posted - Sep 27 2015 : 11:20:05
|
Hello Nigel,
I ImageEn reset to version 6.0.1. I will try in the near future v 6.2 again.
I also believe Uwe's right, the updates come a little late. Maybe should be offered in between even minor updates.
But thanks for your help.
Klaus
www.klausdoege.de |
|
|
|
xequte
39056 Posts |
Posted - Sep 27 2015 : 20:42:03
|
Hi Uwe
Source code is available for IELib, just email us.
There is nothing to prevent you still downloading the latest DC raw code, recompiling your DCRAW.DLL code and using it in ImageEn. Of course you will need to make a unit to read the DCRAW.DLL and add the formats as a custom file format to ImageEn (plus remove ioRAW), but it should not take long if you refer to the old source.
If there are big changes to DCRAW between ImageEn releases we will issue an ielib update, as we have done in the past with out-of-sync DCRAW updates.
We cannot change our development strategy on the chance that we will go out of business. Aiming to fail is not a viable business stategy. Nothing would bring about the end of ImageEn quicker than if we stopped adding features and spent all our time maintaining and implementing "100% native code".
I believe the only two valid arguments for a stand-alone Raw DLL, are: 1. DCRAW updates will become less frequent, and 2: the IELib DLL is large if you only care about raw support. I doubt that 1. will prove true, as previously we will endeavour to issue several DCRAW updates a year.
2. may well be valid, and if enough users advise us that they want a slimline RAW dll then we will do so.
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
|
|
|
Uwe
284 Posts |
Posted - Sep 27 2015 : 20:57:05
|
Hi Nigel,
Source code is available for IELib, just email us
As long as the source for the library is available, I'm happy. I'll send you a message in a minute.
Thanks a lot
-Uwe |
|
|
| |
Topic |
|
Search
v6.2.0 and RAW-Files
