My Virus Polar TI|2 is crashing all over the place. Whenever I try to change a patch in the browser, Cubase 5 crashes. It could be Cubase 5 that's the problem though. Another bug I noticed is that the OS3 beta splash screen always shows up even though I click "Don't show again." Also, randomly I'll get a load high pitch shreek coming from my speakers. I have a feeling the Virus is causing it because it was the only instrument loaded at the time.

3.0.10 disaster area! from a Fruity Looper.
 

Hi,

Since loading .10 I can't get the vst plugin to load at all in FL 8.0.2 - just bombs out with "access violation and a memory address". Everytime.

The stand alone admin tool from the menu loads, detects the TI ok and then also gives the same error.

The TI is on a dedicated usb port and worked fine with release .6 - didn't try .9 and went straight to .10. In hindsight I probably wish I hadn't bothered!

I am sure it will get fixed and am still grateful to Access that they provide such major updates free of charge.


Hope this helps.

The plugin window does not occur bug from 3.01 s back....

load an empty Cubase 5 project, it all works fine, load 5 instances of REV-X, the TI control window will stay gray and not redraw, same test in 3.06/9 works fine.

VC is blank for me too in Cubase Studio 4.5.1 with 3.0.10. Tried exisiting and new project with both VST3 and VST2 and no joy.

Crashing Logic 8.0.2
 

Hi all,

This release is crashing Logic when switching patches in the VC for me. Guaranteed every time without fail. Any other mac users with the same problem?

Cheers.

here too !!!

Wow...
Seems this is the worst version ever!

Remember people, this is just a beta. So we can't expect a version that is somewhat solid until 3.1 is released or something. This is just the nature of software coding... fixing existing bugs or writing new features will induce new bugs. I rolled back to 3.0.09. I can continue working on my tracks for now like this.

That's why I'm still on .05

Yes, I like to tinker and try the latest releases, but this one is particularly bad as it makes the whole thing unusable in Logic. I'll just switch back until it's sorted.

Cheers for confirming all.

Yes, I like to tinker and try the latest beta releases, but this one is particularly bad as it makes the whole thing unusable in Logic. I'll just switch back until it's sorted.

Cheers for confirming all.

Same exact problem! Not really surprised either.

I cannot confirm this... Tried to duplicate and not having this problem. Opened the VC up in new project and switched back and forth through a bunch of patches. No crash. Tried in an existing project and still no crash...

Penryn MacBook Pro, Leopard 10.5.6, Logic Pro 8.0.2, Virus TI Desktop 3.0.10

:no problems with beta 3.0.1.10, so far.
 

i also am having no problems. loaded 3.0.1.10 tonight, and so far it crashed only once, the first time i changed patches. but has been working fine since then, and changing patches / tracks in logic with no problems.

imac, intel core 2 duo 2ghz, leopard 10.5.6, logic pro 8.0.2, virus deasktop 3.0.1.10.

: now it is crashing also
 

i guess i spoke too soon. i took a break for awhile, and upon returning, changing patches and tracks is crashing my system also. but i will try a few more things before i backload to previous ver., since i had it working for awhile, it coud have been sleep mode just messed it up, or something else.

Ok here's the problems I'm experiencing on both 3.0.09 and 3.0.10 with Cubase SX 3.

• Completely out of sync when playing back
• Sounds get ducked away by other sounds, when using multiple channels
• Hanging notes when mutiple channels are playing and when changing presets
• Clicks and pops
• Sounds continue co play although its channel has been muted

okay, i cannot make it crash, no matter what i try. could somebody please send me a crash log to ms [@] access - music . de ?

thanks!

marc

dear marc
what about the vst loading issue ?
did you try to load it as a vst plugin from a DAW ?
i did it from Sonar 8.3.1 and it crashed badly
i think this is also a very important case to investigate

using 3.0.1.09 no problems at all
greetings

Seems some are crashing and some not. Just to confirm my setup, I use a Mac Pro 3Ghz 8 core, 12GB RAM, Logic 8.0.2, Leopard 10.5.6 with RME FF800 and MK1 TI Keyboard. I went down to .09 yesterday, works fine, but I'll put .10 on again later and send the crash log.

Cheers.

please send a crash log, it doesn't crash here.

marc

Hey. Wouldn't post all that often but felt compelled to after installing 3.0.1.10 beta. The update really, really made shit of things on my mac. Every time without fail when loading up a preset though the vc (Through both Ableton live 7 and logic 8 ) A crash would occur.

I have since installed .09 beta and things seem ok now. Lesson learned, come to the forum first and see how others got on with it first. If crash logs etc. are needed I'd happily oblige if it helped to iron out these bugs.


Cheers
Djamel

Ok done,
I've just sent you my crash logs Marc...

Ah, and one other thing that's buging me from version 1 drivers:

"When i plug TI from power for 30 secs and then plug it back in and try to
power it on it pops me the plug n play installer like i've never installed TI's drivers..."

