The Unofficial Access Virus & Virus TI Forum - since 2002 - hardware seq. to send program change for multis [SOLVED]

The Unofficial Access Virus & Virus TI Forum - since 2002 (http://www.infekted.org/virus/forum.php)

- Trouble with your Access Virus? (http://www.infekted.org/virus/forumdisplay.php?f=108)

- - hardware seq. to send program change for multis [SOLVED] (http://www.infekted.org/virus/showthread.php?t=24686)

Hi,

Well I finally got around to emailing Access tech support (work getting in the way of life and all that...).

Here is their reply:

So you're talking about the SysEx commands here, right?

To change from Single to Multi-Single Mode the following command must be sent to the Virus, if the
Virus' Device ID is set to 1:

F0,00,20,33,01,01,72,40,7a,01,F7

To select the corresponding Multi Program you only need to send a simple program change on the
Global Midi Channel of the Virus, but you need to make sure that the MIDI MultiPrgChg menu is set
to "ena" (enabled). Otherwise this won't work.

Unfortunately, this command didn't work. I've sent my midi file back to Access. We'll see what they say.

I couldn't find this command in any of the sysex documentation i've been able to find. Does anyone have a full sysex spec for the Virus? (Virus A)

cheers,
Paul

Quote:

Originally Posted by sputnikcdn

Hi,

To change from Single to Multi-Single Mode the following command must be sent to the Virus, if the
Virus' Device ID is set to 1:

F0,00,20,33,01,01,72,40,7a,01,F7

Support gave you the correct answer, but had a little glitch.

Explanation:

Code:

F0,00,20,33,01,00,72,00,7A,02,F7

|  |  |  |  |  |  |  |  |  |  |

|  |  |  |  |  |  |  |  |  |  sysex end

|  |  |  |  |  |  |  |  |  01=Multisingle/02=Multi

|  |  |  |  |  |  |  |  (dez 122): Playmode

|  |  |  |  |  |  |  part number*

|  |  |  |  |  |  Parameterbank C

|  |  |  |  |  Device ID (0x00..0x0F, 0x10=OMNI)**

|  |  |  |  Product ID (1=Virus)

|  +--+--Vendor ID (Access Music)

Sysex Start



cite from the manual:

* The SysEx Parameterchange affects one of

the sixteen single edit buffer in Multi Mode addressed

by the part number (00..0F) or the Single

buffer in Single Mode (part number 40). If a

global parameter or a Multi parameter is accessed,

which is not part-sensitive (e.g. Input

Boost or Multi Delay Time), the part number is

ignored.





** CAVE: if the Virus is set to DeviceID 1

the value must be 0 (ID2=1,...)



Like MIDI channels the range is counted 1 to 16,

but the values you must send start with 0. 

A Value of 16 (0x10) means DeviceID is set to OMNI.

I hope this will clear it up. Change the device ID parameter
to 00 when you have deviceID=1.

Quote:

Originally Posted by sputnikcdn

I couldn't find this command in any of the sysex documentation i've been able to find. Does anyone have a full sysex spec for the Virus? (Virus A)

You can download the manuals from the access site, maybe not for the A, but the one for Virus B will help you, too.

I have to apologize for the little mistake of our support.

-tk

Hi tk,

Thanks for your reply! I'll try it out as soon as I get home tonight!

I've looked all over the Access site and have not been able to find anything with the text you quoted.

I looked in the sections for the Virus A and B. No luck. I have downloaded several documents, even some sysex specs, but I've never seen anything like what you quoted.

Would you be able to give a direct link to that sysex document? Thanks very much!

Paul

hardware seq. to send program change for multis [SOLVED?]

Quote:

Originally Posted by sputnikcdn

I've looked all over the Access site and have not been able to find anything with the text you quoted.

Would you be able to give a direct link to that sysex document? Thanks very much!
Paul

You?ll find all manuals in the "Documentation" section in the download area of each product.

The sysex commands are described in the appendix of the manuals.

-tk

hardware seq. to send program change for multis [SOLVED]

I guess this means solved?

yes!

I'm very sorry for not updating.

I did a search for the sysex string in all the manuals I could download and didn't find it. That's why I thought there must be another sysex spec floating around. I'm pretty sure I found it in a Virus B manual.

Thanks a lot for your help!

Cheers,
Paul