Buggy wavelab 11

WaveLab
1

now i’m gonna swear

but who the hell made audio driver scan in such a way that it crashes everything what’s possible and beyond possible? why the hell it runs through devices it can’t even handle BEFORE i selected them? like, why?..
and how to prevent it (besides disabling all but one, then launching WL, selecting that one, closing it, re-enabling all the rest and then it’s ok)

after crashing at steinberg’s own invention - asio drivers, should i even start swearing that this thing doesn’t support Steiberg’s own vst2 and 32bit plugins?..

not to start mentioning freezing on scanning scsi cdrw drives…

it’s so horrible, beyond horrible
wavelab 6 costed me 20 euros and well, being so old and meant for windows xp it was acceptable that it’s a bit buggy and can’t support this or that
but that wavelab 11 from decades later would have another bunch of bugs which are a tad nastier… i didn’t expect… even selecting a path and exporting a file… just to find the file ended up in a folder of one-before-the-last export folder… my oh my
how.. in 2025 (ok, 2023) is possible to write stuff so backwards?
ah sorry, maybe not backwards but “rotated 90 degrees” - that’s another good one. if you right click on your level meters the default action that you get - it gets flipped on the side! like… why? and although there is some ‘customising’ provided - if you go there you still can’t get the ‘flip the meters’ option out!.. like… yeah, the most usual stuff i do is flip my monitor on a side and then i’d want to flip my meter (doesn’t matter that the rest of stuff remains unflipped)… why wavelab programmers hate users so much???

now i go to the guts to see if i can help myself by tidying-up .ini files and perhaps selecting needed asio driver in the config that poor thing doesn’t choke again or something… GUESS WHAT
the settings are saved in .DAT files which is semi-machine-language-hex-garbage and uneditable in texteditor.
audio drivers are stored in hidden(!) - let’s hide stuff from the customer - “.last” file in c:\Program Files\Steinberg\WaveLab Pro 11\Settings\Presets\Audio Connections\

and reads like this - try to get it:

