Hoopa Chashi

Chosen Scene Clip Launcher. A plugin that turns clips On/Off in a chosen at the moment (highlighted) scene. 

1. A plugin that allows to use an external (foot, FCB1010) controller buttons on turning On/Off a specific clips in Ableton Live Session view. 

2. Each controller button should launch the clips within one track (vertical line). Button 1 launches clips in the track 1, button 2 in track 2, etc. 

3. This controller button should turn On/Off the clip that belongs to a scene that is chosen at the moment (a horizontal line that highlights when you choose a scene). I think the plugin should look like bunch of numbers (1 through 10, or 20), where each number represents a specific track, and the buttons on the external controller could be mapped to these numbers. And the only thing it will do will be launching a clip that is highlighted in a scene that is chosen at the moment. 

 Chosen Scene Clip Launcher. A plugin that turns clips On/Off in a chosen at the moment (highlighted) scene.  
1. A plugin that allows to use an external (foot, FCB1010) controller buttons on turning On/Off a specific clips in Ableton Live Session view. 
2. Each controller button should launch the clips within one track (vertical line). Button 1 launches clips in the track 1, button 2 in track 2, etc. 
3. This controller button should turn On/Off the clip that belongs to a scene that is chosen at the moment (a horizontal line that highlights when you choose a scene).  I think the plugin should look like bunch of numbers (1 through 10, or 20), where each number represents a specific track, and the buttons on the external controller could be mapped to these numbers. And the only thing it will do will be launching a clip that is highlighted in a scene that is chosen at the moment. 
Thank you.

 Chosen Scene Clip Launcher. A plugin that turns clips On/Off in a chosen at the moment (highlighted) scene.  
1. A plugin that allows to us

need-a-plugin-that-works-like-a-chosen-scene-clip-launcher

