Saturday, April 19th 2014, 9:26am UTC+2

You are not logged in.

  • Login

AtonyB

Professional

Posts: 729

Location: UK

  • Send private message

11

Monday, August 24th 2009, 2:56am

it would all be solved very simply with a softsynth version of the virus...

the bandwith restrictions are a result of a poor design decision imho..

USB 2.0 was a well established standard at the time of release .


Believe me, there is NOTHING 'universal' about USB 2.0 - for the sake of stability, and the ability to be more than 50cm away from your PC, USB 1 was a good decision...

12

Monday, August 24th 2009, 11:33am

This is the whole reason why I use a midi controller to record midi automation instead of using automation lanes.
This way it's much easier to rearrange automation and sort it in cubase.
I use a BCR2000 with alot of knobs. I press record and that's it. No selecting parameters and stuff.
The only downside is that not all parameters are availble, then I have to use the matrix.

I wouldn't need the bcr2000 if the virus sends midi in VC mode. I've stated something like this on the infekted forum, but then marc said something like: get over it :(
On the upside: the knobs on the ti won't wear cause i don't touch them..

13

Monday, August 24th 2009, 12:43pm

I wouldn't need the bcr2000 if the virus sends midi in VC mode. I've stated something like this on the infekted forum, but then marc said something like: get over it :(
did i say that? you could use the remote mode for starters. choose the Virus A-B-C template and voila, you're sending CCs ...

hth, marc
The official Virus TI facebook page: http://www.facebook.com/accessvirus

14

Monday, August 24th 2009, 2:47pm

Ah, didn't know that. Why didn't you say so before?
I'm sure you said get over it when I asked for this feature.. it must have been 2 or more years ago i believe
Thanks anyway.

out2lunch

Beginner

  • "out2lunch" has been banned
  • "out2lunch" started this thread

Posts: 16

Location: Topanga, CA

  • Send private message

15

Tuesday, August 25th 2009, 1:19am

you wont get all the automatable paramaters with midi cc, they will all be unnamed,
and you will also have to use sysex dumps on tracks to pull up patches... not a very good solution marc.

out2lunch

Beginner

  • "out2lunch" has been banned
  • "out2lunch" started this thread

Posts: 16

Location: Topanga, CA

  • Send private message

16

Tuesday, August 25th 2009, 1:23am

AtonyB Wrote:

Believe me, there is NOTHING 'universal' about USB 2.0 - for the sake of stability, and the ability to be more than 50cm away from your PC, USB 1 was a good decision..."

---
?(


I do 15 foot usb2 runs all of the time...

AtonyB

Professional

Posts: 729

Location: UK

  • Send private message

17

Tuesday, August 25th 2009, 1:27am

Indeed, for a successfully engineered product these feats are possible - but, depending on the product, it can take time to get there (also, this IS somewhat of an 'old fashioned' problem...)

ray

Unregistered

18

Wednesday, December 2nd 2009, 9:42am

Just wondering..?

Why not have Firewire in the acess virus ti..? would that help and would that be some thing access might look into in the near future..?

Cutters

Beginner

  • "Cutters" has been banned

Posts: 9

Location: Tasmania, Australia

  • Send private message

19

Tuesday, December 8th 2009, 12:52am

How about a MIDI to MIDI plugin that sends only Note, CC & Sysex parameters to the Master Virus TI plugin, I think that would solve a lot of problems people are having with automation, and surely that's possible. It would certainly streamline production not having to look up through my list of CC's etc.

20

Sunday, October 30th 2011, 7:38pm

"it would be impossible with the current bandwidth restrictions"

well then:
- support as many channels as possible (looking at other usb hardware at least 8 stereo channels shall be possible) - AND: Why not support 2 usb connections?
- let one plugin instance switch between following options:
-> output to vst plugin output
-> output to global, shared channel which appears as audio interface in the daw
- keep supporting more than 1 patch per plugin instance

come on, keep thinking... this concept is weird and so hard to use... i think i will not use it at all but route analog audio output back through an audio interface in the daw. i hope there is an acceptable solution for midi automation - however - having all automation in one track is not acceptable for me. i mean - look at this click-actions you will need to move a clip to some other song position by discretely keeping the automation... this is no fun!

At AtonyB: "for a engineered product all these features are not possible" Please do not use such "kill-them-all" statements. There are lots of features that can be done via a software update to improve this concept.

This post has been edited 5 times, last edit by "CharlyBeck" (Oct 30th 2011, 7:54pm)