God, I hate my TI

[Boyler]

I have so much trouble with this damn thing that it's practically useless. I've had it since it came out and I haven't been able to use it in one f*cking production. Hanging notes, nowhere close to proper arp sync regardless of workarounds, drifting delay in terms of both tempo and pitch, sudden huge delay on all MIDI data, different timing on instruments when using more than one, turning value 1 through value 3 knobs beneath the Polar's display do not write automation, complete silence requiring TI Control to be re-opened which means loosing settings unless previously saved... It goes on. I won't list all the problems I have with it, but I'm not exaggerating when I say I have all problems mentioned in these forums and then some. No OS updates have come close to solving *any* of these symptoms for me. Stuff like the sync problem just... Changed. Access made a reasonable attempt to help me in the beginning. I followed their advice and continued to send them overly detailed descriptions of my problems to be as helpful as possible, but they eventually gave up on me. I think they just assumed a new OS would solve my problems, but this is a couple of months ago now.

Yeah, sure, I could use it as a regular synth with MIDI, but I sold my friggin' Virus C Kb *for* the bloody TI technology!

I'm going to wait for one more OS update, and if that doesn't solve most problems, I'm selling the TI and never taking a second look at Access products out of sheer, frustration and anger.

At this point I would rather have an Andromeda A6 or RADIAS.

[Threlly]

Your not trying to use it with Nuendo are you ?

[dr. orange]

Hi Boyler,
I can feel your frustration. Although access would disclaim this, I'd say that the first batch of viri have many hardware bugs. If you have that much problams, why don't you return it and take one of the newer editions? I got one and I do have problems, but they aren't that numberous as yours...

good luck and (hopefully anytime soon) have fun with your virus ;-)

[Drammy]

As Threlly says though you can never be sure if you're running an unsupported sequencer!

Nuendo is unsupported.

[nutekk]

its funny...
nuendo wasnt always unsupported.
i had "chats" with the access team in early november about some problems i was having and they new i was using nuendo...they didnt
say hey nuendo is unsupported.
this came out later.

in fact i bet some discussions with TK on this forum even show this.
saying its not supported is an easy way of getting rid of a problem.
Nuendo is SX ...the core is the same.
my ti has the same problems with nuendo as it does with sx.

[dr. orange]

There ARE changes between several VTI batches! Obviously the blue colour on the panel of VTI Desktop and Keyboard isn't the same. I got a version of the newest batch, and the blue isn't as shiny anymore as it used to be in the older versions, and I am sure that there are changes on the hardware side as well. I don't experience much of the bugs people seem to have still with OS 1.09. There are some minor bugs, but nothing to prevent me from working...

[Mister Orange]

I have one of the very first TIs to hit the UK, and don't experience anywhere near the scale of problems other people have been reporting.

Mr O

[Guzzy]

I have one of the very first TIs to hit the UK, and don't experience anywhere near the scale of problems other people have been reporting.

Mr O

It's because You don't find the power switch?, no Power= no Problems :lol:

[The girl next door]

I have one of the very first TIs to hit the UK, and don't experience anywhere near the scale of problems other people have been reporting.

Mr O

It's because You don't find the power switch?, no Power= no Problems :lol:
WATCH OUT Comedian from Norway on the Loose :wink:

[Guzzy]

WATCH OUT Comedian from Norway on the Loose :wink:

:mrgreen: ...well I tried ...and failed :roll:

But this one is funny: ROM-Q 31

[dr. orange]

WATCH OUT Comedian from Norway on the Loose :wink:

:mrgreen: ...well I tried ...and failed :roll:

But this one is funny: ROM-Q 31
wanted to turn on my TI to have a quick listening on this patch and got a blue screen :roll: the fifth or sixth in two days :x

[Elektrobolt]

I have one of the very first TIs to hit the UK, and don't experience anywhere near the scale of problems other people have been reporting.

Mr O

Same here, only in the U.S.

[Tarekith]

I know I have one of the very first TI's, barely any issues here. It is NOT a hardware issue. Like anything, there may be a couple of odd defects in certain units, but there is no issues between manufacturing runs.

If you are convinced you have a hardware problem, Access woul sort you out right away.

FWIW, there was a recent discussion on the Nuendo forums where users are starting to see that Nuendo is not as close to SX as previously thought. I beleive the thread title was something like "how to achieve proper midi timing" or some such. Might want to take a look at that.

