| Author |
 Topic  |
|
|
MikeyC
USA
11 Posts |
 Posted - May 07 2018 : 00:21:09
|
I'm thinking about buying ImageEn to be able to use LibRaw in my Delphi (10.1 Berlin) code. I downloaded the camera raw demo but cannot get it to work. I get an access violation when trying to open any raw, including the two sample raws included with the demo. The UI loads but when I click open and pick one of the two sample raws, I get an access violation: read of address 000000004.
Any advise on getting it working? I'm using Windows 10 x64.
Regards,
Mike
Mike Chaney |
|
|
xequte
39053 Posts |
Posted - May 07 2018 : 21:25:49
|
Hi Mike
Sorry, there seems to be something wrong with the ielib dll in that zip. I have reuploaded it. Should be fine now.
Nigel
Xequte Software
www.imageen.com
|
 |
|
|
MikeyC
USA
11 Posts |
Posted - May 07 2018 : 22:09:05
|
OK, it's working now. Thanks. So since my primary reason for getting ImageEn will be to support LibRaw in my Delphi 10.1 Berlin code, I have some questions before I buy:
- I assume it's compatible with 10.1 Berlin?
- Is ImageEn the only product I need to allow LibRaw support?
- Is LibRaw support mature enough at this time to use it in production projects?
- What version of LibRaw is currently used and is it updated with LibRaw updates?
- Are all LibRaw functions supported?
That last one is important to me because I need the ability to load using camera WB and camera color correction (like DCraw which could convert to say Adobe RGB) or do linear loads with no WB and color/gamma correction, and thread safe.
Do you think ImageEn is the right solution based on those requirements?
Regards,
Mike
Mike Chaney |
|
|
|
xequte
39053 Posts |
Posted - May 09 2018 : 04:19:57
|
Hi Mike
- I assume it's compatible with 10.1 Berlin?
Yes.
- Is ImageEn the only product I need to allow LibRaw support?
Yes.
- Is LibRaw support mature enough at this time to use it in production projects?
I would use the DCRAW code at this time as the LibRaw implementation is quite new.
- What version of LibRaw is currently used and is it updated with LibRaw updates?
I believe it is 0.18.9. Until we are satisfied with the stability of LibRaw we will make Dcraw the default RAW engine. While LibRaw is not the default it won't be updated with every LibRaw release.
- Are all LibRaw functions supported?
All the raw properties that we support, should work as well with LibRaw as DCRAW:
https://www.imageen.com/help/TIOParams.html
- Do you think ImageEn is the right solution based on those requirements?
Our DCRAW code is mature and very solid, whereas the LibRaw code is newer and not as field tested, so there may be issues we are not aware of.
Regards,
Nigel
Xequte Software
www.imageen.com
|
|
|
|
MikeyC
USA
11 Posts |
Posted - May 09 2018 : 10:21:30
|
Thanks again for your thorough answer! I understand that LibRaw needs more testing and wouldn't mind providing feedback to help with that. I currently support DCraw but my issue is that DCraw is now 2 years old and more than 100 (new) camera models behind. So LibRaw is my only way to move forward.
I also understand that you can't commit to incorporating every new LibRaw update but as long as you plan to update it somewhat regularly (say every couple months) and your intent is to continue field testing and improving it, it sounds like ImageEn might be a good investment for me.
Thanks again,
Mike
Mike Chaney |
|
|
|
xequte
39053 Posts |
Posted - May 09 2018 : 15:54:53
|
Hi Mike
As you say, DCRAW is no longer being updated, so this is why we are moving to LibRaw. It will become the default once we are happy with its stability (and will be updated regularly).
We'd like to hear feedback on your testing.
Nigel
Xequte Software
www.imageen.com
|
|
|
|
Uwe
284 Posts |
Posted - May 10 2018 : 15:05:19
|
Hi Nigel,
I wish you guys would have implemented LibRaw as a standalone plugin like the old dcrawlib.dll instead of being a hidden part of ielib. Testing new LibRaw versions would be so much easier. Maybe it's a good idea to be a bit more open about how to compile ielib.dll ourselves then and make the necessary files publicly available?
Uwe |
|
|
|
xequte
39053 Posts |
Posted - May 10 2018 : 20:56:03
|
Hi Uwe
There might be some advantages to having a separate library if you want to compile it yourself, but having one plug-in DLL makes it easier for users.
Nigel
Xequte Software
www.imageen.com
|
|
|
|
Uwe
284 Posts |
Posted - May 12 2018 : 16:53:51
|
Hi Nigel,
Since the DLL contains GPL'ed source, you should at least make the necessary files to compile ielib (both 32 and 64bit) publicly available as it used to be in the olden days with dcrawlib. Users who bought the full source should also be given step by step instructions on how to compile that beast. The way how it's handled right now is not very customer friendly, although I understand why you are doing it. :)
My 2c
Uwe |
|
|
|
xequte
39053 Posts |
Posted - May 13 2018 : 16:52:46
|
Hi Uwe
All necessary files to compile ielib are available. Just email us. Though we would prefer users not to compile it themselves as it is quite complex and we already have a lot on our plate without adding an extra support overhead 
If an important update has been released that ielib depends on, you can just email us and request we recompile and issue an update (we have issued out of version updates to ielib before).
Nigel
Xequte Software
www.imageen.com
|
|
|
| |
Topic |
|
Search
Trying the camera raw demo
