Axisential,

I really, really want to like Darktable, mostly because of the name lol. I must’ve tried it 8 or 10 times over the years, but I just can’t get my head around it. Something about the design language or the UI or something just doesn’t click for me and I can’t get decent images out of it. So I keep going back to Rawtherapee, even though I’d rather not…

Sina,

Personally i’m okay with the UI, but the default rendering is often so bad that I have to “fix” every single image. To me it’s either Raw therapee or just reboot into Windows …

manos_de_papel,

You should make a style to apply that brings you (close) to what you want. Out of the box, dakrtable shows you a minimally processed image. Its your job to take it from there.

Sina,

It shows me a very wrongly processed image. It was better when I used Fuji, but even then it was never anywhere close to what an unprocessed bland raw file should like.

manos_de_papel,

This is too vague to provide any further guidance. Again, darktable shows you a minimally processed raw image by default. You can get a good looking rendering by adding a few more modules in a style and applying that style by default.

manos_de_papel,

Have you read the basic editing section in the manual?

You can share a raw image at discuss.pixls.us and people will edit it and post the sidecar so you can see their edits.

RawTherapee is also good tho.

Axisential,

Yes, and I understand the process pretty well I think, as well as what I’m striving to output (long time Lightroom user). But the DT just doesn’t respond how I expect it to, with unexpected results. Frustrating.

Wasn’t aware of the pixls site though; I like that idea!

manos_de_papel,

If you expected to apply your lightroom workflow, then you will be frustrated, yes.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • linux@lemmy.ml
  • localhost
  • All magazines
    •
    200 @ entry_single
    HTTP status 200 OK
    Controller EntrySingleController
    Route name entry_single
    Has session yes
    Stateless Check no
    Time 714 ms
    Total time 714 ms
    Initialization time 123 ms
    Memory 16.0 MiB
    Peak memory usage 16.0 MiB
    PHP memory limit 128 MiB
    Cache 1
    Number of forms 1
    Number of errors 0
    Logger 86
    Errors 0
    Warnings 0
    Deprecations 86
    Cache 80 in 541.71 ms
    Cache Calls 80
    Total time 541.71 ms
    Cache hits 51 / 82 (62.2%)
    Cache writes 26
    640
    Default locale en
    Missing messages 640
    Fallback messages 0
    Defined messages 151
    Security n/a
    Authenticated No
    Firewall name main
    Twig 484 ms
    Entry View entry/single.html.twig
    Render Time 484 ms
    Template Calls 174
    Block Calls 82
    Macro Calls 6
    124 in 436 ms
    user_avatar 20
    settings_row_switch 15
    date 14
    user_inline 10
    date_edited 9
    vote 9
    boost 9
    entry_comment 8
    entry_comments_nested 8
    user_settings_row_switch 4
    magazine_inline 3
    settings_row_enum 2
    entry 1
    entries_cross 1
    editor_toolbar 1
    user_actions 1
    magazine_box 1
    magazine_sub 1
    related_magazines 1
    active_users 1
    related_categories 1
    related_posts 1
    related_entries 1
    support_us_block 1
    featured_magazines 1
    22 in 279.64 ms
    Database Queries 22
    Different statements 17
    Query time 279.64 ms
    Invalid entities 0
    Cache hits 37
    Cache misses 2
    Cache puts 2
    6.4.0
    Profiler token d3761e
    Environment dev
    Debug enabled
    PHP version 8.2.26   View phpinfo()
    PHP Extensions Xdebug ✗ APCu ✓ OPcache ✓
    PHP SAPI apache2handler
    Resources Read Symfony 6.4.0 Docs
    Help Symfony Support Channels