Re: new synth

[ Follow Ups ] [ The QuadraSynth Forum ] [ FAQ ]

Posted by f3 on January 31, 2001 at 14:44:35:

In Reply to: new synth posted by BEAKER on January 31, 2001 at 10:23:44:

Tim -

Sysex (system exclusive messages) is a way to to make a device (in this case the QS 6.1) do various things that you want it to do. In general, whatever you can make the QS do by pushing buttons and turning dials on the device itself, or by sending midi controller types of messages, you can also do by sending Sysex messages. There are always some exceptions to that, depending on the specifics of the device and the operation, but that's a general rule.

Sysex messages are a bit more complicated to put together than the more usual midi controller and patch change messages. On the other hand, once mastered they are a powerful way to ensure that everything on the QS is set up exactly how you want it to be when you begin playing back a midi sequence. There's a document on the Alesis download site that provides info on constructing Sysex messages for the QS units. To say the least, it's a bit of a challenge to follow this particular document (not so "pleasant to read" as you said the manual was), even if you have some Sysex experience. And there are mistakes in it.

One of the things that you can do with Sysex is store the 'code' from the QS unit that tells it how to set up specific programs and mixes. It doesn't capture the sample sound itself, but rather all of the other settings in the program sound layers, effects patches, etc. that tell the QS what to do with that sample in a particualar program. You can transmit this Sysex information to a computer to store that information. For example, if you create your own unique version of a QS program that you've stored in the User Bank, you can use Sysex to transmit the information for that one program to your computer to keep as a backup in case you later inadvertantly over-write it or just want to move it off the QS to create new User Bank space.

A 'bulk dump' refers to the process of transmitting this kind of Sysex information for all programs, effects etc at one time. This info can then later be re-uploaded if needed. Again, in the QS this process does not transfer the sound samples themselves, only the information that the QS uses internally to process those samples in a program.

You can't download the actual samples in the QS by Sysex or any other straightforward procedure I am aware of. I think you would have to "sample the samples" as you would any other sound you'd like to capture, and then use whatever procedures the Nova uses to upload those samples to that device.

As for uploading Nova samples to the QS, it can conceivably be done by sampling those sounds, and burning them to a PCMCIA Flash ram or SRAM card using the Alesis Soundbridge software. An 8 meg Flash Ram card will cost you $100 - $120. When it works, it's great, but it's always a challenge to get things sampled and looped properly.

As for changing the Alesis sounds to make them fatter, one option is to adjust the EQ (and maybe add a short delay or chorus) in the effects patches. Or, if you have a mixer and other processing gizmos, turn the effects in the QS off and process the sound externally. It may be easier than tweaking the EQ within the QS itself, assuming this option is available. See other messages and message-strings here lately about options for turning QS effects on and off.

Sorry for the loooooooooong answer. Hope it helps.


: Hello,

: Since Saturday I've an alesis QS 6.1.  I find the sounds very nice and the but I have a few questions, and maybe you find some time to help me. I've a E-mu esi 2000 sampler and a nova novation.

: Although the manual is very pleasant to read, I don't understand Sysex, why u use it.
: I was thinking, is it possible to get the sounds of the nova into the Alesis and viceversa? 
: I've heared something about "bulck dump" but I don't get it, can I do this with my Alesis?  Do you have some tips of changing the sounds in the alesis a bit heavier, fatter.

: Thanks for your help.

: Tim

Follow Ups: