APC40 - Step Sequencer, Note Mode, 2nd Device Control, etc.

[flippo]

As for the 'but it might be easier to forward the default note for this button, since it’s already sending out a note on each press' - did not think that was thew case? When looking through midi-ox, it seems to prompt the device control knobs to send out an update of their CC values for channel 9, rather than actually sending out its own note. As these values are constantly different I cant use bomes to trigger a note

I'll try to take a look at options for implementing some kind of feedback - or alternatively, a way of forwarding the Master button's MIDI messages (since they are currently getting swallowed...), when I get a chance.

Best,

Hanz

PS: If you MIDI-map the Master button, you'll see that it is sending Note 80 (G#4) on channel 1.

Ahhh, this only happens after a live remote script is activated.



If you turn on the APC without loading up a remote script you get the following output from the master button.



And recorded direct from live into either track or remote it's the same.




But, if you then load up an APC remote script it begins outputting G#4 instead. Strange thing is, if you then de-activate the remote script it still sends G#4, and even if you close live it still sends out G#4. Only if you power down and power on again will it revert back to sending out CCs 16-23. I'm a bit confused as to how that actually works, I guess the remote script leaves an imprint somehow? Regardless of that it means I can now probably use bomes to provide the extra note value I need to run the light feedback from live, just have to do a little dicking around each time I start up a session.

By the way, that's very kind of you to offer to work that out. Please do not feel obliged to do so just for me, however! you've done plenty enough already

[flippo]

success! I can send out an extra note available to assign as remote control, and it does not interfere with activating the python user mode

[dna598]

I m no coder, But I would like to know if you could arrange the lights in the note mode to just be just one colour for the 4x4 drum rack?

Makes it easier to look at....

[Hanz_Petrov]

Based on the suggestions that you all have made, I’ve built a working beta script with 8 “pages” for the various matrix modes - but now I'm not sure what to do with them all. So far, here’s where I’m at (the modes are now selected via Shift + Track Select):

Shift + Track Select 1 = Clip launch (the default mode)
Shift + Track Select 2 = Session Overview (now a toggled mode, no longer shifted)
Shift + Track Select 3 = Note Mode (now extended to include the Stop Clip buttons, for a 6x8 matrix, or 4 complete octaves), on Channel 10
Shift + Track Select 4 = Note Mode, Channel 11
Shift + Track Select 5 = Note Mode, Channel 12
Shift + Track Select 6 = Note Mode, Channel 13
Shift + Track Select 7 = Note Mode, Channel 14
Shift + Track Select 8 = Note Mode, Channel 15

Some of the Note Mode pages could become User Mode pages (for MIDI-mapping, without note sends, like the Launchpad’s User 2 mode). Some could include the Stop Clip buttons as part of the matrix (others might not, so that the Stop Clip buttons continue to function in Note Mode); some could have the notes laid out sequentially - left-to-right & top-to-bottom (instead of being 4-tracks wide, like a drum rack); each individual page could have a different colour pattern.

Not including the Clip Launch and Session Overview pages, there are 6 pages of 6x8 buttons available for assignment – that’s 288 buttons! Any thoughts on useful layouts would be welcome.

Best,

Hanz

[Semuta]

Checking out your 40 20 script, and so far I am totally impressed. Things that could be different:


Cue level controls fine tempo normally, course tempo when shifted. -nevermind, I read more of your site, and I think I understand why this works this way.

I think it would be cool if the LED feedback in the clip matrix represented black keys and white keys instead of simply alternating colors.

I haven't figured out if there's a way to transpose the note mode or set velocity?

I didn't find a copy of your beta script (at least I don't seem to be able to change what the note mode is doing with the channel select keys -using r4 of your script)

So cool! It's like a whole new device!

S

[HeadrickProductions]

I second the note mode having different colors for the minor/flat

[Semuta]

How hard would it be to create a script that made the track control knobs and buttons into the same thing as the device control knobs and buttons. The idea would be so that you can lock the two groups to different racks and devices on the
fly.

Maybe in the form of two separate control surface scripts?

I've never had much use for the Track controls myself.

S

[dna598]

Yeah, i NEVER use the track controls.

I WOULD use them if they operated with the currently selected track, and moved sends 1 through 8 for example.

Any way to get this "per track" functionality??

Sorry for the questions, I am just loving this custom apc action, just I'm not clever or patient enough to do it myself!

[HeadrickProductions]

