Support
Looper's Delight
|
Support |
|
|
good ideas and points. i know that i'm throwing around a stew of
things in a confusing way, but that's because i'm trying a lot of
things to see what works. in the long run, i probably won't run
Ultrabeat patterns in Mainstage - i'll probably program some midi
pattern clips in Live that I will play using the Ultrabeat sounds, in
order to be able to add more real-time variation to the output by
processing the midi stream with midi fx (or i'll use the x-groover
"probabilistic drummer" that came as a Max 5 sample to send midi to
ultrabeat or maybe to a sampler instrument). So, would a Start command
coming from the Song Start function in the middle of a stream of
clocks confuse any of that? I will experiment and see. The empty
pattern idea is a pretty good idea. but it may take me a couple of
days to try these things out - i have a jazz gig on friday and there's
rust all over my fingers - too much configurin', not enough playin'
lately.
On Wed, Mar 11, 2009 at 4:45 PM, Per Boysen <perboysen@gmail.com> wrote:
> Eh, guys... isn't Warren hosting the drum sequencer (UltraBeat) in
> MainStage? Meaning whatever sync signal sent out from the Mobius
> plug-in will target MainStage first hand. Plus Ableton Live, if he
> runs that application too, in parallel. If this presumption is
> correct, it would be best to only send one start command as the MIDI
> Clock starts being sent out from Mobius ("sync = out" that is?). The
> way to bring in a drum pattern could then be one of two ways: (1)
> un-mute the drum thingy (that is running with the host all from the
> start) or (2) start with an empty pattern running inside UltraBeat and
> simply switch to a pattern with notes in it when it's about time. Then
> the quantizing will happen in the drum sequence plug-in (as it is
> designed for, which may be a good point)
>
> Greetings from Sweden
>
> Per Boysen
> www.boysen.se
> www.perboysen.com
>
>
>
> On Wed, Mar 11, 2009 at 9:18 PM, Warren Sirota <wsirota@wsdesigns.com>
>wrote:
>> that might be a good way for me to go - wouldn't force you into a
>> prerelease of MidiSend, or require me to get scripts working. the loop
>> vs. cycle start point issue would definitely be livable for a while.
>> thx.
>>
>> On Wed, Mar 11, 2009 at 3:49 PM, Jeff Larson
><jeff.larson@sailpoint.com> wrote:
>>> [Warren]
>>>> More likely, for the present: i'll arrange for a drum loop (possibly
>>>> in Live) to be triggered by the Start cmd, but i'll start it muted.
>>>> then it should stay synced and be there when i'm ready to un-mute.
>>>
>>> There's something else that might work. One of the Sync Mode values
>>> is "Out User Start", another thing I copied from the EDP. This will
>>> start sending clocks when the loop is closed but it doesn't send a
>>> Start message. When you're ready to trigger the drum loop use the
>>> "Start Song" function. This will wait until the loop start point then
>>> send a MIDI Start message.
>>>
>>> This would avoid having to mess with track mutes in Live, the downside
>>> is that it is always quantized to the loop start point, you can't make
>>> it start on an interior cycle boundary.
>>>
>>> Jeff
>>>
>>>
>>
>>
>>
>> --
>> Warren
>> http://www.ubetoo.com/Artist.taf?_ArtistId=6679
>> http://www.warrensirota.com
>>
>>
>
>
--
Warren
http://www.ubetoo.com/Artist.taf?_ArtistId=6679
http://www.warrensirota.com