Some SFZ files have the loop points embedded in the WAV. How can i migrate the loop to the SFZ ?

[hcv242]

Serum 2 does not load loop points from SFZ files that have them embedded in the wav files.
Serum 2 can only read loop points specified on the .SFZ.
Most of my SFZ files have the loop points embedded in the wav files, instead of having them specified on the SFZ file.

I need to migrate the wav embedded loop points to the SFZ file. Any ideas how can i achieve this?

I have tried Awave with no luck - maybe i am missing something
and i have tried extreme sample converter

Those are the tools that i have.

Are there any free or cheap tools that can do the job ?

[eLawnMust]

If that is the case then Serum needs fixed, hell, old trackers & audio editors read loop points from the WAVs internals, WTF?

So you are looking for like this?



This is what DiscoDSP HighLife spits out after sampling another VSTi & when you save as SFZ... Maybe you could import into it then save out, dunno never tried that, I just use HighLife for sampling output of VSTi to SFZ sample libraries-

soundbytes.de/temp/HighLifeR3_beta.zip

[hcv242]

If that is the case then Serum needs fixed, hell, old trackers & audio editors read loop points from the WAVs internals, WTF?

So you are looking for like this?



This is what DiscoDSP HighLife spits out after sampling another VSTi & when you save as SFZ... Maybe you could import into it then save out, dunno never tried that, I just use HighLife for sampling output of VSTi to SFZ sample libraries-

soundbytes.de/temp/HighLifeR3_beta.zip

thanks, i do have highlife, but not the release in your link, which is an invalid link.
the release i have is 2.2 and it fails importing every sfz on my hard drive.

[hcv242]

manage to do it with bliss 2 which is also very buggy, but it work with some of my sfz files. the curious thing is that serum 2 loads all my sfz, except the wav embedded loop points.

[eLawnMust]

The one I mentioned has been a 'worked over' version of HighLife, I don't use any other version...

http://soundbytes.de/temp/HighLifeR3_beta.zip

That should work...

[moss]

Serum 2 does not load loop points from SFZ files that have them embedded in the wav files.
Serum 2 can only read loop points specified on the .SFZ.
Most of my SFZ files have the loop points embedded in the wav files, instead of having them specified on the SFZ file.

I need to migrate the wav embedded loop points to the SFZ file. Any ideas how can i achieve this?

I have tried Awave with no luck - maybe i am missing something
and i have tried extreme sample converter

Those are the tools that i have.

Are there any free or cheap tools that can do the job ?

You can use ConvertWithMoss (which is totally free).
Get it from https://mossgrabers.de

Choose SFZ as the source as well as the destination.

Note that reading the loop points from the wave files when not present in the SFZ file was broken. I just released an update 12.2.2 which fixes the issue. Therefore, make sure that you have the latest release.

[hcv242]

You can use ConvertWithMoss (which is totally free).
Get it from https://mossgrabers.de

wow this is amazing.
thank you so much

[audiojunkie]

Be aware: More SFZ parsers read the loop data embedded within the SFZ, than those who read the loop opcodes. Your switch to saving loops from the wav file to the opcodes in text may render these SFZ instruments unplayable in many SFZ parsers.

[enroe]

Be aware: More SFZ parsers read the loop data embedded within the SFZ, than those who read the loop opcodes. Your switch to saving loops from the wav file to the opcodes in text may render these SFZ instruments unplayable in many SFZ parsers.

You mean: "read the loop data embedded with the WAVs".

Because that's the most elegant way: The loop data is tightly
linked to the WAV file itself, so it should remain there. The sfz
players will then automatically play this loop data—without a
single additional line.

[audiojunkie]

Be aware: More SFZ parsers read the loop data embedded within the SFZ, than those who read the loop opcodes. Your switch to saving loops from the wav file to the opcodes in text may render these SFZ instruments unplayable in many SFZ parsers.

You mean: "read the loop data embedded with the WAVs".

Because that's the most elegant way: The loop data is tightly
linked to the WAV file itself, so it should remain there. The sfz
players will then automatically play this loop data—without a
single additional line.

Yes, sorry. I meant WAV.