hdavid / launchpad95 Goto Github PK

Hello there,

First of all it's a fantastic work, love it!

I have noticed a case where I have no more note lights feedback in step sequencer Combined mode. It's a weird state, some lights which were on in multi mode stays in combined mode. Restarting Ableton is the only way found so far to reset it.

Currently I avoid using the multi note mode. I've spent some hours playing with your script and so far this clip page navigation bug makes the multi note mode not usable on my gear.

System:

• launchpad mini
• ableton live suite 9.6 32bit

Steps to reproduce:

1. user mode 2 (brings step sequencer Combined mode)
2. 4th scene button (brings step seqencer Multi note mode)
3. right button (moves clip page to the right) (that's the problematic action)
4. 4th scene button again (brings the Combined mode again)

I can provide further details if needed (steps, video,...).
I'll read the source code too but it's a long time since my last python script and I have never done any music script. Anyway I will try, maybe make a pull request if I find anything.

Thanks for the nice script,

spoutnik

The scale function and everything else seems to work fine, but I can't actually get the lit up buttons on the grid to trigger notes.

I'm either running 9.1.3 or 9.1.4 and certain buttons like stop and arm don't seem to function the way they're described in the doc. Stop doesn't work at all and arm triggers session record whether I press it quickly or hold for a second. Also I see dim green lights on the main grid but they don't seem to do anything. Solo and track on/off work however. Could this be because I'm not running 9.1.2? Or maybe I'm using it wrong?

Certain pads will remain green even when the note for that beat is toggled off. The note still toggles on and off regardless of the light staying on, but you lose that feedback from the launchpad.

I have this problem quite freqently. unfortunately i dont really know python, so i cant figure it out myself, what should be changed.

I want to add is user options to make some values read only.
My scenarios is that since I use another controller for track volume/pan (nanoKontrol) I want to make them read only in lp95 so that my physical faders and knobs always are the showing the correct state.

My idea of how it should work is by having launchpad95.ini file in the script directory where read only mode can be set for some track parameter.. If it is easy to generalize this concept without adding lots of code It could be enabled for many parameters.
I'll guess that it should mostly matter for the regular stuff like volume/pan/sends so that is my goal for a first version.

I think that I might have some time for this soon.

Will it continue to be updated for new versions of ableton?

https://www.youtube.com/watch?v=3XTfAOxcQJQ

Is this expected?
Thanks

Default User Modes not working

After uncommenting the following lines, the default Launchpad User Mode 2 is not working since it is not displaying the default keyboard notes with Novation format (see image attached), instead, the LP matrix is turned off with single pad flashing in green.

	USER_MODES_1 = [
			"instrument"
			,"device"
			,"user 1"
	]
	USER_MODES_2 = [
			 "drum stepseq"
			 ,"melodic stepseq"
			 ,"user 2"
	]

The "User Mode 1 - Drum Rack " works fine, although it does not respect the original grid colors:
https://www.youtube.com/watch?v=mHvqwH0xQq8

Expected User Mode 2

The stock launchpad setup has a seperate menu that you bring up by hitting the session button to change settings by velocity. Is there a way to configure my pad velocity in launchpad95 when im in instrument control mode?

Hi, great project, thank you for the effort on this!

It would be very useful to have a more straightforward way to delete clips, like the Ableton Push, by holding a button and click on a clip on Session Mode.
The button to hold could be the Session mode button (it seems that it has no function when hold down), I couldn't find any information in the documentation.

Hey there-

As a random weekend COVID project, I redid the manual in a more graphical style, and made a bunch of edits to the content wording and organization to make it clearer (I think). I did reach out to @hdavid but didn't hear back so wanted to post it here. https://launchpad95manual.mystrikingly.com/ (i'm happy to make any adjustments or changes or anything)

How would you feel about if I change some things to make the code more consistent and easier to read and make a pull request?

You seem to like tabs so let's keep them, allowing longer line lengths than 80 characters might also be a good fit for this project.
Other rules are possibly also good to allow, I haven't really started to get a feel for what else might be suitable to allow yet, I want to get some input from you first.

The most important thing imho to make code much more readable is following the spacing rules for operators, assignments, lists etc. consistently according to pep8.

What follows is a generated report of suggestions for the current code base.
Any of these rules can be disabled individually but some of them are quite helpful.

