Yahoo Groups archive

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

Archive for xl7.

Index last updated: 2026-03-30 01:19 UTC

Message

Re: Modded Command Stations

2019-01-02 by smw-mail@...

Evidently in 2006 I tested the use of direct parameter sysex to change arp patterns within a SONAR midi track.

NOTE: This is just an example based on the file I found.
Please see WARNING(S) below about not using master/global parameters (and the arp pattern editor) for on-the-fly changes.


F0 18 0F 00 55 01 02 03 05 11 00 F7
F0 18 0F 00 55 01 02 03 05 27 00 F7
etc.

MASTER_ARP_PATTERN 
id = 643 (03h,05h) min = 0; max = 199


Without minute testing, I'm assuming it will affect the next note, but if you can set up a slider to go through 100 user arp patterns, maybe we could call it on-the-fly arp pattern >>selection<<. 

IMPORTANT WARNING(S):
For reasons discussed a few years ago, you would probably not want to do this with on-the-fly arp pattern >>editing<<.  IIRC correctly, editing eats up chip write cycles.  So using a slider (either hardware or software) would use up chip-lifetime write cycles very fast!!!!! 

At one point while testing Prodatum (ages ago), I used the virtual slider to play arp pattern changes on-the-fly for a number of minutes.  I was aghast when I later learned that each arp pattern edit was written to the storage chip.

Someone correct me if I am wrong, but I believe the preset edit buffer uses plain-old RAM which has more lifecycles.  If so, for that reason, when I test preset parameters, I now use try to use the edit buffer as opposed to User memory slots.

That being said, I am not sure of what gets stored where--I just know what others have said.  With the above test (Master Arp Pattern changes), obviously there is a pointer to the Master Arp Pattern saved.

As for CC changes, when the initial controller amounts within a family of presets are off and you change presets, the previous CC values are still there (I believe on a channel-by-channel basis), but when the unit is powered down and rebooted, I believe the prior CC values are gone [not tested yet]. So, I am guessing (and hoping!)  those changes use plain-old RAM.

If I recall correctly, sequencer patterns edits get written to non-temporary storage memory only when we use the Save button as opposed to arp patterns which get written each time there is an step change.

I am guessing its similar to the use of the preset edit buffer.  Hopefully to be on the safe side, for on-the-fly FX and other changes, I am going to use the preset buffer parameters instead of master/global parameters.

 


 

Attachments