aum.haa

Yes it makes perfect sense. I’ll see what I can do, thanks!

Had a chance to try this out – it’s sort of working!
– 8 channels map across the faders – nice!
– Sends only work on tracks 1-4. I see some stuff in setup_mixer_control() such as send_controls

I tried the commented line and some other things, but couldn’t get them to work.
`self._mixer.main_knobs_layer = AddLayerMode(self._mixer, Layer(priority = 5,
send_controls = self._knob_left_matrix,
# send_controls = self._knob_right_matrix))
eq_gain_controls = self._knob_right_matrix))
`

– Transport overlays the track mutes and shift

My idea here is to make the controller more of an 8 channel mixer type controller like a Mackie MCU, without automation but with nice knobs and faders. When I get something working well I’d be happy to send a pull request. I can imagine other people would like to use this?

I thought about how to remap, disabling the current functions of the entire top row of 16 buttons makes the most sense.
The top 1-4 buttons could then be mute/solo for tracks 1-4, and 13-16. Mute/solo would be via shift, like now.
The original 4 mute/solo would be unmapped, as would 5-12 on the top row, thus avail for reuse
The 4×4 clip trigger buttons don’t make sense anymore, being 4×4 in an 8 channel red box, so I’d also like to turn their functions off, too. If they could work as they do in user mode, that would be the best – assignable to whatever you like.

I tried but couldn’t turn it off

`self._session.clip_launch_layer = LayerMode(self._session, Layer(priority = 5,
clip_launch_buttons = self._matrix.submatrix[:,:]))
self._session.scene_launch_layer = AddLayerMode(self._session._selected_scene, Layer(priority = 5,
launch_button = self._button[28],))
`

I also tried to deactivate all the encoder knobs so they could be assigned (just in that one same layer) as encoder knobs and buttons like they are in User Mode but couldn’t figure out how. It seems like there are a few places?

Thanks! OK, I’m right there with you, though the controller interface doesn’t activate now. Not sure if thats intended at this stage. (I made a copy so can still use the OG version)

It also looks like we might want to set the following?

mute_buttons = self._key_matrix.submatrix[:8, 1:],
track_select_buttons = self._key_matrix.submatrix[8:8, 1:],))
self._mixer.set_enabled(False)

PDF is in the OP, here’s the Keynote file version:

Working on the factory reset. The Jazz Midi plugin doesn’t appear to work on Chrome, Safari, Firefox, I am guessing because no modern browser supports NPAPI.

Instructions, for others:

So, I downloaded Chromium 44:
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac/330231/

Installed the Jazz Midi extension
https://chrome.google.com/webstore/detail/jazz-midi/jhdoobfdaejmldnpihidjemjcbpfmbkm?hl=en

Visited
chrome://flags/#enable-npapi

and clicked Enable

Visited

http://www.lividserver.com/editor/index.html

Had to allow it to interact with website, and was able to pick “external – controller” and then click “defaults(reset) at the top.

Unfortunately, if I had upgraded to Catalina this would not work at all! I wouldn’t have been able to run the old Chromium 44.

And… it worked! Thank you very much!

It worked a little different than I expected though:

the top right encoder brings me into user mode, not the second from the left as the manual shows.

Then, the you can select the bottom 8 encoders by clicking them to pick a midi channel, 5-12. This needs to be done _before_ entering Live’s MIDI mapping settings.

So my second-to-last question is – how would someone on the latest Mac OS reset their controller?

And finally, a request – could I ask you to please remove the file I uploaded?

Thanks again!