25      E101 indentation contains mixed spaces and tabs
1       E113 unexpected indentation
1       E121 continuation line under-indented for hanging indent
1       E124 closing bracket does not match visual indentation
70      E128 continuation line under-indented for visual indent
18      E201 whitespace after '['
24      E202 whitespace before ']'
20      E203 whitespace before ':'
76      E221 multiple spaces before operator
8       E222 multiple spaces after operator
1       E224 tab after operator
574     E225 missing whitespace around operator
48      E228 missing whitespace around modulo operator
1001    E231 missing whitespace after ','
53      E251 unexpected spaces around keyword / parameter equals
41      E261 at least two spaces before inline comment
37      E262 inline comment should start with '# '
234     E265 block comment should start with '# '
4       E271 multiple spaces after keyword
10      E272 multiple spaces before keyword
20      E302 expected 2 blank lines, found 1
77      E303 too many blank lines (2)
268     E501 line too long (83 > 79 characters)
2       E703 statement ends with a semicolon
372     E711 comparison to None should be 'if cond is not None:'
1       E712 comparison to True should be 'if cond is True:' or 'if cond:'
54      F401 'Live' imported but unused
17      F403 'from _Framework.ButtonElement import *' used; unable to detect undefined names
5       F811 redefinition of unused 'set_update_listener' from line 32
1       F812 list comprehension redefines 'k' from line 143
4       F841 local variable 'non_feedback_channel' is assigned to but never used
5863    W191 indentation contains tabs
122     W291 trailing whitespace
4       W292 no newline at end of file
462     W293 blank line contains whitespace
5       W391 blank line at end of file

Most of these things are not in any risk of directly affecting the application itself but it would make it easier for me and possibly others to contribute if the readability is improved and there is a known way to format the code so that it doesn't lose even more consistency.

Hiya henri,
What's the source code license on this project?

While learning the Launchpad and Launchpad95, I thought it would really be beneficial to have a display for the device.

So I built a proof-of-concept using Python and CircuitPython. Parts needed are under 10 USD in total.

Right now it is more a proof-of-concept than anything, but already now I like it a lot and can see the potential.

Are you interested in collaborating on this?

Notes falling out of the viewport when moving up / down the notes in multi note mode can lead to an invalid note index.

@see #29

Cheers

spoutnik

Mr. David - Thanks for everything you do for the community. I haven't removed LP95 from my setup since i got my LP. I uncommented "user 2" in settings py and loaded a user mode through Novation Librarian, but it's not working. I made a layout of CC message buttons in Librarian, and it works fine when i deactivate LP95, but when I engaged LP95 it doesn't recognize them. I saw in your source code where the channel for user mode 1 has to be 4 and user mode 2 has to be 5, but it still won't work. Thanks for any help if it's something dumb i'm doing, otherwise keep at it with LP97. I'm stoked to see what you come up with.

Hey BTW, i've had alot of great success with that "quick" scale change setting in note mode.

Hi, great project.

A suggestion from someone just starting out and trying to learn: Currently the documentation is hard to read due to low contrast (somewhat brigher gray letters on somewhat darker gray background). It would be much easier to read if it had more contrast (like black letters on white background).
Thanks for considering.

As the title says

Hi! I just downloaded the last release (from yesterday?), and I noticed a bug: when in the melodic step sequencer I can't change the root node when I enter scale edition mode. I installed the older version and it works fine, only the new version is not working.

Thanks!

Hi Henri,
Thanks again for a terrific tool!

Am using Live 11.2.6 with a Launchpad mini MK3 and noted that the upper part of the sequencer (where the notes are) does not scroll when the clip is longer than the 32 steps displayed.
Instead, it shows the first 32 steps and the blue indicator moving through them, while playing the second 32 steps.

As a workaround, I can zoom in with the lower right and then edit.
Can it be changed though?
I tried setting STEPSEQ__LINK_WITH_SESSION = True, which did not have any effect.

Kind regards,
Tobias

There were some exceptions popping up in the ableton log while I was beginning to figure out how the platform api works, I began to fix it but it relates to the osd code that seems to be targeted at the max/msp which I have no knowledge of at all..

The problem is that SubSelectorComponent does not have a _update_OSD function so I've tried to add one but I'm not sure at what level I should add the information or how it should be laid out.. Is there a specifik max/msp patch targeted for this thing?

