Hello all,
Today we have released a new maintenance update for WaveLab Pro 9 and WaveLab Elements 9. This patch updates an existing WaveLab installation to the current version 9.0.15.
It fixes some issues related to plug-ins, WaveLab exchange and OS-X compatibility.
The update patcher and the Version History can be found as always on the corresponding downloads page:
WaveLab Pro 9.0.15 Update >
WaveLab Elements 9.0.15 >
Best regards,
GN
WaveLab Pro 9.0.15 Update now available
-
Guillermo Navarrete Guillermo Navarrete https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=306387 - KVRist
- 478 posts since 4 Jun, 2013 from Hamburg, Germany
-
- KVRAF
- 2048 posts since 13 May, 2004 from Germany
I cant't believe that the issue with the cc121/mackie control etc etc is not fixed till now.
Honestly: who tests this shit fpr you ?
I noticed this after 30 seconds usage 30 seconds!!!!
Thet shouldn't even have passed an alpha test.
I can only strongly advice NOT to buy Wavelab in its current state. Just look at the Steinberg forum. Every second reply from PG is "yes I have to fix that" "this needs a fix" "this will be fixed in..." etc etc
some the most basic functions are only working with workarounds atm
Im completele pissed off atm.
Ihave an 350,00 EUR cc121 from the same manufacturer and have to use a bloody mouse because NOT A SINGLE alpha/beta tester seems to have noticed that things are completely broken ???
Remember: it took me 30 seconds to realise that I have burned my next 150,00 EUR on untestet Steinberg shit.
Honestly: who tests this shit fpr you ?
I noticed this after 30 seconds usage 30 seconds!!!!
Thet shouldn't even have passed an alpha test.
I can only strongly advice NOT to buy Wavelab in its current state. Just look at the Steinberg forum. Every second reply from PG is "yes I have to fix that" "this needs a fix" "this will be fixed in..." etc etc
some the most basic functions are only working with workarounds atm
Im completele pissed off atm.
Ihave an 350,00 EUR cc121 from the same manufacturer and have to use a bloody mouse because NOT A SINGLE alpha/beta tester seems to have noticed that things are completely broken ???
Remember: it took me 30 seconds to realise that I have burned my next 150,00 EUR on untestet Steinberg shit.
-
- KVRist
- 410 posts since 9 Oct, 2013 from uk
Fix for CC121 problems coming in v9.0.20 - found that out, after reading your post, in 12 seconds on the SB forums... any good for your particular complaint...?
System 1 - Win11; i9 13900HK miniPC; 64Gb; Iris XE graphics; Cubase 15.0.10; Studio Pro v8.0.3;UR44 i/o
System 2 - Win10; i7 4790; 16Gb; GTX750Ti; Cubase v14.0.41; WLab Pro v12.0.51; StudioOne v6.6.4
System 2 - Win10; i7 4790; 16Gb; GTX750Ti; Cubase v14.0.41; WLab Pro v12.0.51; StudioOne v6.6.4
-
- KVRian
- 662 posts since 10 Jan, 2008
I may be wrong here, but from what I've read the CC121 is a dedicated cubase control surface. the compatibility chart for the hardware does not even list wavelab, neither is it mentioned in any of the manuals I quickly scanned (just for curiosity, since I wanted to know what the CC121 is all about).
yes, there is a paragraph in the wl9 manual about the integration of the CC121, but still there is a hint like "remember that the CC121 was originally developed for controlling cubase". in my humble opinion this makes clear that wavelab integration isn't exactly the main focus. one could argue that cooperation with wavelab is a nice addition, but a non-working setup does not exactly renders an advertised feature unusable...
I see your point, somehow, that losing a function that worked before is not what you expected, but then... other people had to upgrade their operating system to even install it...
yes, there is a paragraph in the wl9 manual about the integration of the CC121, but still there is a hint like "remember that the CC121 was originally developed for controlling cubase". in my humble opinion this makes clear that wavelab integration isn't exactly the main focus. one could argue that cooperation with wavelab is a nice addition, but a non-working setup does not exactly renders an advertised feature unusable...
I see your point, somehow, that losing a function that worked before is not what you expected, but then... other people had to upgrade their operating system to even install it...