new update 3.0.4.00

[telson]

About TIOS 3.0.4.00 Public Beta
-SE: Vocoder stops working when used with audio streaming through VC (fixed)
-SE: Atomizer can crash or generate noise under certain circumstances (fixed)
-VC: OS3 parameters not responding to Section Lock (fixed)
-HI: (Virus TI Snow) MIDI In didn't work under certain circumstances (fixed)
-SE: Static input mode didn't work as expected with Virus Control (fixed)
-HI: Improvements to DSP heath checks
-SE: Possible crash when changing patches (fixed)
-IN: wrong product name in Windows Vista User Account Control message (fixed)
-VC: In VST3 Plug-Ins, all parameters are grouped in parts now and can be automated without mapping
***************************************************

thanks access

[Sonis]

Can't even install it, I keep getting an error (error 6 it says) when it's trying to install the drivers. Not doing anything differently since I last installed or reinstalled the virus software/drivers and nothing about my system has changed since then either.

Awesome.

[telson]

Really ? Very strange Sonis
I can't try it right now , i will try it at home

[Sonis]

Yeah I'm actually really annoyed. My TI2 is so unstable that it's unusable and I was really hoping this patch would be the one, but I can't even find out now.

[telson]

Did you follow the installation process correctly ?
You have to uninstall the previous version, right ?

[Sonis]

Did you follow the installation process correctly ?
You have to uninstall the previous version, right ?

Yep tried it 5 times already (literally). Uninstall previous version, restart computer (just to be sure), run installer, error. Tried different USB ports and USB cables too and it didn't change anything.

edit:

Also curious about this one:

-HI: Improvements to DSP heath checks

I wonder if that's supposed to say heat or health, unless they'd hidden candy inside the virus that I don't know about:

http://www.saratogacoffeetraders.com/sitebuildercontent/sitebuilderpictures/heath.jpg

[h4nc0]

downloading now. I wish that I didn't have to enter my email/name info everytime I download something from Access!

Failed updating driver 1st time. Removed all Virus related drivers in Device Manager, removed virus software, reinstalled. New update graphics on Virus it seems. It loads in Ableton Live 8 without a problem and seems to work fine so far.

[telson]

downloading now. I wish that I didn't have to enter my email/name info everytime I download something from Access!

Failed updating driver 1st time. Removed all Virus related drivers in Device Manager, removed virus software, reinstalled. New update graphics on Virus it seems. It loads in Ableton Live 8 without a problem and seems to work fine so far.

Sonis pay attention on this !!!!

[Cantankerous]

Was really hoping to hear of 64 bit support. :(

[Atziluth]

@ Cantankerous

Maybe ACCESS is waiting for 64bit Windows 7 and are skipping 64bit Vista support.
But I don't know if this makes sense?

[Cantankerous]

There is definitely an issue with this version and Cubase 4.5.2. Upon installing this OS version, Cubase no longer opens and constantly crashes to desktop while scanning and listin installed plugins/components. When it finishes listing the Virus Ti, Cubase immediately drops to desktop and upon looking at the Virus as this happens, the LEDS slightly flicker/dim and the words configuring Virus Ti show up on the LCD screen then disappears. It will constantly do this until I unplug power from the Virus, reboot the computer, and load Cubase without the Virus plugged in, in which it will start up without issue. Resetting the Virus with ARP Edit for 10 seconds did nothing either.

[telson]

just installed new O.S. 3.0.4

NO problems at all

no problems at all during installation procedure
no problems at all with my DAW
no problems at all during vsti recognition process
no "sneezing"

thanks access !!!

[Doc Jones]

downloading now. I wish that I didn't have to enter my email/name info everytime I download something from Access!

Failed updating driver 1st time. Removed all Virus related drivers in Device Manager, removed virus software, reinstalled. New update graphics on Virus it seems. It loads in Ableton Live 8 without a problem and seems to work fine so far.
what version of Live 8 are you running. I am on 8.0.4 and though VC loads, it is very sluggish.

[Xtigma]

Could someone try this for me please... just installed the latest beta
seems whenever i turn the Amp Decay knob... the filter release knob moves as well

could you try this also please for me ?

[h4nc0]

what version of Live 8 are you running. I am on 8.0.4 and though VC loads, it is very sluggish.

8.0.4 here. Yes, loading VC takes more time than previous version. I wasn't paying too much attention on loadtime. :mad:

[h4nc0]

Could someone try this for me please... just installed the latest beta
seems whenever i turn the Amp Decay knob... the filter release knob moves as well

could you try this also please for me ?

Turning Amp Decay knob moves Amp Release knob here. :confused:

[DiScO]

No 'sneezing', but still the same crash. Using EkoRoad HS on the first part in a newly created Logic project which is a simple 4 bar loop with one other instrument track containing Alchemy. Good to see the nasty outburst has been tamed, been replaced with a few crackles and a few notes of the init sound, but as for the crash, nope! One thing I will say though, the playing latency without using live or direct mode seems much improved @ 128 samples buffer with RME FF800. I would still love to see the option for just 4 parts, maybe user configurable as I never go beyond that cause the patches I use are just too gutsy. With regards to the sync, again, unless the TI is selected in Logic, the playback is erratic. I know you are waiting for a fix for this though from Apple.

[DiScO]

Turning Amp Decay knob moves Amp Release knob here. :confused:

Confirmed :confused:

[Sonis]

Sonis pay attention on this !!!!

Still won't install. There weren't any virus entries in the device manager for me to remove anyways though.

[h4nc0]

Tried going back to 3.0.3. Everything installed but when running VC, it says version mismatch. Removed everything, reinstalled but same error. Virus OS is 3.0.3, VC dll is 3.0.3. :confused:

EDIT: C:\Program Files\Access Music\Virus TI\Common\Virus Control.dll wasn't updating back to 3.0.3. Deleted Access Music folder and everything is back to 3.0.3 and working fine. I can also confirm the better latency regardless of LIVE button with 3.0.4, perhaps this is a bug as well? Also, 3.0.3 loadtime is almost the same as 3.0.4. I am not so sure if VC loaded any faster than this before.

[Paprika]

includes bug-fixes and a refined DSP meter

A meter? Where?

[Sonis]

Got 3.0.4 to install on my laptop and watched the virus crash about 5 minutes after the firmware update finished. I hadn't even opened my sequencer yet. So much for this patch making my virus usable.

It's funny how in any other industry this would be completely unacceptable. If I bought a car and the engine stopped working every 5 minutes the problem would have been fixed months ago or I would have gotten a replacement car by now.

Ridiculous.

[zeno]

Hey Access.

Installed .4.00

Also confirming that the sneezing is gone, but the virus crashes and restarts just the same.

And after restart, Ableton is out of sync. It also appears that there's less polyphony after the crash. Restarting ableton solves these issues.

Update: Had many more problems. Reinstalled .3.00 - First time I've reverted on beta.

[Warren_UK]

Not worth upgrading from the comments here. I was hoping this would fix the issue were my TI in stand alone mode crashes from time to time with OS 3.0.3.

Seems I'm sticking with 2.7.5 then :cry:

[Timo]

A meter? Where?

Maybe I should rephrase that. Looking at the change-log, it's the same meter, but it's more accurate.

[marc]

With regards to the sync, again, unless the TI is selected in Logic, the playback is erratic. I know you are waiting for a fix for this though from Apple.

this is only for the analog outs, not for the USB outs. we discussed this like 4 years ago. i didn't say we are waiting for a fix from apple. i said, only logic can provide addition information to the plug-in which would resolve the problem.


No 'sneezing', but still the same crash. Using EkoRoad HS on the first part in a newly created Logic project which is a simple 4 bar loop with one other instrument track containing Alchemy.


as for the patch which makes it crash, please send me an arrangement

best, marc

[mitchiemasha]

If I bought a car and the engine stopped working every 5 minutes the problem would have been fixed months ago or I would have gotten a replacement car by now.


but if you bought a test car!!!

I've never had a problem with an actual release. Problem they have is rather than just fixing bugs, with each update comes improved ideas, sometimes new ideas. This then creates new bugs.

[telson]

Ridiculous.

First of all you have to learn how to update your machine cause you didn't
Secondary you have to know that this update called Beta Release

After that ask yourself mister WHO ARE RIDICULOUS

GOOD NIGHT

[Sonis]

but if you bought a test car!!!

I've never had a problem with an actual release. Problem they have is rather than just fixing bugs, with each update comes improved ideas, sometimes new ideas. This then creates new bugs.

I've had the crash problem with every version of the ti firmware since I bought my ti2 desktop. It's not JUST the new beta releases.

First of all you have to learn how to update your machine cause you didn't
Secondary you have to know that this update called Beta Release

After that ask yourself mister WHO ARE RIDICULOUS

GOOD NIGHT

If you'd read my post you'd see that I said it updated fine using my laptop and promtly crashed 5 minutes later. It has nothing to do with it being a beta release, it's the exact same crash I've been getting since I bought my TI like I said already. I don't see how you don't understand this. Just because your unit is working fine doesn't mean everyone else's is. I also don't see why you're getting butthurt from me saying it's ridiculous that something I paid $2000 for doesn't work unless it's complete blind fanboyism which I wouldn't put past you.

Oh and I did a system restore to before the last windows update and got it to install on my desktop too so something went wonky when XP updated last time, and it still crashes so that had nothing to do with it. Nice try though.

[zeno]

Sonis, have you contacted support? Just curious.

[Sonis]

Yeah of course haha, they just tell me basic stuff that I've tried 1000x over just doing a hard reset by holding arp edit, and when that doesn't work they tell me that they're working on it.

Either that or the ticket sits unanswered for 2 weeks.

[Kobayashi]

I've had the crash problem with every version of the ti firmware since I bought my ti2 desktop. It's not JUST the new beta releases.



If you'd read my post you'd see that I said it updated fine using my laptop and promtly crashed 5 minutes later. It has nothing to do with it being a beta release, it's the exact same crash I've been getting since I bought my TI like I said already. I don't see how you don't understand this. Just because your unit is working fine doesn't mean everyone else's is. I also don't see why you're getting butthurt from me saying it's ridiculous that something I paid $2000 for doesn't work unless it's complete blind fanboyism which I wouldn't put past you.

Oh and I did a system restore to before the last windows update and got it to install on my desktop too so something went wonky when XP updated last time, and it still crashes so that had nothing to do with it. Nice try though.

I have never really understood what possesses people who use beta software, or early adopters to scream at the top of their lungs until their blue in the face when they have a problem. Does it make you feel better? I have seen guys like you at the Apple Genius Bar just yelling at the top of their lungs and I always just sort of laugh to myself.

"I paid "$XXXX.XX", blah blah blah!".

My man, there is nothing in my studio that makes sound that hasn't had some bugs... Computers, synths, even really old synths I have had some funny errors.

I have used Viruses since the very first Virus. The Access folks have always managed to sort things out at the end of the day, and are light-years more responsive than any other synth company who's products I have used. I am sure they are working on it as we speak. Have some patience, they will get it right. They always have.

And if you want to live a life without ever seeing a bug again... learn to play the Banjo.

K

[Sonis]

I bought the virus on Feb. 20th, 5 months is a bit past the "early adopter" point don't you think? :P

Has nothing to do with the fact that it's beta software like I've said already. I've had the problem since I bought the thing. How is it at all unrealistic to expect a show stopping bug like this to be fixed 5 months later?

Just to help illustrate the severity, it's not an occasion crash every 2-3 hours, that I could totally deal with. The thing crashed twice in the two minutes it took me to type this post, and the USB cable isn't even plu... three times... gged in right now.

EDIT: in fact let me find the battery charger for my video camera so you can see what I'm talking about, I'll get a video of the crash machine up in a few hours. Maybe you'll understand why I sound so angry then.

[Chicago]

I bought the virus on Feb. 20th, 5 months is a bit past the "early adopter" point don't you think? :P

Has nothing to do with the fact that it's beta software like I've said already. I've had the problem since I bought the thing. How is it at all unrealistic to expect a show stopping bug like this to be fixed 5 months later?

Just to help illustrate the severity, it's not an occasion crash every 2-3 hours, that I could totally deal with. The thing crashed twice in the two minutes it took me to type this post, and the USB cable isn't even plu... three times... gged in right now.

EDIT: in fact let me find the battery charger for my video camera so you can see what I'm talking about, I'll get a video of the crash machine up in a few hours. Maybe you'll understand why I sound so angry then.

When the machine crashes, what are you doing? You said USB is not connected, are you playing it? changing patches? or is it just idle and crashing?

[Sonis]

It's just sitting there idle crashing.

Video is uploading to youtube right now. Crashed 16 times in 10 minutes while sitting idle. Just left my camera on a tripod pointing at the virus while I made myself lunch and exported the first 10 minutes worth of video.

Here's the video:

http://www.youtube.com/watch?v=R9KHVGVAnM4

[goldenanalog]

Sonis: Brand-new to this forum; I actually just joined so that I could post directly to you:

It really sounds like your TI2 is defective.

The only other thing that I can think of, is whatever you're using to load in the OS is possibly corrupting the OS data as it streams into the TI2.

I had an interesting experience with a Roland VS-2480 I picked up from GC a couple months back; I reloaded the OS to clear it out (don't initially trust used equipment purchases....especially since this one was so cheap!) several times using a 'reliable' dual-core laptop, and afterward, the VS kept rebooting and rebooting.

I contacted Roland to find out what I could do; they told me that they needed to see the machine for 100 buck minimum; they also hinted that they would reload the OS using an antiquated (but ultra-reliable) computer kept just for the purpose.

Anyway, I came up with a solution:

Since the OS was loaded via midi, I put the OS file into my Triton Extreme, and 'played' the file using the built-in sequencer.

Viola! The VS accepted the file, was restarted, and booted normally.....and has been working fine ever since!

HUGE lesson(s)!

1.) If it ain't broke, don't fix it. That may include chasing every OS update that comes along, and:

2.) There is most definitely a risk when doing an OS update; and in my VS-2480's case, it was my laptop-midi combo.

The fact that Roland support keeps an antiquated computer around just to GUARENTEE updates to VS machines that they see will be done successfully says volumes about the need to keep the OS update data stream pure to avoid the nightmare that your TI2 is causing you...I really hope that you get it staightened out, Sonis.

I got a TI1 and (2) Snows; I love mine, but I only update when the benefits truly out-weigh the risks....

Good luck, Sonis.

Sincerely,

goldenanalog

EDIT: Sonis, just to be clear: I'm hopeful that it's just a bad and/or incomplete OS loaded into your TI2, but my fear is that it is indeed 'broken.'

Please keep us informed, and (hopefully) marc & co make this right. I'd hate to be in your shoes...having something as extremely cool as a TI2, and not being able to even trust it for a minute (saw some of your video on youtube) RJH

[Doc Jones]

wow, yeah Sonis, something is definitely wrong there. That would drive me insane!

[Celestry]

Bitter! (>_<)

I'd be furious! It's stuffed, so send it back, no further debate!! (>_<)

[telson]

Sonis, have you contacted support? Just curious.

that's right. exactly
Sonis after bla bla bla do something useful
also nobody knows your software and hardware setup
and if they function rightly

[Celestry]

that's right. exactly
Sonis after bla bla bla do something useful
also nobody knows your software and hardware setup
and if they function rightly

I can't believe what i'm reading in this thread!! Telson, are YOU actually reading this thread?? You're being a cock to guy that has a machine that is screwed!! And your last post, quoted above, will hopefully be your last on this matter as you shamble away knowing you're trolling a guy for no reason, given the quote from Sonis below, of course, which was posted yesterday!

Yeah of course haha, they just tell me basic stuff that I've tried 1000x over just doing a hard reset by holding arp edit, and when that doesn't work they tell me that they're working on it.

Either that or the ticket sits unanswered for 2 weeks.

[Sonis]

that's right. exactly
Sonis after bla bla bla do something useful
also nobody knows your software and hardware setup
and if they function rightly

Try reading the rest of the thread before you post then. I've said numerous times that I've already contacted support and that it obviously has nothing to do with my software and hardware setup since the virus does the exact same thing when the only cord plugged in is the power cord. I don't see how you don't understand this. I've even posted an uncut 10 minute video of the virus crashing while only the power cord is plugged in and it's sitting on the init patch.

I don't know why I'm even justifying your post with a response to be honest though. It was painfully obvious that don't want to hear any bad words about your precious synthesizer as soon as you started with the personal attacks. Sorry if I accidentally prevented your thread from turning in to the access music circlejerk you were hoping for! :rolleyes:


edit:

I can't believe what i'm reading in this thread!! Telson, are YOU actually reading this thread?? You're being a cock to guy that has a machine that is screwed!! And your last post, quoted above, will hopefully be your last on this matter as you shamble away knowing you're trolling a guy for no reason, given the quote from Sonis below, of course, which was posted yesterday!

Thank you haha.

[telson]

+ 1000 kobayashi

Sonis are you playing with us?
Are you serious?
This error has nothing to do with latest os update.
Try to understand this.
You said that you are facing this problem almost since you bought this.
Are you serious ? Why didn't you ask Access to replace your machine ?

[feedingear]

I think my Polar just sneezed in Cubase... buzz of noise then a staticy burst after about 2-3 hours of (light) usage in cubase, only two parts, happened when in playback changing between oscillator types quickly. Happened the next two times I did playback and tweaking.

I normally dont push the virus like that because I know its sensitive to overload while playing back tracks/reading the forums. That error sound familiar to everyone?

[Mr Ben]

Hi Sonis

After watching your you tube vid there is definitely a major problem with your virus.
I suspect it has nothing to do with the OS it looks more like a major hardware fault.
Maybe a power supply problem i dont know.
But send it back and get a replacement for it man.

I feel for you mate it must be driving you up the wall.

[absynth]

send it back to your dealer and they will send it to access to repair it

its a pain in the ass but thats the only good solution

[Paprika]

it's the same meter, but it's more accurate.

I meant, where is any meter? I always wanted to know how much I load up virus.

[ben crosland]

I meant, where is any meter? I always wanted to know how much I load up virus.

Top right of the Single or Multi play pages. It's a little rectangle that works like a battery meter - the more bars in it, the more DSP the patch is using.

[realtrance]

I would agree with goldenanalogue; first, it definitely sounds like it might be worth the trouble to look into whether there's a hardware defect that's a factor.

If that's too much to contemplate (I can understand this! Shipping around keyboards these days is pretty risky, unless you drive it there yourself), then I really do think the whole USB connection is an area you should investigate more thoroughly.

I've been reading around online and I'd never heard until recently that USB can have real problems with noise, especially if there are any grounding (or worse, ground loop) issues with your computer. It's entirely possible that there's something like that going on with your Virus/PC USB connection.

I would try updating it with a different computer, try a variety of options -- a laptop, a Mac, whatever -- borrow if you have to -- to see whether it makes any difference. Or first, take _everything_ off your USB connections and only connect the Virus and try going that way.

