Package Details: art-rawconverter 1.14-1

Git Clone URL: https://aur.archlinux.org/art-rawconverter.git (read-only, click to copy)
Package Base: art-rawconverter
Description: Raw image Converter forked from RawTherapee with ease of use in mind (including blackfoxx-theme)
Upstream URL: https://bitbucket.org/agriggio/art/wiki/Home
Keywords: photo raw
Licenses: GPL3
Conflicts: art-rawconverter-git
Submitter: guzzisti
Maintainer: guzzisti
Last Packager: guzzisti
Votes: 12
Popularity: 1.43
First Submitted: 2020-02-15 18:33 (UTC)
Last Updated: 2022-06-02 06:57 (UTC)

Pinned Comments

guzzisti commented on 2022-03-02 09:50 (UTC)

The new version enables build against libraw to replace the vendored dcraw.c with a more robust and better maintained raw decoding lib.

To enable the use of libraw version 0.21 is required, so for the moment you need to have libraw-git installed: https://aur.archlinux.org/packages/libraw-git/

It will work fine without libraw-git tough.

Latest Comments

ignace72 commented on 2022-03-26 21:35 (UTC)

Good evening to all.
I read that for an AUR package to pass in the community repository, it needed at least 10 votes, it's done for art-rawconverter.
It would be nice to ask for this passage in the community repository.
Thank you for this.
Ignace.

guzzisti commented on 2022-03-02 09:50 (UTC)

The new version enables build against libraw to replace the vendored dcraw.c with a more robust and better maintained raw decoding lib.

To enable the use of libraw version 0.21 is required, so for the moment you need to have libraw-git installed: https://aur.archlinux.org/packages/libraw-git/

It will work fine without libraw-git tough.

SinClaus commented on 2021-12-05 07:08 (UTC)

Hi! Art can't open raw files from FUJIFILM X-T30 II, or it's issue for libraw?

xrayfur commented on 2021-10-12 19:50 (UTC)

Understandable, thanks

guzzisti commented on 2021-10-12 19:38 (UTC)

@xrayfur - nope.

As mentioned by @grazzolini you should create a personal makepkg.conf to provide the settings you require. Details on https://man.archlinux.org/man/makepkg.conf.5

xrayfur commented on 2021-10-12 19:20 (UTC)

@guzzisti, could you please add make -j $(nproc) in build() function to utilize all CPU cores for compiling?

guzzisti commented on 2021-08-29 08:50 (UTC)

@SinClaus this may be a bug in ART, maybe its already fixed in the dev branch, you should try art-rawconverter-git if its solves the problem.

If not, please report upstream on https://bitbucket.org/agriggio/art/wiki/Home (or https://discuss.pixls.us/c/software/art/36)

SinClaus commented on 2021-08-28 13:38 (UTC)

perl-image-exiftool is installed, ART, version 1.9.3 crashes if running in directory with .CR3 file. Last sentences: /usr/include/c++/11.1.0/array:188: std::array<_Tp, _Nm>::value_type& std::array<_Tp, _Nm>::operator [with _Tp = DCraw::CanonCR3Data::crx_data_header_t; long unsigned int _Nm = 16; std::array<_Tp, _Nm>::reference = DCraw::CanonCR3Data::crx_data_header_t&; std::array<_Tp, _Nm>::size_type = long unsigned int]: Assertion '__n < this->size()' failed. Aborted (core dumped)

guzzisti commented on 2021-07-12 10:43 (UTC)

@SinClaus Do you have the optional dep perl-image-exiftool installed?

If this doesn't fix the crash please report upstream.

SinClaus commented on 2021-07-12 10:40 (UTC)

I read today that ART can open CR3 images... Now Art is installed again in my comp, but crashes trying open directory with CR3 file...

grazzolini commented on 2021-06-29 16:33 (UTC)

Please, remove this line from your PKGBUILD: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=art-rawconverter#n30

it's forcing a NPROC setting on people and it might make them use all their CPU. Everyone should customize their own -j setting with ~/.config/pacman/makepkg.conf.

guzzisti commented on 2021-05-26 14:41 (UTC) (edited on 2021-05-26 14:42 (UTC) by guzzisti)

Seems like the tag has been removed upstream. I'll contact the dev and update the package if needed.

PS: please put log output and so in code tags to make it more readable.

ignace72 commented on 2021-05-26 14:22 (UTC)

ART cannot be built. Here is the output of the terminal translated into English: Building art-rawconverter ... ==> Creation of the art-rawconverter 1.9.1-1 package (Wed May 26, 2021 4:17:16 PM) ==> Checking dependencies for execution ... ==> Checking dependencies for compilation ... ==> Source recovery… -> Update of the art-rawconverter_1.9.1 git repository… Retrieving origin -> bft_20.zip found ==> Validating source files with sha256sums… art-rawconverter_1.9.1 ... Ignored bft_20.zip ... Success ==> Deletion of the existing $ srcdir / directory ... ==> Extraction of sources… -> Creation of a working copy of the art-rawconverter_1.9.1 git repository ... Cloning in 'art-rawconverter_1.9.1' ... made. fatal: invalid reference: 1.9.1 ==> ERROR: Failed to create a working copy of the art-rawconverter_1.9.1 git repository Abandonment ... Cannot build art-rawconverter

nvllsvm commented on 2021-02-24 06:44 (UTC)

Please add perl-image-exiftool to optdepends. It's required to view metadata of CR3 images.

For reference: https://bitbucket.org/agriggio/art/issues/166/no-metadata-for-cr3

nvllsvm commented on 2021-02-04 00:44 (UTC)

1.8.0-1 fails to build as it attempts to use non-existent Git tag 1.8.0.

The Git tag is actually 1.8; changing the pkgver to 1.8 fixes the build for me.

guzzisti commented on 2020-05-23 18:28 (UTC)

After the transition to gcc 10.1 images may become red. I've added a patch to adjust the build params to use -fno-tree-loop-vectorize to mitigate this issue.

As the use of tcmalloc leads to a segfault on startup (atleast on my system) i reverted this option for the moment.

guzzisti commented on 2020-05-22 07:17 (UTC)

Seems like the transition to GCC 10.1 broke something. ART builds fine but segfaults on startup.

I'll have a look at this.

guzzisti commented on 2020-04-12 15:48 (UTC)

I've modified the PGKBUILD to make use of tcmalloc, because of this gperftools is now an additional dependency.

This is should mitigate exhaustive memory usage of ART: https://bitbucket.org/agriggio/art/issues/48/possible-memory-leak