Package Details: chromaprint-fftw 1.5.1-5

Git Clone URL: https://aur.archlinux.org/chromaprint-fftw.git (read-only, click to copy)
Package Base: chromaprint-fftw
Description: Library for extracting fingerprints from any audio source (uses fftw for FFT calculations instead of ffmpeg)
Upstream URL: https://acoustid.org/chromaprint
Keywords: chromaprint fftw
Licenses: GPL-2.0-or-later
Conflicts: chromaprint
Provides: chromaprint, libchromaprint.so
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 62
Popularity: 1.12
First Submitted: 2015-12-27 19:32 (UTC)
Last Updated: 2025-04-04 11:04 (UTC)

Required by (78)

Sources (3)

Latest Comments

1 2 3 4 5 Next › Last »

dbermond commented on 2025-06-01 01:41 (UTC)

@slapjd repository chromaprint needs ffmpeg, but here we use it in the other way around: ffmpeg-full and ffmpeg-full-git requires chromaprint. And yes, the goal is mainly to avoid circular dependency with ffmpeg, as this can be a pain, specially when ffmpeg increases the soname version (as it is happening with ffmpeg-full-git right now at the time of writing). It's a good practice to avoid circular dependencies whenever possible, specially on AUR packages. And splitting chromaprint into different packages for tools and libs does not seem a good idea to me just to separate a single binary executable that is less then 40kb, and this would also cause a circular dependency at build time.

slapjd commented on 2025-05-31 13:28 (UTC)

@dbermond ah, i see. is this package trying to avoid ffmpeg dependencies entirely? thinking about it, i would assume fpcalc only uses ffmpeg directly for transcoding the input file to raw audio and then uses actual chromaprint library for any calculations.

i only ran into issues because i started using ffmpeg-full (for better AAC transcodes) which depends on this specifically, presumably to avoid circular dependency problems? for now i just copied the fpcalc binary into /usr/local/bin to make picard work (for anyone else with this issue).

it would be nice if the official package was split into chromaprint and chromaprint-tools or fpcalc or something, then this could maybe do the same and avoid circular dependency problems while still being able to depend on fpcalc (although packages only requiring the library could/should probably just depend on libchromaprint.so then this could only provide that).

regardless, thanks for clarifying!

dbermond commented on 2025-05-31 01:48 (UTC)

@slapjd because 'BUILD_TOOLS' requires ffmpeg, and this package uses fftw instead of ffmpeg for the fft calculations.

slapjd commented on 2025-05-30 21:33 (UTC)

Hi, is there a reason DBUILD_TOOLS is off? Official chromaprint has it on and Picard depends on it (fpcalc) for AcoustID.

dbermond commented on 2025-03-15 02:04 (UTC)

@Culted package updated. Thanks for reporting.

Culted commented on 2025-03-14 23:13 (UTC)

i see what happened 2 days ago gtest from the official repository was updated and no longer ships the source files

Culted commented on 2025-03-14 23:01 (UTC) (edited on 2025-03-14 23:06 (UTC) by Culted)

getting an error during compilation

-- Using swresample for audio conversion -- Found GTest: /usr/src/googletest -- Configuring done (2.2s) CMake Error at tests/CMakeLists.txt:4 (add_library): Cannot find source file:

/usr/src/googletest/src/gtest-all.cc

Tried extensions .c .C .c++ .cc .cpp .cxx .cu .mpp .m .M .mm .ixx .cppm .ccm .cxxm .c++m .h .hh .h++ .hm .hpp .hxx .in .txx .f .F .for .f77 .f90 .f95 .f03 .hip .ispc

CMake Error at tests/CMakeLists.txt:4 (add_library): No SOURCES given to target: gtest

tried using googletest-git,same issue

dbermond commented on 2023-02-04 16:24 (UTC)

@JeSuisNerd This is an issue with gtest 1.13.0, which does not support C++11 anymore. Fixed.

JeSuisNerd commented on 2023-02-01 18:01 (UTC)

I hit presumably the same issue as Accidentaccio:

error: #error C++ versions less than C++14 are not supported.

Seems to be an issue upstream, it was resolved by patching CMakeLists.txt line 27: set(CMAKE_CXX_STANDARD 11) => set(CMAKE_CXX_STANDARD 14)

Accidentaccio commented on 2023-01-31 22:05 (UTC)

ERROR in build()

1 2 3 4 5 Next › Last »