Beiträge von jhuettner

Check the menu entries for

INPUTS 1/2 - BOOST

and

INPUTS 1/2 - Input Thru

in the CONFIG menu of your TI and make sure these are at 0 respectively "off". High levels for the Input Boost can raise the signal-to-noise floor.

You can only use Midi Files containing Virus SysEx data for this task in the "Virus Control Center". It is not possible to load data from other synths into the unit. If you have Virus sounds as SysEx files, you can convert these with 3rd party apps like "Snoize SysEx Librarian" for instance.

If the unit is connect to your computer via USB, you will only be able to send Midi signals to its Midi Out port if you create a Midi track in your DAW with the Midi out port "Virus TI Midi" being selected. Keep in mind that the TI works like a Midi interface when the USB connection is in use.

In which DAW is this? This is definitely not a known issue, so this must be related to how the plugin is set up in this particular DAW.

Modulating the filter cutoff (no matter which one) will not modulate the panning, but if you have the filter routing set to parallel, then obviously modulating a filter will sound like a panning modulation, too. Check if that is the case.

Dear Jeremy,
The Virus TI PlugIn will react on the actual Midi channel that is currently selected in Logic when you have set up the Virus TI plugin as multi-timbral plugin with 16 tracks for it, so if the Midi track with Midi channel 3 is selected, PART 3 of the Virus TI plugin will react.

Make sure the Virus TI plugin is set to

2 OUTS / NO INPUT

for the INPUT/OUTPUT Configuration (USB Audio Mode) on the PATCH/UTILITY [CONFIG] page of the plugin, otherwise the inputs won't work for the audio interface capabilities.

Could this be a restriction of Cubase Elements by any chance? I don't have Elements here, but this might be the case here.

If the unit has OS 6.5 installed, then this could point to a hardware problem, especially if you are anywhere near exhausting the max. amount of voices the unit can produce. Especially when playing it by itself and no other external unit being able to send any Midi CCs or SysEx to the device, this would point to a hardware issue.

The Virus c is a hardware synthesizer that works like any other hardware synthesizer out there when you connect it to an audio interface and you try to monitor its sound via direct monitoring in a DAW. The latency is not caused by the Virus in this case but by the audio interface setup. You can test this by simply playing the Virus through its Midi In port and connecting either headphones to its output or speakers. You will hear the sound from the Virus c directly then.
Again this is nothing that can be caused by a Virus c at all.

Which Virus TI software version do you have installed right now?

The Virus Control Center is always under

APPLICATIONS -> ACCESS MUSIC -> VIRUS TI

The Virus TI plugin can be loaded in supported music softwares.

Click on "Patch/Utility" in the Virus TI plugin and change the USB audio configuration there to

3 OUTS / NO INPUT

to be able to use all three stereo output streams via USB.

The "classic" mode of the Virus TI only produces a single oscillator signal per oscillator, hence there is no "detune" for this. The "detune" parameter is available in Hypersaw since this mode allows you to create more than a single Oscillator signal which you then can detune against each other.

The only option or better "workaround" in "classic" mode is to use the UNISON mode and then detune the UNISON voices against each other, however this also will eat up voices very quickly at high UNISON settings.

Send me an email to support [at] access-music.de

Maschine is not an officially supported host for the Total Integration.

What is the OS version installed on this Virus unit and when did you first notice this?
Eventually send me an email to support [at] access-music.de

<p>Which Virus model is this and what exactly happens when you try to store a new Multi program? Eventually send me an email to support [at] access-music.de</p>

Dear Michael,
The Virus TI simply "listens" to whatever is send to it via Midi. Since the OSC3 Volume is not a hardware control on the TI surface it also cannot come from a broken potentiometer here. Is this issue with any FL Studio session you're starting even in a brand new one with nothing but the TI in it? If so please disconnect any Midi keyboard/controller connected to this computer setup and check if you still run into the problem. I'm fairly certain that some device sends Midi commands to the Virus causing this or some Midi information is in the particular FL Studio session (however then this would happen at a specific point in the FL Studio session).

I would recommend to use the VST3 version due to For easier parameter automation in Cubase.

The headphones output is basically a copy of the signal coming from the OUT 1 L+R of the Virus. Enabling the "D" button in the Virus TI plugin activates the "direct monitoring" feature which routes the signal to the analog out OUT 1 L+R, hence it also shows up in the headphones out.