LE `ЏGAx AudioStreaming  8 8 Root   P Ш pre ¬  8 h ђ bas x   ofn ђ  tit Untitled
 mdt %Љ¶eЎ8 ј   fad  М   fut  Ь   Rdp  м   psr D¬ ь   srt и    rls    alt  0   agd K \   oid Dante Virtual Soundcard (x64) €   odn Dante Virtual Soundcard (x64) °  8   Inp   num Ш  8 И И Out   num Ш  8 р  pc    cnt     key   Ш , ё val ˜   D € ch T   cnt  d   key t   val €  key1   val1  Ё   cat ё   lay    n Main Playback Bus  8 р и
rc    cnt    key и И  Ш , Ё val ˜   D € ch T   cnt  d   key t   val €  key1   val1  Ё   lay    n Dante rx Stereo 1 а  key1 є™5˜  Ш ь x val1 h  а  X ch $   cnt  4   key D   val  X  key1   val1  x   lay    n Dante rx Stereo 2 °  key2 »™5h  Ш М H val2 8  ° д ( ch ф   cnt     key    val  (  key1   val1  H   lay    n Dante rx Stereo 3 Ђ  key3 ј™58  Ш њ  val3   Ђ ґ ш ch Д   cnt  Ф   key д   val  ш  key1   val1 a    lay    n Dante rx Stereo 4 P  key4 Ѕ™5а  Ш l Д val4 ґ  P „ ¤ ch ”   cnt  ¤   key !   val Д   lay   n Dante rx Mono 1 ш  key5 ѕ™5€a  Ш a la val5 \a  ш ,a La ch <a   cnt  La   key !   val  la   lay   n Dante rx Mono 2 a  key6 ї™50  Ш јa  val6   a Фa фa ch дa   cnt  фa   key !   val     lay   n Dante rx Mono 3 H  key7 А™5Ш  Ш d ј val7 ¬  H | њ ch Њ   cnt  њ   key !   val  ј   lay   n Dante rx Mono 4 р  key8 Б™5Ђ  Ш d val8 T  р $ D ch 4   cnt  D   key !   val  d   lay   n Dante rx Mono 5 ˜  key9 В™5(
 Ш ґ
val9 ь  ˜ М м ch Ь   cnt  м   key !   val 
  lay   n Dante rx Mono 6 @
 key10 Г™5Р
 Ш
ґ
val10 ¤
 @
t
”
ch „
  cnt  ”
  key !   val  ґ
  lay   n Dante rx Mono 7 и
 key11 Д™5  Ш  \ val11 L  и
 < ch ,   cnt  <   key !   val a \   lay   n Dante rx Mono 8

what a lucipher came up with that idea - writing config files in hex and hiding them?

then, if you think i’m looking at a wrong place let’s have a look at another - c:\ProgramData\Steinberg\WaveLab Pro 11\Presets\Audio Connections\

guess what - it’s SAME in there!

WOW. i don’t know what else to say.
and i don’t expect that another 50 euro for WL12 upgrade would fix any of that… or would it???

2

IMO you might try starting by not doing that.

Try reading this: https://helpcenter.steinberg.de/hc/en-us/articles/206087984-Using-32-bit-plug-ins-on-64-bit-systems and this: https://helpcenter.steinberg.de/hc/en-us/articles/4409561018258-VST-2-Discontinued

What do you mean? How? Please clarify.

Why do you need to see them? What are you trying to achieve?

3

Are you running a Merging Technologies Anubis (dante connections) by any chance?

4

hi guys!
i’m trying to achieve a working wavelab 11
but it rose on a wrong leg yesterday (perhaps missing audio output device) and now crashes every time and makes it dangerously close to a bluescreen (my dsp cards freak out with resources and pci allocation warnings, mouse cursor starts to lag and stutter - that’s a sign of digidesign cards having a hard time) - it’s not the first time that it happens but i eventually lost my temper after no WL updates for a year or more - these bugs bug too much!

reading that steinberg decided to abandon technology they invented themselves is a bit ridiculous and does not help at all -
of course i do have jbridge but even that can’t turn vst2 plugin into vst3. now tell me how and where should i re-buy 3000+€ worth of perfectly working algorithmix EQs just for sake that someone at steinberg decided “hell with that, we gonna invent different format for the plugins now”.

for example, new sequoia and samplitude and even cheapest reaper have their own bridge (which might be jbridge inside) and does not bother user with building wraps for every plugin manually;
also they don’t crash any of the old asio drivers - they are either unable to select them either they can use them.
now for wavelab, neither i can set to skip them, neither change priorities manually, it just starts raping the whole system everytime you get near the audio settings window - maybe i just want to have a look at it or select another device - no! it will start raping system the moment i select audio settings - and of course freeze and crash… and what’s the workaround for this? how can i give it a clue to use some driver and not touch the others next time?

@ [Paul_Rat_Blakey] - i’m using apogee symphony mk2 via dante (DVS) (and dante poses no problems for WL, but other drivers do… and if DVS was unavailable last time it hops to whatever else, say pro tools asio driver for the same symphony mk2 via pthd connector - and even if it doesn’t manage to crash on that one - if i disable pthd card for that time -, then it hops upon the next one and crashes there)

5

just tried to start WL11.5pro holding CTRL button while having digidesign card disabled and creamware being occupied through wavelab6 - and WL11 it still crashed successfully on approaching audio settings!
looking at event viewer revealed this - as i’ve guessed and told earlier - it failed on another driver in a queue:

Faulting application name: WaveLabPro11.exe, version: 11.2.0.13, time stamp: 0x63ea7a57
Faulting module name: mgxasio4_x64.dll, version: 2.13.0.0, time stamp: 0x55c8f2c5
Exception code: 0x80000003
Fault offset: 0x00000000000029f7
Faulting process id: 0x0x674C
Faulting application start time: 0x0x1DB9E34090FF454
Faulting application path: C:\Program Files\Steinberg\WaveLab Pro 11\WaveLabPro11.exe
Faulting module path: C:\Program Files\Common Files\MAGIX Services\System\mgxasio4_x64.dll

now i went to that folder and checked that i have already renamed one magix asio dll few years ago to remedy this problem but forgot about it… and a recent magix software install put it there again.

but then again - why WL is so huffy? why it needs workarounds with asio and with scsi? did i mention that it doesn’t burn with certain scsi cdwriters because it hangs them on scanning?
its’ pretty strange as yamaha CDR100 form 1995 works (as perhaps does not care about WL’s deep poking) but yamaha CR-F1SX keeps resetting the bus after being poked and everything freezes. SATA blu ray drive works fine though.

this poking of buses is a bit insane i would say - especially when WL11 inserts a few seconds delay for a soundcard to complete switch to another samplerate - appearing to be gentlest of them all - yet poking everything so fast and hard on audiosettings window that if we had a bus analyzer hooked our hair would have turned gray seeing all that!!

6

WL 11 had a lot of problems. WL 12 fixed a lot of them.

This is a GREAT forum. Swearing and yelling are NOT welcome.

If you are having problems someone here will try to help BUT from reading your messages you seem to have an anger problem that is also NOT welcome.

FWIW

3 Likes
7

This is not part of WaveLab.

2 Likes
8

wavelab by itself can’t put out any sound, can it?
so it depends on asio i/o to access some soundcard.
and what it does it crashes the module and itself while doing that in a not-so-nice-way
and there is no way to tell it not to!
do i care that the magix asio dll is not a part of wavelab? no! because in the end it’s wavelab that crashes, not the module by itself.
if wavelab told ‘oops your asio module blah blah just crashed please choose another’ it would be none of big headache. now the whole wavelab crashes and does it again and again while accessing audio settings. no way to set another driver. the only way is to disable hardware it doesn’t like, then start it, then select hardware that it likes and then you may re-enable your other hardware again… until next time that you want to change it. what the … :frowning: :see_no_evil_monkey:

i observed yet another thing - although it hides older asio drivers from the list it still pokes them wildly on opening audiosettings window! why?

9

yes i am angry because in 20 years of wavelab’s progress they managed to remove bread-and-butter handy ctrl+F shortcut for fade ins and outs, then made asio crash, then made even simplest .mon projects incompatible with old versions of wavelab (put two sausages in a project, save it on WL11 and you won’t be able to open it on WL6!), then removed very handy simple CD project support, then also made cd writers hang the bus, and as if that wasn’t enough, removed vst2 support!

yes, they added a fast multicore processing, a few nice capabilities to projects, way improved master section (it was really rudimentary in WL6), made various new and odd audio formats open, 64bit vsts…
but messed up so many things in exchange - as if - here you go bitches, don’t be too excited with all that :speak_no_evil_monkey:

1 Like
10

You have other fade features with other shortcuts. The easiest one being Control + D to both handle fades in and out.

No. Steinberg is not responsible with buggy Asio drivers.

Montage version is always compatible with older versions.
But old WaveLab version can’t load newer montage versions.
This is very standard.

The montage can be as easy and way more powerful. You just have to spend a little time with it.

4 Likes
11

My Mom always said you will get better results with honey than vinegar. So maybe just list the problems you are having without all the editorializing and I am sure people will be more than happy to help. Getting upset is a sure way to have no help… :roll_eyes:

3 Likes
12

rightclicking brings up this menu and mouse cursor ends up next to “settings” at that point.. closest thing being rotate (wtf?) which sounds somewhat like reset but no, reset is far down below and unmovable to top and rotate is not removable by customising! how often one rotates the screen? how often does reset meters (like… the only function one uses on the meters i would say! why it’s so far away now?)

13

i ran out of honey with WL11, seriously…
my cdrw should be disabled, i’m always anxious about going to audiosettings without extensive preparations - disablement of all hardware but the one i use with wl11, then files sometimes end up in random places after rendering, and that stupid meter rotation function instead of meter reset! like, why it doesn’t reset meters after casual doubleclick on them? like, in pretty much every daw out there? why do we have to go down longish rightlick menu for that?
i think i’ve named all the main bugs and oddities so far so now it’s up to the crew to fix them or not fix them, but blaming it on asio drivers which work perfectly with other daws is really not a good approach - i envision WL13 being with upside down meters by default and no sound output at all - with VST128bit and ASIO-B support only. and blue screens when it finds some other company’s file somewhere :see_no_evil_monkey:

1 Like
14

Sorry, in my opinion, there is no issue with that menu whatsoever.

Also, IMHO your comments with regard to VST2 are way off target. The replacement of VST2 has taken place over a number of years with multiple announcements that it will no longer be supported. The responsibility for updating plugins to the VST3 standard is with the plugin developers and not with Steinberg.

15

there are companies long out of business that did great dsp code in the form of vst2 and that just ain’t gonna magically turn into vst3, and even if it did it would mean extra expenses – and what’s the benefit for end user? don’t fix it if it ain’t broke!

and regarding the menus - if you rotate your meters more often than reset them then of course it’s no issue :] like having a gear lever at the backseat of a car and a spare tyre instead of it at the front.. :slight_smile: