Unexpected Names in Auto Split Series Naming

WaveLab
1

Hi,

Using Assign Key in Series mode and naming by “Name + Key” produces unexpected file names.

Using Auto Split

Options Page:

Assign Key (Enabled)

Series

  • First Key 24 (C0)
  • Semitone Increments +3

Naming Page

  • As Audio File + Key

I’m getting:

(C0)
(F#0)
(C1)
(C1) (01)
(F#1)
(F#1) (01)
(C2)
(C2) (01)
(F#2)
(F#2) (01)
(C3)
(C3) (01)
(F#3)
(F#3) (01)
(C4)
(C4) (01)
(F#4)
(F#4) (01)
(C5)
(F#5)

Note that I used this function extensively during my demo period a couple of months ago, and everything worked perfectly.

In the meantime, I’m using the “As Following List” option, which works as expected, but I would like to know if there is anything I can do on my side to use this feature without errors.

Thanks,
Gustavo

Mac OS Sonoma 14.5 (M1)
Wavelab 12 .0.30 (b696)

2

I did a quick test and it works. What is the name of the source file? How do you split?

3

Hi,

Thanks for taking the time to check this.

I’m splitting by silence. Original file name is monastery.wav.
It’s a classic multisample waveform and there are no issues with the splitting; using a list for the naming works flawlessly.

Here is a dropbbox link where you can find screenshots from the Auto Split settings, the waveform, and the output.

I can’t post links so I replaced dots with “(dot)”

www(dot)dropbox(dot)com/scl/fo/5yfrcm3e7467ks8xyo66b/ADrtXg21aegsg2yNHSNdDE4?rlkey=5ugtqvc235dpvvljd2lsbhbi3&dl=0

As I sais before, I used this feature a lot a couple of months ago, same scenarios, similar material, and the naming feature never created those (01) suffixes before.

Best,

4

Please add the audio file on your picture, in your drop box, for a complete context. Thanks.

5

Hi,

Just replaced the original file for a new one (the previous one is from a client), and updated screenshots, I also added the output files.

Thanks again for your time!

6

After analyzing the problem, I discovered a bug that was introduced in version 12.0.30 or 12.0.20. It concerns the frequency to MIDI note string conversion. I apologize for the inconvenience. This issue will be fixed in the upcoming 12.0.40 release. Thank you for providing the data, which made it easier to identify the issue.

1 Like
7

Excellent! Looking forward to the next update.

Thanks!