Nord Sample editor importing samples with loop points!!!

[Eriknie]

Good to hear you got it working!
No idea why it doesn't work on your first computer, python should work on all devices once installed. But there could be different versions of libraries...
I did not test my software on all possible combinations.
Thanks for the update.

[Zeitfraktur]

I noticed that the Nord sample editor does not allow to manually set a loop start exactly at sample start position but needs a small offset.
Is this a known limitation?
And what would that mean if my samples have loop points from file start to end in regards to your script?

Greetings
Sascha

[Eriknie]

Should work. But i never tested that.
You could try to run the script and use a open source text compare tool like winmerge.
If it are only a few samples, you could manually change the looping points in the project file to loop from start till end.
You could check the python file for the names of the loopingpoints
good luck

[futschikato]

First of all, thank you very much for the script. I have tested it successfully.
Today I had started to edit some samples from my EMAX for the NW:

SF2 to WAV (31khz) with (ExtremeSampleConverter)
Sample rate converted 39 to 44.1kHz (r8brain) -> the Nord Sample Editor allows only 44.1, 48 or 96 KHz Samples

Both sample have loop points in my opinion, but the script reports no loops
What could be wrong, theSF2 format, or the conversion to 44.1kHz or the fixloop?

Greetings

[Eriknie]

Did you use the enhanced version of the wavfile.py? the original does not detect looppoints
I'll write a small python script this week to display the looppoints in wav files.

[futschikato]

yes i use the enhanced version of the wavfile.py
I used some samples from https://www.bjoernbojahr.de/nl3-edm-sample-pack.html for testing and the script doesn't find any loop points in one file (Sample48), but the loop detection works in the other files.

[Eriknie]

Strange, no clue what is going on. Perhaps it has something to do with the conversions.
If my script does not find the loops, you could dive into the wavfile.py to find out what is going on.

[cgrafx]

Changing the sample rate changes where the loop points would need to be placed. They are not based on the waveform, but simply based on time, so I'm pretty sure loop points will not survive a sample rate conversion.

[futschikato]

Strange, no clue what is going on. Perhaps it has something to do with the conversions.
If my script does not find the loops, you could dive into the wavfile.py to find out what is going on.

I did not convert Björn's samples from my second test. They are the original samples, of which not all loop points are recognized.
I will have a closer look at the wavfile.py...

[futschikato]

Changing the sample rate changes where the loop points would need to be placed. They are not based on the waveform, but simply based on time, so I'm pretty sure loop points will not survive a sample rate conversion.

As the screenshots at my first post show, the loop points are still there after converting ?!

Original (31250 Hz)

Wavesize: 53378 pts
Sustain Loop: 21565 to 53369 pts

Converted (44100 Hz)

Wavesize: 75327 pts
Sustain Loop: 30433 to 75314 pts

Here are the two samples in Wavelab 11 LE :