[Khazul]

Hi Boyler,
I'd say that the first batch of viri have many hardware bugs.

Like Tarekith, I also have what I think was one of the first batch sent to buyers rather than pre-launch testers (received mine Oct 3rd last year).

I seem to suffer less frequent problems than many are posting, though I've seen just about every issue at some time or other, not to the extent that it stops me from using it productively most of the time - and thats with or without VC, and syncd from all sort of different devices.
Quality of the sync source does seem to be the one variable that corresponds to have realiable the TI is on any given day. Most of the time its OK with a good sync source.

[dr. orange]

Khazul, if you mean Midy sync, I absolutely agree with you! Sync it to an external device ot itself and the arp issues are gone. however this way, it's quite complicated to have a project with varying tempo...

I don't think a stable sync via USB1.1 is possible, it's the nature of USB1.1 to have unpredictable dropouts and varying latency... how should the hardware know whether there's more latency or a change in tempo? IMHO that's the problem...

They have chosen USB1.1 in order to save money, now, it's a bottomless pit

[Khazul]

Khazul, if you mean Midy sync, I absolutely agree with you! Sync it to an external device ot itself and the arp issues are gone. however this way, it's quite complicated to have a project with varying tempo...

I don't think a stable sync via USB1.1 is possible, it's the nature of USB1.1 to have unpredictable dropouts and varying latency... how should the hardware know whether there's more latency or a change in tempo? IMHO that's the problem...

They have chosen USB1.1 in order to save money, now, it's a bottomless pit

I dont beleive it was specifically to save money. The audio industry is awash with companies who got into trouble at first attempt at writing USB audio drivers and failing miserably. I *beleive* that Access actually bought a known working driver and chip set from another company, and hence the choice of USB1.1. For USB2 they probably would have had to go it alone - which is very high risk and most companies fail miserably on first attempt not realising how hard it is to get a good driver for PC and MAc written first time around.

My personal opinion of the TI->VC audio channel is that its probably one of the most relaible USB audio implementations I have ever come across, allthough I think the latency is unreasonably high (maybe that was the other price of reliability).

From the above you can guess I have absolutely zero problems with the USB driver (as separate from VC). Not helpful tto you I know - I beleive you had a few BSDs? I cant speak for the ASIO implementation as I have never used it as I use a multi-channel firewire audio interface instead.

BTW - Its well worth having a good look around the kind of stuff you have running on your PC - I have had alot of problems in the past with audio caused by the most unlikely applications - especially sys tray apps.

If in doubt - dont let anything none essential apps that didnt ship with the OS (Mac or PC) auto-start. Most stuff that ships with the OS tends to be well behaved. Alot of other stuff isnt. I know especially of a number of people who have had serious audio problems with printer utilities in the sys tray on WinXP (why printer apps ffs??).

On sync - I mean sync either via hardwrae MIDI, or from the DAW application via VC. People with high quality audio cards and sync sources seem to fair better. Where the audio card comes in is that many applications use the audio clock as their reference souce for generating all application audio and midi timing (instead of using system clocks for midi timing). If you are getting the odd audio pop, then something is getting in the way of audio processing - that will also impact midi clock (depending on the App), and so I belive destabilise the TI.

Thats not saying their isnt a problem in the TI clock thats causing it to crash - I think their is - but with this chain of events, I can so easily see how the TI coulod get through internal testing and use by a bunch of beta testers prior to launch in high end studio and never or very rarely hit the issues users are seeing now.

[i3]

I also recieved one at launch. I do have some of the same problems but not all. taking into consideration that there is a buttload of different audio cards and drivers out there. some drivers work better than others. as in productivity all is well. nothing I cant find a work around for. some bugs are more irratating then others.

1. hangin notes. this one is a new one for me so access must be doing some work on the OS's cuz I didnt have this problem in 1.07 and earlier (I fix this by reseting the audio card in device/device setup/VST Audiobay/reset). It seems this bug only occurs with a moderate amount of filter envelope time/slope and release on some patches. not all patches have this problem.

2. arp is always out of sync. I usually work around by making arps manual. ya its a bit more work but eh.

3. delay timing is also a big issue with me and if the delay on the virus if set over 50% it starts to lose sync.

also in 1.09 my leds intermitantly blink on occasion. :lol:

kinda ironic for access though. catch 22 on their hands. the public gets mad if not released on time but when released buggy, the public bitches about non working synth. me I could say I float in both those boats. well people you asked for it and we got it. I know I am grateful to use a great synth and a good idea in the making. you know how long ive been waiting for digital export from hardware via sequencer and that works like a vsti? to long. I only use the virus TI and the occasional jp 8080 in my production and successfully exported material. cmon 1.1!

[Tarekith]

Khazul, probably done this already, but you did change the TI's driver latency to a lower value right? The default latency of the TI driver IS VERY HIGH, but once you set it to a lower value in SX's Device settings, it shoudl be fine. I can run mine at like 12ms or less with no issues. Seems to work better at lower latencies actually.

We can discuss over a Steak if you want....

[Khazul]

Yeh - sounds cool - Ill jump on a plane :)

[The girl next door]

Yeh - sounds cool - Ill jump on a plane :)
Easyjet don't go to Chicago :lol:

[Tarekith]

Nah, there's steak houses elsewhere we could visit. :)

[aisling]

[quote=dr. orange]

I *beleive* that Access actually bought a known working driver and chip set from another company, and hence the choice of USB1.1. For USB2 they probably would have had to go it alone - which is very high risk and most companies fail miserably on first attempt not realising how hard it is to get a good driver for PC and MAc written first time around.



The motu 828 is running usb 2. Access and motu are supposedly "friendly"......usb 2/firewire just makes more sense for a $2,000
item......If it were a $399.00 item well yes usb1.....(i'm not whinning 8))

[Khazul]

Right - secured the company concord for the evening - cu in a few hours :)

[Smag]

Nah, there's steak houses elsewhere we could visit. :)

If you want a steak in the UK then Wimpey burger bars have to be no1 on your list :wink:

[The girl next door]

Nah, there's steak houses elsewhere we could visit. :)

Wimpey burger bars have to be no1 on your list :wink: 8O
Yeah,And Northerners like gravy on there chips 8O
Whippet,Flat cap and outdoor shithouse :lol: :wink:
Should rename this Thread "God i hate my outdoor bog" :lol:
Anyway Eastenders is alot better than Emmerdale cause we've been getting some Girly lessie shots lately :lol:

[Khazul]

Yeah,And Northerners like gravy on there chips 8O


Nah - curry sauce on mine plz :)

[digitalgeist]

Hi Boyler,
I can feel your frustration. Although access would disclaim this, I'd say that the first batch of viri have many hardware bugs. If you have that much problams, why don't you return it and take one of the newer editions?

OK, so you buy the TI at the store, which gives you a 30 day return policy.

You wait 5+ months for Access to update the fucking OS to something resembling a SYNTH THEY ADVERTISED WOULD WORK.

Have you ever tried to return an instrument to a store?

[The girl next door]

OK, so you buy the TI at the store, which gives you a 30 day return policy.


2 years here in Germany.....its a new thing to support consumers

[digitalgeist]

OK, so you buy the TI at the store, which gives you a 30 day return policy.


2 years here in Germany.....its a new thing to support consumers

Awesome, well let me just hop into my jumbo jet/time machine here....

http://lego.bldesign.org/pics/delorean/thumbs/main.jpg

[dr. orange]

OK, so you buy the TI at the store, which gives you a 30 day return policy.


2 years here in Germany.....its a new thing to support consumers
nah, TGND, that's not the same. 1 month return policy, 2-3 years warranty

[The girl next door]

OK, so you buy the TI at the store, which gives you a 30 day return policy.


2 years here in Germany.....its a new thing to support consumers
nah, TGND, that's not the same. 1 month return policy, 2-3 years warranty
Looks like were both wrong 6 months return policy, 2-3 years warranty
But even if you can prove it is not working properly within 2 years of Purchase you can still return your Ti for a full refund..