Hi Hoopa, I could build such a device. Want to contact me via email? (I don't see an email address for you)

Hi Hoopa, I could build such a device.  Want to contact me via email? (I don't see an email address for you)

Scene Clips.amxd

I just added an email to my account here.

Source Audio, you are a genius! I was trying to explain here the idea on following a chosen (with the Ableton buttons) scene, and wasn't sure if it is even possible to detect by a plugin, and you simply added a scrolling through scenes function to the plugin! As elegant and ingenious as usual!)

By scrolling through the numbers with a mouse I checked the functionality, everything is there. Thank you SO much!

I was trying to add the buttons for around 6 hours. I am really a beginner, was going through different kinds of buttons, but no luck so far.

Could you please add 2 buttons (increasing and decreasing scene numbers) to the blue square, and 10 buttons (each corresponding to the tracks 1 through 10) to the red square.

At first I thought that the Refresh button will change the number of tracks and corresponding buttons, but after trying for 6 hours to assign a button to each number in the red square I realized that number of buttons probably could only be constant.

I just added an email to my account here.

Source Audio, you are a genius! I was trying to explain here the idea on following a chosen (with the Ableton buttons) scene, and wasn't sure if it is even possible to detect by a plugin, and you simply added a scrolling through scenes function to the plugin! As elegant and ingenious as usual!)
By scrolling through the numbers with a mouse I checked the functionality,  everything is there. Thank you SO much!
I was trying to add the buttons for around 6 hours. I am really a beginner, was going through different kinds of buttons, but no luck so far.
Could you please add 2 buttons (increasing and decreasing scene numbers) to the blue square, and 10 buttons (each corresponding to the tracks 1 through 10) to the red square.
At first I thought that the Refresh button will change the number of tracks and corresponding buttons, but after trying for 6 hours to assign a button to each number in the red square I realized that number of buttons probably could only be constant.

With buttons I meant messages from FCB Pedal.

Like if button 1 sends program change 1 on channel 1 than one would convert that to number 0

It makes no sense making visual buttons in the plugin,

each song would have different number of tracks and scenes.

You can click on play/stop in the clip anyway, so why buttons in the plugin ?

Refresh button is there just to ask for number of scenes and tracks and limit

I guess one could automate that when something changes in the Live Song,

With buttons I meant messages from FCB Pedal.
Like if button 1 sends program change 1 on channel 1 than one would convert that to number 0
and so on.
That's what you asked for , right ?
What is FCB pedal sending ?
Can You edit that ?
It makes no sense making visual buttons in the plugin,
each song would have different number of tracks and scenes.
You can click on play/stop in the clip anyway, so why buttons in the plugin ?
---
Refresh button is there just to ask for number of scenes and tracks and limit
int boxes range.
I guess one could automate that when something changes in the Live Song,
but let's not overcomplicate that.


There are 12 physical buttons on the pedal. They all (by my initial idea) will be MIDI mapped to the actual (mappable) buttons in the plugin interface. 

2 of them will be constantly dedicated to the increasing/decreasing the number in the blue square (switching the scenes), they are always the same 2 (up and down).

The remaining 10 could be mapped to the 10 MIDI mappable buttons in the plugin where each button always represents the same track (button 1 for track number 1, button 2 for track 2, etc.)

Ableton Live has Toggle as one of the options for launching the clips, which allows to Start/Stop a clip by pressing the same button. That's why the Launch button sitting now next to the red square might not be even needed at all, because the way the plugin is working now allows me to click on the number in the red square, advance to any number, and while simply releasing the mouse button it triggers the Start/Stop action at the corresponding track, at the previously chosen in the blue square song number. So, basically, if there was a MIDI mappable button for every number in the red square then everything would be usable right away.

The presence of the Refresh button made me think that the range of numbers in both squares will be adjustable according to the number of current scenes and tracks, but since the same controller's buttons launch clips in the same track I wasn't sure if this more advanced flexible clip numbers version would make me remap every button after pressing the Refresh button.

There are 12 physical buttons on the pedal. They all (by my initial idea) will be MIDI mapped to the actual (mappable) buttons in the plugin interface. 
2 of them will be constantly dedicated to the increasing/decreasing the number in the blue square (switching the scenes), they are always the same 2 (up and down).
The remaining 10 could be mapped to the 10 MIDI mappable buttons in the plugin where each button always represents the same track (button 1 for track number 1, button 2 for track 2, etc.)
Ableton Live has Toggle as one of the options for launching the clips, which allows to Start/Stop a clip by pressing the same button. That's why the Launch button sitting now next to the red square might not be even needed at all, because the way the plugin is working now allows me to click on the number in the red square, advance to any number, and while simply releasing the mouse button it triggers the Start/Stop action at the corresponding track, at the previously chosen in the blue square song number. So, basically, if there was a MIDI mappable button for every number in the red square then everything would be usable right away.
The presence of the Refresh button made me think that the range of numbers in both squares will be adjustable according to the number of current scenes and tracks, but since the same controller's buttons launch clips in the same track I wasn't sure if this more advanced flexible clip numbers version would make me remap every button after pressing the Refresh button.

Source Audio is right, you probably don't want to do the MIDI mapping thing.

If you use MIDI mappable buttons you'll end up recording automation of your button presses, which may have undesirable results when you playback (unless during playback you are selecting the same scene as when you recorded).

You may be (probably are) better off just taking MIDI input from your pedal and parsing the MIDI CC information to determine when you fire / toggle a clip on a track. Also, if you set up the device this way then once you save your device you don't need to redo the MIDI Mapping of the pedal buttons every time you want to use the device in a new project. You could still build button UI into the device if you really wanted it, just mark it 'hidden' for its parameter mode.

If you use MIDI mappable buttons you'll end up recording automation of your button presses, which may have undesirable results when you playback (unless during playback you are selecting the same scene as when you recorded).  

You may be (probably are) better off just taking MIDI input from your pedal and parsing the MIDI CC information to determine when you fire / toggle a clip on a track.  Also, if you set up the device this way then once you save your device you don't need to redo the MIDI Mapping of the pedal buttons every time you want to use the device in a new project.  You could still build button UI into the device if you really wanted it, just mark it 'hidden' for its parameter mode.

Regarding the recording automation of the button presses. Just would like to emphasize that this setup will be used for a live performance only. A playback, no recording. Do you think in that case the recording problem might still accure?

Regarding the CC instead of MIDI mapping. I think you are right, it should keep the chosen on the controller buttons assigned to the same 10 tracks. Should those CC's be hardwired into the plugin, or could they be assignable?

There is one thing I noticed: the plugin the way it is now is 99% functional, but when I release the mouse on any number in the red square (the tracks choice) it perfectly starts that clip, but if I do the same and choose the same number it wont stop the clip (in the Toggle mode). Only after I Start/Stop any other clip and then come back to the one I started in the beginning the clip will stop playing (in the Toggle "Same button Start/Stop" mode).

Tyler, thank you so much for your reply!
Regarding the  recording automation of the button presses. Just would like to emphasize that this setup will be used for a live performance only. A playback, no recording. Do you think in that case the recording problem might still accure?
Regarding the CC instead of MIDI mapping. I think you are right, it should keep the chosen on the controller buttons assigned to the same 10 tracks. Should those CC's be hardwired into the plugin, or could they be assignable?
There is one thing I noticed: the plugin the way it is now is 99% functional, but when I release the mouse on any number in the red square (the tracks choice) it perfectly starts that clip, but if I do the same and choose the same number it wont stop the clip (in the Toggle mode). Only after I Start/Stop any other clip and then come back to the one I started in the beginning the clip will stop playing (in the Toggle "Same button Start/Stop" mode).


To stay flexible I'd just store the CC numbers in live.numbox objects in parameter mode 'stored only'. That way you can (a) set initial values to be what you currently use and (b) change them on the fly later if needed. Then you can store 'preset' of the M4L device with different CC configurations later if need be.

To stay flexible I'd just store the CC numbers in live.numbox objects in parameter mode 'stored only'.  That way you can (a) set initial values to be what you currently use and (b) change them on the fly later if needed.  Then you can store 'preset' of the M4L device with different CC configurations later if need be.

If you look at the code inside of that amxd it is so minimal and simple.

The only challenging task was to build a list of scene numbers-IDs

because for whatever reason they don't match in Live.

Scenes get assigned some ID, don't ask me why

and can't be scrolled by their position so simply.

I decided for testing purpose to just toggle the state of the clip.

So when track number (red int box) gets fired it asks that clip if it

is running or not, and toggles the state.

So all you need is that 10 midi values coming from the pedal

to fire one of 10 tracks, and 2 midi values to scroll scenes.

That should be a simple enough task, right ?

Being manual control, there is no need to record or automate anything.

It schould be surely possible to make a midi learn or just some sort of selector for the

12 values, but this is your plugin and your pedal, so you can program it the way you want.

That is normal behaviour of Max number object when set value

You don't want to trigger stuff while scrolling to reach desired value,

that's why it is set to output on mouse up only.

The button left to the red number is there to repeatedly

trigger same number without the need to go in and scroll again.

The way tracks get stoped is dependent on launch parameters for the clips and quantisation.

Scene number/ID detector is needed if you want to use scroller

to select scenes, track number detect can be removed, there will be only 10 buttons,

and if one fires into non- existing track it anyway gets ignored.

If you can't manage to insert midi values from that pedal post exactly

what it is sending and I'll add that into patch.

If you look at the code inside of that amxd it is so minimal and simple.
The only challenging task was to build a list of scene numbers-IDs
because for whatever reason they don't match in Live.
Scenes get assigned some ID, don't ask me why
and can't be scrolled by their position so simply.
-----
I decided for testing purpose to just toggle the state of the clip.
So when track number (red int box) gets fired it asks that clip if it
is running or not, and toggles the state.
So all you need is that 10 midi values coming from the pedal
to fire one of 10 tracks, and 2 midi values to scroll scenes.

That should be a simple enough  task, right ?
Being manual control, there is no need to record or automate anything.
It schould be surely possible to make a midi learn or just some sort of selector for the
12 values, but this is your plugin and your pedal, so you can program it the way you want.
-----
There is one thing I noticed: the plugin the way it is now is 99%  functional, but when I release the mouse on any number in the red square  (the tracks choice) it perfectly starts that clip, but if I do the same  and choose the same number it wont stop the clip (in the Toggle mode).  Only after I Start/Stop any other clip and then come back to the one I  started in the beginning the clip will stop playing (in the Toggle "Same  button Start/Stop" mode).
That is normal behaviour of Max number object when set value
is not changed.
You don't want to trigger stuff while scrolling to reach desired value,
that's why it is set to output on mouse up only.
The button left to the red number is there to repeatedly
trigger same number without the need to go in and scroll again.
With footpedal, that would be obsolete.
------
The way tracks get stoped is dependent on launch parameters for the clips and quantisation.
-------
Scene number/ID detector is needed if you want to use scroller
to select scenes, track number  detect can be removed, there will be only 10 buttons,
and if one fires into non- existing track it anyway gets ignored.
--------
If you can't manage to insert midi values from that pedal post exactly
what it is sending and I'll add that into patch.


Here is next one, only midi from pedal shoul be added

Clip-Launcher.amxd

If scenes change it will auto refresh IDs and reselect scene 0

Hold Up / Down button auto scrolls im 250 ms interval

Patch had a mistake inside, reuploaded it fixed

Here is next one, only midi from pedal shoul be added


If scenes change it will auto refresh IDs and reselect scene 0
Hold Up / Down button auto scrolls im 250 ms interval
------------
Patch had a mistake inside, reuploaded it fixed


Source Audio, thank you so much for such great plugin!

The code might be minimal, but the functionality is very important for a live performance.

Launching a clip will start a song, and having the buttons assigned to the same groups of instruments in every scene will allow to hide the computer out of view.

Please assign the CC's 22 to 31 to the clip launching buttons, and 84, 85 to the scene scrolling buttons.

I will look at the code to see where the values entered, and change the numbers if ever needed.

Source Audio, thank you so much for such great plugin!
The code might be minimal, but the functionality is very important for a live performance.
Launching a clip will start a song, and having the buttons assigned to the same groups of instruments in every scene will allow to hide the computer out of view.
Please assign the CC's 22 to 31 to the clip launching buttons, and 84, 85 to the scene scrolling buttons.
I will look at the code to see where the values entered, and change the numbers if ever needed.

assuming that all pedal switches send > 0 when pressed and 0 on release

22 -31 trigger 0 - 9 on pedal down, 84 & 85 activate Down & Up buttons.

Screen Shot 2020-06-06 at 09.01.07.png

midi router is the left one, it could have done a bit simpler, like the blue part

on the right, if CC numbers for 10 clip launchers were left as consecutive numbers.

assuming that all pedal switches send > 0 when pressed and 0 on release
22 -31 trigger 0 - 9 on pedal down, 84 & 85 activate Down & Up buttons.


midi router is the left one, it could have done a bit simpler, like the blue part
on the right, if CC numbers for 10 clip launchers were left as consecutive numbers.
But to stay flexible the left route 22 23 24 25 26 27 ... 84 85 
can be easily edited to any CC# number


Source Audio, I changed the CC numbers on the green strip, saved the file, restarted Max, opened the plugin, and the new numbers were saved! Thank you very much!

The "0"'s underneath represent the value, so, I can change them to 127 if needed, right?

At this time the plugin does not launch the clips when I change the CC numbers on the green strip, nor when I keep them 22 to 31, and match the CC numbers on a controller.

The same with the numbers 84 and 85, they do not move the scene line up and down, and they are after the range 22 to 31, shouldn't they be at or by the squares Down and Up?

The controller board has 12 buttons, and which ones will be used for the scenes line moving or for the clips launching is just the matter assigning a CC numbers to them.

 Source Audio, I changed the CC numbers on the green strip, saved the file, restarted Max, opened the plugin, and the new numbers were saved! Thank you very much!
The "0"'s underneath represent the value, so, I can change them to 127 if needed, right?
At this time the plugin does not launch the clips when I change the CC numbers on the green strip, nor when I keep them 22 to 31, and match the CC numbers on a controller.
The same with the numbers 84 and 85, they do not move the scene line up and down, and they are after the range 22 to 31, shouldn't they be at or by the squares Down and Up?
The controller board has 12 buttons, and which ones will be used for the scenes line moving or for the clips launching is just the matter assigning a CC numbers to them.

You have to upload the patch for me to see what is wrong with it.

If it did, than you made some mistake modifying the patch.

10 trigger buttons only trigger when pedal is pressed, 

and 2 buttons for scrolling the scenes need both up & down pedal detection to work.

And post once exactly what the pedals are sending .

what number when pressed, what when released.

 is as clear as blue sky - means is incoming number greater than zero,

You have to upload the patch for me to see what is wrong with it.
As first, did my original patch work ?
If it did, than you made some mistake modifying the patch.
10 trigger buttons only trigger when pedal is pressed, 
and 2 buttons for scrolling the scenes need both up & down pedal detection to work.
Is that understandable ?
And post once exactly what the pedals are sending .
what number when pressed, what when released.


the > 0 is as clear as blue sky - means is incoming number greater than zero,
If yes than output 1 if not then 0. sel 1 makes a bang and so triggers the clip.



Wait, I just discovered something very strange with midi objects in Max 8

at least on Mac , IAC buss in use for testing, midi data comes inverted

if I send 176 22 $1 to midiout, ctlin outputs cc value 176 - non existing

Tried same patch with max 7 and Max 6 everything perfect.

I realised something like that some days ago using midiselect

on seq playback, output also went scrumbled, had to switch to traditional

match 144 nn nn to get notes out right, but now I see it is more than just that.

It seems if one uses midiin with midiparse, it works partly, but midiin with thresh not

Also received value through midiparse is less than sent one

Screen Shot 2020-06-07 at 15.35.13.png

If one uses ctlout to send it works as expected

Screen Shot 2020-06-07 at 15.37.20.png

Is that problem with the plugin in Live ?

Same patch, same IAC Buss, same time - max 7.3.6

Screen Shot 2020-06-07 at 15.44.48.png

Wait, I just discovered something very strange with midi objects in Max 8
at least on Mac , IAC buss in use for testing, midi data comes inverted
if I send 176 22 $1 to midiout, ctlin outputs cc value 176 - non existing
Tried same patch with  max 7 and Max 6  everything perfect.
I realised something like that some days ago using midiselect
on seq playback, output also went scrumbled, had to switch to traditional
match 144 nn nn to get notes out right, but now I see it is more than just that.

It seems if one uses midiin with midiparse, it works partly, but midiin with thresh not
Also received value through midiparse is less than sent one


If one uses ctlout to send it works as expected


Is that problem with the plugin in Live ?
Same patch, same IAC Buss, same time - max 7.3.6

Well, anyway I even don't know if that is causing your problem or not,

I restarted Max and Mac, it works as expected now, 

maybe launching Live made IAC Buss go nuts, who knows.

So upload the patch with your changes, and maybe infos on computer in use- mac or pc 

Well, anyway I even don't know if that is causing your problem or not,
I restarted Max and Mac, it works as expected now, 
maybe launching Live made IAC Buss go nuts, who knows.
So upload the patch with your changes, and maybe infos on computer in use- mac or pc 


Source Audio , thank you SO much!! Everything is working perfectly! Just the way described, and again even better than described: you added the Fire Selected Scene and the Track buttons.

The problem was that I was testing it with a track Monitor Auto button on (turns on by default), but the plugin should be used with the Monitor In. I am sorry that it caused the misunderstanding on my side.

So many hours I was sitting and going through your notes and trying to see what settings have I done wrong while it was simply the Monitor In..)

You mentioned in one of your notes: If scenes change it will auto refresh IDs and reselect scene 0 Hold Up / Down button auto scrolls im 250 ms interval.

I will count on Global Quantize and hit the Scene Change pedal anywhere in a previous bar, so, 250ms scrolling wont be needed (I think). If I hold the button a little longer it might jump to the next scene. 

Where can I increase this Scene Change pedal hold time for like a full second?

Again, thank you SO much, you are absolutely incredible!

 Source Audio , thank you SO much!! Everything is working perfectly! Just the way described, and again even better than described: you added the Fire Selected Scene and the Track buttons.
The problem was that I was testing it with a track Monitor Auto button on (turns on by default), but the plugin should be used with the Monitor In. I am sorry that it caused the misunderstanding on my side.
So many hours I was sitting and going through your notes and trying to see what settings have I done wrong while it was simply the Monitor In..)
You mentioned in one of your notes:  If scenes change it will auto refresh IDs and reselect scene 0 Hold Up / Down button auto scrolls im 250 ms interval.
I will count on Global Quantize and hit the Scene Change pedal anywhere in a previous bar, so, 250ms scrolling wont be needed (I think).  If I hold the button a little longer it might jump to the next scene. 
 Where can I increase this Scene Change pedal hold time for like a full second?
