aum.haa

So glad you got things working, and thanks for the praise I’ll keep it going as long as I can!

Hehe we cross-posted again.

There’s a lot of places that things can go wrong with the stepprs. Before we get into troubleshooting, can you tell me what versions of Live and Max you have installed?

I notice that your DrumSteppr version (in the picture) is 1.4. Thats an old one….mine says 1.5 here locally for DrumSteppr, and 1.4 for SynthSteppr. Have you tried updating m4m8?

a

Hey Mac,

You have to create a new matrix to get the mappings you want. The sends get mapped based on the dimension of the matrix you send them, and you can’t combine matrixes the same way you could combine a simple Python array.

In _setup_controls, you need to get all the knob elements into a new matrix, so something like:

self._knob_all_matrix = ButtonMatrixElement(name = ‘Knob_All_Matrix’, rows = [])
for index in range(3):
self._knob_all_matrix.add_row(self._dial_left[index*4:(index*4)+4] + self._dial_right[index*4:(index*4)+4])

I didn’t test that code, so you may have to play with it a bit. But that’s the general idea.

Now that you have a matrix that has all the knob elements, you can pass that matrix to the mixer layer as a sends target in _setup_mixer_control:

self._mixer.main_knobs_layer = AddLayerMode(self._mixer, Layer(priority = 5, send_controls = self._knob_all_matrix))

Sorry, not able to test any of this at the moment….does that make sense to you though?

a

Hey there, welcome to the forums I found a copy of the Mac Editor (v.97) and put it here:

[http://www.aumhaa.com/livid_archive/Elements/ElementsAlchemist_097.dmg.zip
](http://www.aumhaa.com/livid_archive/Elements/ElementsAlchemist_097.dmg.zip “http://www.aumhaa.com/livid_archive/Elements/ElementsAlchemist_097.dmg.zip
“)

Let me know if that works!

a

There’s a problem with the script, it won’t compile unless you comment line362:

def _setup_transport_control(self):
self._transport = TransportComponent(name = ‘Transport’)
# self._transport._play_toggle.view_transform = lambda value: ‘Transport.PlayOn’ if value else ‘Transport.PlayOff’

They changed something recently and it snuck past me. I’ll update it in GitHub tomorrow.

Nex, you’ll have to decide how you want to do things. Since there were only 4 tracks in the original script version, there’s really no good way to lay out the buttons for all 8…..you’ll have to sacrifice some things for others if you want to do all 8. I’d probably get rid of the stop clip buttons and set them all as arming track select, something like this:

self._mixer.main_buttons_layer = AddLayerMode(self._mixer, Layer(priority = 5,
mute_buttons = self._key_matrix.submatrix[8:, 1:],
arming_track_select_buttons = self._key_matrix.submatrix[:8, 1:],))

Let me know when you get things compiling, you’ll probably have to experiment a bit to find the right ergonomics…..keep in mind that you don’t overlap assignments! (that’s the real danger here, especially with this script because it does so many different things deepening on the mode its in).

a

Hey there,

Editing the CNTRLR script (and BASE, which is very similar in a lot of ways) is a bit tedious, since there are so many interdependent components. But, the basics:

You have to change the session_ring to accommodate 8 channels:

line 306, in _setup_session_control:
self._session_ring = SessionRingComponent(num_tracks = 8, num_scenes = 4)

Then you have to set the faders to control those tracks, which means removing their assignments from the stock ones in the script. Basically, you’re looking for stuff in _setup_mixer_control().

self._mixer.main_faders_layer = AddLayerMode(self._mixer, Layer(priority = 5,
volume_controls = self._fader_matrix.submatrix[:8, :],))

self._mixer.master_fader_layer = AddLayerMode(self._mixer.master_strip(), Layer(priority = 5,))

That’s just the start, though, as you’re probably going to want to change the select buttons, also. Let me know if you get that working and we can try the next step.

a

ohhh that could be good to have. I know there were some usb connectivity issues with the more recent versions of OSX, so it may be that 1.27 was partly a solution to those too, but got pulled because it didn’t turn out well? Anyway, I’d be interested to try it out if someone has it, I don’t think it ever made it onto my hardware.