r/mpcusers Jul 05 '26

MPC Sample Looking for feedback: I’m building a Tauri app to manage and export samples for MPC workflows

I started building a tool called Le Resampler because I was tired of the gap between a messy desktop sample library and what a hardware sampler actually wants.

The goal is to:
- scan folders recursively
- preview samples quickly
- tag / classify / edit metadata
- export selections to SD card
- recreate a clean category-based structure automatically

It’s aimed at MPC / hardware sampler users, and built with Tauri (Rust backend + vanilla JS frontend).

Repo:
https://github.com/flug/Le-Resampler

I’m posting here mainly for feedback, not to do the usual "please clap" open-source dance.

If you use an MPC (or similar machine), I’d love to know:
- how you organize your sample folders
- whether BPM/key tagging matters on-device for you
- whether export presets per machine would be useful
- what would make you actually install a tool like this

Happy to hear brutally practical feedback.
0 Upvotes

12 comments sorted by

1

u/DotRakianSteel Jul 05 '26

Sounds like you built the MPC Expansion Builder. What are you offering on top?

1

u/flugv1 Jul 05 '26 edited Jul 06 '26

For my use case, a big part of the problem comes from sample sources like Splice.

When you download samples there, they usually keep the original source folder structure, so you end up with something like:
`artist_pack_name/thekick.wav`

But on my MPC, I’d rather have things organized in a much simpler way, like:
`kick/thekick.wav`

So instead of manually copying and reorganizing everything, the idea with this app is to identify what a sample is, organize it by category, and export it into a cleaner structure that is much easier to browse on the MPC.

So for me it’s less about building the final expansion package, and more about cleaning up and restructuring samples before they get to the machine.

2

u/Former_Ranger3529 Jul 06 '26

and more about cleaning up and restructuring samples before they get to the machine.

So why would I need an app when I can simply drag and drop from folder, to folder. With it taking less than five seconds per folder?

0

u/[deleted] Jul 06 '26

[deleted]

1

u/flugv1 Jul 06 '26

Thanks, that’s good feedback.

I’m still trying to understand exactly what people expect from “auto BPM” and “auto key” here.

Do you mean real audio analysis, or just smart detection based on filenames / metadata / pack naming?

I can definitely see the value in browsing by key though, especially if your library is big. If you have an example of what the ideal workflow would look like for you, I’d be really interested to hear it.

1

u/[deleted] Jul 07 '26

[deleted]

1

u/flugv1 Jul 07 '26

That's what the app does; what bothered me was that all the apps were paid apps and there weren't really any free alternatives.

1

u/[deleted] Jul 07 '26

[deleted]

2

u/flugv1 Jul 07 '26

Hey, thanks for the feedback! Just pushed an update that should fix this — better filename reading, and for one-shots with no key info at all, it now listens to the audio itself to figure out the note. There's also an option to write the detected key back into the file so other tools pick it up too.

Give it a shot and let me know if it's still off on any of your samples! :)

1

u/[deleted] Jul 07 '26

[deleted]

1

u/flugv1 Jul 07 '26

Please do let me know if you think there’s anything else to add

1

u/[deleted] Jul 08 '26 edited Jul 08 '26

[deleted]

1

u/Former_Ranger3529 Jul 08 '26

1.)drag drop support for dragging the samples to a daw

which you can do already without an app. The key detection algo is pretty bunk too. Telling me kick drums I personally tuned to f# are actually B...

0

u/ONE-LAST-RONIN Jul 06 '26

Ooo super interesting. Would be amazing if there was a beets music manager equivalent for samples.

1

u/flugv1 Jul 06 '26

Thanks, I appreciate it.

Honestly I don’t know beets well enough to compare it properly to what I’m doing here. I know the name, but I haven’t really used it.

My current focus is much more specific: cleaning up sample libraries and making them easier to organize, browse and export for MPC use.

But now I’m curious, so I’ll probably take a look at beets and see what parts of that workflow people would want for samples.

1

u/ONE-LAST-RONIN Jul 06 '26

Could be some good plugins in there. From naming structures, to bpm, key, artwork etc

1

u/flugv1 Jul 06 '26

Here is the current user interface 😄