OS 3.0.5 Beta is out!!

[drakeblood]

So sad, since 3.0.4 is impossible to make work VC with Reaper. Same for 3.0.5... it will never "link" with the VirusTI...

UPDATE:
I figured out that basically the VirusControlVST, with Reaper, is unable to put the hardware unit in the -SEQ MODE- so you have to do it manually holding together the two buttons MULTI/SINGLE. Doing that you get the VirusControlVST to communicate correctly with the hardware. SADLY this is only the begin of the hell.
Until you make one single automation lane over any knob you are kinda safe, when you make the 2nd one for another parameter (any parameter, both VST or CC messages) HELL COMES ON EARTH. The sound goes on frenzy and the hardware unit screams.

UPDATE 2 (IMPORTANT! CUBASE SLUGGISH GUI issue maybe found!):
Found out that is a GUI redrawing issue of the VST... Crazy but if i close the VC window the sound and automations works perfectly!
If i reopen it back the sound starts again to scream...
I attached the Reaper project showing the issue quite clearly. Just open the FX chain for the VirusTI channel and press the -UI- button (Reaper have the feature to disable, on request, the GUI of the VST, disabling it there is no issue with the VC but it becomes clearly unusable. click that button and the GUI of the VC comes back)
I think the issue is that the VC is asking excessive redrawing of the controls when it receives "automation commands" from the host (probably for syncronization?).
Marc or someone at Access could check it,
I DEFINITELY think this is the cause of "sluggish GUI" that affects also Cubase.

[HomeWrekker]

Originally Posted by drakeblood

So sad, since 3.0.4 is impossible to make work VC with Reaper. Same for 3.0.5... it will never "link" with the VirusTI...

I am experiencing the same issue when I host the Virus in KORE. I have contacted technical support and they advise that there are no plans to include KORE as a host. Hopefully a future update will inadvertently fix this. After a lengthy session yesterday I am pleased to report that I am sneeze free.

[drakeblood]

Today the developers of Reaper contacted the technical support of AccessMusic... let's see if they can do something together.
Cockos (the guys behind Reaper) are totally disponible for find a solution. Solved this one the VirusTI works flawlessy on Reaper.

Here the video showing the bug and how to replicate it:

[marc]

Originally Posted by HomeWrekker

I am experiencing the same issue when I host the Virus in KORE. I have contacted technical support and they advise that there are no plans to include KORE as a host. Hopefully a future update will inadvertently fix this. After a lengthy session yesterday I am pleased to report that I am sneeze free.

kore and reaper are not supported hosts.

hth, marc

[boreg]

Originally Posted by marc

kore and reaper are not supported hosts.

hth, marc

Oops, never knew that ! (and have actually used VC in Reaper several times - although have gotten connection problems a couple of times, as well).

- What's wrong with Reaper?
- Shouldn't VC work in any VST-compatible host?
- Are there plans to support Reaper in the future?

[marc]

Originally Posted by boreg

Oops, never knew that ! (and have actually used VC in Reaper several times - although have gotten connection problems a couple of times, as well).

- What's wrong with Reaper?
- Shouldn't VC work in any VST-compatible host?
- Are there plans to support Reaper in the future?

total integration works with compatible host. with others, your milage might vary. compatible means that we test against the host. if a host is not on the list, that doesn't mean that there is something wrong with it. it just means, it is not officially supported. nevertheless, if we can, we fix incompatibilities - there is no advantage to us in having issues with other products.

best, marc

[drakeblood]

Originally Posted by marc

kore and reaper are not supported hosts.

hth, marc

Hi Marc, i know Reaper isnt a supported host but being both a Reaper and a Cubase user and noticing those stuffs make me wonder if is not the same problem.

[marc]

Originally Posted by drakeblood

Hi Marc, i know Reaper isnt a supported host but being both a Reaper and a Cubase user and noticing those stuffs make me wonder if is not the same problem.

this is getting confusing. which problem do you have with windows XP/Vista and Cubase 4.x or 5.x?

marc

[drakeblood]

Originally Posted by marc

this is getting confusing. which problem do you have with windows XP/Vista and Cubase 4.x or 5.x?

marc

With various envelopes running basically the VC goes crazy. For various i mean 4-5 at a time.
On Cubase i dont get the drastic issue as in Reaper but is still there.
I have also to add that i ran the test with FLstudio and, with 4 envelopes it goes frenzy too EXACTLY like Reaper does. (FL is in the supported list as stated on AccessMusic website)

With Schwa of Reaper developers i ran few tests to trim down this issue and the result (quoted directly from him)

drakeblood ran a test build that confirms the issue is within Virus TI. Specifically (and technically), with the GUI open and automation running, the plugin takes too long to respond to AEffect::setParameter, so the automation messages from Reaper (and other hosts too, NdD) get backlogged.

This is something they need to fix on their side. If for architectural reasons it just takes a while to send the automation message from the plugin to the synth, they could queue the message to the synth and return quickly from setParameter without blocking.

As demostration of this "fuzzy sound" issue here also a project made with latest FLStudio release showing it perfectly (8.5 beta5, but i tested it with FL7 and FL8 too, i can send even those project if required)

I will forward the issue also to AccessMusicSupport, would love that this issue gets resolved.

[absynth]

just testet the new beta in Win XP SP2, works great now and no slugginess at all! great work access

but still sluggy in Windows 7

so my guess was aero & windows 7 skin, changing to classic but that didn´t change the slugginess