diff --git a/MainSelectorComponent.py b/MainSelectorComponent.py
index 7aa7fd2..12e5b81 100755
--- a/MainSelectorComponent.py
+++ b/MainSelectorComponent.py
@@ -57,7 +57,7 @@ class MainSelectorComponent(ModeSelectorComponent):

                self._sub_modes = SubSelectorComponent(matrix, side_buttons, self._session)
                self._sub_modes.name = 'Mixer_Modes'
-               self._sub_modes._mixer.set_osd(self._osd)
+               self._sub_modes.set_osd(self._osd)
                self._sub_modes.set_update_callback(self._update_control_channels)
                self._stepseq = StepSequencerComponent(self._matrix, self._side_buttons, self._nav_buttons, self)
                self._stepseq.set_osd(self._osd)
diff --git a/SubSelectorComponent.py b/SubSelectorComponent.py
index a56d534..37f6b4e 100644
--- a/SubSelectorComponent.py
+++ b/SubSelectorComponent.py
@@ -47,7 +47,9 @@ class SubSelectorComponent(ModeSelectorComponent):
                self._mixer.selected_strip().name = 'Selected_Channel_strip'
                for column in range(matrix.width()):
                        self._mixer.channel_strip(column).name = 'Channel_Strip_' + str(column)
-                       self._sliders.append(PreciseButtonSliderElement(tuple([matrix.get_button(column, 7 - row) for row in ra
+                       slider = PreciseButtonSliderElement(tuple([matrix.get_button(column, 7 - row) for row in range(8)]))
+                       slider.set_parent(self)
+                       self._sliders.append(slider)
                        self._sliders[-1].name = 'Button_Slider_' + str(column)

                self._side_buttons = side_buttons[4:]
@@ -286,3 +288,12 @@ class SubSelectorComponent(ModeSelectorComponent):
                self._session.set_stop_track_clip_buttons(None)
                self._session.set_stop_all_clips_button(None)
                self._mixer.set_global_buttons(None, None, None)
+
+       def set_osd(self, osd):
+               self._osd = osd
+               self._mixer.set_osd(osd)
+               
+       def _update_OSD(self):
+               # TODO Thomas done not use max4live
+               # which seems to be the output of osd (??)
+               pass

I am using Live 11.2.7 and Launchpad Mini Mk3.

When I go into Settings.py and change what the user mode buttons do by trying to assign Drum stepseq to user mode 1 (the drum button on the mini Mk3), it does work but introduces mixed functionality reminiscent of a melody mode.

For instance, It works fine unless I try and preview the sounds by holding the velocity button and hitting a drum pad. In some cases it will preview the sound but in other it will trigger the pressed pad and another pad higher up as if they are linked (the same behavior pitched notes that share a pitch have in melodic modes). This results in me not hearing a preview but a step being placed in the sequencer where the linked note is.

USER_MODES_1 = [
		"drum stepseq"
		,"device"
		#,"user 1"
]
USER_MODES_2 = [
		 "instrument"
		 ,"melodic stepseq"
		# ,"user 2"
]

The Launchpad X has the following buttons (the square ones). I am putting them next to the buttons mentioned in the documentation, which I guess are the buttons from older models (the round ones).

At this point, I am just speculating (but am not really sure) that there is a 1:1 relationship between the old and the new keys.

It would be nice if the documentation would reflect both old and new buttons, since for users of Launchpad X the documentation is constantly referring to non-existing keys.

It works if the scene is triggered by clicking in live, its only if the launch is done on the device itself this happens. Switching to another mode and back again reinitialises the stop buttons.

The reason is that SpecialSessionComponent._stop_track_clip_buttons is cleared, by something.

i cant see light in the mixer sends mode i have to scroll to guse in which channel i m right now
hop for an advice how to fix
greeting for the 95 project it took the launchpad to another level

Hi Henri,
I love your work at Launchpad95! Thank you so much! Today I get my new Launchpad X and I try the newest Launchpad95 version. Sadly the new combined Session/Mixer Mode I like so much with the new Launchpad X is not working. Are you still working on it? Just the default X plus the step Sequenzer in Custom mode would be sooooo great ;-)
Anyway... love your work,
Nils

Hey,

I just started using your scripts with my Launchpad MK2 and the added functionality is incredible, thanks a lot!
I was wondering if it is or would be possible to set the loop start and end positions for recorded clips on audio tracks in a similar fashion to how we can do it for the midi clips in the combined mode of the step sequencer (the blue buttons that can be used to set the window).

I sometimes record from a position where I cannot easily access mouse or keyboard and it would be nice if I can adjust the loop window for audio clips directly from the launchpad (e.g. if I hit the stop button too late when recording or when I recorded a few tries and only want to loop one of them). I already tried mapping some buttons from the user 2 mode to loop position and length in Live directly, but I think they require knobs or faders, the buttons do not change anything.

I also started reading your code base and found the corresponding class and functions in the StepSequencerComponent, but I did not quite yet grasp the overall information flow between live and the controller. Do you think the code could be stripped down and re-used on an audio clip or does Live not provide functions to set the start/end of loops for audio clips?

I thought it might be better to see whether this is clearly impossible or whether there already is a simple solution to this that I missed before really diving into the programming.

Thanks again and best wishes
Niklas

Hi! I just tried to install this script but whenever I pick Launchpad95 from the midi menu the device seems unresponsive. It still sends midi to Ableton, but the script is not working. This is the error I see in the log file when I select Launchpad and then Launchpad95:

80177 ms. RemoteScriptMessage: (Launchpad) Initialising...
82923 ms. RemoteScriptMessage: (Launchpad) Initialising...
83779 ms. RemoteScriptMessage: (Launchpad) Challenge Response ok (mk1)
83789 ms. RemoteScriptError: Traceback (most recent call last):

83794 ms. RemoteScriptError: File "c:\Jenkins\live\output\win_64_static\Release\midi-remote-scripts_Framework\ControlSurface.py", line 456, in receive_midi

83798 ms. RemoteScriptError: File "c:\Jenkins\live\output\win_64_static\Release\midi-remote-scripts_Framework\ControlSurface.py", line 467, in _do_receive_midi

83802 ms. RemoteScriptError: File "MIDI Remote Scripts\Launchpad95\Launchpad.py", line 197, in handle_sysex

83807 ms. RemoteScriptError:
83811 ms. RemoteScriptError: self.init()

83817 ms. RemoteScriptError: File "MIDI Remote Scripts\Launchpad95\Launchpad.py", line 120, in init

83821 ms. RemoteScriptError:
83825 ms. RemoteScriptError: self.log_message("LaunchPad95 Loaded !")

83830 ms. RemoteScriptError: File "c:\Jenkins\live\Projects\AppWebConnector\Resources\third_party\lib\contextlib.py", line 33, in exit

83835 ms. RemoteScriptError: File "c:\Jenkins\live\output\win_64_static\Release\midi-remote-scripts_Framework\ControlSurface.py", line 660, in component_guard

83839 ms. RemoteScriptError: File "MIDI Remote Scripts\Launchpad95\Launchpad.py", line 103, in init

83843 ms. RemoteScriptError:
83847 ms. RemoteScriptError: self._init_note_repeat()

83851 ms. RemoteScriptError: File "MIDI Remote Scripts\Launchpad95\Launchpad.py", line 270, in _init_note_repeat

83856 ms. RemoteScriptError:
83859 ms. RemoteScriptError: self._note_repeat = NoteRepeatComponent(name='Note_Repeat')

83864 ms. RemoteScriptError: File "MIDI Remote Scripts\Launchpad95\NoteRepeatComponent.py", line 21, in init

83868 ms. RemoteScriptError:
83872 ms. RemoteScriptError: Live.Base.log("NoteRepeatComponent - Init Start")

83876 ms. RemoteScriptError: AttributeError
83881 ms. RemoteScriptError: :
83885 ms. RemoteScriptError: 'module' object has no attribute 'log'
83889 ms. RemoteScriptError:

Thanks!

Would it be possible to implement stepless faders for the device controller?

I think it should work like the following:
the higher the difference between current value and the wanted value, the higher the velocity.
I would implement it but i dont know where in all the python files this would happen if at all.

For large drum kits on the MKII, it could be very useful to be able to change the color of the drum pads. For instance, making hi-hats and toms a different color than kicks and snares.

I've read over the user manual and couldn't find any way to do this.

However, it is possible to change the color of the drum hits in the Ableton drum rack. (Screenshot below)

Is there any way to translate these colors to the Launchpad?

Since there is nothing in the manual that I could find I'm assuming the code doesn't have a way to handle this. Working on that assumption, is this even possible?

If it is possible but just not supported, I'm interested in taking a shot at implementing this. I have a pretty good grasp on Python and the code is generally making sense to me, but if you could point me in the right direction on this that would be much appreciated!

Hey, amazing script!

I noticed I get these error messages in Ableton Live 11 with a launchpad mini mk3, thought I'd pass that on.

Documentation says:

For Live Suite users, in the M4LDevice folder is included an OSD (on screen display) Max4Live device that will display information, similarly to what one could see on an Ableton Push screen.

Unfortunately it is not explained how exactly to get this to work.

It would be very helpful to know what needs to be copied where, and whether Live needs to be restarted. Should the window appear automatically, all the time?

Hi,

Looks like a great tool, but unfortunately I'm having problems getting it to work. The regular Launchpad script works fine, but when I switch the ControlSurface (in Preferences) to Launchpad95, no lights light up even if I push buttons. The launchpad acts only as a MIDI keyboard sending note on signals. I have a Launchpad Mini if that makes any difference.

I get the following error in /Users/[username]/Library/Preferences/Ableton/Live 9.0.6/Log.txt:

754411 ms. RemoteScriptError: AttributeError
754411 ms. RemoteScriptError: : 
754411 ms. RemoteScriptError: 'Launchpad' object has no attribute 'release_controlled_track'
754411 ms. RemoteScriptError: 

The error repeats in the log if I press the session or mixer button. Full log text below.

Any suggestions or hints would be much appreciated. Thanks! I write Python for a living, so don't hesitate to ask me to try tweaking the code in various ways.

1774766 ms. RemoteScriptError: Traceback (most recent call last):
1774766 ms. RemoteScriptError:   File "MIDI Remote Scripts/_Framework/ControlSurface.py", line 435, in receive_midi
1774766 ms. RemoteScriptError:   File "/Users/versonator/Hudson/live/Projects/AppWebConnector/Resources/third_party/lib/contextlib.py", line 33, in __exit__
1774766 ms. RemoteScriptError:   File "MIDI Remote Scripts/_Framework/ControlSurface.py", line 609, in component_guard
1774766 ms. RemoteScriptError:   File "MIDI Remote Scripts/_Framework/ControlSurface.py", line 435, in receive_midi
1774767 ms. RemoteScriptError:   File "MIDI Remote Scripts/_Framework/ControlSurface.py", line 444, in _do_receive_midi
1774767 ms. RemoteScriptError:   File "MIDI Remote Scripts/_Framework/ControlSurface.py", line 457, in handle_nonsysex
1774767 ms. RemoteScriptError:   File "MIDI Remote Scripts/Launchpad95/ConfigurableButtonElement.py", line 47, in receive_value
1774767 ms. RemoteScriptError:     
1774767 ms. RemoteScriptError: ButtonElement.receive_value(self, value)
1774767 ms. RemoteScriptError:   File "MIDI Remote Scripts/_Framework/ButtonElement.py", line 82, in receive_value
1774767 ms. RemoteScriptError:   File "MIDI Remote Scripts/_Framework/InputControlElement.py", line 458, in receive_value
1774767 ms. RemoteScriptError:   File "MIDI Remote Scripts/_Framework/SubjectSlot.py", line 68, in notify_method
1774767 ms. RemoteScriptError:   File "MIDI Remote Scripts/_Framework/Signal.py", line 102, in __call__
1774767 ms. RemoteScriptError:   File "MIDI Remote Scripts/_Framework/Signal.py", line 13, in default_combiner
1774767 ms. RemoteScriptError:   File "MIDI Remote Scripts/_Framework/Signal.py", line 107, in _slot_notification_generator
1774767 ms. RemoteScriptError:   File "MIDI Remote Scripts/_Framework/Signal.py", line 38, in __call__
1774767 ms. RemoteScriptError:   File "MIDI Remote Scripts/_Framework/ModeSelectorComponent.py", line 163, in _mode_value
1774768 ms. RemoteScriptError:   File "MIDI Remote Scripts/Launchpad95/MainSelectorComponent.py", line 105, in _update_mode
1774768 ms. RemoteScriptError:     
1774768 ms. RemoteScriptError: self.update()
1774768 ms. RemoteScriptError:   File "MIDI Remote Scripts/Launchpad95/MainSelectorComponent.py", line 260, in update
1774768 ms. RemoteScriptError:     
1774768 ms. RemoteScriptError: self._setup_instrument_controller(not as_active)
1774768 ms. RemoteScriptError:   File "MIDI Remote Scripts/Launchpad95/MainSelectorComponent.py", line 336, in _setup_instrument_controller
1774768 ms. RemoteScriptError:     
1774768 ms. RemoteScriptError: self._instrument_controller.set_enabled(enabled)
1774768 ms. RemoteScriptError:   File "MIDI Remote Scripts/Launchpad95/InstrumentControllerComponent.py", line 66, in set_enabled
1774768 ms. RemoteScriptError:     
1774768 ms. RemoteScriptError: self._parent._parent.release_controlled_track()
1774768 ms. RemoteScriptError: AttributeError
1774769 ms. RemoteScriptError: : 
1774769 ms. RemoteScriptError: 'Launchpad' object has no attribute 'release_controlled_track'
1774769 ms. RemoteScriptError: 

I am in user 1 mode. I select a channel with a drum rack and arm it.
When I press the leftmost bottom button , it launches the C3 note, and the rest of the buttons, from that note upwards.
I want to be able to move that, so it launches the C1 note. But I cant find how to do it

LP95 has been working fine until i started trying to use it with my launchkey mini mk3. Now whenever both are connected, the LP95 mixer won't come up. Also, there's a weird white key at the bottom right of session view. Is there a chance that LP95 is try to impose itself on the LaunchKey mini as well? Thanks for any advice.

I'm loving this tool. Massive props on what you've made Henri.

When I'm in melodic step sequencer mode, I notice that the quantize button works quite a bit differently than it does in the drum step sequencer mode. Hitting it in step seq mode halves the length of the notes, whereas hitting it in drum seq mode changes the loop length. Was this intentional or a bug? I find that I often have to hit the quantize and then press Ctrl+Z to undo the change in notes to get the desired effect (and then do it a few more times to get back to where I was originally).

I was going to post this in the forums, but can't seem to get my login to work there correctly.

Hello!
The clip colors in session and prosession pages is not correct, it's different from abl color clips.
They are all light colors, red is pink, brown purple and gray and they are different.
Is it possible to correct the CLIP COLOR TABLE?
Thanks.

Reproducible with one or two launchpads connected, live 9.1.7.

Played with this quickly, it is a really neat feature, thanks!

22341 ms. RemoteScriptError:     
22341 ms. RemoteScriptError: button = self._stop_track_clip_buttons[index]

22342 ms. RemoteScriptError: IndexError
22342 ms. RemoteScriptError: : 
22342 ms. RemoteScriptError: list index out of range
22342 ms. RemoteScriptError: 

22343 ms. RemoteScriptMessage: (Launchpad) Detected broken listener at: Unknown
22343 ms. RemoteScriptError: Traceback (most recent call last):

22343 ms. RemoteScriptError:   File "/Users/versonator/Jenkins/live/Binary/Core_Release_64_static/midi-remote-scripts/_Framework/ControlSurface.py", line 688, in _call_guarded_listener

22343 ms. RemoteScriptError:   File "/Users/versonator/Jenkins/live/Projects/AppWebConnector/Resources/third_party/lib/contextlib.py", line 33, in __exit__

22343 ms. RemoteScriptError:   File "/Users/versonator/Jenkins/live/Binary/Core_Release_64_static/midi-remote-scripts/_Framework/ControlSurface.py", line 661, in component_guard

22343 ms. RemoteScriptError:   File "/Users/versonator/Jenkins/live/Binary/Core_Release_64_static/midi-remote-scripts/_Framework/ControlSurface.py", line 688, in _call_guarded_listener

22344 ms. RemoteScriptError:   File "/Users/versonator/Jenkins/live/Binary/Core_Release_64_static/midi-remote-scripts/_Framework/SubjectSlot.py", line 329, in <lambda>

22344 ms. RemoteScriptError:   File "/Users/versonator/Jenkins/live/Binary/Core_Release_64_static/midi-remote-scripts/_Framework/SessionComponent.py", line 613, in _on_playing_slot_index_changed

22344 ms. RemoteScriptError:   File "MIDI Remote Scripts/Launchpad95/SpecialSessionComponent.py", line 69, in _update_stop_clips_led

22344 ms. RemoteScriptError:     
22344 ms. RemoteScriptError: button = self._stop_track_clip_buttons[index]

22344 ms. RemoteScriptError: IndexError
22344 ms. RemoteScriptError: : 
22344 ms. RemoteScriptError: list index out of range
22344 ms. RemoteScriptError: 

Hi there,

I recently tried to update my launchpad95 script to the latest in the repo but I couldn't get my launchpad model s to work with it, I tried all the previous commits and found that it did work for commit ae872f3... but not for 3fe8d20 is this expected?

I'm happy to provide more information, thanks for the cool scripts!

Alex

hi,

I am using a launchpad MK1 with the lanuchpad95 and Live 11. I downloaded the script from https://motscousus.com/stuff/2011-07_No ... e_Scripts/
and carefully followed the instructions.

The drum templates (the colors) appear on the launchpad and the sequencer runs and show the notes which are already present in the mdi clip but when I press the buttons nothing change in the midi clip in Live, i.e. I cannot edit (delete or add) notes of the midi clip.
If I press "user 2" button for long time, it also does not turn green, so I cannot access the MelodicStepSequencer.

What could be the problem?
MIDI in/out is already activated in the Live midi preferences.

Hello,

I’m trying to make Launchpad95 Scripts work on Ableton 9.7.1. I have copied the unzipped Launchpad95 folder into /Users/…/Library/Preferences/Ableton/Live 9.7.1/User Remote Scripts/
But in the Preferences/Midi tab I cannot see Launchpad95 script. Only Launchpad is shown which is already seen without custom scripts. Because of that new scripts does not work. What might be the cause?

Hi!

Do you think you could add a fixed length recording option? Like the SRECFIX macro in ClyphX?

Thanks!

Script is not responding with Launchpad S and Live 9.1.2 .
Script name appears on settings but nothing happens when is selected.
Log.txt shows :

11914 ms. RemoteScriptError: warning: Not importing directory 'C:\ProgramData\Ableton\Live 9 Suite\Resources\MIDI Remote Scripts\Launchpad95': missing init.py

11914 ms. RemoteScriptError: Traceback (most recent call last):

11914 ms. RemoteScriptError: File "", line 1, in

11914 ms. RemoteScriptError: ImportError
11914 ms. RemoteScriptError: :
11914 ms. RemoteScriptError: No module named Launchpad95
11914 ms. RemoteScriptError:

I'm thinking that all of the bottom row would have the same delete clip function and that it turns red while being pressed so that any clip can be deleted if it's selected.

This would make it possible to do the most essential clip management directly from the session view.

What do you think about this proposition?

THERE

On just these pads there are 2-3 note positions where the LED light won't change to indicate a note on/off. I moved all the pads down an octave and up an octave and this problem went away both times... so it seems like it's just these two pads. The buttons still function to turn notes on/off but they don't receive an off message it seems, at least on my setup.

Documentation says

Instrument Mode replaces classic User Mode 1. To activate Instrument Controller Mode, press User Mode 1 button (mode button remains amber). Press User Mode 1 button once again, button turns green, activating the Device Controller. Once more the button will turn red, activating the plain old User Mode 1 in case you need it.

However, there is no "User Mode 1" button on the Launchpad X and other newer models.

Instead, the 6th button is labeled "Note".

Mode 1. To activate Instrument Controller Mode, press User Mode 1 button (mode button remains amber).

Assuming that "Note" is the button that should be pressed instead of "Mode 1", the description doesn't match what actually happens:

Pressing the button once shows this pattern, like in the documentation:

But the colors are different. Most buttons are light blue and the highlighted ones are darker blue. So the actual colors of the buttons do not match the colors in the documentation. Either the programming should be changed so that the actual colors match the documentation, or the documentation should be updated, saying which colors to expect on which Launchpad models.

Press User Mode 1 button once again, button turns green, activating the Device Controller. Once more the button will turn red, activating the plain old User Mode 1 in case you need it.

Pressing the same button again goes to dark purple/light purple buttons that seem to act as vertical sliders for something.

Pressing the same button three or more times has no effect, it just cycles between the light/dark blue and the light/dark purple.

At this point I am lost, I cannot see much similarity between what is described in the documentation and what is actually going on on the device.

Hi, first of all your work is great. I can't describe how much I appreciate it. I was almost gonna toss my mk2 away when I found your scripts.

I noticed few things while using launchpad95, I might not know how to use it, or they might be an issue, so here it goes.

• In session mode, if I press one of the clips, track gets armed and I can't disable any clips from it after that.
• In drum/melodic sequencer mode, if i hold mute to extend range with copying, only first loop region gets copied to new ones. I suppose it should copy the ones first clicked to the ones that clicked later. But its always only the first region.

Also, if I can ask a question, whats the purpose of implicit arm? Cant seem to figure it out.