Creating a dedicated hardware-controlled iPad setup

Gravitas

@Gravitas said:

@Gravitas said:

@rs2000 said:
Don't get me wrong @Gravitas, your projects are incredible and about the best one can get without such features natively implemented in Drambo.
The "hacky" relates to the additional effort required when building something new from scratch - you can easily have more modules just for the MIDI feedback than for the actual project itself 😉

Once agreed.

I wouldn't recommend it for the faint of heart and if patience was in short supply. 😁
I had a read of the Mozaic manual the other day.
I'm getting more coffee and I may print it out.

My respect for developers is at Zen level. 🙏🏾

Once such features are inbuilt, the users are going to have so much fun.
I simply am fascinated that some of it could be done with
the current modules themselves and the challenge was
there though I did the realise it at the time.

Actually, thinking about it, building a Launchpad 8 band spectrum analyzer could be fun 😄

You've done it again.

Let me think about that one for abit. 😁

Nah, I can't figure that one out yet. 😂

The LPX doesn't respond to continuous cc messages so that's one for sysex I think.

Do any Mozaic users know how to translate continuous cc messages into sysex?

Creating the audio bands is doable in Drambo as in converting
them into separate cc messages per frequency band using filters.

So Drambo will emit cc message A and Mozaic translates
that into sysex code A that tells the LPX to change
the colour of lighting of the pad or something like that.

Wow, that's awesome concept. 🙏🏾

Really sorry.

Double posted whilst editing.

AlmostAnonymous

@Gravitas said:
Do any Mozaic users know how to translate continuous cc messages into sysex?.

Haven’t converted in Mozaic but have elsewhere. Convert the cc to hex. Drop hex in the sysex string. Send string. I’d assume you just get the cc, convert it to hex and set it as a variable and drop it in the string.

But you shouldn’t have to. If you’re setting these faders up in session/daw mode, they react to midi cc
You only need to use the sysex to set them up (position, color, etc)

This fader is just sending midi cc’s

https://vimeo.com/manage/videos/640609354

rs2000

@Gravitas No need to use Mozaic 😊
Yes, filters can split the audio into bands, and even the different VU level LEDs can be controlled like this:

The Envelope Follower Decay time represents the VU "slow decay", each Graphic Shaper is set at a different VU level (you'll need 8 of them for 8 VU level steps) and by adjusting the height of each Graphic Shaper "high level", you could even trigger the correct note number on the Launchpad according to the VU level.

I've only shown one Note Generator here, you'll most likely need one for each LED and merge them using the MIDI mixer.

AlmostAnonymous

I really should just take a crack at the firmware SDK for this thing.

soundtemple

My attempt to provide a solution to the problem was this
https://patchstorage.com/qkv2-kntrl-midi-control-centre/

It offers 15 fully customisable channels.
Each channel has up tp 64 labeled & coloured parameters
Control up to 960 parameters with one encoder
Comes with many included layouts that you can dial in or you can make your own and save as a Mozaic preset
It stores the current value of all parameters
When you select a parameter to control it updates the encoder to the stored value
Can be used with my other scripts to be fully controllable with full colour on the Launchpad Mini
I use it with a LP mini and a MF Twister.

steve99

@soundtemple said:
My attempt to provide a solution to the problem was this
https://patchstorage.com/qkv2-kntrl-midi-control-centre/

It offers 15 fully customisable channels.
Each channel has up tp 64 labeled & coloured parameters
Control up to 960 parameters with one encoder
Comes with many included layouts that you can dial in or you can make your own and save as a Mozaic preset
It stores the current value of all parameters
When you select a parameter to control it updates the encoder to the stored value
Can be used with my other scripts to be fully controllable with full colour on the Launchpad Mini
I use it with a LP mini and a MF Twister.

QK:KNTRL gets my vote

It’s transformed my iPad experience with LP and Midi Fighter, a pad pushing, knob twiddling dream.

Gravitas

@rs2000 said:
@Gravitas No need to use Mozaic 😊
Yes, filters can split the audio into bands, and even the different VU level LEDs can be controlled like this:

The Envelope Follower Decay time represents the VU "slow decay", each Graphic Shaper is set at a different VU level (you'll need 8 of them for 8 VU level steps) and by adjusting the height of each Graphic Shaper "high level", you could even trigger the correct note number on the Launchpad according to the VU level.

I've only shown one Note Generator here, you'll most likely need one for each LED and merge them using the MIDI mixer.

I've got it react to the sound coming as
I've split the sounds into bands covering the entire spectrum.
I haven't quite got the layout of the LP X yet to match
though I have got notes reacting to the sound.

What I haven't quite figured out yet is the amplitude per band.
and how to display that using only midi notes.

A little side note.
The LP X will react natively to midi notes but it won't react to cc messages.

Ah yes, I've tried the Mozaic patches from Soundtempletgat can be found on patchstorage.
Requires slight modifications for my needs but it is quite fun to play with.

In deep thought.

Back soon.

Gravitas

@rs2000

Have a look at this.

A modern take on an ancient instrument.

The instrument is called ,'nyatiti'.

Back soon.

AlmostAnonymous

Is there a reason you can’t use ccs? Is it a Drambo thing?

Gravitas

@AlmostAnonymous said:
Is there a reason you can’t use ccs? Is it a Drambo thing?

Nah.

It's an LP X thing otherwise the spectrum analyser would've been finished already.

I've tested it using both AUM and Drambo with
Streambyter to monitor the midi side of things and
it will not change colour or switch on and off
when cc's are being to sent to the same pad.

The problem I have at the moment is assigning the midi notes to amplitude.
I have a custom map laid out already with selected notes per octave per line of pads.
For instance column i is C0 - B0, column ii is C1 - B1 etc, etc.

The issue with midi notes is that the LP X only recognises on and off not velocity.
So I have to assign frequencies to velocities somehow and making sure that each note remains on as it increases in amplitude and switch's off as the signal decreases.

I'm still getting my head around how the midi layout should so that may very well change.

uncledave

@Gravitas , this should be easier with a combo of Drambo and StreamByter. Let Drambo do the signal processing and send data to StreamByter in the form of CCs. Then let SB convert those numbers into note on or off as needed. Use an array to remember which pads are lit, and send notes to alter the lights as needed. This is much easier to do in SB, since it can send note on and off messages more or less at random, i.e. not musically, while Drambo is locked in to being musical.

Edit: Don't need an array if always lighting columns from the bottom up. Just remember the last high point in each column. Then light more lights if the signal goes up, turn lights off if the signal goes down, and save the new value. This could be a subroutine, given old value, new value, and number of the bottom note for the column. It sends the required note on or off messages, and updates the old (saved) value.

AlmostAnonymous

Do you need the column to vary in color? Green, yellow, red as the amplitude increases? Like pads 1-3 green, 4-6 yellow, and 7 and 8 red? Or is just a single color for the entire column ok?

Gravitas

@uncledave said:
@Gravitas , this should be easier with a combo of Drambo and StreamByter. Let Drambo do the signal processing and send data to StreamByter in the form of CCs. Then let SB convert those numbers into note on or off as needed. Use an array to remember which pads are lit, and send notes to alter the lights as needed. This is much easier to do in SB, since it can send note on and off messages more or less at random, i.e. not musically, while Drambo is locked in to being musical.

I don't have enough knowledge in regards to both Streambyter and Mozaic.
I use Streambyter to block messages I don't need and to monitor midi.
That's why I'm currently reading the Mozaic manual,
I only got Mozaic a couple of weeks ago.
I'm a total noob.

That's a good idea though.
Using cc's from the initial part of the path and then converting them into midi notes.

Basically the layout for the LPX is a workable map.
It is doable, I simply have to not think about it.
If I think about, it won't happen.

The main reason why I'm able to do so much
in Drambo is because I don't need to code.

AlmostAnonymous

If I am not mistaken, FAC Envolver will take an audiosignal and output midi from it

I’m not sure of your final vision or this helps to get you there.

Gravitas

@AlmostAnonymous

The issue isn't with converting audio to mid or audio to cc's.
It's mapping the signal in the correct way to the LP X
without using sysex at the moment because I don't code
and it hasn't been translated yet.

Note I'm using an octave per strip.
Simply because it's easier to navigate.
So when there is an increase in gain,
note C1 should remain on and the next note up or more should start
to either flicker or remain constant dependant upon the signal going in.

Note 1 + note 2 + note 3 + note 4 etc, etc

So it's assigning each note per increase in volume.

AlmostAnonymous

In my video, I set up the fader with a sysex command. After that, it responds on incoming midi ccs.
So set up 8 faders with sysex with whatever midi cc you want. It will be a little different for your X as I have 4 pages to handle but here’s what I have in my script so far:

SYFADERSETUP11 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 0, 0, 11, 122, 247] // 14
SYFADERSETUP12 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 1, 0, 12, 16, 247] // 14
SYFADERSETUP13 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 2, 0, 13, 122, 247] // 14
SYFADERSETUP14 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 3, 0, 14, 16, 247] // 14
SYFADERSETUP15 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 4, 0, 15, 122, 247] // 14
SYFADERSETUP16 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 5, 0, 16, 16, 247] // 14
SYFADERSETUP17 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 6, 0, 17, 122, 247] // 14
SYFADERSETUP18 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 7, 0, 18, 16, 247] // 14
  SendSysex SYFADERSETUP11, 14
  SendSysex SYFADERSETUP12, 14
  SendSysex SYFADERSETUP13, 14
  SendSysex SYFADERSETUP14, 14
  SendSysex SYFADERSETUP15, 14
  SendSysex SYFADERSETUP16, 14
  SendSysex SYFADERSETUP17, 14
  SendSysex SYFADERSETUP18, 14

This is 8 faders, ccs 11-18, in a vertical orientation, with alternating colors of green and light green. After that…they move with incomming cc values.

Gravitas

@AlmostAnonymous said:
In my video, I set up the fader with a sysex command. After that, it responds on incoming midi ccs.
So set up 8 faders with sysex with whatever midi cc you want. It will be a little different for your X as I have 4 pages to handle but here’s what I have in my script so far:

SYFADERSETUP11 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 0, 0, 11, 122, 247] // 14
SYFADERSETUP12 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 1, 0, 12, 16, 247] // 14
SYFADERSETUP13 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 2, 0, 13, 122, 247] // 14
SYFADERSETUP14 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 3, 0, 14, 16, 247] // 14
SYFADERSETUP15 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 4, 0, 15, 122, 247] // 14
SYFADERSETUP16 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 5, 0, 16, 16, 247] // 14
SYFADERSETUP17 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 6, 0, 17, 122, 247] // 14
SYFADERSETUP18 = [240, 0, 32, 41, 2, 14, 1, 0, 0, 7, 0, 18, 16, 247] // 14
  SendSysex SYFADERSETUP11, 14
  SendSysex SYFADERSETUP12, 14
  SendSysex SYFADERSETUP13, 14
  SendSysex SYFADERSETUP14, 14
  SendSysex SYFADERSETUP15, 14
  SendSysex SYFADERSETUP16, 14
  SendSysex SYFADERSETUP17, 14
  SendSysex SYFADERSETUP18, 14

Okay, I've had a look at your video and that is very useful, very cool as well.

I have no idea what this text means other than SendSysex to a fader.
I presume each line of code is a fader and is directed at the LP Pro.

Bear in mind I'm simultaneously designing
a couple of other instruments at the moment
and I still have to learn Mozaic so, you know, I'll get there eventually.

What you've done with Mozaic is not doable
in Drambo because that requires sysex.

To reiterate, the methods I've been using in Drambo to get things
happening such as the lights, clip launching etc are only Drambo modules
without sysex.

As mentioned earlier if the LP X did respond to cc's directly this would've been done already.

AlmostAnonymous

It’s not sending sysex. Mozaic only sets up the faders as you need the sysex to get that set. It doesn’t convert or handle ccs in anyway to sysex.

The cc’s can come from anywhere and passed straight to the LP.

The sysex is only loaded 1 time to set up the color, position, and what cc the fader responds to.

It does nothing after that. Only ccs are being sent direct to the the LP. You’ll be sending the ccs from Drambo to the LP. No sysex conversion.

Now, the question no one asked…. Are you trying to do this in session/daw mode, or in programmers mode? The above is done in DAW. I’ve found DAW much easier to implement with less coding. You’ll also retain usage of the notes page and other custom layouts. And I think I’ve finally gotten to the point I can state save the entire session mode layout in “banks” and be able to switch them out. So loading an array into the lpp, rather than hand coding everything in programmers mode.

Gravitas

@AlmostAnonymous said:
It’s not sending sysex. Mozaic only sets up the faders as you need the sysex to get that set. It doesn’t convert or handle ccs in anyway to sysex.

The cc’s can come from anywhere and passed straight to the LP.

The sysex is only loaded 1 time to set up the color, position, and what cc the fader responds to.

It does nothing after that. Only ccs are being sent direct to the the LP. You’ll be sending the ccs from Drambo to the LP. No sysex conversion.

Now, the question no one asked…. Are you trying to do this in session/daw mode, or in programmers mode? The above is done in DAW.

