OS 3.0.1.15 release and 3.0.2.01 beta is out

[HUEY]

Not able to test it yet. I will give it a try later

br

[telson]

this is very cool , i will try it asap :cool:

[nidefawl]

About TIOS 3.0.2.01 Public Beta
-HI: Improved recovery of volume and other parameters after crash
-SE: Internal improvement to memory handling
***************************************************
About TIOS 3.0.1.15 Release
3.0.1.15 is a maintenance release and is recommended for every Virus TI owner. Audio side chaining is currently not supported in Steinberg Cubase.
The VST3 version shouldn't be used in a productive environment.
***************************************************
About TIOS 3.0.1.14 Public Beta
-VC: mouse wheel not working in Cubase for Windows and FL Studio (fixed)
-VC: Filter parameters are not always restored correctly (fixed)
-VC: crash when switching pages after second VC plug-in instance has been closed (fixed)
-VC: Plug-In UI can stays empty in large projects on Windows (fixed)

[Talos]

I noticed the 3.0.2.01 changelog was up on friday when the site layout was altered.
Installing now.

[nidefawl]

I noticed the 3.0.2.01 changelog was up on friday when the site layout was altered.
Installing now.

its still up. you have to guess the url ;)

http://www.access-music.de/events/2009-04/OS30201_change_log.pdf

[annikk.exe]

About TIOS 3.0.2.01 Public Beta
-HI: Improved recovery of volume and other parameters after crash
-SE: Internal improvement to memory handling

Maybe this is a stupid question but what does "HI" and SE" stand for?


-Annikk

[Cantankerous]

HI I know means Hardware Interface

SE I think is SEQ mode?

[Cantankerous]

Just installed the new beta. Perhaps it was just me, but I had a driver installer loop that wouldn't end. After the driver was successfully installed it would ask if I had another device to install. I would select no as I always do, and it would scan and want to reinstall the driver again. After 3 times of this I manually force closed the installer in which I was told it was not successfully completed. In order to get the new firmware onto the Ti itself, I had manually do it from Virus Control Center. Everything seems to work despite all these loops I have never had to go through before. Anyone else successfully installed the new BETA without this issue?

[FFoxX]

HI I know means Hardware Interface
SE I think is SEQ mode?

SE - Sound Engine

[Cantankerous]

SE - Sound Engine

Oh great! So that mention of memory optimizations should be a good thing for using the Ti as a whole. Do you reckon this will aid with crackling under high DSP?

[HUEY]

Just installed the new beta. Perhaps it was just me, but I had a driver installer loop that wouldn't end. After the driver was successfully installed it would ask if I had another device to install. I would select no as I always do, and it would scan and want to reinstall the driver again. After 3 times of this I manually force closed the installer in which I was told it was not successfully completed. In order to get the new firmware onto the Ti itself, I had manually do it from Virus Control Center. Everything seems to work despite all these loops I have never had to go through before. Anyone else successfully installed the new BETA without this issue?

Installation went fine here on WinXpsp3 (the beta version)

br

[HUEY]

I'm still able to let the virus crash in just a few seconds in Cubase SX3 on WinXPsp3 and Ti Desktop :( (and I'm not on 2.7.5.)

Make a simple loop of 4 full notes in Cubase on a miditrack with output Virus Ti
Switch some sounds in Virus Control during play and after that stop the sequencer (space bar or hit stop in the transport bar)
After a few switches and stops there is a loud IIIEEEEEEEP sound coming out of the virus followed by 2 distorted scratch sounds. The lights on the virus stop blinking and will go out after a few seconds. (display stays on).

Untill now the Virus boots itself up after a crash, but it's very annoying.

Anybody else ??

Br

[fender2k1]

I'm still able to let the virus crash in just a few seconds in Cubase SX3 on WinXPsp3 and Ti Desktop :( (and I'm not on 2.7.5.)

Make a simple loop of 4 full notes in Cubase on a miditrack with output Virus Ti
Switch some sounds in Virus Control during play and after that stop the sequencer (space bar or hit stop in the transport bar)
After a few switches and stops there is a loud IIIEEEEEEEP sound coming out of the virus followed by 2 distorted scratch sounds. The lights on the virus stop blinking and will go out after a few seconds. (display stays on).

