I'm still having DSP-Crashes with 1.09, what about you?

[Tiphares]

I have the newest TIOS 1.09 installed on my TI, and yesterday, my first DSP-Crash happened. I'm half deaf and scarried to dead, everytime i use my TI :wink:
I asked the access support and they told me that this dsp-crash problem shouldn't happen anymore on the 1.09. Now what about you, is your TI working without crashes?

Thanks for answers!

[MADSTATION]

It's been a few weeks since I had any crashes.

[Doc Jones]

Tiphares, can you explain a little bit more about the crash you had - ie what was the message, what did you have open and running on the TI etc. I have never had a crash on my TI since I got it in November so am very curious about this.

[Tiphares]

Well, i was playing around with some multis i created, the virus was connected through usb-midi (TI-Synth), the analogue outs of the virus were connected to my Firewire-Audiointerface.
While i was pressing the Multi-Edit-Button (Shift+Edit) (I was playing a few chords i think), it sounded like the sound turned into a thousend clicks and then into an init-like buzzer noise, but just at the highest level of volume! This was a matter of about half a second... At this moment, the virus froze, i couldn't even lower the master volume. But nothing like a error message was on the screen. I've pulled the plug - since then, nothing strange occured to me, but I'm rather afraid...

[diy]

After 1.0.9 with 1.1 beta 3 firmware I've started to have blank screens again.
And today as I was using the TI as an effect unit, suddenly a short dsp crash noise was heard and then.. the plug and arp edit reset as usual...

[Doc Jones]

interesting. so when you guys get the dsp crash, hitting the panic buttons does nothing for you? you actually have to pull the power plug so that the TI resets itself?

[Tiphares]

i've pressed the panic button, but with no success. but i've tried nothing else - i must admit, the sound was to painful... :x so i've pulled the power plug...

[Doc Jones]

understandable - you've got to protect those monitors (and ears!!). I am going to see if I can replicate the multi-edit crash later on tonight.

[Darjeeling]

I can confirm I have a lot of DSP crashes with my Virus TI KB with OS 1.0.9 too :cry:

All kinds of buzz, feedbacks, hanging notes, noises, clicks, pops, freezes, appearing randomly, just by changing the presets and tweaking in Single Mode...

...to the point the unit is barely unusable. Can anyone confirm having that kind of problem in Single Mode too ? If not, I really wonder if one of the chips is not defective...is it possible ? Any help would be welcome...

[diy]

My virus doesn't crash frequently(???!!!) but when it does it's kinda scary and it makes me wonder: Are there any users who run their viruses without any problems and if they exist, do we have bought a faulty unit? Access should really consider about that beacuse my local distributor told me that the first shipment was returned back to access beacuse it was faulty. I don't know if it was a good excuse for the shiping delay here in Greece (one month) or it was true.

[Tiphares]

diy, i think, that's an interesting point. Mi ti is one of the first units sold here in switzerland in october 05. So maybe there are different versions of the TI, because of the production dates...

[Doc Jones]

just an update - have yet to experience a dsp crash using both single and multi modes. For the test, I played a few chords repeatedly while changing many parameters (including selecting new sounds)

[Tiphares]

That's interesting, this is obviously a bug of the TIOS. Maybe we should report that to Access, so they can fix it til the next 1.1 update...

[Smag]

Hey,

I bought a Ti desktop and it wouldn't even switch on properly so I changed it for another from the shop and it's been pretty much flawless running 1.08.

The only problem I could detect was the crackling on odd parts in Multimode and that could be worked around.

I installed 1.09 last night so I'll see how it goes - if I have problems I'll roll it back to 1.08.

[marc]

My virus doesn't crash frequently(???!!!) but when it does it's kinda scary and it makes me wonder: Are there any users who run their viruses without any problems and if they exist, do we have bought a faulty unit? Access should really consider about that beacuse my local distributor told me that the first shipment was returned back to access beacuse it was faulty. I don't know if it was a good excuse for the shiping delay here in Greece (one month) or it was true.

the initial shipment does not differ from the rest. there was no recall of units or a shipment which was returned because it didn't work.

if your virus does suffer from constant crashes it appears to be likely that you have a hardware problem. your virus should be serviced. i am aware of the fact that the first revisions of the virus ti operating system did crash but i'm also fairly certain that newer versions are stable. i have a virus ti running here all day, testing things and i honestly can say that it doesn't crash.

best, marc
access music

[diy]

Thanks mark, the crashes and the blank screens are occasional but I hear sometimes dsp crash buzzes especially when I use the TI inputs in seq mode. Do you think it's a 1.1 beta 3 issue? I'd like to give 1.1 a try and if the problem still exists I'll contact my distributor.

[marc]

Thanks mark, I'd like to give 1.1 a try and if the problem still exists I'll contact my distributor.

contact your distributor. what you discover is very different to what we discover here. alternatively contact me privately and explain to me in which way your virus crashs and how i can reproduce it.

best, marc

[diy]

Well, today I've made up my mind, went to the access site and dnloaded official 1.0.9. As I was running 1.1 beta 3 TIOS, now 1.0.9 seems much more
stable even with usb. I've made a test project in sx3 with 4 parts running flawless in virus control most of the time. Realtime export is pretty accurate and the only problem was very occasional missing notes, arp drifting but resyncing asap and with some patches hanging notes, but these problems seem common and not compared with the 1.1 beta mess. No more buzzes,crashes even with the heaviest knob tweaking and at least I have freed up a midi interface on my soundcard. Well done access, my little monster now is ready for tweak n joy after a 4h test everything seems almost fine and I pray for the next update to be 100% problem-free. At least I'm :D now!!

[Jachin]

Hi folks

i dont own the Ti but nearly ! i cant believe what i am reading here . . . ive been told even using just midi cables and audio cables in multi mode the virus ti freaks at times and nearly blows your speakers ?(occasionally it seems but then isnt once every year to much ! you dont spend ?1299 to have this bollocks do you even once ?)

Whats access take on this ? I have emailed then as i want to buy one but i am not buying a synth that locks and spews out noise at high levels :)

cheers

jachin

[mulder]

The unbearably loud, monitor-killing sound has been dubbed "Satan's Saw" on the Amphea Virus mailing list. There's an entire thread there on it. Unfortunately, it's very common even on 1.0.9 and with or without VC.

I was a loyal Virus Kb owner, and I am now a very discouraged (now becoming angry) TI owner. Basically, no one should consider buying this synth yet; it's just not ready for real use. Perhaps 1.1 will change this, but I am not optimistic at this point -- along with most of the Virus community from what I can tell. 1.1 is late, but then that was a promise for the NAMM trade show (possibly made by the same marketing folks that announced the Virus almost year before it even shipped).

I expect that there will be a large number of owners that that will begin demanding to return their units for a refund if things don't improve drastically with another two months or so. It's probably the end of Access as a company if they don't pull it together before the summer.

[mw7]

It's probably the end of Access as a company if they don't pull it together before the summer.

Maybe it's time for one of the big Japanese companies to buy Access, or at least some of their technologies and perhaps hire some of their people. Although I am unaware of them doing anything similar, I imagine Yamaha could fix/finish the TI and bring some quality control to the equation. The TI is a great idea and certainly sounds better (to me) than any Japanese synth I've played lately.

It just appears as though Access bit off more than they could chew with the TI. Heck, a 16-part multitimbral synth with dedicated effects hasn't been done, even without the whole VC angle. These are really smart people to have gotten as far as they have with this project - it'll be interesting to whether or not they can finish it.

A TI that worked as advertised would completely blow the doors off of everything else on the market. I wish them well.

[juno_nuno]

A TI that worked as advertised would completely blow the doors off of everything else on the market. I wish them well.


Those were my initial thoughts!!Now its another different thing.I hope that they solve this,im not a pessimist,but access atitude,leaves me thinking its a terrible problem!!They should tell us anything ...Even some recognized forum senators disapeared misteriously !!!

[mw7]

A TI that worked as advertised would completely blow the doors off of everything else on the market. I wish them well.


Those were my initial thoughts!!Now its another different thing.I hope that they solve this,im not a pessimist,but access atitude,leaves me thinking its a terrible problem!!They should tell us anything ...Even some recognized forum senators disapeared misteriously !!!

There's probably no point in making themselves available to handle questions they don't have answers for. I work for a technology company in management/marketing, and often we are completely at the mercy of the product development and programming staff.

Everyone wants to know when 1.1 is going to be ready, along with guarantees of bug fixes and increased functionality. The future of Access is likely closely tied to how effectively they deal with these challenges. If I was the CEO, I wouldn't want my people talking about anything on internet chat boards.

[juno_nuno]

[f I was the CEO, I wouldn't want my people talking about anything on internet chat boards.


Dont you know ??? the CEO runned away with a Indian Goddess after shooting product main engineer...

Check it out :lol:



http://www.grapheine.com/bombaytv/play_uk.php?id=885191</td>

[technomonster]

[quote=mulder]Heck, a 16-part multitimbral synth with dedicated effects hasn't been done, even without the whole VC angle. These are really smart people to have gotten as far as they have with this project - it'll be interesting to whether or not they can finish it.

A TI that worked as advertised would completely blow the doors off of everything else on the market. I wish them well.

thats for sure.
i wish i could help them out, with technical insights but i know nothing.
i would be there in a second and offer free advice.

i have heard the virus ti in the shop and boy does it sound cool.
i havent bought it because of the problems and i am pretty dum with synth technology.

[dr. orange]

I just had my first VTI crash and experienced that noise or saw or whatever, and it was no way as loud as ppl are telling...

from time to time, it won't start up, hanging notes, arp glitches, the usual stuff...

[snow]

I've had three of these crashes this week. Can't think of anything i've been doing differently (except using the virus as the sound card.) The volume of the noise was deafening.
I'm switching the drivers back to the "built in audio" running the audio out the computer again, and hoping that willl prevent this from happening again.

[TOTAL]

Starting to understand what causes crashes and shit saw in my TI.

Fast program changes when playback is on.

Now I remember the same thing happened with Roland MC-909. It was actually the only way to hang up the machine (but mc suffered quietly).

I think it is due to a specific hardware behavior: unlike with soft synths when u change program whatever previous sounds keep playing they maintain their previous characteristics.

The machine simply gets jammed.

If it weren't this crazy sound I would accept this weakness and simply try to remember not to change progs too quickly.

I suggest that we write to Access to request such an improvement/ear and equipment protection: when the DSPs get jammed the sound is cut off.