Again, thank you SO much, you are absolutely incredible!

250 ms is set in patcher sceneSel, just below the actual buttons.

You have to set it show on lock, lock the patch , then doubleclick on it

either increase 250 in metro. or disconnect metro output,

Would 1 second interval make sense at all ?

So you could remove it totaly ( I mean auto scroll)

but if number of scenes changed or they were rearanged in the list.

If so, than number of scenes gets rescanned and scroll max refreshed.

It has nothing to do with selection of the scenes.

You have to set it show on lock, lock the patch , then doubleclick on it
to open and edit it.
either increase 250 in metro. or disconnect metro output,
to disable auto -scroll.
Hide on Lock when done ...

Would 1 second interval make sense at all ?
One would be much faster tapping.
So you could remove it totaly ( I mean auto scroll)
 -------
What I meant with "if scenes change" 
is not if any scene is selected,
but if number of scenes changed or they were rearanged in the list.
If so, than number of scenes gets rescanned and scroll max refreshed.
It has nothing to do with selection of the scenes.



Source Audio, thank you so much for your reply!

There will be no computer in front of me during a live performance, so, I wont know what scene the scene scroller stopped at. I will simply arrange the song sequence the way I want beforehand, but the live performance conditions are pretty hard to control sometimes, so, to hold a pedal for less than 250ms might be not 100% of the time convenient.

I followed your instructions and adjusted the hold time perfectly. Thank you so much!

Now, testing the plugin I see that certain things turned out to be better than expected (launching the clips buttons work as if the Toggle mode was already selected, so, it is not necessary to set this mode for every clip one by one), and also I see that the Fire Selected Scene button you incorporated makes much more sense because depending on a scene you want to start it with one instrument or all of them playing right away.

Could we please have the Fire Selected Scene button as the 13th button on the green strip? I switched to the Roland PK 5A, and it is a 13 buttons controller, so, it will make perfect sense)

 Source Audio, thank you so much for your reply!
There will be no computer in front of me during a live performance, so, I wont know what scene the scene scroller stopped at. I will simply arrange the song sequence the way I want beforehand, but the live performance conditions are pretty hard to control sometimes, so, to hold a pedal for less than 250ms might be not 100% of the time convenient.
I followed your instructions and adjusted the hold time perfectly. Thank you so much!
Now, testing the plugin I see that certain things turned out to be better than expected (launching the clips buttons work as if the Toggle mode was already selected, so, it is not necessary to set this mode for every clip one by one), and also I see that the Fire Selected Scene button you incorporated makes much more sense because depending on a scene you want to start it with one instrument or all of them playing right away.
Could we please have the Fire Selected Scene button as the 13th button on the green strip? I switched to the Roland PK 5A, and it is a 13 buttons controller, so, it will make perfect sense)