I mentioned this earlier.
The LP X doesn't respond to cc messages.
Not at all.
It needs sysex.

Tried and tested.

I think the LP Pro may respond to cc messages directly but not the LP X.

Nope, I've tried using both DAW and midi.
I'm not doing this in programmers mode either.
It's pointless for me at this moment but you can do this.

Split the frequencies into eight separate bands and assign
them individual cc messages that your code will understand.

You should be able to get it happening in no time at all.

AlmostAnonymous

I’m also in you boat working on too many things at the same time.

AlmostAnonymous

It does. It’s the exact same code in both manuals:

I send this once, and after that…it’s all cc’s

Gravitas

How do you put the Launchpad into Programmers mode??

I cleared the Custom Modes that were the Factory default using MidiSynth Control.
When doing that I removed the Custom Templates that from reading the LP X manual comes as Factory default.

If someone has the Factory default settings as sysex then I could send that to my LP X
and see about getting the LED's to respond to cc messages directly.

AlmostAnonymous

I didn’t use programmers mode. You would send this which activates the session mode light:

Gimme 10 and I’ll try and whip it up for you…..

AlmostAnonymous

I dont have an LPX to test with, but this SHOULD setup the same 8 faders i just showed you under your session button:

@onLoad

    sydaw = [240, 0, 32, 41, 2, 12, 16, 1, 247]
    SendSysex sydaw, 9

    SYFADERSETUP11 = [240, 0, 32, 41, 2, 12, 1, 0, 0, 0, 0, 11, 122, 247] // 14
    SYFADERSETUP12 = [240, 0, 32, 41, 2, 12, 1, 0, 0, 1, 0, 12, 16, 247] // 14
    SYFADERSETUP13 = [240, 0, 32, 41, 2, 12, 1, 0, 0, 2, 0, 13, 122, 247] // 14
    SYFADERSETUP14 = [240, 0, 32, 41, 2, 12, 1, 0, 0, 3, 0, 14, 16, 247] // 14
    SYFADERSETUP15 = [240, 0, 32, 41, 2, 12, 1, 0, 0, 4, 0, 15, 122, 247] // 14
    SYFADERSETUP16 = [240, 0, 32, 41, 2, 12, 1, 0, 0, 5, 0, 16, 16, 247] // 14
    SYFADERSETUP17 = [240, 0, 32, 41, 2, 12, 1, 0, 0, 6, 0, 17, 122, 247] // 14
    SYFADERSETUP18 = [240, 0, 32, 41, 2, 12, 1, 0, 0, 7, 0, 18, 16, 247] // 14
      SendSysex SYFADERSETUP11, 14
      SendSysex SYFADERSETUP12, 14
      SendSysex SYFADERSETUP13, 14
      SendSysex SYFADERSETUP14, 14
      SendSysex SYFADERSETUP15, 14
      SendSysex SYFADERSETUP16, 14
      SendSysex SYFADERSETUP17, 14
      SendSysex SYFADERSETUP18, 14

@end

Route mozaic script to DAW port of LPX to get it to enable
Route midi CC’s to LPX DAW port in your host or controller
(Here im just using the LCXL to send midi ccs because its handy at the moment)
Route from LPX daw port to whatever you want the faders/CC’s to control. (Not shown here)

Again, i dont have an LPX, but this is exactly what im doing on the pro, but just using the code in the LPX manual.

AlmostAnonymous

This is faders 1-8 on cc’s 11-18.

Keep in mind, faders react on channel 5 on the daw port (at least on my mk3), so my LCXL is sending on channel 5 on all faders, cc’s 11-18, all routed to the DAW midi port.

Not sure if its till ch5 on the X

AlmostAnonymous

I was originally using a LPmini and was able to do the same thing as well.
I was gonna upgrade to the X, but went to the pro instead because it allows you to write your own firmware for the device.

YThis was my end game….but i never really touched it yet.

AlmostAnonymous

This really needs it own topic at this point, lol

Gravitas

@AlmostAnonymous said:
This really needs it own topic at this point, lol

Lololol agreed.

Thanks for the pointers and the heads up.

I’ve had a browse through your
instructions and they make sense.

I’ll try them on the morrow.

It also be good practice in learning
how to get code etc into Mozaic.

wim

I'm really, really, really glad I don't have a Launchpad right about now so I can't get sucked into this. 😂😎

wim

I'm just starting to mess around with these nifty little encoders that are kind of like the old, old, style iPod control. Five buttons and a rotary encoder in a circle a bit bigger than a quarter.