Synth-DIY Yahoo! Groups Archives

Thread

Re: [xl7] Re: Modded Command Stations

2018-12-29 by Adsr Multimedia

Not in my case.

Waldorf microWave1, OS 2.0.

WaveIdea Bitstream Pro as controller, fully set up for SYSEX control, as the mW1 lacks pots and sliders.

Works absolutely perfect in real-time.

I have the same experience with an Oberheim Matrix 1000, Yamaha FS1R, Access Virus C Rack.

Ok, the M1k has a slow microprocessor, but keeps up as much as it can.

Regards,

Zsolt

2018. dec. 29., Szo 22:30 dátummal deepwhy47 deepwhy47@... [xl7] <xl7@yahoogroups.com> ezt írta:

I concur with Bruno. I researched this with my Yamaha Rs-7000 back in 2005. My eventual conclusion was that it is useful for things that you can change in advance, but not very much so for fading parameter values, which is what I was hoping for. I've used SysEx with a number of other machines as well and they all have behaved similarly.

Sent from my Sprint Samsung Galaxy S8+.

-------- Original message --------
From: "Bruno brunorc@... [xl7]" <xl7@yahoogroups.com>
Date: 12/29/18 13:31 (GMT-07:00)
To: xl7 <xl7@yahoogroups.com>
Subject: Re: [xl7] Re: Modded Command Stations

Remember, that SysEx is not as realtime, as one would think (or wish). I did some research with Yamaha SY77, but I believe that (almost) every other synth would work the same way - all the changes made by transmitting the SysEx will be only taken into account upon the generation of the next note. That being said, it can be still useful while editing the sounds - e.g. editing SY77 with a control surface like BCR 2000 is much more "hands-on" than diving in the menus.

Just my 0.02$

Bruno

pt., 28 gru 2018 o 16:09 'fabio-spicuglia@...' fabio-spicuglia@... [xl7] <xl7@yahoogroups.com> napisał(a):
I won’t open or mod my Mp7 but using sysex to further manipulate that synth in realtime is quite interesting to me: for es. by programming my SL remote Zero or using an iPad generic midi editor. Thank You for the hint!

------------------------------------
Posted by: "fabio-spicuglia@..." <fabio-spicuglia@...>
------------------------------------

------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/xl7/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/xl7/join
(Yahoo! ID required)

<*> To change settings via email:
xl7-digest@yahoogroups.com
xl7-fullfeatured@yahoogroups.com

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

<*> Your use of Yahoo Groups is subject to:
https://info.yahoo.com/legal/us/yahoo/utos/terms/

Re: [xl7] Re: Modded Command Stations

2018-12-29 by Adsr Multimedia

SYSEX, as above.

Sometimes parts of the gear is under CC control, if available. But I made full SYSEX templates on the Bitstream, so I'm independent of actual patchcord assignments and can directly modify parameters.

Zsolt

2018. dec. 29., Szo 23:45 dátummal Bruno brunorc@... [xl7] <xl7@yahoogroups.com> ezt írta:

sob., 29 gru 2018 o 22:51 Adsr Multimedia adsr.multimedia@... [xl7] <xl7@yahoogroups.com> napisał(a):
Not in my case.
Waldorf microWave1, OS 2..0.
WaveIdea Bitstream Pro as controller, fully set up for SYSEX control, as the mW1 lacks pots and sliders.
Works absolutely perfect in real-time.

Just to be sure we're talking about the same thing: it is SysEx, as opposed to the regular MIDI CCs, right?
Also, by "realtime" we mean "the sound of a sustained note is affected by the SysEx messages sent to the device"? E.g. while Command Station can change the frequency of the filter in realtime, the resonance is a note-on parameter (but that's because of the way E-mu implemented filter lookup tables, rather than cubes).

I have the same experience with an Oberheim Matrix 1000, Yamaha FS1R, Access Virus C Rack.

I have FS1R and Virus Rack, but probably clarifying will be faster, than setting up my BCR2000 to control any/both of them ;-) In the past I';ve been using BCR2000 to control them _together at the same time_ (can yield some quite surprising results), in realtime, but I was using regular CC messages, not SysEx.

Bruno

Re: Modded Command Stations

2018-12-30 by smw-mail@...

Footnote re: non-immediate CC control of resonance in the released [non-beta] OS:

THREAD: Re: [xl7] older O/S (v1.32) download?

https://groups.yahoo.com/neo/groups/xl7/conversations/messages/15123

Why do you want an older OS? There's no reason at all to downgrade to an
older OS for the XX-7's. Well, except that beta version with realtime Q
enabled, but you won't find that :)

rEalm

https://groups.yahoo.com/neo/groups/xl7/conversations/messages/15133

Wish I had it in the E-Mu. (And if I had known it was deliberately
disabled, I might not have spent so much time trying to figure out what I
was doing wrong.)

>>>Yes, res is only calculated at Note On. <<<

I imagine in the wrong hands realtime control over resonance with filters
such as EaryRizer could pop an E-Mu into oblivion--either that or it would
enable presets that would be way too amazing for audience comprehension.
Any idea why it was disabled?

>>>Basically because the engineers at Emu felt that it didn't sound as

smooth as they'd like, and gave unpredicatble results with some of the
esoteric filters. I argued long and hard that more options (no matter how
they sound) are always a better thing when it comes to sound design, but
to no avail. It was felt that people would not be able to get over the
fact that the resonance didn't behave like on other gear in some
instances, and thus would be a cause for complaint. Personally, I never
noticed any of the above, at least not in a way that I thought was
negative. <<<

rEalm

Re: [xl7] Re: Modded Command Stations

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

Glad to hear!!! If it helps, I can start a spreadsheet of parameter IDs I tested and the results. I used the form:

F0 18 0F dd 55 01 02 xx xx yy yy F7

I used dd = 7F.

For preset select I sent -1 to parameter 897 to use the edit buffer.

For layer select I used 0 for layer 1 (parameter 898).

Tested:

Next-Note change: Layer Instrument, LFO 1 Shape, Layer Cord Amount [I used DC -> pitch because its easier to hear!], Filter Type, Layer Pan, Filter Cutoff, Filter Q, and maybe some others I didn't write down.

Immediate change:

FXA algorithm [both master and preset], FXA Decay.

With direct parameter changes my guesses are that:

--most if not all preset layer parameters will not be immediate,

--some of the preset common parameters will be immediate

--most if not all of the FX parameters will be immediate

I am pretty sure I tested the 4 FX send percentages, but I didn't write down the result.

I did not test arp pattern changes, but assume those are next-note effects.

I'd be interested in the results of any results you get.

BTW, to test I used an audition riff at BPM = 1 and sent the individual sysex banks from SONAR.

As for embedded sysex, I can't imagine them not working. Hmmmmm. Maybe the next test will be a drum pattern using a 4 layer preset with track 16 as a ROM Instrument Control Track with embedded sysex to vary the 4 layers. Hmmmmm.

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.