Hmm I’ll have a look but works on mine - cubase 14 but I think these midi device xmls are a standard format that isn’t version specific. I was going to upload a slightly amended version given the recent firmware update soon so I’ll have another look then

Thx a lot for your detailed answer!
I will then implement 0-99 as this is the range Behringer is documenting BUT use Note #12 for all values <12 as well.

Which octave is Note #12 ? C0 or C1?
If C0 then 12 to 99 would then mean C0 to D7#
Asking because I''m showing the actual note ;-)

If you name MIDI note #60 as C3, than MIDI note #12 is C-1.

But this is just the name, but not the actual played note, as you change the oscillator frequency in the tuning page. So using the note name would not make sense without naming the settings in the tuning page.

There's no specific answer. The lowest note can be C-2, C-1, C0 or even C1. MIDI goes 0-127 and does not assign actual note frequencies to MIDI numbers. If you're making an editor specific to a synth, use the mapping to match the synth's displayed values.

Agree and disagree...
The synth shows 00-99. No very speaking...
Without any octave transpose, the first C key is giving you a C at a certain frequency, right?
Is that a C3?
From there, we know we can transpose -2 octave max so the lowest split key (not very useful) would be C1.
Or am I wrong when thinking like that?

One thing to note is that there is no "C3" which corresponds to an absolute pitch in the synthesizer world. Instead, synthesizers have a "middle C" which has a definite pitch/frequency. On Roland synthesizers, C4 is considered middle C, while on Yamaha synthesizers, C3 is considered middle C. I'm not sure what it is on the PPG.

I'm at a point where if I need to use a software editor with a hardware synth, I will use a similar-sounding plugin instead. I will make an exception only if the hardware synth is a very compact desktop module with a totally unique sound and ample patch storage, i.e, at least 500 patch locations on the device itself. And even here, the software editor must be cross-platform, well-supported, and visually appealing.

The only hardware synths I own that fit this criteria are the Michigan Synth Works Xena and Dave Smith Evolver Desktop. But if Arturia or another plugin developer ever emulates these, I will gladly use the software version instead.

I haven't had a chance to program a Behringer Wave. But I suspect I will feel as you do that I can't be bothered with the archaic UI and all of its cryptic abbreviations. And since the Wave is a keyboard (albeit a compact one,) I can't see myself buying one, especially since there are only 256 patch locations and no cross-platform editor/librarians for it that are likely to be supported over the long haul.

YMMV.

Just a heads up for folks trying to update their Wave to the latest firmware - several people seem to have problems with the process. On Macs (with Sequoia?) the update process seems to fail often putting the unit in DFU-mode ("bricked"). While the first update after I bought the machine several weeks ago went without a hitch, the new one now failed 8 times before it just succeeded. I could not identify any contributing factor (did restarts, different ports/USB cables, removing the MIDI device in A/M-setup...) it just failed in different states and succeeded at last. So - if you have fails - just try and try again until it goes through... (Synthtribe app 2.9.6)

I like the new firmware mode=2 for the exponential amp envelope (some patches subjectively seem to ring out too long now and might need some editing) and the new user transients and sounds are nice too.
Two problems I still encounter are missing notes when keys played too softy and when editing the WT selection the OLED display sometimes doesn't update.
All in all a nice synth though (at a really good price) but you'll have to accept a lot of quirky behaviour. (which not everybody might like and so I had the luck to get a returned pristine unit for 50 bucks off! Yay!)

Mac here, and i had an „update failed“ message as well. But the wave display showed „voice updating“ fo ca. a minute. Autorestart after that and it looks like the update went through nonetheless.

So, maybe don‘t immedialey shutdown the synth when this message appears in the synthtribe app (as a tip for anybody else)

DIGITAL page: is VF and VL used?
Especially with VL≠0 I get this sometimes. There is no way to just use a little bit of Velocity to loudness.

On the original PPG wave2 there was no velocity by the keybed (just some aftertouch for faking velocity per note function was mapped to these velocity parameters when using the keybed. Most PPG users never used it).

Do you guys find the new envelope modes still don’t match the original properly ? Some presets (bank 1 -23) only sound correct to me with envelope mode set at 0 (original ) mode

Did you A/B it with a real PPG wave 2.2/2.3?
This is the only way to check if it does sound "correct".

I have the same thing you have velocity setting on and play a scale then odd notes don't sound while the rest do. I'm using the same pressure on every note. To be sure of my playing been doing the same scales on my other velocity synths and running through a number of upright pianos, a grand and the three electric stage pianos at work. Have no problems except on the wave. It's not always the same notes so not an issue with keys and similar happens with a midi keyboard into the wave. Others are saying similar across the net the velocity is so poor. I also find that with the latest firmware and factory reset that if I select firmware 2 and bank 1 every preset has VF and VO at zero ? While bank 0 with firmware 2 has VF and VO settings for the presets. I'm on the verge of sending it back as numerous other glitches keep occurring. While my Microwave 1 RevA is just a pleasure to use.

The bank 1 sounds are recreation of PPG factory sounds. And as the PPG had no velocity sensing in its keybed, these are set to zero VF and VL to be played the vintage PPG way.
If they would use velocity, they would not sound like a real PPG wave 2.2/2.3.