#Steinberg wavelab elements 7 64 Bit
#Steinberg wavelab elements 7 drivers
#Steinberg wavelab elements 7 driver
#Steinberg wavelab elements 7 mac

I fully understood that distinction from the outset and to make sure it wasnвЂ™t confused, repeated my agreement with specificity in my reply to you above.ДЄnd with that distinction accepted and repeated I asked a separate question, apart from the OPs concern, which remains unanswered. I AGREED with you that it was irrelevant, as I noted what mattered. I made the same distinction in the first post here. So any clarity would be appreciated (not on specific plugs but the WL7 host).

#Steinberg wavelab elements 7 64 Bit

My world is AU (allows 32 or 64 bit words between stages), TDM (24 bit words) and RTAS (32 bits).

#Steinberg wavelab elements 7 mac

IвЂ™m pretty vague about VST in general and VST3 in particular, as a mac guy with a PT background. Is that the case? I suppose IвЂ™ve violated LudwigвЂ™s Dictum by assuming this is the case based on anecdotal reports on an earlier version (WL6). I think weвЂ™re ssaying the same thing here VP.ДЄs long as WL can pass 64 bit words between plugs that support that, IвЂ™m golden. They are not the same thing and have nothing to do with each other. LetвЂ™s not confuse a compiling and running Wavelab as a native 64bit executable vs. One of the main benefits of my other daw is that while the application runs in вЂњ32 bit modeвЂќ it runs a 64 bit calculation engine and some select plugs are able to exchange that dataвЂ¦ the same plugs in daws that chop back to 24 (PT) or 32 bits (Peak) just donвЂ™t sound as good with the same settings, over many iterations they measurably lose fidelity. Well, as long as itвЂ™s capable of passing 64 bit data-words from stage to stage in plugs IвЂ™m in agreement. So, in summary, as far as audio processing is concerned, it does not matter whether WaveLab 7 as an application is compliled for 32-bit or 64-bit CPU architecture, the audio processing would be identical because this happens in the floating-point domain.

16-bit, 24-bit) for playback via an audio interface or for burning to disk is the resolution decreased.

Only when the result is converted back to integer samples (e.g. a 16-bit (integer) sample as it might exist in an audio file to a value between 0 and 1, but with all possible values between 0 and 1 available, thus giving infinitely more resolution during processing.

In the case of audio resolution, when audio is passed between VST plugins, it is done only after each sample is converted to whatвЂ™s called a вЂњfloating pointвЂќ number вЂ“ think of this as mapping e.g. Even the 32-bit version of Cubase can benefit from being run in a 64-bit OS, something which many of us are doing (usually in cases where thereвЂ™s no 64-bit version of a favourite VST plugin, and the VSTBridge doesnвЂ™t work). Referring to CPU architecture, 64-bit is almost always a good thing as it allows the use of practically unlimited RAM, and even assists 32-bit applications running under a 64-bit OS so for example, Cubase users who use large sample libraries which need to loaded into RAM will certainly benefit from the use of both a 64-bit OS and the 64-bit version of the application. IвЂ™ve run WaveLab (albeit version 6) in as little as 512MB RAM without any problem, so I donвЂ™t think 64-bit technology has anything to offer as far as WaveLab is concerned at this point, and moreover, if there were a 64-bit version of WaveLab 7, I donвЂ™t think anyone would be able to tell the difference subjectively between 32- and 64-bit.ДЄs usual the confusion here is the use of the term вЂњ64-bitвЂќ in relation to both CPU architecture and audio resolution.

#Steinberg wavelab elements 7 drivers

32-bit applications run fine on 64-bit Windows as long as you have 64-bit drivers for all your hardware.

#Steinberg wavelab elements 7 driver

I run Cubase 64-bit and WaveLab 7 on Windows 7 64-bit, with an RME 64-bit (only) driver and use ASIO without any problems.