Total Integration Discussion
 

Original post by synthman1:

I think Soarer means just a stand alone synth editor and librarian like everyone else does rather than total integration. I for one am behind this as well.

This is just my observation, but the VC is a never ending rat race of constant os releases and an Access resource hog to try and make the virus ti work on every combination of software DAW that comes out for every platform in realtime. While they have done a good job at attempting this, its far from perfect. It was a good idea on paper. It simply doesnt work for everyone and as a consequence the Virus TI OS is still riddled with bugs.

I say drop it. No one else does this and with good reason. I dont have it on my other synths and dont use it on my Virus. For those who do fair enough, you have it working on whatevery you are using. That doenst mean Access is obligated to continue this maddness.

It eats up to much development resources. Just make a stand alone editor and librarian and call it a day. This way Access can get back to adding feature updates regularly rather than always putting out fires evertime a software manufacturer comes out with this years revisions.

While Access keeps tinkering with this bug and that bug other synth makers are adding Flash RAM for sample usage through their signal path.

While Access is at it, maybe they can release an OS version without all the TI nonsense for those who dont need it. One thats lighter and better optimized like good old days freeing resources for more valuable things like more filter options, new osc types and additional envelope generators.


Reply by Marc:

the developer teams for virus control/OS integration and the sound engineers are independent. even if we would stop all this "nonsense" (which brought us a couple of awards, good press and eventually some happy users as well), the development of new synthesis functions wouldn't benefit from it. i can understand your notion for a lighter product but in this case there would be no benefit.


Reply By Synthman1:

The end results appear to be the same as many can attest to per the latest OS release. These issues have been fairly constant for years and will continue as long as TI is supported and modified to incorporate more software compatibility. Why wouldnt it based on past history?

I want me a Virus D!

Its hard enough to develop a rock solid software/hardware hybrid synth with the level of complexity of the Virus let try to make one operate in every possible music software application on the planet and systems via USB network.

This is an important topic and definitely a discussion that should continue elsewhere if not here in this thread.

I'm not sure how this doesnt relate topically to the initial post, but ok, I'll let you get back to your specifics in this tread by request. If anyone would like to comment on anything I've posted about TI, please start a post and I'll be happy to discuss there.



I think its fair to say most including myself, appreciate the effort and time the team puts into the product including total integration. That shouldnt be lost in this discussion. A lot of people do see value in it regardless of how others may view it.

The answer very well may lie in what Marc refers to as "parallel time". Why not release an OS without TI for those dont use it? That way, the people who dont use it wont have to deal with the bugs from these features in the OS that effect the Virus operation regardless.

Following this for years and seeing all the issues, its just hard to believe the Virus wouldnt be far more evolved and different instrument today if there was a simple stand alone editor and Access spent more of their resources on more frequent feature evolution like they used to rather than this nightmare. TI has obviously had to affect this.



Thats why everyone else makes a simple stand alone editor.

At some point TI support may end. If Access decides to retire the TI and come out with something new, you cant expect them to support TI forever on a past model. What if its too cost prohibitive to continue in order to compete with what the rest of the market is doing or to stay afloat? I can only imagine how time consuming and costly it must be to test TI on different systems with all the different DAW applications. Every time they change something extensive QA testing must be done.

At some point all synth makers move on. Just because they have a Virus TI today doesnt mean they will in 2 years. The next Virus maybe Virus S for sample ram integration. It doesnt necessarily have to include TI anymore. What if Access isnt around? (god forbid!) Roland, Yamaha or Korg dont continue to

support the past models indefinitely. The problem with software TI is its always one step away from being obsolete. Electronic music equipment has a nice universal time tested total integration method since 1986. Its called MIDI.

You said it.

I like the Korg Radias way of things in that it has a standalone graphical editor and librarian (like SoundDiver but 100x times better), and you can use the USB connection as a MIDI device instead of the standard 5-pin MIDI ports.

No audio is swapped between the Radias and the computer. Most people still have dedicated soundcards for that (me included).

Let's face it....

TI is a dead, head-fuck-ie niche that people who are doing tunes for cash never use, and those who can actually get it to work, can't remember what sort of music they wanted to make before they built a computer to handle it in the first place.

Now that should get some action on the board surely! :)

Well I have used TI direct record functionality and I find it very useful, but yes if there were choice between TI usb recording functionality and a modulation/step-sequencer I would immediately chose the last one ;)

TI is there as an option people!
There's is nothing forcing you to use TI, if you can program better with the hardware do that (I do, cos I'm used to the old boxes and small screens).

If you still complain (about TI) then you are hoping for something that doesn't exist, why?

The Virus TI is an amazing synth by almost any standard, use it to make music not list specs and failings! It's much more rewarding trust me.

Why create a decoupled OS when you already have that? My Virus TI doesnt force me to use the TI software in any way.
I see nothing stopping people from using the TI whichever way they please, apart from the people themselves.

I'm starting to suspect certain people on here will complain regardless of how well the TI is performing.

wouldn't that be a good reason to step away from buying plug-ins at all and focus exclusively on hardware ;) ?

marc

I'm not following what you mean here? I'll give it a stab though.

A plug-in is developed in a software standard like VST. Its up to the daw producer to make sure that standard is compatible and supported in their own software. It's up to the end user to make sure their system is powerful enough to run it and make sure it works in conjunction with their own various customized DAW hardware and software configuration. None of those things are the obligation of the soft-synth developer.

What Access appears to be doing with TI is exactly the opposite by assuming the obligations and responsibilities of end users and music software manufacturers.

If you want a software plug in, then why not release a single instance software VST plug-in.

I understand the concept of trying to create one hardware/software product that does it all while off-loading the processor requirements to the Virus, but something has to give and usually its latency, stability and performance when you push it too far and try to be all things to everyone.

It is obvious that you do not know at all how the whole market works.
I think you just want to troll. If you don't like TI, don't use it.

Let the other 99% be happy with it.

r

I'm also wishing Access would make an editor like this one for the TI.

Another good product with a similar approach is Lexicon's MX series effects processors which utilize the USB for MIDI only and they give you a VST editor that gives you full recall for your project.

Could it really be that much effort to develop and achieve this kind of functionality?

With that said, I'm finally getting acceptable reliability and timing with OS 3.0.4 (aside from the amp envelope bug).

I just hope the next release doesn't change that.