Feature Request: Export loop data into a .txt file or similar.

[Al666v]

I love your software, but downside is that i have to edit each one of the audio files' loop metadata and that's a massive undertaking.

I'm modding a visual novel right now, and it has 100+ audio files for BGM. All of the BGM had loop metadata embeded to them. I was trying to normalized the audio, repack them back into the game files. It worked but the loop is missing. That's why i use your software.

It would be cool if you can extract a file or folder of audio with loop data into something like a .txt file and then import them into another batch of new files.

[larspalo]

It would be cool if you can extract a file or folder of audio with loop data into something like a .txt file and then import them into another batch of new files.

In a9c51b6 I've implemented a batch process for exporting the loop information to a .tsv file but I think there's a better option than actually importing from that. There's a batch process for copying existing pitch info from one directory with .wav files to corresponding files (in another directory).

I personally don't see much use for it, in the context of LoopAuditioneer primarily being a tool for preparing samples for a sample player like GrandOrgue, but I think I could relatively easily implement a batch process to copy over loop information from one set of (.wav) files to another (if the start/end would still be valid). There's of course no guarantee that loops will still be okay if the audio data is changed/different, though simple changes in amplitude should normally not cause much issues.

[Al666v]

Thanks alot!

[larspalo]

Bacth copying of loop(s) from corresponding file(s) is implemented in 258b756 and intermediate builds can be found at the bottom of the page at https://github.com/GrandOrgue/LoopAuditioneer/actions/runs/21320036325 until a new release is done.