Untill now the Virus boots itself up after a crash, but it's very annoying.

Anybody else ??

Br

Well I'm at work and can't test it, but i don't want to go home to the same problem again :(

[telson]

test ok
thanks access :cool:

[DiScO]

Tight as a drum in Logic 8.0.2! Arps trigger without the glitch type effect I was experiencing and the led's stay true to the metronome! This is all I have been after for a long time now!! The only things I seem to be experiencing are midi buffer overflows (as shown on the TI display) and loss of sync occasionally when changing patches whist the sequencer is running. As stated in the VC lower display though, stopping and restarting seems to clear it. Sometimes I get some nasty crackles when it's trying to sort it's self out, but this is the best I have ever known it, so I ain't complaining.

Cheers.

[absynth]

Really final?? waht about the Sidechaning in Cubase??

is it now supported or not?

[marc]

Really final?? waht about the Sidechaning in Cubase??

is it now supported or not?

no, it's not. and it won't unless steinberg gets some work done :(

marc

[absynth]

steinberg has to update cubase for the function? or what exactly do you mean?

if thats true probably they will only make an update for cubase 5 then

[Chicago]

I'm still able to let the virus crash in just a few seconds in Cubase SX3 on WinXPsp3 and Ti Desktop :( (and I'm not on 2.7.5.)

Make a simple loop of 4 full notes in Cubase on a miditrack with output Virus Ti
Switch some sounds in Virus Control during play and after that stop the sequencer (space bar or hit stop in the transport bar)
After a few switches and stops there is a loud IIIEEEEEEEP sound coming out of the virus followed by 2 distorted scratch sounds. The lights on the virus stop blinking and will go out after a few seconds. (display stays on).

Untill now the Virus boots itself up after a crash, but it's very annoying.

Anybody else ??

Br


Which version did you install - 3.0.1.15 or 3.0.2.01?

[civan]

