you can probably fix that by selecting the AU manager in logic and scan both plug-ins again. they work with logic 8.0.2 for a fact. you might want to repair permission before you do that also.
best, marc
you can probably fix that by selecting the AU manager in logic and scan both plug-ins again. they work with logic 8.0.2 for a fact. you might want to repair permission before you do that also.
best, marc
did you check out the remote mode?
marc
i've moved this thread to the trouble shooting section, where it belongs.
mattc, you need to provide more specifics so we can help you.
marc
hopefully next week
best, marc
it is totally down to you which OS you use. i just wanted to point out that there is a good chance that you can make things work without running a OS version which is a year old. there is literally thousands of people using 3.x versions with XP and they don't have connection problems.
best, marc
hi,
2.7.5 was released like a year ago, obviously many things have changed in the last year. but at the same time, the driver has hardly changed and it doesn't seem that many people are suffering from the problem you've described above. are you in contact with access support? i'm pretty sure that they can help you in finding the root of the problem.
best, marc
thanks for letting us know. refx can be contacted here: http://support.refx.com/index.php?_m=tickets&_a=submit
best, marc
AtonyB, what did you change?
best, marc
How to install additional Virus TI patch libraries?
For Windows users:
Drop the MIDI file (*.mid extension) onto the following location and launch Virus Control. The
new bank will be shown in the browser as a part of the user libraries.
Access-Music\Virus TI\Patches in "My Documents" folder
For Mac OSX users:
Drop the MIDI file (*.mid extension) onto the following location and launch Virus Control. The
new bank will be shown in the browser as a part of the user libraries.
/Library/Application Support/Access Music/Virus TI/Patches
best, marc
grobinez,
the dsp code in version 3.0.5 and version 3.1.0 is the same. i doubt very much that it behaves differently.
best, marc
i'm sorry, but this is not a statement a dealer should make. our support is dealing on Virus related topics every day, full time. i doubt that's true for a sales person at a music shop. i'd be totally interested to learn who at DV said that.
i'm sure, we can help you out. understandable that you're annoyed because you want to work with what you've obtained - so let support help you out.
best, marc
are you in touch with access support?
best, marc
we cannot replicate the problem. it would be interesting to know in which version it works and in which version it doesn't. simply opening virus control in different sequencers doesn't do the trick, that's what we tried so far.
your help is appreciated
marc
did you install the software on your PC/Mac? did you try out the tutorial projects?
best, marc
okay great, please post updates here
thanks, marc
that depends on the features used by the individual sounds. in other words, sound where were made with the virus TI are likely to make use of e.g. the additional oscillator models etc. those sounds will not sound remotely the same on a virus c type product.
best, marc
the VST3 version works like a VST3 instrument but cubase doesn't support side chaining for virtual instruments. you're barking at the wrong tree
marc
can you explain again what you mean? i'm not sure if i can follow you.
best, marc
simonbura,
basically, when the TI's DSP crash, it might not receive MIDI well, produce stuck notes and play only on odd or even parts. but pretty much everything in this list can also be a USB data transmission problem. therefore it's pretty hard to help unless we get more info.
obviously the TI should never crash. from 3.0 - 3.0.3 there were bugs which made it crash. those bugs should be ironed out, at least, we cannot make it crash here under normal circumstances. if your TI crashes frequently, even when you don't even touch it or you just play in single mode, i'd say there is a good chance that we're dealing with a hardware problem. if it crashes only when you work with it we need to take a closer look.
simonbura and circuite_damage - are you both using 3.1?
best, marc