Package Details: spleeter 2.4.0-3

Git Clone URL: https://aur.archlinux.org/spleeter.git (read-only, click to copy)
Package Base: spleeter
Description: Deezer music source separation library and tool using pretrained models
Upstream URL: https://github.com/deezer/spleeter
Keywords: broken
Licenses: MIT
Submitter: fordprefect
Maintainer: xiota
Last Packager: Auerhuhn
Votes: 2
Popularity: 0.000008
First Submitted: 2019-11-14 08:38 (UTC)
Last Updated: 2024-04-28 12:23 (UTC)

Pinned Comments

davinosuke commented on 2024-06-30 14:34 (UTC)

I've found a couple of reasonable alternatives, at least for my needs, but they aren't available in the aur. I had to install them with pip in python3 virtual environments.

https://github.com/adefossez/demucs https://github.com/sigsep/open-unmix-pytorch

They both offer simple shell command interfaces for splitting. demucs seems to be better and more configurable, but it is very slow, taking over a minute to process a 3 minute song. Open-Unmix is fast (<15s), but the non-vocal "residual" audio file it produced didn't sound as clean to me. That may just be my imagination, though. Also, FYI, the --ext (extension) option needs the dot included to work.

Auerhuhn commented on 2024-04-28 12:23 (UTC) (edited on 2024-07-01 07:50 (UTC) by Auerhuhn)

tl;dr This package no longer works on Arch Linux.
Also, the upstream project seems unmaintained.
You may want to start looking for alternatives.

In April 2024, the tensorflow package on Arch Linux was updated to v2.16, which no longer supports the Estimator API.
This means that the spleeter package is no longer working.

Additionally, the upstream project seems to have pivoted to focus their development efforts on Spleeter Pro, leaving Spleeter’s community edition essentially unmaintained.

Given upstream project’s track record of ignoring community contributions including critical bug fixes, I feel that contributing a fix to migrate away from Estimator would be a waste of everyone’s time.

Instead, I recommend everyone to migrate away from Spleeter altogether and to look for alternatives instead.

I’m going to orphan this package after 2024-06-30 so it can be reaped on the AUR’s next Spring cleaning. Update 2024-07-01: Disowned.

Latest Comments

1 2 3 4 5 6 Next › Last »

Auerhuhn commented on 2024-06-30 14:49 (UTC)

Thanks for sharing your research @davinosuke.

Pinning your comment.

davinosuke commented on 2024-06-30 14:34 (UTC)

I've found a couple of reasonable alternatives, at least for my needs, but they aren't available in the aur. I had to install them with pip in python3 virtual environments.

https://github.com/adefossez/demucs https://github.com/sigsep/open-unmix-pytorch

They both offer simple shell command interfaces for splitting. demucs seems to be better and more configurable, but it is very slow, taking over a minute to process a 3 minute song. Open-Unmix is fast (<15s), but the non-vocal "residual" audio file it produced didn't sound as clean to me. That may just be my imagination, though. Also, FYI, the --ext (extension) option needs the dot included to work.

Auerhuhn commented on 2024-04-29 10:32 (UTC)

@Potajito Not that I know of, but I haven’t done any research yet.

Potajito commented on 2024-04-29 10:30 (UTC)

@Auerhuhn is there any alternative/fork for this?

xiota commented on 2024-04-29 03:43 (UTC)

I’m going to orphan this package after 2024-06-30 so it can be reaped on the AUR’s next Spring cleaning.

@Auerhuhn You could also open a deletion request.

Auerhuhn commented on 2024-04-28 12:23 (UTC) (edited on 2024-07-01 07:50 (UTC) by Auerhuhn)

tl;dr This package no longer works on Arch Linux.
Also, the upstream project seems unmaintained.
You may want to start looking for alternatives.

In April 2024, the tensorflow package on Arch Linux was updated to v2.16, which no longer supports the Estimator API.
This means that the spleeter package is no longer working.

Additionally, the upstream project seems to have pivoted to focus their development efforts on Spleeter Pro, leaving Spleeter’s community edition essentially unmaintained.

Given upstream project’s track record of ignoring community contributions including critical bug fixes, I feel that contributing a fix to migrate away from Estimator would be a waste of everyone’s time.

Instead, I recommend everyone to migrate away from Spleeter altogether and to look for alternatives instead.

I’m going to orphan this package after 2024-06-30 so it can be reaped on the AUR’s next Spring cleaning. Update 2024-07-01: Disowned.

Auerhuhn commented on 2023-11-05 20:33 (UTC)

is there any practical difference?

@xiota It’s just a smaller dependency, no difference other than that.
(The non-core part of poetry is simply not needed for the build.)

Do I need to revise other python packages?

I’d say that’s up to you.
(I did change it in all my packages for consistency’s sake.)

xiota commented on 2023-11-05 20:31 (UTC)

@Auerhuhn python-poetrypython-poetry-core, is there any practical difference? (Do I need to revise other python packages?)

xiota commented on 2023-10-23 01:54 (UTC)

@sekret I also have all passing tests with no mock plugin. While mock and python-mock are not in the PKGBUILD, they are in the poetry.lock file Don't know why/how/whether it changes results.

Not a clean chroot if not cleaned before build. Here's the dependency tree of the AUR packages:

python-ffmpeg-python 0.2.0
python-museval 0.4.0
  python-musdb 0.3.1
    python-stempeg 0.1.8
      python-soundfile 0.12.1
python-norbert 0.2.1

Since the failing tests are for 4stems, if you don't use 4stems, you can build with --nocheck.

Auerhuhn commented on 2023-10-22 11:12 (UTC) (edited on 2023-10-22 11:17 (UTC) by Auerhuhn)

@sekret Ok, I tried makechrootpkg -n -r $CHROOT but tests are still passing for me.

I've never used aurutils. It installs the executable /usr/bin/aur, but I don't see the switches -c, -f nor -N.

Apologies for my confusing comment. I was referring to the aur build subcommand. I invoke it from inside the checked-out PKGBUILD directory like so:

aur build -cfN .

and cannot manage to get it running right now. I'll investigate this further another day.

Alright, let me know if and when you get around to it, or if you find another way that allows me to reproduce those failures.