A landscape picture with two trees in the foreground and a range of hills in the background.

88/365

Judging from the thin black line at the top of the picture I think there could be another bug in darktable 😉 But hey before anyone gets worked up about it, please please look at this first, ok?


Kommentare

8 responses to “88/365”

  1. @Stephan your profile says "software developer"… why haven't you had a go at fix it yourself?

    1. stephan avatar

      Believe me, I’d love to get involved in darktable development. But, as I wrote in my reply to Nielso:

      “If I didn’t already have three different lives at the same time, I’d tackle it myself, but I can’t possibly make time for yet another project”

      That’s the plain truth. I spend half the week working at the animal sanctuary, the other half as a software developer to pay the bills, and in between I try squeezing recording my next album (and eating and sleeping ;-)). There’s simply no way I could make the time.

      But of course I appreciate all the work you people are doing. If I have given you a different impression I’m sorry.

      1. @Stephan yeah, time, or lack of it, is a problem.

        That is why things like "But really the simplest solution would be to fix #darktable." and "could you maybe, well, you know, fix the bug?" is generally met with a collective groan. 😉

        1. stephan avatar

          Right, I overshot the mark there. I’m sorry.

          In my defence – still having to fight yellow/greenish pictures a year later is also just a tiny little bit groan-inducing. But I understand that priorities vary and everything takes time, and I’ll patiently wait from now on (and then celebrate you guys big time when it works – promise!)

          1. @Stephan than you for your understand. For the record, I hope it gets fixed soon for you, I just don't think these posts are the right way to go about it (and I see it a lot, which is why it bothers me).

            But also… if sigma can barely make a working solution for their own product… then … ? 😜

            1. stephan avatar

              Yeah, the problem with Foveon has always been that Sigma were sitting on a goldmine of technology that they just don’t know how to mine. Over time they learned how to make good and stylish hardware, and they figured out the firmware as well. But as far as software goes, it’s an ugly mess.

              If they had opened X3F specifications from the beginning and invited the open source community to participate, things would have gone very differently.

              At least they finally understood that open standards are a good thing and integrated (albeit half-assed) DNG support in the last generation of Foveon cameras…

              1. @Stephan I am willing to bet a lot that if the X3F spec was open you'd not have ever had this problem.

                FWIW I've had the same issue with Nikon in trying to reverse engineer their embedded lens correction data. What is in there that they think is so special? I'd have to sign an NDA just to find out if they even have that information documented in their NDA, becaue they won't even tell me if it is in there.

                It is very silly.

Leave a Reply

Your email address will not be published. Required fields are marked *