Is this normal?Can anyone reproduce it?

yup, I've got the patch change crash too! I'm also completely unable to use the vocoder. Vc just crashes logic.

Another issue on every version.. Has anyone else had an issue where some patches don't load correctly with a song? I find quite often that filters or lfos sound different when I reopen a project, reloading the patch (providing it's saved) from the browser sorts it but I'm sure it's a bug??

Mac pro 2008 octo 6g, logic 8.02, tios 3.0.1.10

Whoa. Glad I read this thread here first. Sticking to .09 for the time being, no offense Access!

event log c/o .10 on a pc
 

From a XP pro , 2gb RAM core2 E8400 and FL Studio 8.0.2. pc -

Faulting application virus control center.exe, version 3.0.1.10, faulting module virus control center.exe, version 3.0.1.10, fault address 0x0000ed87.

All was good (not perfect but getting there!) with .06.
All is very bad with .10

Thanks.

here's some news:

we can replicate the crash when browsing through patches and we can reproduce the white window syndrome on one PC. it might be that the patches loading with wrong settings will be solved with solving the crash bug but that needs to be determined.

apologies for version 3.0.1.10, especially to TI2 users who cannot roll back to 2.7.5 - we hope to have news this week.

best, marc

how is the easiest way to revert back to 2.7.5 for a virus snow user?

Yes, since I can remember. I'd say its like 50% of the time from power on of the Virus TI if computer is already on. Usually the TI doesn't come to life, no boot cycle on the machine, then windows says 'new hardware' and attempts to find drivers. I just unplug power from TI, cancel windows driver attempt and re plug power, usually fixed every time. Maybe Access needs a 'safe to remove hardware' option in windows.
I know if I turn off my RME FF800 I can crash my computer to instant reboot, only if I use "safely remove hardware" option in windows can I turn off my FF800.

Exactly!
That's how i do it too...

Access please we need something like "safely remove hardware" for us
who have all our gear hooked up on a main power switch and like to turn
it off at nights when we go to sleep to rescue our last brainwave cells...hehehe:)

3.0.1.10 Removed
 

Thank god, access removed the faulty version 3.0.1.10 from their download page. This is a concrete answer to my support request...:D

I hope the next 3.0.1.10 will cause less troubles...

Is that 3.0.10 version currently on the site now, different that the other 3.0.10 version?

As well, I saw version 3.0.05 appear on the site yesterday.
Haven't seen that one before:confused:

Don't know which page you are monitoring, on the page I visited today there is no 3.0.1.10 any more. 3.0.1.09 is the most recent now.

www.access-music.de/downloads.php4?product=virustidesktop

Had the patch change crash problem with 3.0.1.10 and have gone back to 3.0.1.9 which was fine for me before.

Patch change only seems to happen for me if I select a patch from a user library. If I use a ROM bank no problem, Thought it could be a helpful point? Anyone else experience the same??

I cant believe people get so upset!
 

I mean god forbid Access trys to make your work experience more enjoyable by trying to update the hardware! I mean c'mon if it was roland you would have to spend a zillion dollars just to get some crappy update or manual or add-on, and a zillion hours just to find it! And most other manufacturers are like this is all you get! Thanks for giving us $2000, You seen the new Roland gear?? Garbage!!! It's not that hard to realize the word BETA in the update!

If you dont want to help get the BETAS propperly working go back to the real release and stop the crying!


Marc you guys got your shit right and I'll sit and work with whats available G!!

Personally I cant wait to get my 3rd and 4th TIs so I can run all 4 on my JazzMutant and multi network! Just sayin live synths is where its at!:)

+1 VERY impressed with support and velocity of updates, happy to try some more. 3.010 was a bit of a miss, but i am pretty sure 3.011 is going to show real progress. I find tremendous value in my TI with V3 SW, THANK YOU for that! please stay on the ball with the blank VSTi window. it now showed in 10 but i had it in 001 and 003 as well.. (006 and 009 were perfect)

thanks for saying that. some times back, we debated with users if it's better to put out betas fast, to cure little problems, than wait and collect bugs. okay, we found that frequent betas are welcome but also there is a chance to release a bad one - because we simple don't have the time to test a beta with the same level of detail. i guess, now it's down to us to get the mix right.

best, marc

3 out of 10 being a bit of a dud is not a bad score :)

What i found in 10 as well, is that it seems that the USB driver is claiming an interupt differently? I also have a SSL Duende PCIe and since 10 i needed to do several reboots before it's properly initialized, never had that problem before. dunno if this is related, but the behaviour change was definately tied to installing 3.0,10

Please marc keep in mind that for every post with a bug there must be hundreds of people who have no problems with the betas. Ever since 2.5 (maybe earlier) the OS has been great for most of us.

Cheers,
B

of course boys
no hard feelings at all for Access or Marc
they are trying the best for all of us
just think how reliable are other companies to their customers ;)