TIOS 3.2.0.07 Beta is Out

[HUEY]

This is a public beta which among other things includes experimental support for MacOS 10.6 (Both 32 bit and 64 bit). Audio side chaining is currently not supported in Steinberg Cubase. The VST3 version shouldn't be used in a productive environment.



-VC: Improved sync with Apple Logic 8 and 9
-VC: VST3 plug-ins were not saving their state reliably
-HI: Tweaking Shift Osc Balance on hardware shows wrong parameter (fixed)
-DR: Better handling of multi client audio streams on mac
-DR: (MacOS X) Improved compatibility with Mac OSX 10.6
-VC: Reaper (unsupported host) was crashing when VC was instantiated (fixed)
-DR: Sound card audio can be distorted under certain circumstances (fixed, Mac OS X only)
-VC: On some systems, parameters sporadically stop sending events (fixed)
-VC: Automation data of VST3 Plug-In could not be edited in Cubase (fixed)

Cheers

[rapapar]

I just receive my TI desktop 1 and I install it ... no problem
I hope I'll not have any of the problems of automation in cubase sx3 that apperas in other os release....

[grs]

I just receive my TI desktop 1 and I install it ... no problem
I hope I'll not have any of the problems of automation in cubase sx3 that apperas in other os release....

Yeah, automation lanes mapped to nothing from something when going from 3.0.5 to 3.1

Makes me hate automation even more. I going to have to swap everything to midi cc automation and re-do everything.

[Alakhai]

-VC: Reaper (unsupported host) was crashing when VC was instantiated (fixed)


this means that VC now works with Reaper? aaaw tell me it works! :D

[djones]

Ok installed, but not working as it's supposed to.

When dialing the send buttons of FX 2, it shows very weird negative values instead just going from 0-127.
Aswell dialing the Lfo buttons in the Lfo section, it now shows percentages (like 12.2 % for example) instead of going from 0-63.

And third.
In Cubase, when I want to automate something by drawing it in, it only shows me a bunch of parameters like filter 1 and 2 and a few softknobs.
There's nothing else to be automated there.
This has been a problem ever since I got my Snow, but so far it hasn't been resolved.

[Hell Yeh]

Ok installed, but not working as it's supposed to.

When dialing the send buttons of FX 2, it shows very weird negative values instead just going from 0-127.
Aswell dialing the Lfo buttons in the Lfo section, it now shows percentages (like 12.2 % for example) instead of going from 0-63.

And third.
In Cubase, when I want to automate something by drawing it in, it only shows me a bunch of parameters like filter 1 and 2 and a few softknobs.
There's nothing else to be automated there.
This has been a problem ever since I got my Snow, but so far it hasn't been resolved.

I'm not in front of my system now, but if I recall correctly... you have add parameters to the automation list... I think by right-clicking the parameter and then choosing some other option. If you can't figure it out, I can try it when I get home.

[feedingear]

You can choose any parameter to automate - read the Cubase Tutorial that should be in the Access folder to learn how.

Also the percentages are normal changes now for better or worse - I personally preferred it the other way, but it does make sense.

[fgimian]

Yeah, automation lanes mapped to nothing from something when going from 3.0.5 to 3.1

Makes me hate automation even more. I going to have to swap everything to midi cc automation and re-do everything.

Trust me and don't do this! :) MIDI CCs are not sample accurate like proper automation and thus you'll find the timing of your automation is not dead-on and drifts.

I actually moved all my CC automation to VSTi automation and it was spot on.

Good luck mate :)

[feedingear]

What is the difference between CC automation to VSTi automation, specifically when using Cubase 5?

[HUEY]

[quote=djones;293428]

When dialing the send buttons of FX 2, it shows very weird negative values instead just going from 0-127.
Aswell dialing the Lfo buttons in the Lfo section, it now shows percentages (like 12.2 % for example) instead of going from 0-63.
quote]

As far as I know this is on purpose and not a bug as i read in a post from Marc if I reminder right

[grs]

Trust me and don't do this! :) MIDI CCs are not sample accurate like proper automation and thus you'll find the timing of your automation is not dead-on and drifts.

I actually moved all my CC automation to VSTi automation and it was spot on.

Good luck mate :)

I guess my automation is more sweeps rises and tweeks that don't require sample accurate timing.

Pluss I like dragging and copying midi CCs around with the other midi data. I think my brain gets more done this way quicker.

BTW if you want the old way just for a bit like when you load an old project with automation that gets lost you can do a registry tweek to go back to the old way.
HKEY_CURRENT_USER\Software\Access Music\Virus TI\Virus Control
then look for
UseParameterMapping
and set it to (0) instead of (1)
then you can load your old project and keep all your old automation.