Screen Shot 2020-06-10 at 13.43.45.png

I added an option to hold the Fire Scene button longer than 1000 ms

to reset scene counter and recall scene 0

You can easily remove it as shown, if that does not serve you,

Clip-Scene-Launcher.amxd

I can't test this in Live at the moment,
but it should work I hope.
I added an option to hold the Fire Scene button longer than 1000 ms
to reset scene counter and recall scene 0
You can easily remove it as shown, if that does not serve you,
or change hold time...


After holding the Fire Selected Scene button over 1 second the scene choice jumps to the 1st scene.

At first I thought that this function should be given to the Scroll Up the scene button, but later I I realized that the Fire Selected Scene button will not be used as much and its extra function of choosing the 1st scene line after holding it over a second is appropriate.

Overall this is a very interesting feature to play with, makes me want to arrange the scenes in more evolving way).

 Source Audio, thank you so much!
Everything works great!
After holding the  Fire Selected Scene button over 1 second the scene choice jumps to the 1st scene.
At first I thought that this function should be given to the Scroll Up the scene button,  but later I I realized that the  Fire Selected Scene button will not be used as much and its extra function of choosing the 1st scene line after holding it over a second is appropriate.
Overall this is a very interesting feature to play with, makes me want to arrange the scenes in more evolving way).
More creative tool than just a launcher)
Thank you SO much!

Source Audio, I use Behringer Motor as a 2nd keyboard, because it has 8 motorized sliders. If a song has more than 8 active tracks the Motor makes a new page with every new 9th track, and then I can scroll through the pages with 2 buttons (increasing/decreasing the numbers of pages).

The Motor is connected to the Ableton with Mackie Control protocol, so, the keyboard's sliders control the tracks levels, and the tracks levels control motorized sliders, transporter, e.t.c.

Do you think there is any way to synchronize the first 8 tracks launch buttons in this plugin with a chosen sliders page?

In other words, if page 3 in the sliders pages scroller is chosen could the button 2 turn On/Off the second track on that 3rd page (track 18 in actuality)?

This way the 8 sliders on the Motor will always correspond to the first 8 launch buttons of this plugin, no matter what page is chosen.

 Source Audio, I use Behringer Motor as a 2nd keyboard, because it has 8 motorized sliders. If a song has more than 8 active tracks the Motor makes a new page with every new 9th track, and then I can scroll through the pages with 2 buttons (increasing/decreasing the numbers of pages).
The Motor is connected to the Ableton with Mackie Control protocol, so, the keyboard's sliders control the tracks levels, and the tracks levels control motorized sliders, transporter, e.t.c.
Do you think there is any way to synchronize the first 8 tracks launch buttons in this plugin with a chosen sliders page?
In other words, if page 3 in the sliders pages scroller is chosen could the button 2 turn On/Off the second track on that 3rd page (track 18 in actuality)?
This way the 8 sliders on the Motor will always correspond to the first 8 launch buttons of this plugin, no matter what page is chosen.

