Skip to content

[Bug]: Error when creating Stems when they are already created #635

Closed

Description

@wastedbits

Before reporting

  • I'm on the latest release and the issue still happens.
  • I searched existing issues and didn't find a duplicate.

What happened?

If a song is already split into the stems and I click on the SPLIT STEMS button, it changes from SPLIT STEMS to PROCESS and throws an error. After that you can change songs but the button stays as PROCESS

Steps to reproduce

Use Split Stems to splits a sons into stems

  • Then Click Split Stems again. It generates the error shows on the attached screenshot. The button changes to PROCESS
  • Then switch to any song, the button stays as PROCESS

Split Stems is a button that is relevant to the top row only in the UI only if you upload a song. I think that's is confusing usability especially if I just search for song and then expect the button to act

Suggestions:

  1. Simple -- When a song is upload, the Split Stems is active, and when the song is split successfully, either grey out the button or replace it with transport buttons. If UI space is an issue, I'd recommend remove all those bullets points in each of the boxes in the Extract section.

  2. More than Simple:

  • Only when a song is uploaded, the button is called Split Stem and is active, it processes, and once the song is split button changes to Re-SPLIT. That means I can reselect my Extract choices and apply Re-Split
  • this also implies that if I click on any song in the library, the button shows Re-Split

Operating system

Windows

StemDeck version

0.17.2

How did you install it?

Windows ZIP

Logs / screenshots

Image

Activity

  1. wastedbits commented on Sep 17, 2026

    @wastedbits
    Author

    another thought, is once the song is split, that SPlit Stems button could be replaced with Export MIX
    The export mix button seems to be in a spot that is all about click track and loops etc

  2. thcp commented on Sep 20, 2026

    @thcp
    Collaborator

    Hi @wastedbits , if you go to settings/logs, could you please share the logs of this given error? Also, when this error happens, no message with the issue shows up on the notification ?

    Regarding

    another thought, is once the song is split, that SPlit Stems button could be replaced with Export MIX
    The export mix button seems to be in a spot that is all about click track and loops etc

    Still trying to figure out a best placement without bloating to much the UI, I'm going to keep your proposal possibly for 17.04

  3. wastedbits commented on Sep 21, 2026

    @wastedbits
    Author
  4. wastedbits commented on Sep 21, 2026

    @wastedbits
    Author

    screenshot of error and the stemdeck.log both uploaded. please check.

  5. self-assigned this
    on Sep 21, 2026
  6. thcp commented on Sep 21, 2026

    @thcp
    Collaborator

    Fixed in #646, merged as be52bf0. It ships in the next release.

    All three things in this report had the same root: the button acted on the composer, not on the track you clicked.

    The error. Opening a track writes its source back into the composer. For a link that is a URL the button can submit. For a file import the source is the synthetic local:my song.mp3, and stripping the prefix put the bare filename in the box, so pressing the button sent my song.mp3 as though it were a link. The box now holds only something that can actually be imported.

    The button staying as PROCESS. It restored a different label from the one the markup ships, so the first submit of a session renamed it permanently, on a successful import as much as a failed one. It keeps its name now.

    Acting on the track. This is the one that needed the most. A file import had nothing the button could act on at all, because the source file was deleted once separation finished. Uploads now keep their source, and POST /api/jobs/{id}/resplit separates one again from it. Pressing Split stems on an imported file re-splits it with whatever you have selected in Extract, and a pill in the composer names the track so it is clear what will be split. A staged file or a typed URL is still a new import and wins.

    The label itself is unchanged. What the button does is the same thing it always did, and only where it reads the track from differs.

    Two things worth stating plainly:

    • Every uploaded track now keeps its source, 100-300 MB each, where before only the stems survived. That is the price of being able to split an imported file a second time at all.
    • Tracks split before this shipped had their source deleted, so they cannot be re-split. Only imports made from the next release onward can be.

    One thing found while building it, rather than reported: reusing the original's source for the new job made the library replace the very track the re-split came from, leaving its job directory on disk with nothing referencing it. Caught by asserting the original was still there afterwards, and it was not.

  7. thcp commented on Sep 21, 2026

    @thcp
    Collaborator

    @wastedbits thanks for this one. Splitting the error from the usability point is what made it findable, because the two turned out to be the same thing: the button was reading from the search bar rather than from the track you had clicked.

    Your first suggestion was to grey the button out once a song is split. I went with the second one instead, minus the rename. Pressing Split stems on an imported file now re-splits that file with whatever you have selected in Extract, and the composer shows a small pill with the track name so it is clear what the button will act on. The label stays "Split stems", since what it does has not changed.

    Worth knowing for your own library: this only works for files imported from the next release onward. Splitting used to delete the uploaded file once it was done, which is why there was nothing to re-split from, and anything already in your library was cleaned up that way. New imports keep their source.

    If you want updates, @stemdeckapp on Twitter is where they go. Try it when the next release is out and let me know how it holds up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions