Youtube slomo edit1/13/2024 ![]() The specific example you gave was the workspaces. However in blenders case it was for good as people then gave it a try and discovered thet blenders workflow is actually pretty good. ![]() so make the color scheme darker add a drop down menu and most importantly get rid of the undeserved bad reputation by telling everyone we rewrote the whole thing" That is, it was sort of exactly the same thing as this darktable drama, more marketing than actual change. But it was not some "complete rewrite to make it more accessible" It was closer to "We have a good UI but it has a reputation for being weird and hard. The blender team has done amazing work on the ui. Blenders UI has always been infinitely customizable, but without bundling that capability into a feature that benefits the user, it really just lead to confusion.Ģ.8 was a huge update for them and they’ve sort of been going all in on that user-centric direction with every subsequent release since then. Just the other day I wanted to make an animated intro from an svg image, so I just opened it in the 2d animation workspace and was off to the races. One of the things I really like that they added was workspaces, so you can quickly start in a UI that makes sense for what you want to do. They decided to really focus on the UI and bring it into a more standardized experience, where people who were not intimately familiar with blender would stand a chance - and overall I think everyone has loved it, even those who used it extensively. This all started with the release of Blender 2.8 - here are the release notes: and you can see a hacker news post about it here: īasically blender had a ton of features but you had to learn all sorts of shortcuts and read endless documentation to even become aware of them. The log of work done is may be quite worth looking at, rather than incendiary blog posts. Steady work by a committed community matters. If we take a moment to page back to page 3, one can note that we're back to two weeks ago (rather than June). I totally understand that good developers need to work carefully and sit on things, then release them in due time. of Ansel commits is by its mono-author from the last week. It appears that Ansel is being developed more by direct commits from its main author. On the first page, I see about five authors offering PR's over the course of all of 2023 - a much slower pace of community development. But here are the recently merged pull requests from the software which is posted about in the blog post: ![]() There are many ways to develop, and it may be a bit cruel to compare a one-man show to a long-term international collaboration. All what one would hope for in a software project headed to its bi-annual release next month. ![]() They range from bugfixes to performance improvements to documentation to translation work. Others cycle/in out, of course - this is a spot sample. So why don’t invest the effort there instead? I’m no stranger to donating to open-source projects, but I don’t feel like investing any time or money into something, that has no future (even the OP admits that).įWIW, here is the recent merged pull requests from darktable:Īt the moment, this is about a week's work by eight authors. Later in his post, the OP mentions, that dtvk is the future. And at that point I wonder, why didn’t OP fork some earlier version, like 3.6, without that MIDI revolution and all the regressions. I tried Ansel, and unfortunately, although, it fixes some of the issues, it doesn’t fix all of them (and some are absolute productivity killers). But when even very basic features do not work, the advanced ones become less relevant. I enjoyed Darktable’s instruments, and I like how my images ended up looking. It is lightning fast, has AI masks, comes with 100GiB of cloud storage and works on any decent tablet or phone. So for now I’m paying for Lightroom mobile. Darktable is painfully slow, it takes over 1s to see the result of very basic brightness adjustments, the interface is laggy (OP mentions that as well, a simple mouse hover issues over a dozen of SQL requests)… While the mask was positioned perfectly when zoomed in 400%, it would jump up or down on different zoom levels, and would end up somewhere else when exported (Aurelien Pierre, the OP, mentions screen vs raw coordinates in his post, I guess I’ve seen the manifestation of that).Īt that point I decided, enough is enough. My fascination with Darktable (I used to use it actively) ended after I tried creating a selective mask, an ellipse, to darken the moon on a picture.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |