f16sunshine
Moderator
I mentioned this in another thread.
Why would Fuji not build a RAW processor that could be installed as a plugin for Aperture, LR, PS etc.... ?
Basic exposure, WB, lens correction, etc.. Then, flip it over to Aperture3 or LR4 as a Tiff. All the cataloging, Creative PP, re-sizing, formatting, exporting...etc could be done there.
It seems like a simple solution to a lay person like me.
I'm sure we must have a few developer types around here to either concur or appropriately shoot holes in this method.
Comments please...
Why would Fuji not build a RAW processor that could be installed as a plugin for Aperture, LR, PS etc.... ?
Basic exposure, WB, lens correction, etc.. Then, flip it over to Aperture3 or LR4 as a Tiff. All the cataloging, Creative PP, re-sizing, formatting, exporting...etc could be done there.
It seems like a simple solution to a lay person like me.
I'm sure we must have a few developer types around here to either concur or appropriately shoot holes in this method.
Comments please...
GaryLH
Veteran
That is not a bad idea.
But I think it may be a skill set related issue.. They may not have the right sw developers for this type application.
If they had the right sw developers, the other way to do it would be a object library (lib.a), which has a set of binaries for windows and Mac environment that has the function calls required.
In the plugin model or the object level model, it introduces several issues that they may not want tot take on...
- existing silky pix agreements that may have given some exclusivity.
- support and sustaining model for this different type of sw
- free plugin vs paid
-- paid means additional support burden
Given what I saw in how long they took to figure out the save configuration issue after each new firmware update, I suspect it is first a sw skill set issue.
Gary
But I think it may be a skill set related issue.. They may not have the right sw developers for this type application.
If they had the right sw developers, the other way to do it would be a object library (lib.a), which has a set of binaries for windows and Mac environment that has the function calls required.
In the plugin model or the object level model, it introduces several issues that they may not want tot take on...
- existing silky pix agreements that may have given some exclusivity.
- support and sustaining model for this different type of sw
- free plugin vs paid
-- paid means additional support burden
Given what I saw in how long they took to figure out the save configuration issue after each new firmware update, I suspect it is first a sw skill set issue.
Gary