Can import from CD Drive, but not burn

Oh sorry, I just remembered you still don’t have the Gear drivers installed sucessfully (which is what sfc could have possibly fixed), so another drive or 32 bit probably won’t make any difference. (???)

Contact Gear, I guess ?

I have. I’m awaiting a reply. This is very frustrating as every other app on this machine can burn without issue. Even JRiver…

I reproduced your problem exactly on another Windows 10 computer. “service not running”. Actually nothing about the Gear installs and uninstalls would go right, nothing ever removed by the uninstalls. Even tried Gear’s manual uninstall (which was a real pita. Seriously, they can’t make a reg file or script to do that ???), without success. I think they have some real problems with new installs on the latest version of Windows 10. But I hope you get a solution.

My Wavelab on the other Win 10 (not the new Gear installs) continues to work ok though.

Its been three attempts over the past 10 days and I can not get a reply from GEAR. So… I doubt they will reply.

I doubt it too. The page I linked was just general contact because they don’t seem to have general support contact, and it seems like they shut down their forums a long time ago. But I thought they might read the contact emails and make an exception for unresolvable problems. Maybe it’s going to take a contact from Steinberg.

PG, would this ever be possible? The current default Match Source File always gives 32 bit float from montage, no matter what the bit depth of the files in the montage, or the fact there’s no processing or leveling going on, and that’s almost never what I want to be rendering. Match Input Stream (after the dither section) is always what I want to be rendering, whether it’s 16 or 24 bit from the dither plugin, or even if it happens to be 32 bit float if there’s no plugin.

That would make a lot more sense to me, and would save me having to use multiple presets like I do now.
Wavelab WAV Default.PNG

WaveLab does not know what a plugin is doing. To know if a plugin quantizes to 16 bit, WaveLab would need to analyse the whole audio streaming of the montage before making sure this is a quantized stream from A to Z.
Obviously, not a good approach.

Maybe I don’t mean Match Input Stream then. Maybe I mean Match Output Stream. I just always want the rendered file to be the bit depth that’s happening after the dither slot. What’s showing on the bitmeter. A 16 bit file if it’s being dithered to 16, 24 bit if it’s being dithered to 24. I think that’s what the OP expected to happen, coming from another program, and was surprised that it didn’t happen.

I also meant output stream. I can reformulate it otherwise: to know the real bit depth of the montage, the whole montage would need to be rendered internally (for analysis), before knowing to which bit format to save it to disk.
Obviously not a good workflow.


Sorry, had no idea this was so complicated.

You say Wavelab can’t know if a plugin (like the dither plugin) quatizes to 16 bit.

Can Wavelab play a tiny random sample from the montage, and tell what the bitmeter is saying? That would accomplish the same thing to automate what I’m talking about.

That’s all I’m doing manually. Looking at the bitmeter for a very short random period of time, and setting the output file format to have the same bit depth as that, for the whole montage.

Sorry if I’m being a pain about this. On the surface it just seems to me that I’m now manually setting the file format to a fixed value based only on what I’m seeing on the bitmeter at any small random time I pick to play in the montage. And that works for me. Would just like to have it happen automatically.

I can think of a scenario if I’m not using a dither plugin where this might need to be analyzed for the whole montage I guess, but not if I’m using a dither plugin as the final thing, I wouldn’t think.

Can Wavelab play a tiny random sample from the montage, and tell what the bitmeter is saying?

Not sufficient. A montage could start with a 16 it clip, then some 32 bit clips could follow.


Personally, I like the way things are now - even though newcomers will have to adjust. The fact I consciously have to decide the output format keeps me focused and not end up with low bit depth files after forgetting to change a setting on a dither plugin.

The only proper possibility, would be to add an option in the SDK specification, to be followed by the manufacturers that do dither plugins.

Thanks PG,

I just wish the simpler method could be added and given a different name, like Match Dither or Match Final Dither. I think most people would know what that meant, and that it would be a good aid to workflow. I’d use it all the time.

I would love to be helpful here, but I don’t yet understand the workflow of the engine. As someone who has used almost every major mastering software (for production deliveries), every one of them says:

“HEY, pick your dither in this preference. If you are generating a DDP, Burning a CD, or exporting to a 16-bit file from a higher bit-depth, I will always put this dither last.” Done.

But WL is so configurable that I don’t know if such a process could be placed in a global preference.

Just another note to remind everyone that burning a CD on Windows 10 with WLpro 9 is not working for everyone. That’s kind of a big deal.

It’s a big deal for whom it concerns for sure. But the question is, for how many does it not work? 0.002%? 20%? I don’t think there is any (Windows) software title that needs to interact with hardware and also works on all possible hardware combinations.

Arjan, I’m not sure it’s about specific hardware. I couldn’t do a first install or proper uninstall of the Gear drivers on a separate Win 10 computer either. And never got past the error in the Gear verifier. I would think there are possibly some issues with new Gear installs and Win 10 with latest Win updates.

Can’t get support from Gear. The Gear site says program developers have to do the support. Seems like Steinberg should possibly be testing this on different configurations.

My point is exactly that it’s not about specific hardware. In my case, with two Plextor burners on a Win 10 Pro (all updated) machine, I never had a problem as long as I can remember. Don’t even remember if Gear is installed or not.