Just trying to help! I had problems with one version of the TI OS update, back around the 2.x time frame, and Access proved very helpful. Like many boutique synth companies (Clavia, Waldorf), they're small, so patience and good cheer is required in communication (hey, this is even true with big companies! <g>). Just hang in there and eventually you'll find a solution, one way or another.

[Sonis]

Finally got ahold of access support by closing a ticket that was unanswered for 2 weeks, and they're getting in contact with the place I ordered it from (sweetwater) to see if they have another TI2 that I can swap it out with and can send my unit back to the access office.



+ 1000 kobayashi

Sonis are you playing with us?
Are you serious?
This error has nothing to do with latest os update.
Try to understand this.
You said that you are facing this problem almost since you bought this.
Are you serious ? Why didn't you ask Access to replace your machine ?

I never said it had anything to do specifically with the latest update. The problem hasn't been this severe since I got the unit, and some days it isn't AS bad as others (it'll only crash every 20-30 mins or so and not ever 50 seconds on some days). Not to mention in the first two months worth of contact with access support they specifically told me to wait for an update to fix the problem, so why would I not think it was a problem with the software originally?

Also, why would I be playing with you? It's not like I have anything to gain by making an internet forum think my synthesizer is broken... That'd be totally imbecilic.

[Hollowcell]

Just read through the thread...

First of all I feel sorry for you guys having trouble with the TIs - so many problems, so much money spent!

Secondly, Telson my friend, you are a complete wanker and should be kicked off the forum. I am not one for personal attacks (stop grinning old UaVF members), but your comments are not helpful to anyone, and your obvious fanboi style can affect Access as threads like these go for much longer than they need to.

So suck it up and fuck off. Meant in the nicest way of course. :)

[telson]

Hollowcell

My Polar works FINE, stop crying girl
You have to live with that because it's something that bothers you
So suck it up and fuck off. Meant in the nicest way of course. :smile:

[feedingear]

Can we keep these posts constructive? This forums generally got a nice vibe and most threads are worth reading - a rarity in most internet forums.

[Timo]

Telson, we're happy that your v3.0.4 OS works brilliantly, however that's no reason to troll/chastise other people for issues regards theirs. Access previously stated via email that the OS following v3.0.3 may help Sonis, which is why he posted here. It now appears he clearly has a hardware fault and Access are finally trying to remedy that issue with the distributor for him. So hopefully things will be better for him.

We try to keep freedom of expression as much as possible here, but it doesn't mean you can abuse that privilege. Further unconstructive comments or one liners to the argument will be deleted. After which, bans will be issued.

Respect other people and respect will be given in return.

Let's get back to the discussion of TI OS v3.0.4. :) Cheers.

[Ingo]

Hello,

i installed OS 3.0.4 pb on my Virus TI (mk I) desktop today. Used it via USB and VC and no problems so far in Ableton Live 8.0.4. The pops and clicks seem to be disappeared. The polyphony seems to be slightly increased, from sometimes only 9-10 notes to about 15. This has to be further investigated. So far after nearly 3 years the first time i could really use the Virus TI. Wanted to sell it about 10 times during the years. Now that i have the Waldorf Largo softsynth this still might happen sometimes.

[fgimian]

Regarding the DSP meter, I have always really wished for something along the lines of a CPU meter to let me know exactly how much polyphony I am using, and how much is left.

Does anyone else crave this? Do you think Access could make it happen?

Regarding the noise bursts, I recently (since upgrading to OS3) have had several noise bursts (I'm still on the latest stable build though). On my system, they sound like stereo noise (without much high freq content) being distorted very heavily. They aren't excessively loud, but they still give me a scare every time. Unfortunately, I have not yet been able to confirm that it is the Virus TI causing these noises, the only other suspect is ArtsAcoustic Reverb (although that has never caused my trouble in the past).

Good luck to all with issues, I hope you get them sorted soon :)

P.S.: On this particular forum, I have to click EDIT twice to edit my posts, anyone else have that issue? Firefox 3.5.1 here

[absynth]

any change of that slow-down problem in Windows 7? when in browser tab vc and changing tabs?

[Cantankerous]

Regarding the DSP meter, I have always really wished for something along the lines of a CPU meter to let me know exactly how much polyphony I am using, and how much is left.

Does anyone else crave this? Do you think Access could make it happen?

Regarding the noise bursts, I recently (since upgrading to OS3) have had several noise bursts (I'm still on the latest stable build though). On my system, they sound like stereo noise (without much high freq content) being distorted very heavily. They aren't excessively loud, but they still give me a scare every time. Unfortunately, I have not yet been able to confirm that it is the Virus TI causing these noises, the only other suspect is ArtsAcoustic Reverb (although that has never caused my trouble in the past).

Good luck to all with issues, I hope you get them sorted soon :)

P.S.: On this particular forum, I have to click EDIT twice to edit my posts, anyone else have that issue? Firefox 3.5.1 here

Instead of having a 'bar meter' why not give a % value. 0% is no DSP being used, 100% means totally maxed. I am sure every user can read a numeric value over a 'bar estimation'.

[Doc Jones]

any change of that slow-down problem in Windows 7? when in browser tab vc and changing tabs?

Absynth, I haven't had a chance to test out 3.0.4 yet, but with 3.0.3 I was able to get around the very sluggish VC UI (and other issues with Windows 7) by running my daw (Live 8) in compatibility mode.

[Doc Jones]

that last line should read Live 8

[HUEY]

Installation went fine here.
So far so good

I can confirm the bug, that when you change the " amp decay" (in Virus Contol!!!) the "amp release" moves as well
when you move the amp decay on the virus itself the amp release doesn't move in virus control.

WinXPsp3, TI1 Desktop, SX3

Br

[TheHobbit]

Keep trying to install this (thought id play) but my system keeps blue screening on the firmware update.

The driver install is fine but just before updating the virus BSD (Blue Screen of Death) appears...never had a problem with my PC and using same USB socket since ever getting the virus.

Only software to do this,.

Any ideas and anyone else had this issue.

