OS 3.0.1.15 release and 3.0.2.01 beta is out - The Unofficial Access Virus & Virus TI Forum

L.F. · #1 13.05.2009, 04:31 PM

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?

Hell Yeh · #2 13.05.2009, 07:15 PM

Quote:

Originally Posted by 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?

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 · #3 13.05.2009, 09:16 PM

Quote:

Originally Posted by Hell Yeh

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 · #4 13.05.2009, 11:34 PM

Quote:

Originally Posted by marc

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. · #5 14.05.2009, 12:00 AM

Quote:

Originally Posted by marc

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 · #6 14.05.2009, 02:11 AM

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

Spacer · #7 14.05.2009, 03:24 AM

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

HUEY · #8 14.05.2009, 07:38 AM

Quote:

Originally Posted by fender2k1

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 · #9 14.05.2009, 10:34 AM

Quote:

Originally Posted by HUEY

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/showpo...70&postcount=8

Hell Yeh · #10 14.05.2009, 03:25 AM

Quote:

Originally Posted by marc

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.