Access Virus Editor – Troubleshooting

When I change preset in hardware, Editor is not receiving the data

Cause 1: If hardware DeviceID differs from the Editor DeviceID set. Usually when DeviceID matches with the hardware, then data flow works perfectly.

Cause 2: If DAW playback is on, then data transfers are held back because of excessive MIDI data flows. This is to prevent hanging notes and mis-aligned data.

Cause 3: Request Data on Program Change is toggled OFF. In this case you can change presets in hardware without interactions with the Editor. Use case: you want to quickly go thru sounds to find the sound you need. Remember to Sync Data from HW if this is toggled off in purpose.

I get connection timed-out messages when changing programs

See above!

I don’t get sound from Hardware after chancing programs

Cause 1: During the initial MIDI Input / MIDI Output configuration step, Editor was unable to sync data with the hardware, therefore Editor can not route MIDI channel messages to appropriate Layer.

Cause 2: When Multi is changed, it might have changed the Part MIDI Channels to different channel configured on your DAW MIDI track.

My DAW freezes when I insert the Virus Editor or when I import a bank

Cause: Our Editor checks the file you have chosen to import into the Editor. During this time, if the Editor detects an error with the file, it might get stuck.

Check further details on How to Enable LOG article for details to reveal which bank is causing the issue and how to resolve it.

I can only play one Part when MIDI is triggered on Editor track

Cause: Incoming MIDI channel from DAW track usually determines which Part is played, if channels match. You can engage SHOW KEYBOARD function to force incoming MIDI data to currently selected part.

Data is not recalled properly when I re-open my project

Cause: Maybe the DeviceID has changed or something else is wrong with the configs. Double check your MIDI ports on the Editor, DeviceID on both ends and then try PUSH DATA TO HW from LIBRARIAN VIEW.

MIDI input and MIDI output is not memorized on new instances

Cause: This is by design. We have learned that in some cases where MIDI input and output ports are stored within the Editor, it has potential to crash the DAW on plug-in insertion. We are looking to fix this in upcoming release.

In the meanwhile, if you are confident your setup can handle memorizing the MIDI ports, you can setup the Editor as usual and then save the entire channel strip as a preset to your DAW channel strip settings. Next time you recall the channel strip setting, MIDI is assigned and data from the Editor is pushed to the hardware (unless its disabled via the Utilities menu).

Something else that buzzles me…

You can open a ticket from my-account page if your issue is not listed above. We will update the FAQs and Troubleshooting page as time goes on.

Closure

Hopefully this User Manual helped you understand how the Editor works and how it is designed to work. Now start making some awesome tunes and don’t forget to review our product – that would make our day!