I sent hanz a bunch of ideas but one idea I liked (if it's possible)

have an entire section that was devoted to production and performance shortcuts.

Something like being able to select sample/instruments/audio/midi effects without having to grab the mouse
It would only take 5 buttons or so. an up down select shift buttons to grab multiple samples

also something for loop control
being able to set loop, adjust loop length, etc

some shortcut for closing and opening vst's (hate the three key shortcut)

zoom in zoom out

open group racks/drum racks/instrument rack in session view


maybe insert/audio/midi tracks

just ideas that would save up all a lot of mouse play no matter if you use it for performance or productions



Let's toss some more ideas around since hanz is nice enough to ask for our input to make this already solid piece of hardware MUCH better.



Really like the idea of being able to lock multiple devices, had not thought of that one

[flippo]

Hanz yoiu're a gem. I was going to ask you if you could help me get some extra pages going.

As for what should be on them, I have a few ideas but I think they probably would not suit most peoples existing setups. Personally I will be diving into the code and adjusting the notes and colours myself.

I recon given that everyone is likely better off minimizing perpetual modification requests by making a simple tutorial to explain which parts of the code provide the notes and colour patterns and letting people design their own? I think it would be less work for you and get the best result for users aswell.

Give a man a fish/teach a man to fish etc.


Otherwise, a I do have a few ideas for the types of things mapping could be used for, and you might want to think about what message/colour configurations would make the best sense to allow them to be used as such.

- EQ3 kills for each channel
- adjusting in/auto/off for each channel.
- vertical columns of consecutive notes to provide stepped control over a continuous parameters for each track (could be used for effect wet/dry etc)
- horizontal rows of consecutive notes to provide higher resolution stepped control of a continuous parameter.
- blocks of colored buttons; solid color used for on/off of an effect, flashing used for parameter control of said effect.


Just a quick question if you wouldn't mind - I can't really use many more notes on other midi channels as they will interfere with my other mappings - so I will be squeezing the user modes onto as few midi chans as possible. I'd have a great capacity for this if I could assign CC values to the squares instead of notes. Would this be relatively easy to code? If you know how, could you possible give me an example of the code or point me to where it might exist in the other scripts?

[HeadrickProductions]

- EQ3 kills for each channel
- adjusting in/auto/off for each channel.
- vertical columns of consecutive notes to provide stepped control over a continuous parameters for each track (could be used for effect wet/dry etc)
- horizontal rows of consecutive notes to provide higher resolution stepped control of a continuous parameter.
- blocks of colored buttons; solid color used for on/off of an effect, flashing used for parameter control of said effect.

The first two are great ideas.

Could you explain what you mean by the other three.



You gonna offer up the python script you've been working on to the public once it's done??

[Semuta]

Ok, so I hacked up what I want. Almost. I used the Nocturn remote script and by substituting the correct base numbers and channels, I have the Track Control group following the selected device, able to browse the first four banks of parameters.

In the APC40 scripts, I removed all references to the tap tempo button as well as the Global controls and mode settings. I setup the metronome button as the device lock for the Device Control group.

I want to use the tap tempo button to lock the device for the Device Control group, but the nocturn script doesn't seem to provide this facility for me to bastardize.

Help?

S

[Hanz_Petrov]

Thanks for the suggestions guys. I can only realistically implement some of the easier stuff (due to time/motivation/skill constraints), but I’ll do what I can. Plus, some things simply can’t be done using Python scripts alone, particularly where the LiveAPI does not allow.

On the other hand, user modifiable matrix colour and note/cc mapping should be relatively simple. Also, I had already started on shifted reassignment for the Track Control encoders (the next obvious target for customization) - but I wanted to get the matrix pages done first…

I’ll upload new betas soon.

Best,

Hanz

[Markemark]

Hey Hanz, I agree with everyone else this is great work, maybe include some documentation/applications in the future downloads, this way we can start to do some modes on our own(learn to fish). What where you thinking about doing with the Track Control section???

[Semuta]

Thanks for all that you do Hanz! This is awesome. As it turns out in my hacking up of your scripts and fiddling with the nocturn script, I break the shifted functions... :oops:

I'm no programmer, so instead I offer my thanks for your work and I'll be looking forward to your future scripts. I really like how you are approaching this device. Many of the really tricky m4l mods for the APC are too complex. There isn't anything to tell me what all the knobs and buttons are doing in a particular mode and my memory isn't too good... This is very straightforward stuff that seems to follow the logic of the device interface really well.

S!