no, it's not. and it won't unless steinberg gets some work done :(

marc

If Cubase 5 supports VST3 then why doesn't VC work with sidechaining? I thought VST is Steinberg's technology... :confused:

[Crossfire]

Tight as a drum in Logic 8.0.2! Arps trigger without the glitch type effect I was experiencing and the led's stay true to the metronome! This is all I have been after for a long time now!! The only things I seem to be experiencing are midi buffer overflows (as shown on the TI display) and loss of sync occasionally when changing patches whist the sequencer is running. As stated in the VC lower display though, stopping and restarting seems to clear it. Sometimes I get some nasty crackles when it's trying to sort it's self out, but this is the best I have ever known it, so I ain't complaining.

Cheers.

Which version? 3.0.1.15 or 3.0.2.01?

[Hell Yeh]

I am very glad to see that upon an official OS release, Access has also released a new public beta. I just love praising the Access development team.

Anywho, I'm installing 3.0.2.1 and hopefully this resolves the weird issue I've been experiencing with 3.0.1.x where, randomly, any MIDI sequence I have going to the Virus TI will be shortened by what sounds like 1/16th note and only by closing Cubase 4/5 and power cycling the TI will the issue go away temporarily. (Unfortunately, I don't have a real repro case.)

[telson]

http://i253.photobucket.com/albums/hh54/telsonn/DSCN2250.jpg


As you can see in the foto , the right led it's not so bright and so "strong" as the left one
After installing 3.0.1.15 release , this problem was fixed
and now the right led it's too "strong" as the left

thanks access
thanks marc

[HUEY]

Which version did you install - 3.0.1.15 or 3.0.2.01?

I Installed 3.0.2.01, but I had it with all 3.0.x beta versions

br

[HUEY]

Well I'm at work and can't test it, but i don't want to go home to the same problem again :(

Untill now it looks you are the only one with exactly the same problem as I have. (only with fruity loops in stead of Cubase I read in another thread?)
I don't hope for you that you still have this problem, but if you do, please post so we can try to help access to solve it

best regards

[marc]

If Cubase 5 supports VST3 then why doesn't VC work with sidechaining? I thought VST is Steinberg's technology... :confused:

because steinberg didn't implement side chaining for instruments.

best, marc

[fgimian]

So far so good for me, I love the improvements. Although, I must admit that the new startup / shutdown LCD animations are hideous and unprofessional, v2 looked much better in this regard.

[feedingear]

agreed....

[absynth]

because steinberg didn't implement side chaining for instruments.

best, marc

but cubase 4 allready has sidechaining included, can´t that be used with the virus??

[Ronkaz]

but cubase 4 allready has sidechaining included, can´t that be used with the virus??

read "instruments"

r

[ElMute]

could you test the pan in the VC because with me only pan on USB 1 L+R work.

when the parts are routed to USB 2 L+R or USB 3 L+R pan are not working ...

[absynth]

i know its not supported by instruments

but some plugins like the Fabfilter ProC compressor have sidechaining also in cubase

...so what about releasing an effeckt plugin for the virus then?? so cubase users can also use the great features

[Mr Ben]

I have now downloaded and installed OS 3.0.1.15

Up to now everything seems ok,I'm still getting the sync error every now and again in vc but stopping and staring now sorts out the problem.
It does seem alot more stable.

I'm using an iMac 2.8 24" with OS 10.5.6 and logic 8.0.2

And i still really don't like the browser page.
But hey ho you can't have everything he he

[erolz]

do i have to uninstall the "old" virus ti software first or can i just run the installer while my TI (snow) is connected with usb to my pc?

[HostileReality]

I'm pleased to say that the bug that was stopping me from using Cubase 5 is now fixed - the filter settings not being recalled correctly. Thanks Access!

[Ronkaz]

do i have to uninstall the "old" virus ti software first or can i just run the installer while my TI (snow) is connected with usb to my pc?

for old version to new version, you can just install it without installing the older one.

r

[erolz]

for old version to new version, you can just install it without installing the older one.

r

ok. thanx! let me guess. when i want to go back to the old software, i do have to uninstall the new first?

[Prime NL]

ok. thanx! let me guess. when i want to go back to the old software, i do have to uninstall the new first?

No, you don't have to.... :)

[HUEY]

could you test the pan in the VC because with me only pan on USB 1 L+R work.

when the parts are routed to USB 2 L+R or USB 3 L+R pan are not working ...

Pan is working perfect here on al outputs USB and analog

WinXPsp3, SX3, Ti Desktop

br

[DiScO]

@ Quickfire - Sorry, not been about, 3.0.2.01. Seems real tight to me but has a few issues here and there but generally catches up. I like it compared to anything previous.

Cheers.

[Berni]

Well the arps in the RTAS version are STILL all over the place...with this version & ANY other RTAS version. I mean, am I asking too much that the arps sync to the beat of the project???? It's a basic fundamental & not a minor bug I can live with. I am also confused how they can release a 'finished' version with yet another beta version along side it...this is bullshit!

[~BHG~]

Maybe your Apple is just garbage?!?!?!

[Berni]

thankyou for your wonderful insight, what a genius you are. The fact that the VST version in Live works fine on the same computer, with the same Virus, USB cable etc. etc. is still mystifying though. Only sad, pathetic wankers start platform flamers.

[h4nc0]

wanted to say that I am pretty happy with the frequent beta releases. Just hope that the VST3 version become usable soon.

[fgimian]

wanted to say that I am pretty happy with the frequent beta releases. Just hope that the VST3 version become usable soon.

Just out of curiosity, what sort of issues have you encountered with the VST3 version? For me it's only that I can't switch to linear control of the knobs, it's always circular. Are there any other major bugs with it?

[marc]

Just out of curiosity, what sort of issues have you encountered with the VST3 version? For me it's only that I can't switch to linear control of the knobs, it's always circular. Are there any other major bugs with it?

the knobs cannot be switched because steinberg didn't implement this function into cubase' VST3 support so far. we don't have a records of open and VST3 specific bugs, so h4nc0 what makes it unusuable for you?

marc

[fgimian]

the knobs cannot be switched because steinberg didn't implement this function into cubase' VST3 support so far. we don't have a records of open and VST3 specific bugs, so h4nc0 what makes it unusuable for you?

marc

Hey Marc, thanks for the response. Are you certain about the linear / circular motion for VST3 plugins? I only ask because I just tested out many of the VST3 effects and instruments included with Cubase 4 and they do respond to both modes as set in the preferences. I can post a video to demo this if that helps.

Cheers :)

[marc]

Hey Marc, thanks for the response. Are you certain about the linear / circular motion for VST3 plugins? I only ask because I just tested out many of the VST3 effects and instruments included with Cubase 4 and they do respond to both modes as set in the preferences. I can post a video to demo this if that helps.

Cheers :)

