Emu XL-7 & MP-7 User's Group

Also, if you have more than one rom installed, make sure you select a 
Preset on that ROM before randomizing.  As near as I can tell, the 
Randomize function only work on the current ROM, not on all of them at 
once. 

rEalm




P.S: Thanks again for Randomizing advice ! Not a day without trying 
it..... (1/100 I get extraordinary sounds !!!!)








[Non-text portions of this message have been removed]

--- In xl7@yahoogroups.com, erik_magrini@B... wrote:
> Also, if you have more than one rom installed, make sure you select 
a 
> Preset on that ROM before randomizing.  As near as I can tell, the 
> Randomize function only work on the current ROM, not on all of them 
at 
> once. 
> 
> rEalm

I have one randomized preset that get XROM in some layers (but it's 
set to none !) and BEAT GARDEN in another (with a valid instrument on 
it).......I don't know , maybe I tweaked it and don't remember maybe 
because I'm overusing this function , I'll check this out a little 
better in near future....

XROM

No, that could be, I'm not sure exactly.  The few times I tried to check 
this out, it always came up with the same ROM for all layers.  But, since 
it's random, we may never really know :)

rEalm




I have one randomized preset that get XROM in some layers (but it's 
set to none !) and BEAT GARDEN in another (with a valid instrument on 
it).......I don't know , maybe I tweaked it and don't remember maybe 
because I'm overusing this function , I'll check this out a little 
better in near future....

XROM



To unsubscribe from this group, send an email to:
xl7-unsubscribe@yahoogroups.com

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 







[Non-text portions of this message have been removed]

--- In xl7@yahoogroups.com, erik_magrini@B... wrote:
The few times I tried to check this out, it always came up with the 
same ROM for all layers.  But, since it's random, we may never really 
know :)
 
 rEalm

I have one randomized preset that get XROM in some layers (but it's 
 set to none !) and BEAT GARDEN in another (with a valid instrument 
on it).......I don't know , maybe I tweaked it and don't remember 
maybe because I'm overusing this function , I'll check this out a 
little better in near future....
 
XROM

>>  These are some of the reasons I want to develop the parametizer 
software.  I've been working on it as time permits.  I've been 
testing a number of possibilities, including a short cut using sysex 
commaands.

>> Unfortunately, I cannot trigger randomize via sysex EXCEPT to 
automate simulated front panel button presses.  Its a far cry from 
what I have in mind for the parametizer, but I could create a midi 
file that would automate, for example, 127 presses of the randomize 
button, storing each result in User bank 0.  Let me know if this 
would be helpful as a start.

>>BTW, to minimize the chance of an accidental/unwanted erasure of an 
entire bank of presets, I would set the mid file to operate on an 
upper device ID--eg 120.  

>> I'm also getting "random" presets with the same ROM instrument in 
all 4 layers.
 
>> To address an earlier suggestion, part of my goal is to have 
namable randomizer configurations.  EG, you may want to save a 
configuration file to generate "randomized" presets that use 1 or 2 
layers, each with a different ROM instrument selected from a 
customized list of instruments, where certain parameters selected 
from a customized list are "randomized," while others are left 
untouched, etc.  
 
Dr. Steve

> >> Unfortunately, I cannot trigger randomize via sysex EXCEPT to 
> automate simulated front panel button presses.

I used to think (with other synths) that EVERYTHING was possible thru 
SYSEX , not only front panel commands but many other hidden 
operations not doable by any other means than sysexes....(Maybe 
because these synths had very limited front panel commands....Anyway 
Mega Kudos for KORG X5dr, TR Rack etc...)Obviously (unfortunately) 
Sysex implementation seems to be one of the weak point of our beloved 
command stations...(BTW why P2500 understand some sysex functions 
that our XX7 just ignore , are'nt they supposed to be very similar ?)
  

> Its a far cry from what I have in mind for the parametizer, but I 
>could create a midi file that would automate, for example, 127 
>presses of the randomize button, storing each result in User bank 
>0.  Let me know if this would be helpful as a start.

Automated generation of whole banks of randomized presets ! Sure it 
could be usefull ...though it would be cool we had some way to choose 
the target user bank (to avoid erasing the one where our most used 
presets are stored : in my case banks 0 & 3 )...But if it's not 
possible I can go with bank 0.......


> >> I'm also getting "random" presets with the same ROM instrument 
in all 4 layers.

After discussing with rEalm I tried many times randomizing presets 
today and always had the same rom on all layers too, so .....


> >> To address an earlier suggestion, part of my goal is to have 
> namable randomizer configurations.  EG, you may want to save a 
> configuration file to generate "randomized" presets that use 1 or 2 
> layers, each with a different ROM instrument selected from a 
> customized list of instruments, where certain parameters selected 
> from a customized list are "randomized," while others are left 
> untouched, etc.  

If you could manage to do this it would make me very very happy !!!!

Best Regards 

XROM

Unfortunately, I cannot trigger randomize via sysex EXCEPT to 
automate simulated front panel button presses.  Its a far cry from 
what I have in mind for the parametizer, but I could create a midi 
file that would automate, for example, 127 presses of the randomize 
button, storing each result in User bank 0.  Let me know if this 
would be helpful as a start.

>>>Any chance the User Bank could be specified?  I personally have Banks 0 
and 1 full already, so for me personally, bank 3 would be the best.  Also, 
from a writing standpoint, when I work on music I like to hear what I'm 
doing while playing with Randomize.  So even though I could get around the 
problem by just doing a sysex back up of my Bank 0, I then wouldn't be 
able to hear my patterns that needed those Presets, and thus I wouldn't 
know which Randomized Presets I might want to end up using.  I'm tired, 
did that make sense?  :) <<<