Have done a cold reset on virus-rolled back drivers etc but still same issue odd but true :(

Only update its happened with is 3.0.4 all the other fine including back dating to 3.0.3.

[boborulz]

I think my Polar just sneezed in Cubase... buzz of noise then a staticy burst after about 2-3 hours of (light) usage in cubase, only two parts, happened when in playback changing between oscillator types quickly. Happened the next two times I did playback and tweaking.

I normally dont push the virus like that because I know its sensitive to overload while playing back tracks/reading the forums. That error sound familiar to everyone?

Hey,

Yea i've seen on many posts about the same problem. I have a Ti desktop and it does this too....i'll email access to see what they have to say.

[absynth]

Absynth, I haven't had a chance to test out 3.0.4 yet, but with 3.0.3 I was able to get around the very sluggish VC UI (and other issues with Windows 7) by running my daw (Live 8) in compatibility mode.

hm...gonna try that

i guess i´ll wait for the release version of the new update, sounds like too many problems

[h4nc0]

There's Live 8.0.5b5 which supposedly fixes slow GUI issues with Win7, perhaps try that?

[Ingo]

Installation went fine here.
So far so good

I can confirm the bug, that when you change the " amp decay" (in Virus Contol!!!) the "amp release" moves as well
when you move the amp decay on the virus itself the amp release doesn't move in virus control.

WinXPsp3, TI1 Desktop, SX3

Br
Confirmed the bug for the Amp envelope. On the filter envelope it's normal. The bug does not appear when using the hardware.

So far the only bug i could confirm (finally, after around 30 months !!). Running OS 3.0.4 pb on Virus TI desktop (mk I), Ableton Live 8.0.4, Win Vista 32-bit.
I had no installation problems in all 3.x.x updates. I only deinstalled the old VC software before installation (not the drivers !!).

[tranqui]

skipping 64bit Vista support.
But I don't know if this makes sense?
skipping anything vista-related makes sense!

in my case, this OS didn't even survive the first bootup after unpacking my laptop. I got so pissed waiting that I turned the f***er off and popped in the xp cd :D

ontopic, I have never had any issue with any OS update - beta or not. strange to see so many problems reported, even with the installation? damn. I'll try it tomorrow and report.

[DIGITAL SCREAMS]

I've had the crash problem with every version of the ti firmware since I bought my ti2 desktop. It's not JUST the new beta releases.



If you'd read my post you'd see that I said it updated fine using my laptop and promtly crashed 5 minutes later. It has nothing to do with it being a beta release, it's the exact same crash I've been getting since I bought my TI like I said already. I don't see how you don't understand this. Just because your unit is working fine doesn't mean everyone else's is. I also don't see why you're getting butthurt from me saying it's ridiculous that something I paid $2000 for doesn't work unless it's complete blind fanboyism which I wouldn't put past you.

Oh and I did a system restore to before the last windows update and got it to install on my desktop too so something went wonky when XP updated last time, and it still crashes so that had nothing to do with it. Nice try though.

Sonis - I feel your pain....

But have you ever asked yourself.....maybe its your computer that is the problem? For alot of people (myself included) I've never really had the 'problems' or 'issues' that some people seem to rant about. I have a dedicated audio pc which was customed built by digital village. There is no unnecesary programs on my machine...and its been tweaked (both bios and windows) for optimum audio performance. I just feel that maybe there is a conflict in your connections or computer software that is running in the background.

Practically all software has bugs...and a combination of these bugs might result in strange behaviour in your sequencer or virus?

DS

[Sonis]

Access contacted the people I ordered it from and they're sending me a new unit today! Before I even sent the one I currently have back which actually really surprises me, but whatever it means I get a working virus faster so yay!

But have you ever asked yourself.....maybe its your computer that is the problem?

Read the thread lol, it crashes when it's not even plugged in to the computer, dunno how many times I've said that.

[TheHobbit]

Update to 3.0.4 no more BSD. Problem solved.

Tried again and it's worked updated to 3.0.4. Had a nasty Win32/Rootkit.Agent.ODG trojan in my system (teach me to surf on the DAW)...installed itself as a driver and kept renaming itself. Took a little while to remove but no real issue. Appears it tries to interrupt with any ports when communicating ethernet/usb and the like hence the system crsahing.

[Celestry]

Access contacted the people I ordered it from and they're sending me a new unit today! Before I even sent the one I currently have back which actually really surprises me, but whatever it means I get a working virus faster so yay!

RESULT, SONIS! \(^_^)/ YAY, indeed!

My TI2 Polar is pretty reliable; I can be in the middle of updating the bugger to the latest beta, so I'll go and put the kettle on, and sure enough, the MAC will go into standby, and as soon as I wake it up, the TI2 continues to accept the firmware upgrade! I always worry it'll corrupt the little sod, but it never does! Same thing happened with OS 3.0.4. Made myself a cuppa, had to wake the MAC up (must reconfigure the power settings! LOL) and it just went about its business.

It's not all good, though. I've had to wipe its nose after a sneeze on occasion.

LOL, wipe its nose, sneezing! Our Viruses all have H1N1! (@_@)

[soulidstate]

Hi Sonis,

Good for you that your unit was replaced.I have the same problem as yours where the TI2 crashes even without anything connect except the power. Analoguehaven said unit replacement is only good for 45 days counting from purchase date . After which,the manufacturer takes over the warranty obligation. I bought mine last April. Since Access will not admit that this is a hardware problem then I am stuck to wait until Access comes up with an OS that will cure the sneezing and God only knows when. My take here is that if your replacement unit for example does not show the same problem as your original unit then it's confirmed that it's really a hardware problem and Access should do something about those that have problems just like mine.

Your input regarding your new TI2 would be very important. I hope you can post how it goes.Thanks

[pixie]

Actually, I don't own a Ti but a Kc
Since I'm considering upgrading to Ti, I've been reading most of the TI related threads with interest.


Something is bugging me, a fact that everyone seem to be missing :

Why the very same hardware configuration can lead to so many different buggy behaviors ?
Why after a hard reset, same machines, with same OS, have different stability issues ?
Why some of you cannot even upgrade the machine ?
Do viruses have life of their own ?

I mean, viruses are more or less computer with analogs and digital outputs. So far, I have never seen computers fitted with the same hardware components and OS acting differently after a clean install.

Some of you seem to be lucky with their virus while other can't even consider doing music with it, that's odd.
I think you should stop blaming your computer, USB cable, midi player or whatever, and ask yourself :

Is there any chance that, Virus stability issues are internal hardware related ?
(and yes the OS is probably buggy too, but not that buggy)

From my experience with computer and VAs, I know there are different qualities of hardware components (especially RAM chip), I'm also pointing this direction because my virus Kc had stability issues which were solved by sending it back to germany and having a faulty chip replaced.

just my 2 cents

frederic

[soulidstate]

I think the challenge here is to make Access admit that it's a hardware problem. Until they come into terms with this reality if ever this is really the case then TI2 owners like myself is destined to suffer.The problem is Access support keeps on insisting that the problem we face isn't hardware related but the problem with this claim is that if this isn't really HW related but the OS, then ALL TI2 sold will have the same problem. This is something that cannot be answered as there are only a handful of people having such a complain and I am sure there are more than 100 units sold worldwide.

Come on Access, give us the real score!

[Paprika]

So guys, how to fix Decay->Release knobs issue?

[Sonis]

Hi Sonis,

Good for you that your unit was replaced.I have the same problem as yours where the TI2 crashes even without anything connect except the power. Analoguehaven said unit replacement is only good for 45 days counting from purchase date . After which,the manufacturer takes over the warranty obligation. I bought mine last April. Since Access will not admit that this is a hardware problem then I am stuck to wait until Access comes up with an OS that will cure the sneezing and God only knows when. My take here is that if your replacement unit for example does not show the same problem as your original unit then it's confirmed that it's really a hardware problem and Access should do something about those that have problems just like mine.

Your input regarding your new TI2 would be very important. I hope you can post how it goes.Thanks

Yeah I'll definitely post and let you know how the new unit ends up working. They're having me ship my old one direct to them so that they can look at it and see what was causing the crashing so hopefully they'll find something that'll work out in your favor.

[h4nc0]

c'mon access. give us 3.0.5! :D

[Ingo]

Hi Sonis,

Good for you that your unit was replaced.I have the same problem as yours where the TI2 crashes even without anything connect except the power. Analoguehaven said unit replacement is only good for 45 days counting from purchase date . After which,the manufacturer takes over the warranty obligation. I bought mine last April. Since Access will not admit that this is a hardware problem then I am stuck to wait until Access comes up with an OS that will cure the sneezing and God only knows when. My take here is that if your replacement unit for example does not show the same problem as your original unit then it's confirmed that it's really a hardware problem and Access should do something about those that have problems just like mine.

Your input regarding your new TI2 would be very important. I hope you can post how it goes.Thanks
When i hear that problems concerning the TI2 i am glad that i have the TI Desktop mk I and didn't try to update. With my mk I Desktop (around 30 months old) most problems seem to be finally solved with the new update 3.0.4 pb.
I hope that those annoying problems with some TI2 and TI units will be solved by another update soon. Like i stated in an older post i was around 10 times up selling my TI but with every update it was getting a bit better. Now i have the hope that all problems could be fixed sooner or later. Not sure about those TI2 problems since i don't have one of those.

[djones]

Installed and everything seemed to work fine untill I came accross the Lfo section.
Now, when I dial just lfo '1', then the dial of lfo 2 goes allong as if I have they are linked, but they are not.
And it only happens when I edit the dial of lfo 1, not vice-versa.

[Paprika]

Now, when I dial just lfo '1', then the dial of lfo 2 goes allong as if I have they are linked, but they are not.
And it only happens when I edit the dial of lfo 1, not vice-versa.


Good to know. I never install beta again before it's well tested here :) Back to 3.03..

[Paprika]

Someone may also notice that VC GUI in 3.04 is much slower, when you tweak knobs in particular. Now I'm even more certain about that with 3.03 on a board.

[marc]

Someone may also notice that VC GUI in 3.04 is much slower, when you tweak knobs in particular. Now I'm even more certain about that with 3.03 on a board.

on which platform/sequencer etc. ?

thanks, marc

[Paprika]

on which platform/sequencer etc. ?

thanks, marc

That was on latest FL Studio.

[marc]

That was on latest FL Studio.

details please :)

marc

[Paprika]

details please :)

marc

FL Studio 8.0.2, XP SP2. VC was like on very low frame rate. I don't want to install 3.04 again, but I took a few videos with 3.03 now. We can compare with future release later.

[Timo]

Posts removed, let's stay on topic. TI OS v3.0.4.00...

(Telson, I haven't got time for clearing up your mess. Last warning.)

[djones]

Good to know. I never install beta again before it's well tested here :) Back to 3.03..

Same problem occuring while dialing the 'decay' button in the amp envelope, with the 'release' button going along.

[cl516]

I've installed 3.0.4 now, does anyone know if it still 'sneezes'?

I didn't even bother turning my speakers on, I just keep trying to change patches and wait for a crash like on the 3.0.3.

I always use it as a standalone machine, never with Virus Control.

3.0.3 was frustrating because only in the past week or so did it start crashing. Just straight up turn-machine-on, suddenly crash. No apparent reason.
Anyone getting this on 3.0.4? I ask because I want to protect my eardrums. The last zap I got was really really bad, I got a headache.

[starcorp]

3.04 gives me big cpu spikes and crackle.
i am step back to 3.03.

cubase 5.01, vista 32, i7

jan

[soulidstate]

I've installed 3.0.4 now, does anyone know if it still 'sneezes'?


When I first installed 3.0.4 I thought it was the final solution but after 2 days,my hope turned into frustration.Yes it still sneezes in 3.0.4.

[Sonis]

For everyone who is interested the replacement for my TI2 desktop got here today and it's been running all day without crashing. It's like I just bought the virus all over again. Been using it from about 4:30pm to now (11:30pm) and it's been flawless aside from a couple slip ups in the arp timing which resolved themselves by stopping and starting playback of course.

So it definitely was a problem with the unit itself.

[Mr Ben]

Nice one Sonis

Glad its all been sorted for you

Have fun

As far as 3.0.4 goes i for one am not gonna update.
3.0.3 is ok here i sometimes get a few timing issues but i just restart from the beginning of the tune and all is well.:grin:

[telson]

Posts removed, let's stay on topic. TI OS v3.0.4.00...

(Telson, I haven't got time for clearing up your mess. Last warning.)

άντε και γαμήσου ρε μαλάκα

Edit: Likewise. Have fun elsewhere.
User got the boot for this post.

Let's continue with the original topic...

[DiScO]

Working ok here in Logic 9 so far. A few sync issues but no 'sneeze' so far. Not been running it for long though. Any chance the TI can take advantage of some of my unused cpu power? Just like SSL have done with Duende?

[Hollowcell]

Great news Sonis!

[Doc Jones]

good deal Sonis!

[diy]

As a greek,I have to admit that people like telson make me feel ashamed of my origin.I'm fed up with all these "keyboard warriors". Not intented to be off topic but these smartasses are the reason why I don't post in greek music tech forums. They know everything and they produce nothing except mess...sorry again for the off topic :)

[tranqui]

let's not get worked up over a guy who's overstepped the boundaries. he's gone, it's done.

ontopic: new beta works fine with ableton 8.0.4; the only little problem I am still facing is that when playing live and switching programs, VC says "out of sync - press stop and play to resolve". it stays in sync though.

[thomas]

Ok, I'm gonna try this beta.
Version 3.0.3 keeps messing up my patches.
I can save them in VC but they sound different
- tape delay doesn't always sound as is set in the patch
- sometimes a filter parameter get randomised

[solconnection]

This latest beta isn't working for me either :( Im on a macbook pro, osx and logic 8 with a motu ultralite.

Ive had a TI since the early days and it's worked like a charm pretty much the whole time.

unfortunately since all the v3.x os updates it has become a lemon with bad syncing/timing/arp issues...some synth lines will start playing off time or just stop outputting while others seem to play ok. it also emits a strange buzz (which sounds like the init patch) every now and then, even when not receiving any midi (ie. the VC plugin is loaded in my project but im not using it) and i need to hit panic on the TI hardware. I also get the "out of sync - press stop and play to resolve" message ALOT, even on an empty project with just one or two channels of TI.

reverting back to trusty old 2.75...think ill wait quite a while to try OS3 (which is a shame as it's got lots of nice new features)

-Dan

[solconnection]

hmmm, reverted back to 2.75 and still getting issues, even though they didn't start until i installed 3.x they seem to be persisting on revert. Maybe 3.x changed some settings? maybe i could get 3.x to work properly with some further tweeking.

-Dan

[Kobayashi]

hmmm, reverted back to 2.75 and still getting issues, even though they didn't start until i installed 3.x they seem to be persisting on revert. Maybe 3.x changed some settings? maybe i could get 3.x to work properly with some further tweeking.

-Dan

What issues specifically? Details holmes, details.

[Werner schijvenaars]

I'm new at this forum so hello everybody.
It look like i had te read this forum a little earlier.


i bought an virus TI2 resent and up to now it seems an very bad investment.
with os 3.03 i did suffer the sneezing problem everybody explains. but only ones or twice a day.

so i did try the new 3.04 os to see if this would solve this.

Wel now it is hopeless, my cubase is crashing al the time
Cubase is saying an serious error occurred, and then it closes.

it does this every 5 min making it completely useless.

so i tried to go back to 3.03 by installing the 3.03 software from the Access website, unfortunately it makes no difference at all.

I even completely re installation of my system from scratch
with only cubase and virus, it still is crashing.

starting the Virus controll center sometimes give blue screens,
In the controll center it say's OS 3.03
but when it is updating the virus the screen on the virus says Update mode 3.04

so it looks like there is still some 3.04 in the virus, is there an special procedure for going back to 3.03.

at this moment i would be very happy with the situation it was before.

anyone experience with downgrading the OS ??

Regards

Werner

[Doc Jones]

Hi Werner, welcome to the forum. Bummer you are having so many problems. Can you post a little more info about your daw's configuration - (eg OS, 32 v 64 bit, service pack level, sound card etc.)

also, I may be able to debug your dump file (created with your computer blue screened - assuming it is a windows machine). PM your email address and I'll give you mine to email over the dump file.

[gnome]

fixes nothing........nothing.Still the ti cant run in multi mode properly without its audio data becoming corrupt when you try and use more than the cpu can handle .Why cant they build in a failsafe mechanism .

[gnome]

werner , 100's of people have ahd these issues, its a virus ti and thats what they do , honestly i give up on mine , its a substandard faulty synth which access know has design issues , hardware problems and bad build quality .




i bought an virus TI2 resent and up to now it seems an very bad investment.
with os 3.03 i did suffer the sneezing problem everybody explains. but only ones or twice a day.

so i did try the new 3.04 os to see if this would solve this.

Wel now it is hopeless, my cubase is crashing al the time
Cubase is saying an serious error occurred, and then it closes.

it does this every 5 min making it completely useless.

so i tried to go back to 3.03 by installing the 3.03 software from the Access website, unfortunately it makes no difference at all.

I even completely re installation of my system from scratch
with only cubase and virus, it still is crashing.

starting the Virus controll center sometimes give blue screens,
In the controll center it say's OS 3.03
but when it is updating the virus the screen on the virus says Update mode 3.04

so it looks like there is still some 3.04 in the virus, is there an special procedure for going back to 3.03.

at this moment i would be very happy with the situation it was before.

anyone experience with downgrading the OS ??

Regards

Werner

[gnome]

latest os 3.04 for me is no different from 2.75 , 3.03 etc etc etc etc etc .......all make no difference.

In multi mode with no usb . pc control and using headphones i still can only run 4 parts max before it glitches and pops and about 15 midi notes.Multi mode has a design flaw access wont admit.

[soulidstate]

With 3.0.4 VC plug in in Acid pro is unstable. It hang during VC start up.If I cancel it and restart the VC again, it cannot see the TI anymore. Well, it seems
3.0.4 is more problematic than the previous 3+ OS. where I don't experience this problem.

[lukas412]

With 3.0.4 VC plug in in Acid pro is unstable. It hang during VC start up.If I cancel it and restart the VC again, it cannot see the TI anymore. Well, it seems
3.0.4 is more problematic than the previous 3+ OS. where I don't experience this problem.

Is acid even a supported host?

[Werner schijvenaars]

Hi Werner, welcome to the forum. Bummer you are having so many problems. Can you post a little more info about your daw's configuration - (eg OS, 32 v 64 bit, service pack level, sound card etc.)

also, I may be able to debug your dump file (created with your computer blue screened - assuming it is a windows machine). PM your email address and I'll give you mine to email over the dump file.


Hello,

2 doc Jones these are mine setup configurations i send jou an PM.
Intel Core i7 920 - Motu HD192 - Uad2Quad - Powercore mkII
Windows XP 32 SP3 - Steinberg Cubase 5.01 - Midex 8


But anyone experienced with goeing back to 3.03,
when i load Virus control the display on the virus keeps saying "Update mode 3.04"
that looks strange to me becouse i already installed 3.03 (multiple times).

Thanks

[HUEY]

but when it is updating the virus the screen on the virus says Update mode 3.04

so it looks like there is still some 3.04 in the virus, is there an special procedure for going back to 3.03.

at this moment i would be very happy with the situation it was before.

anyone experience with downgrading the OS ??

Regards

Werner


My procedure for downgrading the OS: (It always worked for me)
*Do a good de-installation of all software and drivers (Via installed software in Windows)
*Force the Virus Ti in update mode (Holding down the exit button while powering up)
*Run the "older" software-installer, in this case 3.0.3
*After downgrading reset your virus!! Remove the power cabel for 30 sec. Hold down the "ARP-edit" button a few secconds while powering up

That's it

Hopefully it works for you

best r

[h4nc0]

Hello,

2 doc Jones these are mine setup configurations i send jou an PM.
Intel Core i7 920 - Motu HD192 - Uad2Quad - Powercore mkII
Windows XP 32 SP3 - Steinberg Cubase 5.01 - Midex 8


But anyone experienced with goeing back to 3.03,
when i load Virus control the display on the virus keeps saying "Update mode 3.04"
that looks strange to me becouse i already installed 3.03 (multiple times).

Thanks


There's Virus Control.dll in C:\Program Files\Access Music\Virus TI\Common which stays at 3.0.4 even if you install 3.0.3. Just delete the whole folder and reinstall.

[Chicago]

werner , 100's of people have ahd these issues, its a virus ti and thats what they do , honestly i give up on mine , its a substandard faulty synth which access know has design issues , hardware problems and bad build quality .

Now you are just talking absolute nonsense, gnome.

1. You have no idea how many people are having issues and how many are not, you pulled this number out of thin air.

2. There is nothing "substandard" about any Virus. Period. If you think the build quality is "bad", I am assuming you are new to the synth game, and again, are pulling this out of thin air.

3. Since you are in absolutely no position to comment on "hardware problems" or "design issues", this is potentially slanderous as you are making this up.

4. Could there be some bugs with 3.0.4? Sure, and Access will fix them surely. But looking at some of your statements, it looks to me like you did not even open the user manual, and have a very limited understanding of how the Virus works.

Sorry man, someone had to check you. Your post does not speak for all of us at all. I have done many projects with the TI, and the TI was a vital part of each.

[soulidstate]

Is acid even a supported host?

I used Acid 6 to launch the VC where I can edit programs,etc. As I have mentioned in my post, I didn't have any problem doing this using earlier OS versions.

[Warren_UK]

When are we going to get a new beta release? Its been ages since the last one.

[h4nc0]

Been testing Win 7 and confirmed slow GUI response with Live 8.0.5b7. Could this be Aero related? On XP, GUI response was normal.

[Timo]

Been testing Win 7 and confirmed slow GUI response with Live 8.0.5b7. Could this be Aero related? On XP, GUI response was normal.

I don't think Win7 is supported yet. That said, Win7 uses Vista drivers, so whatever works on Vista should with Win7.

Are your GPU drivers fully supported/updated with Win7? I know nVidia already supply Win7 certified (fully native) GPU drivers for their graphics cards.

[h4nc0]

I don't think Win7 is supported yet. That said, Win7 uses Vista drivers, so whatever works on Vista should with Win7.

Are your GPU drivers fully supported/updated with Win7? I know nVidia already supply Win7 certified (fully native) GPU drivers for their graphics cards.


Yes. Updated with latest Nvidia driver. GUI slowdown issue only occurs when Virus Control is showing on screen. Other plugins work fine.

[Doc Jones]

Been testing Win 7 and confirmed slow GUI response with Live 8.0.5b7. Could this be Aero related? On XP, GUI response was normal.
I can confirm this. Same issue here, even when running live in compatibility mode.

[drakeblood]

moving from 3.0.3 to 3.0.4 got the following issues in my lovely unsupported Reaper3.x

1) ALWAYS: making an automation on a midiCC (modwhell in my case) gets the VC "out of sync error" and the virus in frenzy with audio instantly slowing down until burst+crash (the crash happens after 2-3 minutes of having it running in that "slowmode" condition). Disabling the automation all goes back working (after stop/play, of course).
2) sometimes (quite often, 60% chances): after you load the VC it will tell you that it's connected to the Virus but it isnt. The Virus stay in Single/Standalone mode (perfectly working, but cant control it by the VC in this condition). After this issue only hard-reset would allow me to reconnect VC to the Virus.
3) sometimes, while playing, all leds goes dead for half-second but there is no VC disconnection or any other counterside (not even audio clicks). This never happened to me with 3.0.3