I am sure that something you ask can be done,

I don't get the relation sliders - launch buttons

Hardware buttons on behringer or abletons GUI buttons ?

In any case one should use page number to shift control of that

I am sure that something you ask can be done,
but have no idea how to go about it.
I don't get the relation sliders - launch buttons
What are track launch buttons ?
Hardware buttons on behringer or abletons GUI buttons ?
In any case one should use page number to shift control of that
"launch buttons"


By the "launch buttons" I mean the 10 buttons in this plugin that were controlled in the red box. Now they have assignable CC #'s on the green strip, 22 through 31.

There are 2 kinds of control in this plugin: one goes through the scenes (Up and Down), the other launches (Starts/Stops) the clips within a chosen scene (left and right). This second kind of the buttons I call a "launch buttons".

The way the plugin is now it launches (Starts/Stops) the first 10 clips in a chosen scene, I am hopping that there could be a way to Start/Stop the clips that are currently chosen by the page scroller in the Motor, within the scene chosen in the scene selector.

By the "launch buttons" I mean the 10  buttons in this plugin that were controlled in the red box. Now they have assignable CC #'s on the green strip, 22 through 31.
There are 2 kinds of control in this plugin: one goes through the scenes (Up and Down), the other launches (Starts/Stops) the clips within a chosen scene (left and right). This second kind of the buttons I call a "launch buttons".
The way the plugin is now it launches (Starts/Stops) the first 10 clips in a chosen scene, I am hopping that there could be a way to Start/Stop the clips that are currently chosen by the page scroller in the Motor, within the scene chosen in the scene selector.

