Lightroom and other commercial software works with camera makers under NDA in order to reproduce the camera's processing. Even if you can read settings like "saturation" and "portrait mode" from the metadata, you don't know which algorithm exactly that implies. They are proprietary to the camera maker and not published. Picture control things like saturation etc that you select in camera are post processing steps that the camera applies to the raw in order to get a "developed" jpeg. You would probably get better results by doing your own calibration, but that is somewhat involved. DT does have this data and applies it automatically, but the calibration is provided by users and might not be ideal. "Color space", by which I assume you mean input color profile aka the color matrix of the camera's sensor, has to be calibrated or reverse engineered by shooting standardized color targets under standard illuminants. Out of those you listed, yes, white balance can be trivially read from the metadata and applied to the processing automatically, and in fact DT does do exactly that. It's not a simple case of reading data from the raw though. Life's just too short to mess about with an app that hangs twice, requiring a force quit, before I've even managed to do a single thing with it. Then the spinning beachball of doom starts again. I see there's a tickbox marked 'Recursive' so I click on that as I have subfolders in my photos archive. This time it allows me to select my photos archive folder. Finally manage to make it usable by hitting the fullscreen widget. It won't rezise, even though I get resize arrows when hovering over the corner. App opens in a weird window the full width of my screen but only half the depth. * Open app, Select 'Add to Library' -> spinning beachball of doomĭelete the ~/.config/darktable directory, to give me a clean start. I just downloaded V4 to see if there was any improvement from last time I tried to use it >I'm also glad it exists but have never figured out how to use it on MacOS Note than 0.7mb of that 3.9 is the spellcheck dictionary, 0.4 my enormous config, 0.5 the AppImage overhead and 0.7 all the legacy plugins still written in vimscript. It's 3.9mb compared to the upstream one which is 15mb without any config. My NeoVIM appimage linked above "really, really" bundles all dependency and compile your NeoVIM config to luajit bytecode. Obviously this doesn't scale very well to projects with 300 dependencies like Digikam. A proper AppImage (this one is by me) look like this. Making perfect AppImages is often possible, but the automated tooling isn't smart enough. OpenSSL and a few other a libs you usually want to use the system one and have a built-in fallback because of security concerns. Using any system library forces you to use glibc (AppImage don't work on Alpine). You can't just bundle those, you have to use the system ones. The best example is libGl (GLX or EGL) for hardware 3D acceleration or libvdpau for hardware media decoding. While some terminal and bitmap only X11 app can be compiled as static binaries, anything that depends on system libraries needs to be compiled with an older version of glibc. There's also upper limits to how self-contained they are. So merging a simple typo fix or dependency update might cost half a day, just to get the dev env back up.ĪppImages are only as self-contained as the author put effort into making them self-contained. And often software that I put on a back burner will require me significant effort to get back into. Don't just throw in PR or feature request, but ask: is this welcome? How do you work? Any particular details that you wish me to pay extra attention to (tabs, spaces, tests, documentation, design).Īs a FLOSS maintainer myself, it can be very intimidating to have someone throw a PR at you that rewrites everything (it comes across as: you suck, your software sucks, but watch me fix all that), or that disregards things that I deem critical (tests, architecture) It is really hard to review it, without coming across as an arrogant bastard. Read issues, threads, subscribe to an ML etc. It's a pity that made you give up.Ī general tip, I give to people wishing to contribute to OSS is to first watch from the sideline. I'm sorry you did not stumble into them, but instead in the few hostile ones. There are loads of friendly and welcoming OpenSource communities.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |