Hi,
that sounds like one of the endless AMD GPU stability issues other
people and myself (RX 570, RX 6600 XT, ...) have been having for years.
ROCm is simply not reliable on consumer cards and never has been. ROCm
6.0 officially only supports the MI100/MI200/MI300 data center GPUs, the
Radeo
Hi,
I'm against taking an official stand on this for the following reasons:
1. There is no consensus on what "AI" means. darktable already uses
algorithms that may count as "artificial intelligence" depending on
someone's viewpoint, and on the other hand algorithms classically used
for genera
Hi,
can confirm, has been down since Friday.
Kind regards,
Simon
14.07.2023 12:50:24 Bernhard :
> Hi there,
>
> I get
> Failed to connect to www.darktable.org port 443: Connection refused
>
> anyone else also experiencing this?
> --
>
> regards
> Bernhard
>
> https://www.bilddateien.de
> _
Hi,
Am 16.08.22 um 20:19 schrieb Jeronimo Pellegrini:
during GIMPLE pass: graphite
what CFLAGS are you using? Graphite is known to be error-prone and
unmaintained.
cheers,
Simon
OpenPGP_0xCE9228264D6BD39A_and_old_rev.asc
Description: OpenPGP public key
OpenPGP_signature
Description: Ope
Hi,
there is a workaround:
darktable ships an utility called "purge_non_existing_images.sh". If you
move the problematic picture to a different location and run the script
with "purge_non_existing_images.sh --purge", it will remove the data for
this image from the database because the path stored
Hi,
Am 15.08.20 um 13:21 schrieb Dusenberg:
[..] I shouldn't be seeing the problem as it only affects the/open
source/ OpenCL package running with the/open source/ amdgpu driver. Have
I got this right?
Yes. There have been problems with ROCm, darktable and visual artifacts
for years. AMDGPU-
Hi Lorenzo,
as far as I understand, this is the same situation as with Sony's DRO,
Canon's ALO, Nikon's Active D-Lighting and Fujifilm's D-Rng.
These dynamic range modes don't just affect in-camera JPEG processing,
but also dynamically manipulate exposure metering (Nikon's Active
D-Lighting
Hi Andreas,
On 16.12.19 20:13, Andreas Schneider wrote:
darktable is setting a flag for images to be HDR and SDR. It doesn't really
make use of it, but we probably have to change that in future.
After thinking about it a bit more:
What is this flag going to be used for in the future? I think
Hi Andreas,
On 16.12.19 20:13, Andreas Schneider wrote:
sRGB -> SDR
AdobeRGB -> SDR
PQ Rec2020 -> HDR
HLG Rec2020 -> HDR
Does that make sense? I could look into that next.
Where do RAW files fit into this definition? They have no color space.
A 16 Bit AdobeRGB out-of-camera TIFF file might
Hi Owen,
On 14.12.19 19:02, Owen Mays wrote:
1) Why go to the trouble of adding hostname to PID in the lock file, why
not just check for existence of the lock file and treat that as evidence
that the database is open? It looks like many lines of code have been
written in database.c dedicated
Hi Owen,
the locking mechanism could probably be extended to also include the
hostname in the lockfile.
The problem with putting SQLite databases on a network share is that
it's discouraged by SQLite [1] to begin with because too many things can
go wrong. If darktable's locking mechanism fai
Dear list,
for future reference:
The command was initially called "update-lensfun-data" and then later
renamed to "lensfun-update-data".
Ubuntu actually didn't ship it before Ubuntu 18.04 (bionic). So it's not
included in Ubuntu 16.04 (xenial).
cheers,
Simon
On 06.12.19 18:26, Dimitri
Hello Jesus,
I have a D850 too. At least Ubuntu 18.04.3 LT still seems to ship a
lensfun database snapshot from 2015, so I usually have to run the
"lensfun-update-data" command from the "liblensfun-bin" package once to
make sure the local lensfun database is up to date.
cheers,
Simon
On 02
Hello Timur,
you probably have to suggest this on the matching website of this
third-party service:
https://build.opensuse.org/package/show/graphics%3Adarktable%3Amaster/darktable
cheers,
Simon
On 05.12.19 15:23, Timur Irikovich Davletshin wrote:
Nicolas, I'm talking about builds provide
Hi,
AFAICT your card hasn't been on the list of supported chips since the
AMDGPU-PRO 14.04 driver. This was discussed on the darktable mailing
list two years ago
(https://www.mail-archive.com/darktable-user@lists.darktable.org/msg02791.html).
If you want to run Ubuntu 18.04.3 with the Hardwa
Hi,
GCC 6.3.0 is just three years old (December 21, 2016). Most codebases
don't profit as much from optimization as darktable does, so it's no
wonder most build with GCC 6.x and even much older releases. Red Hat 7.7
still ships GCC 4.8.5...
cheers,
Simon
Am 18.10.19 um 17:55 schrieb Marco Teda
Hi,
Am 02.10.19 um 14:31 schrieb Julian Rickards:
> This is not clear to me because the mouse wheel can be rolled towards
> the user or away from the user. Perhaps Ctrl+(scroll wheel away) and
> Ctrl+(scroll wheel towards).
Different environments have different defaults. In some "away from the
us
Hi,
this doesn't look like a problem with the actual build process, but more
like a problem with your local operating system installation.
Try running /usr/local/bin/jsonschema manually on a terminal. Does it
crash with the same error message?
Where did you get the spec file for the package from
Hi,
I don't think there currently is a way to automatically apply a style to
a tag, and if it was there might be conflicting tags with conflicting
associated default styles etc.
At least in 2.7.x you can filter images by tag in the "collect images"
module and then apply a style to all filtered im
Hi,
Am 12.04.19 um 10:26 schrieb Christian:
> Understand. But there may be users who prefer a consistend size
> between ooc and processed images or when using several raw converters in
> parallel.
>
> So I suggest an option in the export-pane :
>
> [x] crop to original/nominal size
I guess the
everal raw converters in
>> parallel.
>>
>> So I suggest an option in the export-pane :
>>
>> [x] crop to original/nominal size
>>
>> logic: if image is larger than original size and not
>> has been cropped manually then crop to original size.
>>
>
Hi,
many higher-end camera sensors have more pixels than advertised. These
pixels are used to improve image processing around the edges of the
image, but they can also be recovered and presented to the user. Which
not all RAW converters and in-camera JPEG engines do.
So these additional pixels ac
HD
> Graphics NEO
> clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR) No devices
> found in platform
> clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM) No devices found
> in platform
> clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL) Success (1)
> Platform Name
Hi,
Am 08.03.19 um 09:47 schrieb Björn Sozumschein:
> However, as far as I undestand, although 512 MB VRAM is reported, the
> integrated graphics may allocate more shared memory
Yes and No. On one hand it depends on the chip generation, operating
system, driver and system configuration. Most of t
Hi,
are you sure your GPU has enough resources to handle a dual-monitor
setup plus the Darktable GUI plus OpenCL? It's a six years old device
which was usually shipped with just 2 GB of dedicated video RAM.
I used to run a dual-monitor setup with a GeForce GTX950 2GB and had
exactly the same prob
Hi,
Am 23.02.19 um 16:34 schrieb Florian W:
> Thanks for your answers guys.
>
> Simon, I'm curious to know why to you it's not the best idea ?
(oversimplifying it a bit)
Full-frame lenses are designed to deliver their full sharpness across
the whole full-frame image circle. If I put a full-fram
Hi,
it does, as long as lensfun can find the lens in its database. I've been
using full-frame-only lenses on both my Nikon D750 (full-frame) and
D7100 (APS-C) for years.
(It's not the best idea, though, so I'm about to replace the D7100 with
a second full-frame body).
cheers,
Simon
Am 23.02.1
Dear Robert,
Am 18.02.19 um 17:54 schrieb Robert Krawitz:
the comment holds some validity in this particular case since darktable
can't losslessly crop a JPEG file, but other tools can. If the original
poster ended up just cropping (and not rotating) most files, something
like cropgui[1] would
Hi,
Am 15.12.18 um 17:51 schrieb Timur Irikovich Davletshin:
> 1. Default settings (95%, lossy) provides rather mediocre results and
> IMO is unusable. Probably something higher should be used.
it looks like that module doesn't actually take care to set that default
internally and in the configur
Hi,
I usually come up with something I want to change (my first patch for
darktable added a "Compression Level" slider to the PNG output module)
and then work through the source code until I know everything I need to
get it done. This has been my general strategy for the last ~20 years,
and it has
Hi,
Am 17.11.18 um 11:51 schrieb Andreas Schneider:
> This happende in darkroom and in the export and if I turned off OpenCL it
> works in darkroom.
>
> It could also be a bug in the ROCm OpenCL implementation.
I think this might have happened with my Radeon RX570 on Linux too, so
it could act
Hi,
I just had a look at the code and at least to me it looks like the two
TCA sliders are not updated after the lens model is set/changed. They
will always stay on 1.0, until the user changes them manually.
cheers,
Simon
Am 14.11.18 um 10:30 schrieb Christian:
> Hi,
> The TCA correction in
Hi,
libexiv2 is shipped as a part of Linux Mint and not part of darktable.
Debian still only ships version 0.26 in the "experimental" branch,
Ubuntu depends on Debian, and Linux Mint depends on Ubuntu. So you would
have to build and install exiv2 manually.
kind regards,
Simon
Am 05.11.2018 um
Hi,
ignoring that this is one of the cases where not setting the camera to
"Auto" would have resulted in a much better picture and avoided most of
the issue to begin with:
Profiled Denoise in Wavelet mode with strength 0.2 already looks pretty
identical to what DPP does, at least to me. XMP is at
Hi Andreas,
Am 02.11.18 um 13:23 schrieb Andreas Schneider:
> On Friday, 2 November 2018 12:58:52 CET Sturm Flut wrote:
>> Dear list,
>>
>> I guess this can also depend a lot on the hardware and the specific
>> X.Org/Mesa/GTK/driver version combinations. I've
Hi,
Am 31.10.18 um 16:50 schrieb Postmaster:
> Its not so easy to make this work. cmake seems to be an issue.
>From what I've been seeing in a couple of mails now, it feels like you
might be running into issues which seem to be more specific to RHEL and
Fedora than to darktable and the general G
Dear list,
I guess this can also depend a lot on the hardware and the specific
X.Org/Mesa/GTK/driver version combinations. I've been using darktable on
a 4K display with Arch Linux running on a Ryzen 1600X for one and a half
years and there haven't been any noticeable lags, neither with the old
NV
37 matches
Mail list logo
