Hey all,
New Max For Live user and relatively new Launchpad user here. I recently purchased the J74 Step Sequencer 64 and have been enjoying it so far. However, I wanted to make some basic changes to the setup: The Launchpad in the User 1 mapping currently controls on/off for notes in the sequencer. How should I go about mapping User 2 so that it controls note pitch? E.g., I press the first Launchpad button and a C1 is placed in the current step in the sequencer, the 2nd button would input a C#1, etc.
I understand I'd have to go about writing my own mapping as a text file for the step surface to read, likely through editing the included Setup SS64 text. However, that's an area I'm quite unfamiliar with, so I was hoping someone could either show me what to write or point me in the right direction for learning how to do so.
Thanks!
Step Sequencer J74 / General Launchpad question
-
Smoking_Gnu
- Posts: 12
- Joined: Fri Jan 03, 2014 3:28 pm
Re: Step Sequencer J74 / General Launchpad question
I'd contact the company you bought the sequencer from!
Cheers
D
Cheers
D
-
[email protected]
- Posts: 105
- Joined: Sun Mar 21, 2010 4:14 pm
Re: Step Sequencer J74 / General Launchpad question
We had a conversation offline about this, but for the sake of clarity for any other reading this,here some notes.
- In StepSequencer64 you can map the functions to any MIDI controller as long as this sends MIDI notes and/or CC's (you can build your definitions as explained in the user manual). The Launchpad User 1 is perfectly fine for that (the Launchpad Control Surface in Live sends MIDI in User Mode 1). The User 2 mode is unfortunately not good for that because Live won't let it send any MIDI CC through (just let's you maps the buttons for MIDI mapping). If you want the use the Launchpad you are limited to User mode 1. Anyway you can couple User mode 1 with any other controller for mapping other functions in the StepSequencer64 (as long as this controller sends MIDI CC or notes).
- For the APC40 there is a differnet story: the APC40 does something useful only if a Control Surface in Live makes it "intelligent". As the APC40 is a wonder in terms of how many controls it gives you, I included in the StepSequencer64 a special auto-mapper fully "API based" which maps all the StepSequencer64 functions to the APC40. It supports Live native APC40 Control Surface, as well as the Hanz Petrov Control Surface and the ISO Controllers control surface.
I hope this clarifies the possibilities for mapping.
Cheers
Fab
- In StepSequencer64 you can map the functions to any MIDI controller as long as this sends MIDI notes and/or CC's (you can build your definitions as explained in the user manual). The Launchpad User 1 is perfectly fine for that (the Launchpad Control Surface in Live sends MIDI in User Mode 1). The User 2 mode is unfortunately not good for that because Live won't let it send any MIDI CC through (just let's you maps the buttons for MIDI mapping). If you want the use the Launchpad you are limited to User mode 1. Anyway you can couple User mode 1 with any other controller for mapping other functions in the StepSequencer64 (as long as this controller sends MIDI CC or notes).
- For the APC40 there is a differnet story: the APC40 does something useful only if a Control Surface in Live makes it "intelligent". As the APC40 is a wonder in terms of how many controls it gives you, I included in the StepSequencer64 a special auto-mapper fully "API based" which maps all the StepSequencer64 functions to the APC40. It supports Live native APC40 Control Surface, as well as the Hanz Petrov Control Surface and the ISO Controllers control surface.
I hope this clarifies the possibilities for mapping.
Cheers
Fab