we have a confirmation from steinberg that the functionality will be added with a future version of the VST3 SDK which will be supported by a future version of cubase. we know that steinberg's own plug-ins can already do that but we don't have access to this type of functionality.

best, marc

[incubatid]

we have a confirmation from steinberg that the functionality will be added with a future version of the VST3 SDK which will be supported by a future version of cubase. we know that steinberg's own plug-ins can already do that but we don't have access to this type of functionality.

best, marcHoly crap. Steinberg must actually be retarded.
This functionality was there in VST2. How on earth can they possibly take it away from the VST3 SDK, and then use the functionality themselves?! And then not produce a QUICK fix to the problem? I just can't see the logic here...

Do they want developers to actually use VST3 or what? :roll:

[incubatid]

Thankyou (again!) Access for all your hard work and support.

v3 is done! Amazing. Please have some beers on behalf of your fans, you all deserve it! :)

Cheers

[fgimian]

we have a confirmation from steinberg that the functionality will be added with a future version of the VST3 SDK which will be supported by a future version of cubase. we know that steinberg's own plug-ins can already do that but we don't have access to this type of functionality.

best, marc

Thanks for the confirmation Marc, silly Steinberg, hopefully they will fix this in the SDK and actually implement input for VSTis in Cubase soon :)

[h4nc0]

the knobs cannot be switched because steinberg didn't implement this function into cubase' VST3 support so far. we don't have a records of open and VST3 specific bugs, so h4nc0 what makes it unusuable for you?

marc


Hello marc,

A few revisions ago when I tried, it was not working too well. I actually haven't even installed the VST3 version in the latest beta. Maybe I should, but I just don't see the reason for using VST3 version without sidechain working.

[wehurlbert]

So far so good for me, I love the improvements. Although, I must admit that the new startup / shutdown LCD animations are hideous and unprofessional, v2 looked much better in this regard.

Yep - I have to agree.

-Wayne

[marc]

Hello marc,

A few revisions ago when I tried, it was not working too well. I actually haven't even installed the VST3 version in the latest beta. Maybe I should, but I just don't see the reason for using VST3 version without sidechain working.

idealistically there shouldn't be a difference in between the VST2 and VST3 version of the plug-in. if the VST3 version doesn't work well for you, i'd be interested to learn more about it. maybe you want to give it another try sooner or later.

best, marc

[L.F.]

First of all, thank you Access and Marc for a great update. 90% of (my) issues seem to be fixed now. :-)
Glad to see the "blank VST GUI" problem has been adressed.

As far as steinberg is concerned, I'm almost sorry to have bought their C5. This kind of behaviour on their part is simply pathetic. But it's not the first bad move they made, and it's obviously not the last... just wish some1 made a DAW I liked using more than cubase :-|

Also one question; What's the current advantage in using the VST3 version?
Is there any difference? If not, then why make a VST3 version?

Also if anyone knows... are steinberg plannig to adress these issues?

[h4nc0]

idealistically there shouldn't be a difference in between the VST2 and VST3 version of the plug-in. if the VST3 version doesn't work well for you, i'd be interested to learn more about it. maybe you want to give it another try sooner or later.

best, marc

Actually, if they are really identical, I might have to try it again. But like I said before, without sidechain working, it's pretty much pointless, imo. I will try to use VST3 version instead of VST2 from now on, since you say they should be identical.

[Hell Yeh]

First of all, thank you Access and Marc for a great update. 90% of (my) issues seem to be fixed now. :-)
Glad to see the "blank VST GUI" problem has been adressed.

As far as steinberg is concerned, I'm almost sorry to have bought their C5. This kind of behaviour on their part is simply pathetic. But it's not the first bad move they made, and it's obviously not the last... just wish some1 made a DAW I liked using more than cubase :-|

Also one question; What's the current advantage in using the VST3 version?
Is there any difference? If not, then why make a VST3 version?

Also if anyone knows... are steinberg plannig to adress these issues?

