Photographer - Camera Exposure, White Balance, Autofocus, Physical Lights, Bokeh, Render Queue

Indeed, but at the same time it was kind of relevant to the overall approach with different addons, (mind you I’m not targeting Photographer, love it, it just happens that many addons have a non-modular nature but I’m more familiar with this specific one).

I meant that when (if) you do implement it, there could be a generalized way to enable such behaviour, and not just tunneling onto the specifics of what Heinzelnisse is doing.

eg. Have an option to toggle for Builtin/Heinzelnisse’s/Custom. I can’t recall how it happens right now, but if it’s NodeGroup based, there could a list of expected SocketInput names, in order to be able to build our own custom nodes and still display them in the Photographer UI.

I also thought you were not questioning if devs should be payed, it would indeed be quite ironic. There’s two ways I see how the general incompatibility problem is solved (not just for photographer, for addons in general):

  1. Contact between the addon devs, resulting in a specific fix for each addon
  2. Modularizing and generalizing the addon:
    • separate it into smaller chunks that communicate with each other
    • keep it close to vanilla blender use cases

Sidenote: Also, I really enjoy your addon, but at some point I had no need for some features, others were empairing some workflow (or file) so I ended up rewriting (cherry picking your code) for a tailored one with my own idiosyncrasies. I would gladly contributed some fixes but there’s no public repo for me to refer to.

1 Like