| Summary: | ReplayGain 2.0 Tagging Support | ||
|---|---|---|---|
| Product: | [Applications] kid3 | Reporter: | siddasquid |
| Component: | general | Assignee: | Urs Fleisch <ufleisch> |
| Status: | REPORTED --- | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 3.9.x | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
siddasquid
2025-12-29 22:33:38 UTC
Thanks for the feature request. Probably, it does not make sense to duplicate the rsgain functionality in Kid3. It could also be a problem if the third party libraries and the replay gain functions would both try to modify the files. Kid3 can easily be extended with User Actions. So if the easy mode of rsgain is enough, you could just add a user action with command "rsgain easy %d", or for custom mode you can use %F to pass multiple files. Note, however, that you would have to make sure that all files inside Kid3 are saved before running rsgain or they might be corrupted. Therefore, it would probably be better to use a simple QML script which first calls app.saveDirectory() and then script.system() to run rsgain. QML would also make it possible to provide a simple UI for the options. What exactly would you prefer? Thanks for responding. Whichever is simplest to implement and works, as I'm not a programmer at all. Using a simple UI and being able to select between scanning "per-file track gain" or "as a single album" I think would be great. As long as it will support ReplayGain 2.0 tagging, I'm happy if you'll consider it. |