The VST3 version was made to eventually allow the internal sidechaining feature of the Virus to work in Cubase. Right now, that feature is not available because Steinberg has to allow internal sidechaining for VSTi's, which Marc has said they will be releasing in an update to thier SDK. So right now, it is kind of useless, but will be necessary in the hopefully near future.

[marc]

So right now, it is kind of useless, but will be necessary in the hopefully near future.

i think there is more. as far as i understand it (correct me, if i'm wrong) there is currently no way to switch from a VST2 to a VST3 version of a plug-in without loosing data, such as the automation you wrote to the tracks accessing the plug-in. in order to keep songs compatible and allow yourself to open them in the more or less distant future without compromise you need to move on to VST3 sooner or later. in fact, all those who are waiting for 64bit support among other things should start to use the VST3 version if possible. we supply the VST3 version of virus control as a part of the public beta program so we can iron out bugs before you really needs to rely on it. i cannot tell if there are still bugs but so far it looks promising.

by the way: thanks to everybody who participated in the beta program and reported bugs. we owe you for testing this new version. i think, offering a public beta was mutually beneficial for you and us. we plan to continue going down this road.

best, marc

[LivePsy]

by the way: thanks to everybody who participated in the beta program and reported bugs. we owe you for testing this new version. i think, offering a public beta was mutually beneficial for you and us. we plan to continue going down this road.

best, marc

Thanks to Access for being committed to improving the TI products! No one would want to read through pages and pages of "No problems here", but in fact that is the case. Its been problem free for most people for some time now.

Regards.
B

[L.F.]

all those who are waiting for 64bit support among other things should start to use the VST3 version if possible. we supply the VST3 version of virus control as a part of the public beta program so we can iron out bugs before you really needs to rely on it. i cannot tell if there are still bugs but so far it looks promising.

best, marc

Well why didn't you say so? ;)
I will begin testing asap (as, I'm sure, will many other users). Anything we can do to help the 64bit version along :)

[fender2k1]

I am getting stuck in an infinite driver install loop. Anyone else experiencing this?

[Spacer]

Guys... I only tried the 2.01 beta from the one I had 3.0.12 I think was the last one..

Its really fucked up... I try sounds and suddenly Polar acts like reboots itself and generally easy gets in panic mode - pure noise sound,

Really with the beta of 3.0.12 didnt have any problems at all, this beta is really the worst version I had from before OS2

[Hell Yeh]

i think there is more. as far as i understand it (correct me, if i'm wrong) there is currently no way to switch from a VST2 to a VST3 version of a plug-in without loosing data, such as the automation you wrote to the tracks accessing the plug-in. in order to keep songs compatible and allow yourself to open them in the more or less distant future without compromise you need to move on to VST3 sooner or later. in fact, all those who are waiting for 64bit support among other things should start to use the VST3 version if possible.

Ahhh! You are right and have an extremely valid point. I did not think of that at all.

[HUEY]

I am getting stuck in an infinite driver install loop. Anyone else experiencing this?

See page 1 of this thread.
There is a other one

br

[Cantankerous]

See page 1 of this thread.
There is a other one

br

That other one was me. Yes, I too experienced the infinite driver install loop. The only way to get out of it was to manually cancel after it successfully installed at least once. I then had to manually flash the firmware via VCC.

http://www.infekted.org/virus/showpost.php?p=289970&postcount=8

[rjay]

Infinite driver loop here also, but when I try to follow your method of updating via VCC, I get a "No Virus TI found" error. Following the onscreen instructions and putting the Virus into Update mode doesn't do anything either ....

[rjay]

Infinite driver loop here also, but when I try to follow your method of updating via VCC, I get a "No Virus TI found" error. Following the onscreen instructions and putting the Virus into Update mode doesn't do anything either ....

Eventually I fixed it by choosing the 'Reinstall drivers' option in the same start folder as VCC.

[fender2k1]

I've installed 3.0.2.1 and i'm still experiencing the same issues as i've posted about in the following topics:

http://www.infekted.org/virus/showthread.php?t=30903

Me and HUEY seem to be having the exact same problem. Switching a patch during playback and stopping/pausing the project causes the virus to crash.

more info of me or someone else experiencing this issue:

http://www.infekted.org/virus/showthread.php?t=30947
http://www.infekted.org/virus/showthread.php?t=30550

hope this can get worked out, we're all using different daws and can now trigger the crash.

[Prime NL]

After updating my TI Desktop to Beta 3.0.2.1 i experience the same Sound crash error then before : http://www.infekted.org/virus/showthread.php?t=30947

Seems more and more related to just this sound (AutoKit BC) as every other sounds just doesn't produce the same error.

[TheHobbit]

No issues here with the latest beta.

Just to clarify :

1. VST3 is now stable to start using in projects to avoid future migration issues with projects?

2. We will shortly see input-sidechaining with Cubase 5 thanks to access's VST3 integration?

3. This will make me a happy hobbit ;)

Thanks

[HUEY]

I've installed 3.0.2.1 and i'm still experiencing the same issues as i've posted about in the following topics:

http://www.infekted.org/virus/showthread.php?t=30903

Me and HUEY seem to be having the exact same problem. Switching a patch during playback and stopping/pausing the project causes the virus to crash.

more info of me or someone else experiencing this issue:

http://www.infekted.org/virus/showthread.php?t=30947
http://www.infekted.org/virus/showthread.php?t=30550

hope this can get worked out, we're all using different daws and can now trigger the crash.

Thanks for posting.
I almost cann't imagine that nobody else experience this, because I can let it happen so easily. (It also happens when I don't want to and thats why it's annoying to me).

br

[HUEY]

To make it happen:
Make a simple setup as in the picture. Make a loop.
Change sounds in VC during playback and stop/pause the sequencer. After a few switches/stops it will crash.

I also have a MP3 file here with the ieeeep sounds and distorted scratch sound that you will hear when it happens but I can't manage uploading it here directly. (too big)


It happens on the USB outs and the analog outs

br

[civan]

Is access going to post an updated manual now that OS 3 is official?

[marc]

Is access going to post an updated manual now that OS 3 is official?

what are you missing in the manual+addenda?

marc

[civan]

The manual that I have shows the old VC layout and doesn't really talk about the new features; for example, characters.
Edit 1: Okay I'm still a newb when it comes down to Mac use. I didn't realize that a lot of my software installs were putting documents in the Library->Documentation folder. :!:

This reminded me just now. Is Access thinking about making a option to choose between the white VC and red/black VC color themes?

A bug that I've seen in probably the last couple updates. The Welcome screen keeps showing up in VC every time I open it up even though I select "Don't Show Again."

[marc]

The manual that I have shows the old VC layout and doesn't really talk about the new features; for example, characters. This reminded mejust now. Is Access thinking about making a option to choose between the white VC and red/black VC color themes?

A bug that I've seen in probably the last couple updates. The Welcome screen keeps showing up in VC every time I open it up even though I select "Don't Show Again."

the addendum explains the new features in detail. as for your report, are you on Mac or PC?

thanks, marc

[civan]

Mac Pro OS 10.5.6

[h4nc0]

A bug that I've seen in probably the last couple updates. The Welcome screen keeps showing up in VC every time I open it up even though I select "Don't Show Again."

This happens here with the latest beta on PC. Also, when using VST3 version, after writing automation data (by using mouse on VC), I can't seem to change them. VST2 works fine.

[civan]

I was just wondering something. I know that in Cubase 5 we are currently unable to use the Virus input plugin to send audio through USB.

However, if I were to setup Atmizer for example, in cubase as an external effect in Cubase. Should I be able to accomplish this by routing the Virus Input and one of its outputs to my soundcard?

I should be able to then set one of the 16 channels in VC to accept the analog input and then setup the analog output. Correct?

[absynth]

you can use the analog input to the virus and the analog outputs out of the virus into your soundcard for using the atomizer, effeckts... in cubase

i tested this, i think its too complicated to set it up right and also to use it in your workflow

it´s much easier and more fun to use it with the usb in with ableton for example

i really hope steinberg will bring that sidechain feature for vst instruments, also posted in the steinberg forum here in this topic http://www.cubase.net/phpbb2/viewtopic.php?t=116034&start=30

Sidechain audio input support on VST Instruments Please (http://www.cubase.net/phpbb2/viewtopic.php?t=116034&start=30&postdays=0&postorder=asc&highlight=&sid=ee34dfe17f3c9e0cfb55b0d8956a014c)

Anyone who is using Cubase please also post in that thread and vote "Steinberg have our dosh & support give us what we need please"

Any Plans for making a VST Effeckts only Plugin for the Virus? Could that work with sidechain then?

[Hell Yeh]

I was just wondering something. I know that in Cubase 5 we are currently unable to use the Virus input plugin to send audio through USB.

However, if I were to setup Atmizer for example, in cubase as an external effect in Cubase. Should I be able to accomplish this by routing the Virus Input and one of its outputs to my soundcard?

I should be able to then set one of the 16 channels in VC to accept the analog input and then setup the analog output. Correct?

Yes, you can. You will just need to adjust the delay of the external effect so that you don't hear the latency. It's kind of a pain to get setup, but once it's all done it works very well and super easy to use.

[Cantankerous]

you can use the analog input to the virus and the analog outputs out of the virus into your soundcard for using the atomizer, effeckts... in cubase

i tested this, i think its too complicated to set it up right and also to use it in your workflow

it´s much easier and more fun to use it with the usb in with ableton for example

i really hope steinberg will bring that sidechain feature for vst instruments, also posted in the steinberg forum here in this topic http://www.cubase.net/phpbb2/viewtopic.php?t=116034&start=30

Sidechain audio input support on VST Instruments Please (http://www.cubase.net/phpbb2/viewtopic.php?t=116034&start=30&postdays=0&postorder=asc&highlight=&sid=ee34dfe17f3c9e0cfb55b0d8956a014c)

Anyone who is using Cubase please also post in that thread and vote "Steinberg have our dosh & support give us what we need please"

Any Plans for making a VST Effeckts only Plugin for the Virus? Could that work with sidechain then?

This is exactly what I would LOVE to see. An FX version that strips out the engine manipulation portion of Virus Control. Have it contain only the 2 FX tabs, and whatever else could be used to process external audio routed into it. This would be great for processing without worrying about it not working due to it looking as if it is still a VSTi running.

[civan]

Yes, you can. You will just need to adjust the delay of the external effect so that you don't hear the latency. It's kind of a pain to get setup, but once it's all done it works very well and super easy to use.

I tried to get this setup last night. I couldn't get it to work. I'm pretty sure I selected the the right inputs and outputs for the Virus as an external FX. When I loaded the input for the external effect on the master channel, all sound was cut off. I went into virus control and setup 3 outputs and 1 input. (Here I got a message that side chaining feature was not supported in my daw, but I was still able to enable it.) Then in the FX page I set the input to L&R. No sound. I tried different input presets from the browser and that didn't work. I also tried turning on the Atomizer and that didn't work either.

Any suggestions? Or could someone try this in Cubase 5? Thanks.

[Hell Yeh]

^^ Until the instrument sidechaining feature is enabled in Cubase, you won't ever use the 3out/1in setting in the Virus. Just leave it on 3out/0in. You should get back sound after that.

[civan]

^^ Until the instrument sidechaining feature is enabled in Cubase, you won't ever use the 3out/1in setting in the Virus. Just leave it on 3out/0in. You should get back sound after that.

So last night I took your advice and it did work. I also realized that even though my cabling was correct, the settings for my T.C. Near (using Studio Konnekt 48 ) were also wrong.

So after I got a signal going through the virus I was able to choose patches and I was able to play with the FX section and Filters. There are a few problems at first though. The signal going through the virus was not the same as the bypass signal, even when I used an init patch. Later I realized that the Boost setting in the Virus config was distorting the input signal. I was able to fix that. For some reason the Atomizer was working; all I got was the channel signal going straight through the virus. [Note that I used the Virus as an external input fx on my song's master channel.]

Another problem: even though the only channel out of 16 in VC was outputing the input signal to analog output 2 L/R, in NEARs direct monitoring I was getting a duplicate signal in analog output 1 L/R also.... weird.

Overall I wasn't too happy with the experience. Even with a clean signal going through the virus I was still getting some sound artifacts (like pops and clicks) which are not present in the bypass signal.

I hope someone at Access can make something of this information. I would eventually like to get a snow to use as a dedicated FX processor for my studio and also for on the go with my DJM-800 but not anytime soon.

[DiScO]

When it works in CB you'll be reveling it! I use it in Logic lots, one of the best features they sorted with VC. I seem to try and process all sorts of material through the TI, it gives the sound something other plugins just can't.

Cheers.