Author Topic: Photo Mechanic to dcraw - floating point  (Read 5273 times)

Offline Gary_G

  • Newcomer
  • *
  • Posts: 37
    • View Profile
Photo Mechanic to dcraw - floating point
« on: December 15, 2015, 02:49:00 PM »
Has anyone tried using a dcraw floating point windows 10 implementation in conjunction with Photo Mechanic?
If you know where to download the binary, please let me know and give me some feedback on your experience with it.
I'd like to try it, for interests sake, but can't find a compiled version.


Offline Kirk Baker

  • Senior Software Engineer
  • Camera Bits Staff
  • Superhero Member
  • *****
  • Posts: 25020
    • View Profile
    • Camera Bits, Inc.
Re: Photo Mechanic to dcraw - floating point
« Reply #1 on: December 15, 2015, 04:14:23 PM »
Gary,

Has anyone tried using a dcraw floating point windows 10 implementation in conjunction with Photo Mechanic?
If you know where to download the binary, please let me know and give me some feedback on your experience with it.
I'd like to try it, for interests sake, but can't find a compiled version.

But what would you do with it?  Unless it were to produce a JPEG or a TIFF, PM isn't going to load any floating point bitmap that it might produce.  And if the JPEG or TIFF have pixels that have not been developed, the image data would still be linear and not suitable for display purposes.

-Kirk

Offline Gary_G

  • Newcomer
  • *
  • Posts: 37
    • View Profile
Re: Photo Mechanic to dcraw - floating point
« Reply #2 on: December 15, 2015, 07:31:44 PM »
Hi Kirk.

You're probably right Kirk. I read a bit about dcraw being the basis for many editors and thought it might be worth a look. After reading more on dcraw, I can see that at best it might form the front-end for an editor and not a fully standalone editor (which is what I really want to find).

I should explain, because I sometimes mentally jump over the details and confuse people with where I'm going in a post.

Back in the days of tape players, one could get a package with a radio and a turntable as well. Audiophiles soon discovered that these combination systems tended to be average at many things and really good at nothing in particular. They also couldn't accept other components that might be better at a particular function. So; they voiced their opinion and before long we had component stereo systems in which the user could mix and match components to meet his/her needs, quality requirements and budget.

Similarly; these days photography seems to be going the way of the all-in-one stereo system. Every time I find a decent editor, it seems to come with other software components, often none of which are stellar in functionality and an implicit workflow that I don't need or want.
What I really hope to find (one day) is a set of discrete workflow components each of which fulfill a particular function, do it very well and that have a somewhat standard interface paradigm, such that they "play nice together".

I know this is a tall order and I may have to settle for less. Surprisingly; I've been successful at getting all but one of the components I need.

I chose Photo Mechanic because it is a great front-end for ingestion, metadata embedding, culling and ranking. It also has a logically independent portion of the design that is good for the back end of the workflow and getting things out in a publishable format. (If it ends up getting a DAM element, I do hope it's designed such that one could either use or not use it without affecting the independent use of the other functionality). I've got the Adobe DNG Converter, which does RAW to DNG conversion well and nothing more. What I'm missing is a decent DNG-capable editor, that's essentially just an editor. ACR seems to be the only one I've seen so far that seems to fulfill the editing function alone, but I'd like to see one or two others before being forced into a subscription to get one element of a package. I should note that I also use a standalone version of Noise-Ninja (which I've had a few years and works very well) to address any noise issues.

Anyways; that's the rationale behind this post. Let me know if I've not been clear. I'll try to be clearer in future posts.




Offline Kirk Baker

  • Senior Software Engineer
  • Camera Bits Staff
  • Superhero Member
  • *****
  • Posts: 25020
    • View Profile
    • Camera Bits, Inc.
Re: Photo Mechanic to dcraw - floating point
« Reply #3 on: December 15, 2015, 09:43:21 PM »
Gary,

Anyways; that's the rationale behind this post. Let me know if I've not been clear. I'll try to be clearer in future posts.

I understand completely.  Now. ;)

-Kirk

Offline ron_hiner

  • Full Member
  • ***
  • Posts: 222
    • View Profile
Re: Photo Mechanic to dcraw - floating point
« Reply #4 on: January 25, 2016, 03:25:24 PM »
What I really hope to find (one day) is a set of discrete workflow components each of which fulfill a particular function, do it very well and that have a somewhat standard interface paradigm, such that they "play nice together".

That pretty much describes perfectly the combination of PM & Nikon's Capture NX2 with Nik Software plug-ins.  Of course, it was only a solution for Nikon shooters.   Sadly, Capture NX2 is dead, and I haven't seen any news or updates from Google's Nik Software in a very long time.   Like you, I've not been a fan of the one-app-that-does-everything kind of product.  Some year back in this forum, I recall there being a discussion of adding some image editing capability to PM.   I'm so glad that Kirk and the PM team have resisted venturing into that space.

My workflow now is pretty much PM as a front-end to Photoshop for anything that needs further editing.  Though in the fullness of time, i'd like to try other raw converters.

Ron