then you need to retreive that "page number".

The Scene-Clip launcher receives midi from footpedal

so it can't receive midi from control surface as well.

I don't use live but can't remember seeing any pages splits

so that footpedal routes the page number infos

2- check if Live would be able to route that page number

to Scene-Clip plugin internaly, by automation or something else ?

one can easily add renumbering of the 10 buttons, once you kow how to get that info into the plugin.

then you need to retreive that "page number".
The Scene-Clip launcher receives midi from footpedal
so it can't receive midi from control surface as well.

I don't use live but can't remember seeing any pages splits
for more than 8 tracks..
So how do we get there ?
Maybe playing with automation in Live ?
You have to find that out.
One can try it 2 ways :
1- merge midi from motor and footpedal
so that footpedal routes the page number infos
to the Scene-Clip plugin
2- check if Live would be able to route that page number
to Scene-Clip plugin internaly, by automation or something else ?

one can easily add renumbering of the 10 buttons, once you kow how to get that info into the plugin.



To my surprise this Up/Down Sliders Page Scroller physical buttons do send a MIDI signal, the MIDI indicator in Live shows a signal going in AND out of Live when I click these Up/Down buttons.

But when I try to map them to any button in Live it is not doing it (I hopped that it will show me some CC#).

What kind of a MIDI signal could be sent, and where in a DAW it could be registered and analysed (if it does not send a CC#)?

To my surprise this Up/Down Sliders Page Scroller physical buttons do send a MIDI signal, the MIDI indicator in Live shows a signal going in AND out of Live when I click these Up/Down buttons.
But when I try to map them to any button in Live it is not doing it (I hopped that it will show me some CC#).
What kind of a MIDI signal could be sent, and where in a DAW it could be registered and analysed (if it does not send a CC#)?

The Motor controls the Live by the Mackie Control protocol, I don't know much about it, but I think because of that the buttons (that are acting through the MC protocol) will not show a CC#, right?

If so, is there any way to still get a hold of them anyway?

The Motor controls the Live by the Mackie Control protocol, I don't know much about it, but I think because of that the buttons (that are acting through the MC protocol) will not show a CC#, right?
If so, is there any way to still get a hold of them anyway?

make max4live device with midiin and thresh and message.

Screen Shot 2020-06-18 at 13.02.43.png

If you would be more informative about that gear,

I would plug midi out of the footpedal to that motor

behringer thing, merge it's midi with motor output and 

But I have no idea what this units can do and if that is possible.

Anyway, the main problem is Live and it's midi routing restrictions

Need a plugin that works like a Chosen Scene Clip Launcher