Thanks Paul for these useful updates. I think I am going to try to make a diagram of all your apps showing which ones work well with others for specific applications. It already is making my head hurt thinking about it because there are so many options. Lol
This app is a real power tool. I started with AUM - a couple synths, Cality and MelodyBud - and with a few tweaks and in less than 5 minutes with the app turned it into something quite workable. Really fun. The pretty appearance of the layers and the smooth movement, the deep layers of options and controls make this really appealing.
There are many apps that we can choose to use in a project, some may not get used as often as they should, but Midi Layers is different, I shall incorporate it with all my Cubasis3 projects past and present. There is a lot to work out here, the mind boggles at the endless possibilities for live playing. Once again, thanks Paul, you truly are amazing 👍 Mike.
Paul, it would be awesome if each layer had a midi channel filter. This way multiple external midi sources or controllers can be used at the same time with Layers. Thanks!
Great programme Nevertheless, I miss a few features that are essential for controlling external midi devices. Under options (e.g. as second row) for each layer 1. user-defined CC filter (e.g. for sustain) 2. volume (cc 7) 3. at least 3 user-defined CCs (e.g. for reverb send or attack etc.) Nice to have: It would be great if you could receive a midi dump per layer and send it when you call it up (CC, PC, SysEx). It's a bit unfortunate that you can't configure the layers for mutes and scenes. Often 3 or 4 keys would suffice. So you lose a whole octave if you want to control via keyboard. It would also be helpful to be able to enter values directly (e.g. for PC), e.g. by double-clicking. It would be nice if you could send PC permanently when making changes. A small detail: The scene name currently in use should be visible as a header.
hi paul ive been using midi layers and it has helped me a lot! question, is there a way for the scene /mute control layer to be assigned to a physical knob on my controller.? thanks again
If you are running under AUM then you may be able to map CC controllers and notes inside AUM to MIDI Layers exposed parameters. I suggest you take a look at the AUM manual as it's quite complicated to explain.
No, MIDI Mixer is used to automate the mixing process as a song plays. MIDI Layers is used to allow a single keyboard to play multiple keyboards at once with the ability to create overlapping layers and fades etc.
I have a request. I want the image quality to be higher. For foreigners, with the precision of this screen, it is blurry and it is difficult to see what is being selected. I kind of understand what you're saying, but I'm not sure which Kadget was chosen.
Hi Paul, There are times the piano sustain pedal is passed to the auv3 instruments, and other times it does not. Not sure what sequence causes and clears the blocking of the sustain pedal. Other than that, I have been very happy with midi layers. Craig
I haven't noticed this to be honest, but I will do some testing. You now have to turn on ModWheel / CC in the layers palette in order for CC to be sent to the layers port/channel.
@@PaultheMusicMan thanks. Very basic to reproduce on my setup. Launch aum, add midi with midi layers. Add audio instrument. Tie everything together wrt paths. Add midi layer. If there is a better venue to discuss, let me know.
@@1csmellon Did you ensure CC passthrough is enabled for the layer? It sounds from your description above you didn't enable it? See my previous comment.
@@1csmellon You are right, nut I thing it maybe it is not working as intended so I am taking a look right now. You should not have to turn on MIDI Thru for it to work.
Under Drambo, when I map mutegroups parameters or. Scene parameters, after reloading project in Drambo, or. Even saved. Preset of MIDILAYERS (created in Drambo) - MIDI LAYERS crashes.
I wasn't aware of this issue. It does seem odd that it works fine under AUM, Cubasis, Loopy and others, yet crashes in DRAMBO. Is this an issue with old presets created outside of DRAMBO, or does the problem exist when creating new presets?
Hi! Can I ask you pleae fix (update) MIDI Layers with updating parameters when changing in the gui? for example when I change parameter in host like MUTE GROUPs, the gui shows (Reflect) changes. But otherwise not: when I change (mute,unmute groups) the the window of the plugin (gui), the parameters in the host stars not changed. Sometimes I like to change in the gui , sometimes via parameters in host (Drambo), would be great If the values are always in sync. Also I think when recording automation from gui, will be easier when parameters are updated to host. Maybe its user error , i hope so. Please respond, thank you for your hard work. I love ❤️ MIDI layers. 🎉
This is not possible, and not the way MIDI Layers works. It was written to automate settings in AUM and not the other way around. It is possible to change AUM's params by sending MIDI, but we are never told that AUM's parameters change. If you've seen my videos you will appreciate that MIDI Layers allows you to record parameter changes over a whole song, and play them back. This would not work if other factors were involved. The Sound Test Room did a great video on using this app, it might be worth taking a look at Doug's video.
@@PaultheMusicMan true! Under Cubasis there is no problem, at now 15-02-2023 in Drambo I cannot write automation from GUI of the MIDI LAYERS, and plugin crash error on load when parameters are visible (maped). Thank you for fast reply.
@@przemysawjakubszczypek3922 This program was written for use under AUM for automation of AUM's interface, I wouldn't have thought it was useful under DRAMBO or Cubasis for that matter. I assume you are trying to host MIDI layers inside of DRAMBO?
@@PaultheMusicMan from message developer of Drambo sent me in PM (translated by me from Polish):: ‚,1. Drambo set saved state of plugin (during load project) 2. Drambo set values of parameters maped to knobs in Drambo 3. MidiLayer crashing Most DAWs dont processing step 2, so Bug accour only in Drambo, but it is Bug in the midi layer’’ I hope i can help spmehow to find and fix crashing in Drambo during load project with midi layer with maped parameters to knobs.
Hi Paul, can the lowest note in a Layers be lower than midi note 24? I am trying to assigned a sequence to the lowest note om 88 keys master Controller but the Layers Low region stops at C1 (24)
Yes, sure you can. Look at the Master Keyboard setting in Settings. By default we assume a certain range, but you can extend the range down to MIDI note 0 if you wish.
@@PaultheMusicMan Thanks, excellent! Also is there a way to decide the midi through chanel in a layer? Say that I creat a midi through enabled layer with omni chanel input, but want the MIDI signal that goes through only be transmitted on chanel 2 of a port. Is this possible?
Thanks Paul 🧙♀️ Reminds me of the old days 😁🥹I remember how awkward midi was
Yeag, sadly those problems haven't got any easier for those wanting to play hardware or live performers!
Paul, you are a genius ! Thanks for this very well presented tutorial. 👍🏼
Thanks Paul for these useful updates. I think I am going to try to make a diagram of all your apps showing which ones work well with others for specific applications. It already is making my head hurt thinking about it because there are so many options. Lol
Excellent idea! Do it! :)
I started making a list of all of Paul’s apps butIran outof paper. 😂
This app is a real power tool. I started with AUM - a couple synths, Cality and MelodyBud - and with a few tweaks and in less than 5 minutes with the app turned it into something quite workable. Really fun. The pretty appearance of the layers and the smooth movement, the deep layers of options and controls make this really appealing.
Awesome! Just what I’ve been looking for to use within AUM. Thanks!
Paul, the new features are a fantastic update.Thank you for adding them.
Craig
Some great additions there Paul. Very professional tools from the master of midi.
Thanks mate, there are so many great ideas being put forward I'm having a blast with this one.
There are many apps that we can choose to use in a project, some may not get used as often as they should, but Midi Layers is different, I shall incorporate it with all my Cubasis3 projects past and present. There is a lot to work out here, the mind boggles at the endless possibilities for live playing. Once again, thanks Paul, you truly are amazing 👍
Mike.
This app is pure magic. Now what would be useful is if it could convert aftertouch to cc. Well done Paul Hope your doing well.
Yes mate, improving every day....
Paul, it would be awesome if each layer had a midi channel filter. This way multiple external midi sources or controllers can be used at the same time with Layers. Thanks!
The next version has a MIDI In Channel for each layer so you can control which source can trigger the layer.
Excellent tutorial and extremely useful additions, Paul!
Thanks David, now get back to bed mate!!
Great programme
Nevertheless, I miss a few features that are essential for controlling external midi devices.
Under options (e.g. as second row) for each layer
1. user-defined CC filter (e.g. for sustain)
2. volume (cc 7)
3. at least 3 user-defined CCs (e.g. for reverb send or attack etc.)
Nice to have:
It would be great if you could receive a midi dump per layer and send it when you call it up (CC, PC, SysEx).
It's a bit unfortunate that you can't configure the layers for mutes and scenes. Often 3 or 4 keys would suffice. So you lose a whole octave if you want to control via keyboard.
It would also be helpful to be able to enter values directly (e.g. for PC), e.g. by double-clicking. It would be nice if you could send PC permanently when making changes.
A small detail: The scene name currently in use should be visible as a header.
The red arrows are very helpful. I hate it when a presenter is talking about features that are not readily visible.
At least under LOOPYPRO the MIDILAYERS not crashes when widget is controlling a MUTEGROUP parameter.
hi paul ive been using midi layers and it has helped me a lot! question, is there a way for the scene /mute control layer to be assigned to a physical knob on my controller.? thanks again
If you are running under AUM then you may be able to map CC controllers and notes inside AUM to MIDI Layers exposed parameters. I suggest you take a look at the AUM manual as it's quite complicated to explain.
Hi again Paul … is there an AUv3 synth that seems to work better with your apps than other synths?
If you don't already own it I would suggest SynthMaster 2. It ha everything you need.
HI Paul, I have the Midi Mixer and it looks similar to Midi Layer. Do they have similar functions? Thanks
No, MIDI Mixer is used to automate the mixing process as a song plays. MIDI Layers is used to allow a single keyboard to play multiple keyboards at once with the ability to create overlapping layers and fades etc.
I have a request. I want the image quality to be higher. For foreigners, with the precision of this screen, it is blurry and it is difficult to see what is being selected. I kind of understand what you're saying, but I'm not sure which Kadget was chosen.
The video was uploaded in 1080p so make sure you are viewing in 1080p as UA-cam often deops the quality.
@@PaultheMusicMan Thank you so much.
Hi Paul,
There are times the piano sustain pedal is passed to the auv3 instruments, and other times it does not. Not sure what sequence causes and clears the blocking of the sustain pedal. Other than that, I have been very happy with midi layers.
Craig
I haven't noticed this to be honest, but I will do some testing. You now have to turn on ModWheel / CC in the layers palette in order for CC to be sent to the layers port/channel.
@@PaultheMusicMan thanks.
Very basic to reproduce on my setup. Launch aum, add midi with midi layers. Add audio instrument. Tie everything together wrt paths. Add midi layer.
If there is a better venue to discuss, let me know.
@@1csmellon Did you ensure CC passthrough is enabled for the layer? It sounds from your description above you didn't enable it? See my previous comment.
@@PaultheMusicMan I did not. If I turn on Midi Pass Thru, the sustain pedal works fine. Thank you.
Sorry for the misfire.
@@1csmellon You are right, nut I thing it maybe it is not working as intended so I am taking a look right now. You should not have to turn on MIDI Thru for it to work.
Under Drambo, when I map mutegroups parameters or. Scene parameters, after reloading project in Drambo, or. Even saved. Preset of MIDILAYERS (created in Drambo) - MIDI LAYERS crashes.
I wasn't aware of this issue. It does seem odd that it works fine under AUM, Cubasis, Loopy and others, yet crashes in DRAMBO. Is this an issue with old presets created outside of DRAMBO, or does the problem exist when creating new presets?
@@PaultheMusicMan with new Presets, the for response
Hi! Can I ask you pleae fix (update) MIDI Layers with updating parameters when changing in the gui? for example when I change parameter in host like MUTE GROUPs, the gui shows (Reflect) changes. But otherwise not: when I change (mute,unmute groups) the the window of the plugin (gui), the parameters in the host stars not changed. Sometimes I like to change in the gui , sometimes via parameters in host (Drambo), would be great If the values are always in sync. Also I think when recording automation from gui, will be easier when parameters are updated to host. Maybe its user error , i hope so. Please respond, thank you for your hard work. I love ❤️ MIDI layers. 🎉
This is not possible, and not the way MIDI Layers works. It was written to automate settings in AUM and not the other way around. It is possible to change AUM's params by sending MIDI, but we are never told that AUM's parameters change. If you've seen my videos you will appreciate that MIDI Layers allows you to record parameter changes over a whole song, and play them back. This would not work if other factors were involved. The Sound Test Room did a great video on using this app, it might be worth taking a look at Doug's video.
@@PaultheMusicMan true! Under Cubasis there is no problem, at now 15-02-2023 in Drambo I cannot write automation from GUI of the MIDI LAYERS, and plugin crash error on load when parameters are visible (maped). Thank you for fast reply.
@@przemysawjakubszczypek3922 This program was written for use under AUM for automation of AUM's interface, I wouldn't have thought it was useful under DRAMBO or Cubasis for that matter. I assume you are trying to host MIDI layers inside of DRAMBO?
@@PaultheMusicMan Yes, under Drambo - and at now Drambo not write and read automation from MIDI layers gui (plugin window), and crashes
@@PaultheMusicMan from message developer of Drambo sent me in PM (translated by me from Polish)::
‚,1. Drambo set saved state of plugin (during load project)
2. Drambo set values of parameters maped to knobs in Drambo
3. MidiLayer crashing
Most DAWs dont processing step 2, so Bug accour only in Drambo, but it is Bug in the midi layer’’
I hope i can help spmehow to find and fix crashing in Drambo during load project with midi layer with maped parameters to knobs.
Hi Paul, can the lowest note in a Layers be lower than midi note 24? I am trying to assigned a sequence to the lowest note om 88 keys master Controller but the Layers Low region stops at C1 (24)
Yes, sure you can. Look at the Master Keyboard setting in Settings. By default we assume a certain range, but you can extend the range down to MIDI note 0 if you wish.
@@PaultheMusicMan Thanks, excellent! Also is there a way to decide the midi through chanel in a layer? Say that I creat a midi through enabled layer with omni chanel input, but want the MIDI signal that goes through only be transmitted on chanel 2 of a port. Is this possible?
@@fredsaboonchi2975 I believe the MIDI Thru Settings in Settings allow you to choose a destination Port and Channel, but by default it is set to Omni.
@@PaultheMusicMan Great, thanks! But this is on an overall level right? Can it be done on layer by layer level?
@@fredsaboonchi2975 The Layer Channel controls the output on a per layer basis.