Re: [darktable-dev] Fuji Compressed RAW Files
On Thu, Mar 16, 2017 at 11:30 PM, Uwe Müsselwrote: > Hello Roman, Hi. > I've cloned darktable-org/rawspeed and have started to ported the compressed > RAF support. You can find it at https://github.com/muessel/rawspeed. > Now I use the CFA from camaras.xml. Cool :) > I changed the copyright header: I took the standard one and inserted the > people from libraw. Mabe there is missing a reference to the libraw project? Looking at it again, i'm not sure what i was commenting about. So just keep it as is i guess. Now, the important question: do you know if that code is noticeably different from the vanilla libraw/rawtherapee version? Does it have any behavior-changing changes? Like, producing different output for the same raw? The reason being, there is some kind of rudimentary regression testing in rawspeed. It may make sense for me to merge it somewhere in this current state (with absolutely minimal amount of changes) so that going forward, all the changes will be test-able. Oh, and, please apply clang-format to decompressors/FujiDecompressor.* and install clang-format git hook, so that the formatting is uniform. > Regards >Uwe Roman. ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Fuji Compressed RAW Files
Hello Roman, I've cloned darktable-org/rawspeed and have started to ported the compressed RAF support. You can find it at https://github.com/muessel/rawspeed. Now I use the CFA from camaras.xml. I changed the copyright header: I took the standard one and inserted the people from libraw. Mabe there is missing a reference to the libraw project? Regards Uwe ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Lua Scripts
Hello I agree with Aurélien, I'm just a user of Darktable, I look at the email here from time to time to see what's going on, I have a technical background, but I had NO idea what Lua scripts were. I thought it was some dev files that could be included in a future version. I only discovered recently that they were actually plugins. have a nice day guys ! François On Thu, Mar 16, 2017 at 2:36 PM, Aurélien PIERREwrote: > Hi ! > > This is NOT a message of the utmost importance but just a thought. > > The DT "Lua scripts" should be renamed "plugins". For us geeks, "script" > describes what it is and "Lua" how it's written, but for the end user, it > may sound unfamiliar if not dangerous. "Plugin" describes what it does and > anyone having used Firefox or WordPress or Photoshop knows what a plugin > is. > > Now that scripts become popular and numerous, it could be the right time > to make them more understandable. > Have a good day. > -- > > *Aurélien PIERRE* > aurelienpierre.com > -- > > ___ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Darktable stopped working; symbol lookup error libdarktable.so
On Thu, Mar 16, 2017 at 3:33 PM, Matthew Malthousewrote: > Hi Roman, > > tl;dr that worked. Thank you. Good :) > I'm still baffled about what happened. > > Re-installing DT caused libexiv2-14 to be installed as a dependency and gave > /usr/lib/x86_64-linux-gnu/libexiv2.so.14 etc. No such files existed when I > was looking before, although they obviously must have at some point and I > assume that a prior install, subsequently damaged, was what dpkg.log was > referring to. > > It's worrying that dpkg.log says that this was updated on Tuesday > > dpkg.log:2017-03-14 06:25:04 upgrade libexiv2-14:amd64 0.25-2.1 > 0.25-2.1ubuntu16.04.1 > > but the only related files existed in /usr/local/lib. > > I can be confident that I didn't compile by hand, I almost never do these > days and I think that trying to compile DT from source on Tuesday was the > first time I'd done so on this particular machine (started about 11:00, so > hours after that entry in dpkg.log) in large part because I had to install > the cmake tools to build the dependencies to build DT. > > I can only guess that some unrelated and dodgy package install did the > breaking but have no clue what that might be. Maybe I'll find out the next > time I discover something that doesn't work. :) dpkg -S is your friends here > Cheers, > > Matthew > > > ___ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Darktable 2.2.X Plugin Enfuse Professional
Hi Ulrich,Here it doesn't work (with darktable 2.2.x): LUA ERROR : Invalid index for combo box : 0 > If you have installed beta1 before you need to remove all enfuse_pro entries from your darktablerc. Cheers, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Darktable stopped working; symbol lookup error libdarktable.so
Hi Roman, tl;dr that worked. Thank you. I'm still baffled about what happened. Re-installing DT caused libexiv2-14 to be installed as a dependency and gave /usr/lib/x86_64-linux-gnu/libexiv2.so.14 etc. No such files existed when I was looking before, although they obviously must have at some point and I assume that a prior install, subsequently damaged, was what dpkg.log was referring to. It's worrying that dpkg.log says that this was updated on Tuesday dpkg.log:2017-03-14 06:25:04 upgrade libexiv2-14:amd64 0.25-2.1 0.25-2.1ubuntu16.04.1 but the only related files existed in /usr/local/lib. I can be confident that I didn't compile by hand, I almost never do these days and I think that trying to compile DT from source on Tuesday was the first time I'd done so on this particular machine (started about 11:00, so hours after that entry in dpkg.log) in large part because I had to install the cmake tools to build the dependencies to build DT. I can only guess that some unrelated and dodgy package install did the breaking but have no clue what that might be. Maybe I'll find out the next time I discover something that doesn't work. :) Cheers, Matthew ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org