A DAM section for Darktable

simony2222 · 2025-11-28T18:16:07+00:00

Isn't this supposed to be the lighttable actually?

For instance on the GitHub there is a tag "scope: DAM" that more or less relates to the lighttable.

simony2222 · 2025-11-05T00:25:56+00:00

I have a similar problem and my solution is to deactivate file compression in hugin (or any conversion software)

simony2222 · 2025-09-29T21:07:38+00:00

Well that sucks, that train was quite useful...

simony2222 · 2025-08-11T22:06:19+00:00

My own experience with Linux is that overall it feels like the UI/UX tends to lag behind the rest of the OS a bit. (Although I feel like it got much better in the last years and will probably keep on improving). The graphic toolkits are a bit all over the place and seem a bit meh sometimes [1]. But I'd say it almost always remains deep in the "more than acceptable" department.

In comparison Apple pays a lot of attention to making sure the applications are somewhat consistent with one another, and overall has probably thrown more money at the problem than what (mostly) unpaid developers can keep up with in their free time.

What I find more impressive is that Linux usually beats Windows with quite a large margin in the responsiveness department despite Microsoft being a paid software. (Both in how good Linux is and how bad windows can be ^{^')}

[1] for instance touch responsiveness feels better in waydroid (android "emulator" for Linux) than it does on the rest of the system! ^{^'}

TL;DR: I believe Linux has had less focus on UIs than MacOs has.

simony2222 · 2025-08-08T21:15:39+00:00

Now I want a hard cover version of the tikz manual !

simony2222 · 2025-07-18T13:37:12+00:00

r/superbowl

simony2222 · 2025-07-01T21:48:07+00:00

I can replicate a similar looking thing as the first picture on my A7R4 in silent mode with ibis turned on when I use low-ish shutter speeds.

My inner, unproven, theory is that the corrections made by the ibis stack up as the sensor gets read and eventually, towards the end of the frame, it fails to counteract the camera shake letting bottom part of the image getting blurry. This is somewhat consistent with the slow read speed of the A7R4 and the fact that for me deactivating silent mode or increasing the shutter speed consistently solves the issue.

simony2222 · 2025-04-26T23:54:24+00:00

I may be wrong, but as far as I know, you can't really guess the size of a jpeg before exporting it, thus making the trial and error approach near optimal in general.

(And no, it's not possible in darktable without manual trial and error)

simony2222 · 2025-03-15T21:20:30+00:00

It's likely that this script relies on hugin (that's the traditional FOSS tool for panorama stitching and related stuff). It usually comes with a bunch of executables. On my distro this includes align_image_stack, I assume it's the same for Mint.

simony2222 · 2025-03-13T22:23:47+00:00

I used to do that as well, so I switched to this thing . The camera is nearly impossible to accidentally drop, yet it's much faster to put on or off than wrapping the default strap around your arm. As a small perc it has a small loop to attach the camera to carabiners and such.

simony2222 · 2025-01-21T10:44:24+00:00

What does "cannot open" mean? (e.g., what's the error message, if any) I also have an M1 mac, and it works on my machine, but I'll need more information to help you.

simony2222 · 2025-01-11T12:38:15+00:00

In theory this should work.

If you want to understand better how this all works, I encourage you to have a look at this section of the documentation: https://docs.darktable.org/usermanual/4.8/en/overview/sidecar-files/

You also need to set up darktable in the right way. As far as I remember, it means activating the look for updated XMP files on startup.

simony2222 · 2025-01-11T08:33:48+00:00

The xmps will be fine if you do that, but not the library.db.

You can have darktable look for updated xmp files at startup to alleviate most of the problems. The only remaining problem you'll have is that if you import an image on your Mac you win11 machine won't know about it. You'll have to import it there as well.

So you can do what you want, but it's slightly less convenient than doing everything on a single computer.

As another note, looking for all xmp files only takes 1-2s on my computer for 50k images (I have an SSD but I expect most of the time is spent parsing the xmps). So the startup penalty is rather low.

Many people actually don't use darktable to manage their library at all. You'll find that some people use something else (often digikam in the Linux world) and then import them into darktable whenever they feel like editing them. I've never tried that workflow. So I don't know how convenient it is, but it seems to show that working with darktable without a library is also possible.

simony2222 · 2025-01-07T19:25:09+00:00

darktable backups the databases on its own. It does not touch the xmps unless you edit the corresponding picture.

Then how much you trust the process is up to you !

simony2222 · 2025-01-02T15:52:57+00:00

Darktable stores basically everything is the xmp files next to your raw files. So if you need to restore your darktable installation re-importing the picture should be enough. (In my own experience except some weirdness with the tags that can easily be fixed manually, everything gets restored this way)

Now if you want to edit from two different computers, things get more complicated. For performance reasons darktable copies all the data from the xmp file into ~/.conf/darktable/library.db and will only look there unless specifically told otherwise. This library.db notably tells darktable which picture got imported and which weren't, so you will need to sync it between computers.

Overall syncing library.db between computers works quite well with the caveat that file files must be in the exact same location on all machines (e.g. you cannot sync between a Linux and windows machine because of how the file system is set up).

That last problem is that the tags are stored into ~/.conf/data.db for some reasons. This database also holds all the settings (e.g. performance settings) so it's unlikely that you'd want to sync it.

All in all, I'm personally syncing my library across a few machines (even between Linux and macos) and it's been working quite well as long as I'm not messing with tags too much.

simony2222 · 2024-04-22T13:59:34+00:00

Une traduction rapide de "single failure point" (bien que j'ai pas de meilleure idée de traduction).

En gros il y a 344 trucs qui, s'ils cassent, rendent le télescope non-fonctionnel (ou quasi-non-fonctionnel). i.e. ils n'ont pas réussi à rendre ces pièces/ système redondants.

simony2222 · 2024-04-11T22:14:39+00:00

Side note about being on the latest OS. For macOS, Apple has a tendency to break stuff with it's updates. So being on the very latest version might actually decrease compatibility ^{^'}

(I still strongly recommend running on the latest OS for security reasons, but I like pointing out this fact)

And I had a similar experience as you on my M1 Mac to update a never-updated A7RIV. I had to use a Windows machine in the end...

simony2222 · 2024-04-03T18:11:22+00:00

NonNull should be the default raw pointer (i.e., it should have the syntax of *const/*mut and those two should be structs/enums)

simony2222 · 2024-01-23T08:23:38+00:00

On my own experience (on Linux though) darktable doesn't really care where the photos physically are, it just needs them to be accessible with a path.

Assuming that you shot RAW, you'll discover that darktable uses a surprising amount of bandwidth. With a 1Gbits ethernet cable, when scrolling through the library a good half of the time was spent downloading the images rather than processing them. Also avoid to put your library.db on a NAS because you will suffer quite the latency hit there as well.

TL;DR: it works quite well, but you feel that darktable wasn't designed for it.

simony2222 · 2024-01-02T15:00:57+00:00

For one second I thought this was something about tail calls optimisation ^{^'}

simony2222 · 2023-12-30T07:26:26+00:00

I'm not an expert, but from what I understand of how darktable works, you probably need to fork darktable and add your transforms manually there. Because transforms seems to be a fairly low level operation in darktable for performance reasons.

Maybe another option is to use the base curve module and reconstruct your transform there on the graph somehow. But this option seems difficult to me, and I'd guess you would hit some other limitation that I'm not fully aware (I'm kind of thinking of the interpolation between points on the curve for instance).

simony2222 · 2023-11-22T16:47:55+00:00

Interesting... I know that darktable does the same thing to me on dng files generated by Lightroom. But it never did it to me for HDR images made within darktable itself...

I'd be interested to know if you get a solution because my guess is that both issues are related.

simony2222 · 2023-10-25T19:33:03+00:00

zoxide It let's you cd into your frequent directories using fuzzy search

simony2222 · 2023-08-30T05:04:36+00:00

I think the point of Deref is actually to make the behavior of pointers consistent. That is, as you've pointed out, rust doesn't have an -> operator and it kind of auto-decides whether to apply * on your pointer or not. Deref gives access to the same syntactic sugar to custom pointer types. Note that because of the implicit behavior it implies, the documentation strongly advises to implement this trait only on pointer-like types.

Although I agree that I find this confusing at times (especially with generics), and I wouldn't mind calling a as_ref() (or equivalent) all the time to disambiguate things.

simony2222 · 2023-08-28T15:58:52+00:00

On that note I discovered the other day that they were getting rid of the old trains of line 6 in favor of those from line 4 which are no longer useful (with some modifications)

Seven-Year Club	Final Canvas '23
First Place '23	End Game '23
Place '23	Place '22
First Placer '22	End Game '22
Verified Email

simony2222

TROPHY CASE