rEalm





[Non-text portions of this message have been removed]

--- In xl7@yahoogroups.com, "xromxx7" <bonneau-c@w...> wrote:
> Automated generation of whole banks of randomized presets ! Sure it 
> could be usefull ...though it would be cool we had some way to
> choose the target user bank (to avoid erasing the one where our
> most used presets are stored : in my case banks 0 & 3 )...But if
> it's not possible I can go with bank 0.......

Thanks for the feedback.  It may be possible to do this.  The current 
(in progress) version has 5 basic sysex banks as follows:

     0 - Open Remote Control Session
     1 - Reset Current Preset to 000-0
     2 - Reset Save Preset to 000-0
     3 - Randomize & Save # 1
     4 - Randomize & Save # 2 +
     5 - Close Remote Control Session

The file "plays" sysex banks 0 -> 3 and then bank 4 126 times to 
randomize and save a total of 127 presets.

I might be able to rewrite the banks so that if you omit one of the 
sysex banks, the presets will be stored starting from whatever preset 
you manually set up in the "save preeset to" menu.

Another option is to have a sysex bank that holds only the sysex 
command for the starting preset.  This way, you could set it yourself 
by editing the one sysex command and then save your customized file 
for future use.

Part of the design allows users to decide how many consecutive 
presets to create by editing the number of times sysex bank 4 (in the 
above configuration) is "played."

Of course, all this presumes you have a sequencer that gives you 
access to the sysex banks.

Not to get anyone's hopes up, but this is nothing more than 
automating front panel button presses.  The really cool software 
(parametizer) has a long way to go.

Question: Does using MIDI Sysex ID 120 make sense to you?  I see it 
as a way to help minimize accidental overwriting of desired presets. 

Dr. Steve

--- In xl7@yahoogroups.com, erik_magrini@B... wrote:

Thanks for the feedback. Some comments:

> >>>Any chance the User Bank could be specified?

See reply to XROM on this issue

> Also, from a writing standpoint, when I work on music I like to
> hear what I'm doing while playing with Randomize.

I have several thoughts on this, but it would help if you could give 
me a brief explanation of your "modus operandi" with regard to 
testing out randomized presets.

Dr. Steve

--- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@p...> 
wrote:
>It may be possible to do this.  The current 
> (in progress) version has 5 basic sysex banks as follows:
> 
>      0 - Open Remote Control Session
>      1 - Reset Current Preset to 000-0
>      2 - Reset Save Preset to 000-0
>      3 - Randomize & Save # 1
>      4 - Randomize & Save # 2 +
>      5 - Close Remote Control Session
> 
> The file "plays" sysex banks 0 -> 3 and then bank 4 126 times to 
> randomize and save a total of 127 presets.
> 
> I might be able to rewrite the banks so that if you omit one of the 
> sysex banks, the presets will be stored starting from whatever 
>preset you manually set up in the "save preset to" menu.

I was thinking about a bunch of sysex strings all in one midi track, 
you hit play and there you go...Dividing it in five parts is so much 
clever ! I like the idea of omiting sysex banks in order to manually 
set up the starting preset (=bank to be overwritten : In my case it 
would be preset 000Bnk1 or preset 000Bnk2!)
 

> Another option is to have a sysex bank that holds only the sysex 
> command for the starting preset.  This way, you could set it 
>yourself by editing the one sysex command and then save your 
>customized file for future use.

This way is even better, but it could scare people unfamiliar to 
sysex editing. It would be cool to have both options but if it's not 
possible, last method with a detailed "How to" document could do the 
trick !!


> Part of the design allows users to decide how many consecutive 
> presets to create by editing the number of times sysex bank 4 (in 
>the above configuration) is "played."

Haaaa sounds quite good to me !!!(BTW how would you do this ?)


> Of course, all this presumes you have a sequencer that gives you 
> access to the sysex banks.

My SONAR 2.2XL is awaiting for your file my friend !!!!


> Not to get anyone's hopes up, but this is nothing more than 
> automating front panel button presses.  The really cool software 
> (parametizer) has a long way to go.

BTW rEalm said he likes to hear each randomized preset, this is not a 
bad idea ! Could it be possible that after every randomized preset we 
hear 2 or 3 notes played in sequencer or audition button or whatever ?

 
> Question: Does using MIDI Sysex ID 120 make sense to you?  I see it 
> as a way to help minimize accidental overwriting of desired 
>presets. 

Hmmmm...I do think that the easiest & safest way, is to do a sysex 
dump of user banks BEFORE dealing with Parametizer ! If I use it 
intensively, nothing will prevent me from doing wrong after I have 
set up my machine ID to 120 !(after 2 or 3 beers for example !) 


Best Regards

XROM

Typically, once my drums are more or less laid out, I just start jamming 
on a free track.  I'll pu the Xl-7 so it's on the Randomize page (with the 
knobs in Quick Edit mode) while my pattern plays, and just keep hitting 
the Enter button while I play until I find something that catches my 
interest.  Sometimes the randomized preset is good as is, sometimes I 
think I can tweak it to get the desired result.  Once I get something I'm 
happy with, I name it, disable any unused layers in the preset, and then 
move on to the next track.  All while the patterns plays though. 

Some randomized sound cool on their own, but more often than not it's how 
it fits in the context of the song I'm working on that matters.

rEalm






I have several thoughts on this, but it would help if you could give 
me a brief explanation of your "modus operandi" with regard to 
testing out randomized presets.









[Non-text portions of this message have been removed]