Been thinking about it this morning and would love to have some kind of elektronesque 'parameter lock per step' function in BM3. Struggling to visualise a way to do it tho without a button added to the BM3 left column, (or something....) which takes it outside of something you could potentially develop by yourself
I guess step locks will be possible via cc but after I thought about it I kept arriving back at the fact that p-locks are so fun/fast on Elektron sequencers down to the workflow -
Hold down a step, navigate to a param on screen and tweak param value for that step.... Having to kind of plan ahead and assign CC's etc would lose most of that vibe. As an option, yeah it's better than nothing, but maybe you and intua could work on something in partnership that totally nailed it for workflow?
Or maybe it's just me that would even want this kind of p-lock function, in which case all of this is moot and would be a lot of hassle for nothing! haha.
But yeah, ideally I'd have a 'lock' button on the left BM3 column and then -
Select step/note in pattern>
press 'lock' button>
navigate to param and tweak value>
repeat with other params if desired>
press 'lock' again to return to normal functions.
Dunno if someone with a better understanding of the midi au possibilities/limitations can come up with a potential way to make something that would have that kind of Elektron spontaneous fluid workflow between au sequencer + BM3 sampler/synth/fx for p-locks?
As mentioned by @StudioES, floating scalable windows could be an option but yeah, that does seem like something that would take a ton of work/serious overhaul....
Thanks for heads up, haven't heard of Braveheart Ton before, still kind of an outsider to the world of ios production/apps, so many out there! will check it out. Vaguely remember someone posting something on elektronauts.com about an app that looked pretty cool and quite close to elektron workflow. But back then I think it involved IAA/clunky page switching and midi etc.. Will try and find the post...
@tk32 When you put it like that its hard not to begin to think that BM3 and Brambos should do some work TOGETHER on some IAP's.... Best of both worlds. Some extended/creative sequencing and arpeggios from brambros coding efforts.... Total integration of those features in to BM3 from intua's coding efforts.... Haven't entirely thought it through and there's a ton of behind the scenes coding considerations that I'm probably totally neglecting.. So I dunno if feasible.. but if it is....
Everyone gets paid and things could develop in a slightly less handicapped way. Less catering to the negative aspects of ios (and also lack of dev resources/time/manpower)... And intua wouldn't be spending a ton of time on coding some of the more niche requests/requirements and users could cherry pick some of their BM3 extended options/environment...
Probably unrealistic and not attractive to either party for one reason or another.. But would possibly be the ideal end game from my POV under current circumstances considering both devs' heavy workloads/specialist areas..
@Heyez it's not for me to comment.. but if I was BramBos I'd much sooner make universal AUv3 plugins rather than vendor-specific IAPs.
When you consider the small margins these developers get from selling apps at 4.99-9.99 I have complete sympathy for them wanting to sell products compatible for all DAWs/workflows rather than just one.
Propellerhead tried a similar experiment with Rack Extensions.. with mixed results... but they still ended up adding VST support in the end.
I didn't mean for brambros to make some stuff 'exclusive' to IAP necessarily. Not like the Auria Fabfilter deal (lame move from fabfilter.....) etc.
More like BM3 IAP editions of his existing stuff (and new things..). I'd be more inclined to buy something that integrated fully in to BM3 than something that linked in au fashion. And brambros might occasionally get people buying both versions even
Maybe the efforts involved in making BM3 IAP specific versions wouldn't weigh up tho in a business/time/hassle sense. I just hate page switching in BM3. My no.1 issue with it. So anything that could potentially be added as streamlined functionality under the hood on the keys/pads/sequencer pages/left column VS things like midi AUv3 etc would be killer..
@StudioES I couldn't find anything on the app you mentioned? But found the one I was trying to remember. Theres brief talk about its p-locks at 6.45min. Seems quite limited tho and looks based on specifying Cc etc rather than a spontaneous fluid workflow that feels as fast/flexible as an elektron box. Didn't watch whole video but might check the app out if I get some spare £...
Edit - I think midisteps also has a function for probability per step, similar to elektron trig conditions..
@brambos just thought... Most obvious/simple thing I'd love in a midi AU would be to have op1 Endless sequencer. Super simple, fast sequencer. Basically the same as the playable/transposeable sequencer in sunrizer but with added 'Oct up/down', tempo divisions(I forget if sunrizer has this) and ability to change the note cycles etc. Maybe a mode that could be added to your odessa arp?
This looks very exciting, wondering if this internal MIDI works across banks too ?
I'm wondering that too, and it must be a newer beta than 3.0.6 beta #4
(The Odessa Plug-Ins load fine in #4 but their midi output can't be routed).
I've always wanted to have to option to select a 'bank/pad' as a midi-source for another pad, maybe this time we'll see it in action? Pure midi-pads could be a positive side effect of this...
So it works like this: a new virtual MIDI source is created per AUv3 that offers MIDI output. Then you're up to use it as a source for either an AUv3, IAA, sampler... Pretty straightforward. Also, instantiation of new banks and plugins has been improved, so you can set this up really quickly.
Basically:
Load an AUv3 MIDI plugin on a bank, for example, @brambos 's Odessa Rhythm
Load a synth or sampler on another bank, setup MIDI to receive from the virtual MIDI input device created for the plugin
???
Profit!
I posted this video earlier: 3 different Odessa apps sending MIDI to Bank B, loaded with Redshrike:
On a side note, we have this new "Single Channel" and "Multi Channel" option available in the MIDI settings of each track, for more routing (and easy) routing options. More on this shortly, when we'll post the 3.0.6 change log.
I still can't shake the idea of being able to select the output from one pad as input for another.
This would make it easier to chain multiple 'midi plug-ins' without creating too many virtual ports and also make it possible to merge input from multiple pads and feed them to one destination. Maybe this sounds easier than it is to actually implement it?
@samu said:
This will be fun to check out when released
I still can't shake the idea of being able to select the output from one pad as input for another.
This would make it easier to chain multiple 'midi plug-ins' without creating too many virtual ports and also make it possible to merge input from multiple pads and feed them to one destination. Maybe this sounds easier than it is to actually implement it?
@mathieugarcia will it be possible to have multiple AU midi windows open at the same time, or is it one pad at a time?
If multiple, then the pad name would be useful to see in the window. The last video hints that there will only be one window at a time, in line with the pad/plugin concept. Which is fair, if much easier to implement.
@mathieugarcia so how are those three AU MIDI plugins summed together to all go to one Redshrike ?
Do the pads now have multiple MIDI inputs or are these chained together like a MIDI Thru ?
Im curious if the AUv3 can be sent to the bank MIDI input too, so if we have a drumkit across pads, can the drum sequencers be sent to the entire bank or just a pad.
Chomping at the bit to try this out haha.
Yup same here. Hoping we can arpeggiate/sequence across pads in a bank.
Always struggle to get my head around the possibilities/limitations of this kind of thing before messing around with it. Like will I be able to assign the odessa lfos to auFX params on a BM3 pad that has an au synth on it? And similarly will I be able to have 'bank/pad macros' as Odessa Lfo destinations? Both of these would be OK workarounds till native modulation options are expanded Also wondering how much of the odessa UI's will be automatable by BM3, could be pretty fun tangling it all up
@5pinlink Exactly, a new virtual MIDI device will be created for each AUv3 MIDI plugin. I set up the 3 Odessa plugins to send to Channel 1. Then Bank B simply listen to those virtual MIDI devices. So that would work with the sampler too, or to record new patterns, etc.
I’m still confused because right now a bank can only have one MIDI input, but it uses all three, looking forward to seeing how it does it all, awesome that it is across banks so you can stick all your MIDI generators in one bank.
One last question, what happens with an AU MIDI pad or a bank that only has AU MIDI inside, in the mixer, they won’t have channels right ?
@5pinlink said: so if we have a drumkit across pads, can the drum sequencers be sent to the entire bank or just a pad.
If I can send Odessa's drum sequencers to a bank with drum samples (or other kinds of samples!! hehehe!) across the pads, I am going to be screaming like a little girl.
Seriously, then I could use the rhythm sequencers to randomize melodic one shot samples across the pads and get:
super crazy happy dopeness sound design shizzle...
Comments
I love this development cycle..
Been thinking about it this morning and would love to have some kind of elektronesque 'parameter lock per step' function in BM3. Struggling to visualise a way to do it tho without a button added to the BM3 left column, (or something....) which takes it outside of something you could potentially develop by yourself
I guess step locks will be possible via cc but after I thought about it I kept arriving back at the fact that p-locks are so fun/fast on Elektron sequencers down to the workflow -
Hold down a step, navigate to a param on screen and tweak param value for that step.... Having to kind of plan ahead and assign CC's etc would lose most of that vibe. As an option, yeah it's better than nothing, but maybe you and intua could work on something in partnership that totally nailed it for workflow?
Or maybe it's just me that would even want this kind of p-lock function, in which case all of this is moot and would be a lot of hassle for nothing! haha.
But yeah, ideally I'd have a 'lock' button on the left BM3 column and then -
Select step/note in pattern>
press 'lock' button>
navigate to param and tweak value>
repeat with other params if desired>
press 'lock' again to return to normal functions.
Dunno if someone with a better understanding of the midi au possibilities/limitations can come up with a potential way to make something that would have that kind of Elektron spontaneous fluid workflow between au sequencer + BM3 sampler/synth/fx for p-locks?
As mentioned by @StudioES, floating scalable windows could be an option but yeah, that does seem like something that would take a ton of work/serious overhaul....
Everyone gets paid and things could develop in a slightly less handicapped way. Less catering to the negative aspects of ios (and also lack of dev resources/time/manpower)... And intua wouldn't be spending a ton of time on coding some of the more niche requests/requirements and users could cherry pick some of their BM3 extended options/environment...
Probably unrealistic and not attractive to either party for one reason or another.. But would possibly be the ideal end game from my POV under current circumstances considering both devs' heavy workloads/specialist areas..
@Heyez it's not for me to comment.. but if I was BramBos I'd much sooner make universal AUv3 plugins rather than vendor-specific IAPs.
When you consider the small margins these developers get from selling apps at 4.99-9.99 I have complete sympathy for them wanting to sell products compatible for all DAWs/workflows rather than just one.
Propellerhead tried a similar experiment with Rack Extensions.. with mixed results... but they still ended up adding VST support in the end.
More like BM3 IAP editions of his existing stuff (and new things..). I'd be more inclined to buy something that integrated fully in to BM3 than something that linked in au fashion. And brambros might occasionally get people buying both versions even
Maybe the efforts involved in making BM3 IAP specific versions wouldn't weigh up tho in a business/time/hassle sense. I just hate page switching in BM3. My no.1 issue with it. So anything that could potentially be added as streamlined functionality under the hood on the keys/pads/sequencer pages/left column VS things like midi AUv3 etc would be killer..
Bless! Intua, Brambos, Kymatica etc etc..
King
..
Edit - I think midisteps also has a function for probability per step, similar to elektron trig conditions..
This looks very exciting, wondering if this internal MIDI works across banks too ?
I'm wondering that too, and it must be a newer beta than 3.0.6 beta #4
(The Odessa Plug-Ins load fine in #4 but their midi output can't be routed).
I've always wanted to have to option to select a 'bank/pad' as a midi-source for another pad, maybe this time we'll see it in action? Pure midi-pads could be a positive side effect of this...
requesting renaming this thread to something that makes sense.....
As Dean suggests.. any chance you could rename this thread to something like:
AUv3 midi - coming soon to BM3
@DeanDaughters @tk32 @philowerx - Thread has been renamed :-)
So it works like this: a new virtual MIDI source is created per AUv3 that offers MIDI output. Then you're up to use it as a source for either an AUv3, IAA, sampler... Pretty straightforward. Also, instantiation of new banks and plugins has been improved, so you can set this up really quickly.
Basically:
I posted this video earlier: 3 different Odessa apps sending MIDI to Bank B, loaded with Redshrike:
On a side note, we have this new "Single Channel" and "Multi Channel" option available in the MIDI settings of each track, for more routing (and easy) routing options. More on this shortly, when we'll post the 3.0.6 change log.
Cheers!
Amazing!
Thanks @mathieugarcia and @brambos ...you just made Odessa an instabuy for me
This will be fun to check out when released
I still can't shake the idea of being able to select the output from one pad as input for another.
This would make it easier to chain multiple 'midi plug-ins' without creating too many virtual ports and also make it possible to merge input from multiple pads and feed them to one destination. Maybe this sounds easier than it is to actually implement it?
"Zen code" VS "Priorities"
@mathieugarcia will it be possible to have multiple AU midi windows open at the same time, or is it one pad at a time?
If multiple, then the pad name would be useful to see in the window. The last video hints that there will only be one window at a time, in line with the pad/plugin concept. Which is fair, if much easier to implement.
@mathieugarcia so how are those three AU MIDI plugins summed together to all go to one Redshrike ?
Do the pads now have multiple MIDI inputs or are these chained together like a MIDI Thru ?
Im curious if the AUv3 can be sent to the bank MIDI input too, so if we have a drumkit across pads, can the drum sequencers be sent to the entire bank or just a pad.
Chomping at the bit to try this out haha.
Always struggle to get my head around the possibilities/limitations of this kind of thing before messing around with it. Like will I be able to assign the odessa lfos to auFX params on a BM3 pad that has an au synth on it? And similarly will I be able to have 'bank/pad macros' as Odessa Lfo destinations? Both of these would be OK workarounds till native modulation options are expanded
@5pinlink Exactly, a new virtual MIDI device will be created for each AUv3 MIDI plugin. I set up the 3 Odessa plugins to send to Channel 1. Then Bank B simply listen to those virtual MIDI devices. So that would work with the sampler too, or to record new patterns, etc.
I’m still confused because right now a bank can only have one MIDI input, but it uses all three, looking forward to seeing how it does it all, awesome that it is across banks so you can stick all your MIDI generators in one bank.
One last question, what happens with an AU MIDI pad or a bank that only has AU MIDI inside, in the mixer, they won’t have channels right ?
If I can send Odessa's drum sequencers to a bank with drum samples (or other kinds of samples!! hehehe!) across the pads, I am going to be screaming like a little girl.
Seriously, then I could use the rhythm sequencers to randomize melodic one shot samples across the pads and get:
super crazy happy dopeness sound design shizzle...