Ableton Forum

fixed_up wrote:This seems to do something as now all my pads (including the solo/mute/cue and transport controls play a midi note. However I cannot get the step sequencer to run. When I hit shift and master volume nothing happens.

kclarkmusic wrote:Has anyone figured out how, when using the Step sequencer, to change Midi clips and get the Button Mattrix to refresh? It seems as though it will only "change clips" if manually selected with the mouse.

kclarkmusic wrote:Hello noble Ableton Enthusiasts,

Has anyone figured out how, when using the Step sequencer, to change Midi clips and get the Button Mattrix to refresh? It seems as though it will only "change clips" if manually selected with the mouse.

Example:

Clip one:
- Holds a sequence

Clip 2:
- Holds a different sequence

If I'm editing clip 1 in the step sequencer mode, then I go back to Clip Launch mode (Mode 1) and Launch Clip 2, Clip 2 then begins to play like you'd expect.

But when I go back to Step Sequencer mode, it is still focussed on Clip 1, and won't change to Clip 2 unless I select the clip with the mouse.

I've posted this on Hanz's blog but just thought I'd shop around for other help. I'll try posting it on Live forum as well.

Cheers,
Kendall Clark
[email protected]
http://www.kendallclarkmusic.com
http://www.neonblackmusic.com

Markemark wrote:

kclarkmusic wrote:Hello noble Ableton Enthusiasts,

Has anyone figured out how, when using the Step sequencer, to change Midi clips and get the Button Mattrix to refresh? It seems as though it will only "change clips" if manually selected with the mouse.

Example:

Clip one:
- Holds a sequence

Clip 2:
- Holds a different sequence

If I'm editing clip 1 in the step sequencer mode, then I go back to Clip Launch mode (Mode 1) and Launch Clip 2, Clip 2 then begins to play like you'd expect.

But when I go back to Step Sequencer mode, it is still focussed on Clip 1, and won't change to Clip 2 unless I select the clip with the mouse.

I've posted this on Hanz's blog but just thought I'd shop around for other help. I'll try posting it on Live forum as well.

Cheers,
Kendall Clark
[email protected]
http://www.kendallclarkmusic.com
http://www.neonblackmusic.com

Try this,
Go into the Preference's.
Go to the "Record, Warp, Launch" tab.
Turn on "Select on Launch"

Should now work without using the mouse Have fun!!!!

Hanz_Petrov wrote:

fixed_up wrote:This seems to do something as now all my pads (including the solo/mute/cue and transport controls play a midi note. However I cannot get the step sequencer to run. When I hit shift and master volume nothing happens.

Have you selected the correct Input and Output ports under MIDI preferences? Have your turned Track and Remote to "On" for the MIDI input port?

Hope that helps.

Hanz

Hanz_Petrov wrote: Okay, as promised, here's how to get the step sequencer to Navigate Up/Down 5 rows at a time:
In the file StepSequencerComponent.py, change the following lines:

Code: Select all

    def _nav_up_value(self, value):
        assert (self._nav_up_button != None)
        assert (value in range(128))
        if self.is_enabled() and self._is_active:
            button_is_momentary = self._nav_up_button.is_momentary()
            if button_is_momentary:
                if (value != 0):
                    self._scroll_up_ticks_delay = INITIAL_SCROLLING_DELAY
                else:
                    self._scroll_up_ticks_delay = -1            
            if ((value != 0) or (not self._nav_up_button.is_momentary())):
                if self._key_index < (123 - self._height): #<------------------- Change from 128 to 123
                    self._key_index += 5 #<------------------------------------- Change from 1 to 5
                    self._update_matrix()

Hanz[/quote]

This worked great thanks HANZ! I did have to change,
assert (value in range(128)) to 123 as well to get the lowest C-2

JuanSOLO wrote:This worked great thanks HANZ! I did have to change,
assert (value in range(128)) to 123 as well to get the lowest C-2

Hanz_Petrov wrote:

JuanSOLO wrote:This worked great thanks HANZ! I did have to change,
assert (value in range(128)) to 123 as well to get the lowest C-2

Glad it worked for you, but changing the "assert" line as you've done is basically forcing a (non-fatal) script error every time the MIDI nav value is higher than 122. To do it "properly", the code would need to drop the grid down below the lowest note, then filter out presses on blank rows (since C-2 can't be reached in steps of 5, starting from middle C, without including blank rows). I'll look at addressing this issue in the next revision.

Best,

Hanz

PS: Thanks to donations received so far, I've managed to fund the purchase of an APC20, which means I can start work on an APC20 version of the step sequencer (and probably some "APC80" combination mode stuff too). Stay tuned.

JuanSOLO wrote:So it would be better not to change the assert value and just set my lowest not to C#-2 for now?

fixed_up wrote:I for the life of me cannot get this working! I'm obviously doing something blatantly wrong as everyone elses seems to be fine.

Ive moved the script into my live midi scripts folder and it shows up as a control surface in my live preferences.

This seems to do something as now all my pads (including the solo/mute/cue and transport controls play a midi note. However I cannot get the step sequencer to run. When I hit shift and master volume nothing happens.

Please help!