Cubase 9.5 launch today!

[fmr]

use windows, it just works.

So does Sierra. Does 9.5 work with Windows 2K, though.

No, but it works with Windows 7 (and 8, and 8.5, I guess)

[Romantique Tp]

snip

I'm no VST plugin developer but I was under the impression that the VST2.4 standard only officially supported 64 bit double precision input and internal processing. In VST3 the output can be 64 bit, but as explained in that article:

"Whether a VST3 plug-in or instrument supports 64-bit processing precision is up to the manufacturer of the plug-ins. Some manufacturers advertise an internal (!) 64-bit processing for their plug-ins but still do not support a complete audio processing in 64-bit double precision throughout the whole signal path."

[fmr]

snip

I'm no VST plugin developer but I was under the impression that the VST2.4 standard only officially supported 64 bit double precision input and internal processing. In VST3 the output can be 64 bit, but as explained in that article:

"Whether a VST3 plug-in or instrument supports 64-bit processing precision is up to the manufacturer of the plug-ins. Some manufacturers advertise an internal (!) 64-bit processing for their plug-ins but still do not support a complete audio processing in 64-bit double precision throughout the whole signal path."

IMNSHO, 64-bit (or double precision) is a complete overkill. 32-bit float is more than adequate for any job. Benefits of double precision have yet to be demonstrated.

[SJ_Digriz]

Pretty sure these are all issues with your setup, not Cubase.

it's a fresh install today.. still a mess.

it crashed and wouldn't record with only windows 10 64, sound card drivers, cubase and the virus ti drivers installed

What is the thing being beat on? I'm running 64bit mode with mics, pres, keyboards, fx loops, modular multi-mixer input and other assorted junk. Everything works fine.

I have a 300 track soundtrack going right now. Smooth as silk.

[SJ_Digriz]

IMNSHO, 64-bit (or double precision) is a complete overkill. 32-bit float is more than adequate for any job. Benefits of double precision have yet to be demonstrated.

I don't think that is entirely true. I'm pretty sure it provides increased headroom for multi-channel summing with fewer rounding errors.
I thought it also provided a better base for SRC. I'm probably wrong on that or just misunderstand something I read. I'm not sure if it helps the VSTi guys in their processing domain for things like oversampling or not.

[barryfell]

snip

I'm no VST plugin developer but I was under the impression that the VST2.4 standard only officially supported 64 bit double precision input and internal processing. In VST3 the output can be 64 bit, but as explained in that article:

"Whether a VST3 plug-in or instrument supports 64-bit processing precision is up to the manufacturer of the plug-ins. Some manufacturers advertise an internal (!) 64-bit processing for their plug-ins but still do not support a complete audio processing in 64-bit double precision throughout the whole signal path."

That was my impression as well until I read it was only possible with VST3 plugins according to the article. That said, my query is if Steinberg has just done that to further hobble using VST2 in Cubase consider other DAWs 64bit audio engines have no such issue as far as I am aware.

[barryfell]

snip

I'm no VST plugin developer but I was under the impression that the VST2.4 standard only officially supported 64 bit double precision input and internal processing. In VST3 the output can be 64 bit, but as explained in that article:

"Whether a VST3 plug-in or instrument supports 64-bit processing precision is up to the manufacturer of the plug-ins. Some manufacturers advertise an internal (!) 64-bit processing for their plug-ins but still do not support a complete audio processing in 64-bit double precision throughout the whole signal path."

IMNSHO, 64-bit (or double precision) is a complete overkill. 32-bit float is more than adequate for any job. Benefits of double precision have yet to be demonstrated.

Indeed i'm intrigued to do some A/B tests on my projects now. I know bouncing at 96k rather than my old standard of 48k was an improvement (46k I what I am forced to run my projects at due to system load).

I always master at 96k though as again, I def notice a different, esp when using AA plugins.

64bit audio engine processing precision is another question though....

[SJ_Digriz]

That was my impression as well until I read it was only possible with VST3 plugins according to the article. That said, my query is if Steinberg has just done that to further hobble using VST2 in Cubase consider other DAWs 64bit audio engines have no such issue as far as I am aware.

I would be interested to hear from a plugin dev on the topic. I haven't used either SDK in earnest for a long time.

But, just because a DAW has a 64bit processing engine, doesn't mean the plugins are feeding it 64 bit data. So, just like Cubase continues to function with all the existing plugins, so the others with 64 bit engines may just be getting 32 bit feeds from the VST2 based instruments. I'm just speculating here by the way. I'd actually like an actual plugin dev answer.

[wickfut]

What is the thing being beat on? I'm running 64bit mode with mics, pres, keyboards, fx loops, modular multi-mixer input and other assorted junk. Everything works fine.

I have a 300 track soundtrack going right now. Smooth as silk.

Vermona DRM1 analogue drum machine which is wired straight into my soundcards analogue inputs. I'm pressing the left side buttons which trigger the different sounds.

[SJ_Digriz]

It makes no sense that the 64 bit mode would have anything to do with the vermona. What is the audio card? Is it an ASIO driver? There is something goofy going on for sure.

[wickfut]

It makes no sense that the 64 bit mode would have anything to do with the vermona. What is the audio card? Is it an ASIO driver? There is something goofy going on for sure.

I never said it was the vermona, I'm simply using the Vermona as a noise input. The card is a Marian Seraph AD2 with ASIO.

I've deleted the old video and uploaded a new one. I'm going to send it to both Steinberg and Marian.

[SJ_Digriz]

that seems an audio card issue. If the audio card has an internal mixer, it should be showing the trigger from the Vermona regardless of the Cubase mode.

[wickfut]

The only thing to have changed between hearing audio and not hearing audio is changing the bit mode from 32 to 64 in cubase. How is it a sound card issue ?

All the sound card settings are correct. The audio shows on the DSP mixer perfectly fine.

Here's a video of cubase incorrectly mapping the midi devices, I believe something similar is happening to me but with the audio..

[SJ_Digriz]

For some reason I thought you were on windows. I have an issue with the Aurora driver I use where after whatever the last big windows update was, I can now no longer hot change my sample rate. I have to change sample rate and reboot. I can't imagine what Cubases internal processing depth would have to do with it, but who knows. Maybe if you set it to 64bit mode and then reboot, does it work?

[SJ_Digriz]

By the way, I had your mapping problem in C9 and then in C9.5. But, it was my C8 template that I had been updating constantly for years as I went along. I bit the bullet and started a new template from scratch and so far it is working properly.

It looks like we set things up similarly. I also use VEP extensively. Here is my string view. I have that set to visibility filter 1 (alt+1). The way I have it, the audio channels are hidden normally. I just put them here so you could see them. But, the mixer view is just those audio channels, with midi and instrument channels hidden. So, I see audio on the mixer and midi in the project. Hope that makes sense lol..