Question? I need Help Implementing my TouchOSC replica of the AKAI APC40 MK2 with abelton.

548 viewsCSS Controller TemplatesAPC40Mk2
0
0 Comments

>>>Project will continue soon 🙂 got a new device.
Because my 2016 iPad Air 2 is on it’s last leg the display is see trough like a ghost showing the home screen while app is open.<<<

Note. This Post has been edited and the bellow answered questions will be different from the first initial question being answered.
The reason being is I don’t wish create another post and flood the communities blog with similar questions scattered around so it’s more inline of my questions. Thank you kindly for understanding.

My TouchOSC – APC40 MK2 Replica Controller

Mixer View – Highlighted Yellow coloured tab under Pan encoders.

Mixer View – Highlighted Yellow coloured tab under Pan encoders Showing Sends.

Pads grid, Scene select button on the right, Stop clip & Track Select below.

Transport control & FX encoders. 

My modified CSS APC40 MK2 template

Duplicated the PAN encoders added containers & moved FX encoders which were hidden behind the 8 controllers.

I’m trying to create a custom script for the Apc40 Mk2 to work with my custom recreated version of the Apc40 Mk2 in TouchOSC.

The challenging parts for me are wrapping my head around the vast majority of options available and their implementations such as the modifiers/ action/ functions and reactions stuff. But I will try my hardest.

What I have trouble with implementing so far are some of the actual Apc40 Mk2 controllers paremeters/features below:

  1.  Track Select button
    (Not sure if this is the right way. But I used the Highlight Navigation mapping type and it semi works. I’m only able to select the tracks 1-8 but outside of the sessionbox).
    So my question really is how would I implement them so they work while being selected where ever the session box is?
    From Akais Apc40 Mk2 manual:Press and hold (emphasis on the SHIFT button) Shift and then press one of the first eight Track Selectors to select a Global Quantization setting: None, 8 Bars, 4 Bars, 2 Bars, 1 Bar, 1/4, 1/8, or 1/16.
  2. Pan, Send, User buttons
    (On the Apc40 Mk2 the Pan Encoders act as Send and User by being activated with the SEND or USER buttons).
    How can I set them up the same way as on the apc40 mk2 so they switch between their states and which Im assuming are Banked & Grouped together but work independently meaning depending on their state selection?
    For example when I move the SEND A Encoder on my touchosc controller only the sends are activated/triggered they work.
    But when I try the created User Encoders (keep in mind as mentioned above) they are currently just copies of the PAN encoders and have the same Midi CC values they move the PAN encoder in Abelton, to what CC numbers would I have to change the midi cc messages for the encoders so they don’t clash?

    From Akais Apc40 Mk2 manual:    Assignable Knobs: Use these knobs controls track panning, track send levels, or other user- assignable parameters. Press the Pan button, Sends button, or User button to put the these knobs in the corresponding mode (described below).Pan:
    Press this button to put the Assignable Knobs in Pan Mode, allowing them to control the panning positions of the current eight tracks.Sends.
    Press this button to put the Assignable Knobs in Sends Mode, allowing them to control the levels of Send A for the current eight tracks.You can select a different send by pressing and holding Sends and then pressing a Track Selector (Track Selector 1 will select Send A, Track Selector 2 will select Send B, etc.).User: Press this button to put the Assignable Knobs in User Mode. You can then assign them in Live’s MIDI Map Mode, allowing them (while in User Mode) to control whatever mappable parameters you want.
  3. SEND button
    For Now I’ve coppied the Pan Encoders x2 in the CSS template and set them up as,
    using the Track Send Mapping to control 1-8 Track Sends A, B, C, D, E, F, G, H.Only work in Track Selected state.

    From Akais Apc40 Mk2 manual:
    (To adjust send levels, press the Sends button to put APC40 mkII’s Assignable Knobs in Sends Mode, allowing them to control the levels of Send A for the current eight tracks.You can select a different send by pressing and holding Sends and then pressing a Track Selector (Track Selector 1 will select Send A, Track Selector 2 will select Send B, etc.).To use the Assignable Knobs to control other functions, press the User button to put APC40 mkII’s Assignable Knobs in User Mode. You can then assign them in Live’s MIDI Map Mode, allowing them (while in User Mode) to control whatever mappable parameters you want).
  4. BANK/Quantisation Button 
    On the Apc40 Mk2 is tied somehow to the Track select button which switches/activates their state to Bank Select buttons as well as Quantisation buttons function.So my question is how would I implement them so they change change their state/ switch/ and act as a Bank Selector and Quantisation buttons?
  5. BANK Left/Right buttons
    On the Apc40 Mk2 they act as FX encoders bank switching selection buttons.My question is how can I make it that when the Bank Left/Right buttons are triggered/pressed they switch the FX encoders page going left/right to access more encoders?Ideally I would like to be able to use the Bank Left/Right button to change the 64 Encoders are implemented in the Apc40 Mk2 CSS template/script.
    For now I have them implemented and I can change the FX encoders selecting the respective Page Tab in my touchOSC Page.
    Which lets me use them in Abelton and are working and i can change the encoders page in touchosc.
    Ideally I’d like to be able to use the BANK left/right button if that makes sense?
  6. SHIFT button.
    Which has a lot of functions and function changes.In the Apc40 Mk2 the manual states that the shift button does the below:Track Selectors: Press one of these buttons to select its track, allowing you to use the Device Control Knobs for a device on that track. The right-most button (labeled Master) selects the Master track.Press and hold Shift and then press one of the first eight Track Selectors to select a Global Quantization setting: None, 8 Bars, 4 Bars, 2 Bars, 1 Bar, 1/4, 1/8, or 1/16.

    Also The BANK button….

Bank: Press this button to activate or deactivate while using the Bank Select buttons to move the selection by 8 tracks (left or right) or by 5 scenes (up or down), effectively shifting the entire 8×5 matrix controlled by the Clip Launch buttons (represented in Live by a rectangle). The Clip Launch buttons’ colors will match the clips’ colors as assigned in Live.Shift: Press and hold this button to access certain buttons’ secondary functions.When holding down this button, the 8×5 matrix of Clip Launch buttons will enter Session Overview Mode. In this view, each Clip Launch button represents an entire 8-track-by-5-scene matrix of clips in Live. You can then press one of them to view that 8×5 matrix in the Clip Launch buttons. This allows you to access and use more than the 5 rows and 8 tracks represented by the Clip Launch buttons. While in Session Overview Mode, the Clip Launch buttons’ colors represent the following:

From Akais Apc40 Mk2 manual:

    1. Select a track by pressing the desired Track Selector.
    2. If the Device View is not shown at the bottom of the window, press the Clip/Dev. View until it is.
    3. Use the Device Left/Right buttons to select the desired device.
    4. Use the eight Device Control Knobs to control the parameters of the current device’s first bank. You can use the Bank Left/Right buttons to select the previous or next bank in that device.

Any help would be greatly appreciated.

PS. Am not able to upload the TouchOSC, CSS Script, Template or Mode.
So I just linked them in my google drive for download below:
https://drive.google.com/drive/folders/1dLgtRx_STjpDMBAnWGK3OuYDgKd0LBUw?usp=share_link

Ps. If you have a spare iPad lying around just download TouchOSC and use the free desktop(Which does have a 7 second wait pop up message every time you save the template but still 100% usable) enjoy.

Harmonique9 Changed status to publish September 12, 2024

2 Answers

1
Glenn Verhaeghe 1 Comment

Hi again, thanks for cleaning up the post, it’s a lot more digestible. I’ll look into it from time to time to see if I can help you out.

1) Track Select button

Press one of these buttons to select its track, allowing you to use the Device Control Knobs for a device on that track.

So my question really is how would I implement them so they work while being selected where ever the session box is?

I think you’ll want to use the Select Device mapping for this one. There’s an option called “Relative to session box position” that will help you out.

6) SHIFT button

Modes can be considered as overlays. Your controller has a fixed set of physical buttons but modes make it so that you can overlay those physical buttons with different functions or abilities. In the case of your Track Select buttons, in mode 1 you want a button to make it select a device for the corresponding track, in shift mode you want to have that same button function as one of the quantization options.

The way this works is:

  1. In the Modes section, create the modes you want to use.
  2. To make a button function as a Shift Button, you’ll first want to make sure your button is set to Momentary, because you only want to enter Shift Mode while the button is held down. When you release the button, you want to return to the Previous Mode. This won’t work if the button itself sends Toggle messages, so it needs to be Momentary.
  3. To create the Shift Mode button, you’ll need (at least) two Mode Selector mappings (the amount depends on the amount of Modes you’ll use but for this example we only use Mode 1 and Shift Mode), both set to the same button you want to use as your Shift Button.
  4. The first one will take you to the Shift Mode (if you use multiple other modes, then you’ll need to repeat this one for the other modes as well).
    1. You’ll need to make sure the Mode for this mapping is set to Mode 1.
    2. In Section 2 of the mapping, set “mode to select” to Shift Mode
    3. In Section 3, set the Controller to the Shift Button you want to use, leave everything else default.
  5. The second Mode Selector mapping returns you to the Previous Mode when Shift Button is released.
    1. Make sure the Mode for this mapping is set to Shift Mode, because you want this to occurr whenever you are inside Shift Mode.
    2. In Section 2, set “Mode to Select” to Previous Mode
    3. In Section 3, select the Shift Button as your controller (the same button as before) but change Controller Override to Custom. All you need to do in here is change “Invert values” to On. This will make it so that this mapping only fires whenever you release the Shift Button.
  6. Now that the Shift Button is ready, all you need to do is make other mappings and set the ones you want to use inside Mode 1 to that mode, and set the one’s you want to use while in Shift Mode to Shift Mode.

    In my example, I’m using Mode 1 to select a Device in the first Track, and I use Shift Mode to select a Device in the second Track, both with the same Button 6.

I don’t see a Mapping specifically designed to select a Quantization Mode with, so you’ll need to use a Reaction to do that. But the principle of Modes works the same with Reactions.

Harmonique9 Edited comment September 7, 2024
Harmonique9 commented

Thank you, yes I thought better clean up the post a bit and I’ll continue to keep cleaning and reorganising it.

I see, that’s what I did wrong. My tracks use the Highlight Navi instead Select Device.
(Thank you for your patience. I’m still learning and trying to understand how everything works).

Now it clicked and the light bulb went off after reading your explanation and rewatching the tutorial about modes.

Again thank you very much for your help Glen.V. I understand whenever you have the time.
You are viewing 1 out of 2 answers, click here to view all answers.

Categories