For reference about the 1st issue, the exact same project was the one making the virus crash with the burst. The fact is that the chances to crash for each play was moderate, like 10-20% chances. With 3.0.4 instead the issue of slowdown+burst+crash happens ALWAYS.

1st note: yes, i did hard reset after 3.0.4 install.
2nd note: no, dont spam me about "your host is not supported, you must die on the stake", i know is not supported but i'm happy like that because 3.0.3 works WAY better on Reaper than on Cubase.

Cheers everyone ^^

[zeno]

I can confirm this. Same issue here, even when running live in compatibility mode.

I have this same problem in WIN 7 and VISTA. I'm using XP now and it's all fine.

I'm using a ATI Raedon 2600 card. Drivers fully updated.

[Cantankerous]

Hi Marc. Have you guys over at Access been able to confirm or replicate any of these crashes that are still occurring despite the recent beta update? Do you possibly have any news on when a new firmware may be out to test? I for one cannot even get Cubase 4 to load if I install 3.4.0. It just crashes to desktop each and every time. Going back to 3.3.0 I have no problems, though the unit obviously still crashes. This morning was a weird one. My transpose LEDs wouldn't work at all despite the buttons being pressed, the BPM led totally went out and I only had a few other LEDs randomly blinking on and off in sync with each other. The unit was definitely not behaving as should.

[marc]

Hi Marc. Have you guys over at Access been able to confirm or replicate any of these crashes that are still occurring despite the recent beta update? Do you possibly have any news on when a new firmware may be out to test? I for one cannot even get Cubase 4 to load if I install 3.4.0. It just crashes to desktop each and every time. Going back to 3.3.0 I have no problems, though the unit obviously still crashes. This morning was a weird one. My transpose LEDs wouldn't work at all despite the buttons being pressed, the BPM led totally went out and I only had a few other LEDs randomly blinking on and off in sync with each other. The unit was definitely not behaving as should.

we should have a new version by monday. "should" as in if no problem comes up. it's holiday season here which makes it more complicated to release an update.

i'm not sure about the problems you describe though. in fact, crashes aside, to my knowledge we didn't get reports about problems with cubase 4 and the transpose LEDs.

best, marc

best, marc

[Cantankerous]

Thanks for the reply Marc. Going back to 3.03 has fixed the above mentioned problem. I will try the new update (hopefully Monday) and see how that fares.