III. Keine Verj?hrung der Gew?hrleistung
Verj?hrung hat zur Konsequenz, dass die betreffenden Anspr?che - hier die Gew?hrleistungsanspr?che - gerichtlich nicht mehr durchsetzbar sind.
Die regelm??ige Verj?hrungsfrist f?r Gew?hrleistungsanspr?che betr?gt 2 Jahre (? 438 Abs. 1 Nr.3 BGB), sie betrifft den Kauf beweglicher Sachen. Hat der Verk?ufer den Mangel arglistig verschwiegen, gilt gem. ? 438 Abs.3 BGB die regelm??ige Verj?hrungsfrist des ? 195 BGB von 3 Jahren.
Die Verj?hrung beginnt mit der Ablieferung der Sache.
Der Begriff "Ablieferung" wird von der Rechtsprechung so ausgelegt, dass dem K?ufer die Kaufsache ?berlassen wird, so dass er die M?glichkeit hat, sie zu untersuchen und ggf. bestehende M?ngel festzustellen.
Bei der vereinbarten Anlieferung durch den Verk?ufer ist diese Voraussetzung daher gegeben, wenn die Kaufsache dem K?ufer an seinem Wohnsitz ausgeh?ndigt oder (bei Montagevereinbarung) bei ihm aufgestellt worden ist. Holt der K?ufer die Sache selbst ab, dann l?uft die Frist mit der Aush?ndigung an den K?ufer am Verkaufsort (z.B. dem Lager des Verk?ufers).
Die Verj?hrungsfrist muss im Zusammenhang mit der rechtlichen Konstruktion der Gew?hrleistung gesehen werden. Die Gew?hrleistungsregelung geht davon aus, dass der Mangel bereits bei der ?bergabe vorhanden ist (vgl. auch ? 434 Abs.1 BGB). Grundgedanke der Gew?hrleistung ist also nicht, dass der Verk?ufer f?r einen bestimmten Zeitraum f?r die Funktionst?chtigkeit der Sache haftet, sondern, dass er f?r einen bei der ?bergabe an den K?ufer vorhandenen Mangel einsteht.
Hierin liegt auch der Unterschied zwischen Gew?hrleistung und Garantie. Bei der (zus?tzlichen) Garantie sichert der Verk?ufer und/oder Hersteller zu, dass die gekaufte Sache f?r einen bestimmten Zeitraum und bei normalem Gebrauch funktionst?chtig ist und verspricht im Falle des Versagens bestimmte Leistungen zu erbringen, die die Funktionst?chtigkeit der Sache wieder herstellen.
Wegen dieser Besonderheit der Gew?hrleistung sollte der K?ufer die M?ngelfreiheit der Ware bei der Ablieferung pr?fen, um M?ngel zu erkennen. Allerdings erleichtert der Gesetzgeber dem K?ufer beim Verbrauchsg?terkauf (s.oben) den Nachweis, dass der Mangel schon beim ?bergang der Sache auf den K?ufer vorhanden war ganz erheblich.
Gem. ? 476 BGB gilt f?r Verbrauchsg?terk?ufe n?mlich eine sog. Beweislastumkehr. Tritt der Mangel innerhalb von 6 Monaten nach dem Gefahr?bergang (in der Regel der ?bergabe der Sache an den K?ufer) auf, so wird vermutet, dass die Sache von vornherein mangelhaft war. Der K?ufer braucht dann nicht die Mangelhaftigkeit zum Zeitpunkt der ?bergabe beweisen, sondern der Verk?ufer muss - will er den Gew?hrleistungsanspruch abwehren - seinerseits die Mangelfreiheit bei ?bergabe beweisen. Diese kann sich aus der Art der Sache aber auch aus der Art des Mangels (etwa beim Kauf von Tieren, die sp?ter erkranken) ergeben.
Jedoch gilt dies gilt nur f?r Verbrauchsg?terk?ufe , nicht also z.B. f?r Verk?ufe unter Privatleuten und auch nur f?r die ersten 6 Monate nach ?bergabe an den K?ufer, danach tr?gt der K?ufer die Beweislast. Daher ist es wichtig, m?glichst schnell die gekaufte Sache auf M?ngel zu untersuchen.
Macht der K?ufer Gew?hrleistungsanspr?che gerichtlich geltend, ist der Lauf der Verj?hrung gehemmt, die Frist l?uft also (zun?chst) nicht weiter. Gleiches gilt f?r den Zeitraum, in dem zwischen K?ufer und Verk?ufer ?ber die Anerkennung des Anspruchs verhandelt wird, und zwar so lange, bis eine Partei die Fortsetzung der Verhandlungen verweigert (vgl. ?? 203,204,209

[TOTAL]

I wonder what it means "prove".

Isn't it so that what they are obliged is either money return or repair or exchange?

They wouldn't refund then.