miRack — now AUv3! — for Beginners

bygjohn

@mifki said:
That's true however there's a separation between control knobs and CV inputs, if module provides both for a certain parameter, there's no problem. But if not, you need a workaround. Knob->CV is surely possible, but the other way is currently not (and therefore not possible to build macros for knobs). Of course, in hw modular if there's no CV input, you can't control that parameter and that it's it. But for software features like MIDI mapping, AU parameter mapping or building custom modules, I feel like it should be possible to control anything you want in some unified way.

Ah, so I was missing something obvious! Thanks for clarifying. And looking at your latest screenshots, this will be amazing!

Carnbot

@Luxthor said:

@Carnbot said:
There's already touch strip module which you could add to the controls, so you could make a touch based macro controller

So, you could touch and slide through the wavetable?! Well… 😅

That seven seas wavetable module is already touch capable so hopefully that still is possible in the macro version too, but only @mifki knows at this point

sevenape

@tyslothrop1 said:

@sevenape said:

@scrape said:

@sevenape said:

@scrape said:

@HotStrange said:

@scrape said:
Is there something similar in VCV Rack or is this unique? Amazing update.

On iOS you mean? Besides MiRack there’s Audulus which is also fully modular. Then semi modular you have KQ Minisynth, Branches, Ripplemaker, Model 15, MS20, Factory, Drambo, and Tera Pro.

Ah, sorry. I wasn’t very clear. I meant the new macro module. Great for anyone who wants to build and share a synth/patch with people not familiar with miRack. And for jamming on it yourself. You don’t have to use 2 apps, portable between hosts.

You can build front plates in Audulus but it all seems a bit more complicated to me

Cheers. Audulus does look good too. iPad only though.

yep it's a shame... Drambo allows you to hide stuff in compact view so you can leave only the knobs you want visible, that's pretty good, although that's the extent of the customizability of the 'front plate'

In Drambo, you can also connect modulatable knobs directly to sliders and knobs (unmodulatble need a morph-module, that you can then connect to a knob or slider). If you hide everything but the added controls, you can control the order of stuff and rename the modules etc. The xy-pads are cool, too.

oh yes, that's definitely true, the morph controls are a godsend

hghon

@Luxthor said:

@mifki said:

@mifki said:

@Carnbot said:
Will the custom modules also include ability to use module displays for things like Simpliciter waveform view and lfo displays etc?

I haven't tried yet, but it should be possible, same for lights.

Tried now, it works. Also implemented snapping when positioning components, much easier now.

Make that scale touch-sensitive, then we can talk!

That’s Nyshti Seven Seas!! It’s already touch-sensitive

hghon

@dendy said:

@hghon said:

@dendy said:

@wim
To me a separate module would be better for "macros".

this is already possible, you can use these modules to build set of macro knibs and buttons ans even label them using that module on right ...

I’m guessing they meant to control stuff that don’t have CV inputs. Otherwise yes you can control them that way and I also like Nysthi Surveillance for macros with individual attenuverters 👍

Ah ok that makes sense. Solution would be module with "morp" knob like in Drambo

Yes Morph would be ideal for it

Luxthor

@Carnbot said:

@Luxthor said:

@Carnbot said:
There's already touch strip module which you could add to the controls, so you could make a touch based macro controller

So, you could touch and slide through the wavetable?! Well… 😅

That seven seas wavetable module is already touch capable so hopefully that still is possible in the macro version too, but only @mifki knows at this point

@hghon said:
That’s Nyshti Seven Seas!! It’s already touch-sensitive

Yeah, the main question was, can we keep the same functionality as it is on the copied control element? As it looks, it’s probably possible, which means we could do this with every other element. Pure madness! 🤩

hghon

@Luxthor said:

@Carnbot said:

@Luxthor said:

@Carnbot said:
There's already touch strip module which you could add to the controls, so you could make a touch based macro controller

So, you could touch and slide through the wavetable?! Well… 😅

That seven seas wavetable module is already touch capable so hopefully that still is possible in the macro version too, but only @mifki knows at this point

@hghon said:
That’s Nyshti Seven Seas!! It’s already touch-sensitive

Yeah, the main question was, can we keep the same functionality as it is on the copied control element? As it looks, it’s probably possible, which means we could do this with every other element. Pure madness! 🤩

Yes! Tact controllers! Big Mi Triggers! Turing Machines 🤤 Big button Seq! I’m getting dizzy 😄

mifki

@Luxthor said:

@Carnbot said:

@Luxthor said:

@Carnbot said:
There's already touch strip module which you could add to the controls, so you could make a touch based macro controller

So, you could touch and slide through the wavetable?! Well… 😅

That seven seas wavetable module is already touch capable so hopefully that still is possible in the macro version too, but only @mifki knows at this point

@hghon said:
That’s Nyshti Seven Seas!! It’s already touch-sensitive

Yeah, the main question was, can we keep the same functionality as it is on the copied control element? As it looks, it’s probably possible, which means we could do this with every other element. Pure madness! 🤩

Yes of course you can touch-control the copy, otherwise, why would I be showing it:)

wim

This is all so amazingly cool and innovative. miRack is taking a huge leap forward!

waka_x

the update with auv3 support (host module) is OUT now!
works great on my iPad Air 3 but
fails to start (crashes at start) on my old iPad Air with iOS 12.5.7...

@mifki
please please fix that if possible...
I still use my old machines for fx live.
thanks!!!

dasgoods

So a member of our Apple family share, purchased MiRack for us all to use.

But is it possible that all the members in our family, can share the AUV3 that I have purchased?

mifki

@waka_x said:
the update with auv3 support (host module) is OUT now!
works great on my iPad Air 3 but
fails to start (crashes at start) on my old iPad Air with iOS 12.5.7...

Sure I’ll have a look.

@dasgoods said:
So a member of our Apple family share, purchased MiRack for us all to use.

But is it possible that all the members in our family, can share the AUV3 that I have purchased?

Yes I will enable family sharing for it.

Also, people who helped to beta-test the AUv3 module can PM me for a promo code.

hghon

Mmm I seem to have lost the miRack folder on my iPhone after the latest update. Any help @mifki ? I had turned off iCloud storage and only stored to phone and now the folder disappeared.

mifki

I've made a new beta version available introducing the Controller module allowing to make custom front panels for patches to be used in AUv3 mode as shown in a demo some time ago. Please see the beta notes and Controller module manual as they include a lot of important info. Let's see what you'll make with it!

HotStrange

@mifki said:
I've made a new beta version available introducing the Controller module allowing to make custom front panels for patches to be used in AUv3 mode as shown in a demo some time ago. Please see the beta notes and Controller module manual as they include a lot of important info. Let's see what you'll make with it!

Cool, I’ll start testing tonight!

auxmux

Awesome! Will have more time to test this weekend!

Kashi

Every time I open mirack and select one of the new AUv3 hosting modules, it’s as though I haven’t purchased them (?) I am given the option to “purchase module pack” but I have already bought them.
Please help

bygjohn

@Kashi said:
Every time I open mirack and select one of the new AUv3 hosting modules, it’s as though I haven’t purchased them (?) I am given the option to “purchase module pack” but I have already bought them.
Please help

I’ve only had that happen when using MiRack as an AUv3, where the modules won’t do anything anyway as you can’t nest AUv3s inside each other.

(FWIW, I was wondering if you could load an existing MiRack patch as an AUv3 - you can’t!)

Kashi

@bygjohn said:

@Kashi said:
Every time I open mirack and select one of the new AUv3 hosting modules, it’s as though I haven’t purchased them (?) I am given the option to “purchase module pack” but I have already bought them.
Please help

I’ve only had that happen when using MiRack as an AUv3, where the modules won’t do anything anyway as you can’t nest AUv3s inside each other.

(FWIW, I was wondering if you could load an existing MiRack patch as an AUv3 - you can’t!)

I don't quite understand. Do you mean it will work if I open mirack standalone? But not within AUM?

wim

@Kashi said:

@bygjohn said:

@Kashi said:
Every time I open mirack and select one of the new AUv3 hosting modules, it’s as though I haven’t purchased them (?) I am given the option to “purchase module pack” but I have already bought them.
Please help

I’ve only had that happen when using MiRack as an AUv3, where the modules won’t do anything anyway as you can’t nest AUv3s inside each other.

(FWIW, I was wondering if you could load an existing MiRack patch as an AUv3 - you can’t!)

I don't quite understand. Do you mean it will work if I open mirack standalone? But not within AUM?

That's correct. No app running as an AUv3 plugin can load AUv3 plugins in itself.

@mifki - messaging that you need to purchase the modules when you try to add them in the AUv3 is very confusing. It would be much better to explain that those modules can't be used when miRack is running as a plugin.

Kashi

@wim said:

@Kashi said:

@bygjohn said:

@Kashi said:
Every time I open mirack and select one of the new AUv3 hosting modules, it’s as though I haven’t purchased them (?) I am given the option to “purchase module pack” but I have already bought them.
Please help

I’ve only had that happen when using MiRack as an AUv3, where the modules won’t do anything anyway as you can’t nest AUv3s inside each other.

(FWIW, I was wondering if you could load an existing MiRack patch as an AUv3 - you can’t!)

I don't quite understand. Do you mean it will work if I open mirack standalone? But not within AUM?

That's correct. No app running as an AUv3 plugin can load AUv3 plugins in itself.

Gotcha! Makes sense. Thanks @wim - really appreciate you answering all my dumb questions with such patience and understanding

@mifki - messaging that you need to purchase the modules when you try to add them in the AUv3 is very confusing. It would be much better to explain that those modules can't be used when miRack is running as a plugin.

Yes - I agree. Very confusing

bygjohn

The confusion is made worse due to the ability to restore purchases within the AUv3 (which will probably be needed down the road for paid modules), so you can get them to add to your patch, they then just don’t work. A clear message saying they don’t work when MiRack is in AUv3 mode would help a lot.

Kashi

Am curious to hear what people are thinking, in terms of how these new AUv3 host modules will open up new possibilities.

I just watched Leo's 3 recent videos (thanks @sfm ! very clear and useful as always) - and everything he explains can be easily achieved in AUM (i.e connecting a keyboard to an instrument, then playing that instrument through an effect,...and then connecting a sequencer to an instrument, and then modulating parameters with an LFO).

I'm not being coy. I'm not playing devil's advocate. I am genuinely interested to hear people's thoughts about how this implementation will open things up.
My hope is that your suggestions/ideas will allow me to "see" this in new ways, so that I can explore further...
Cheers!

wim

@Kashi said:
Am curious to hear what people are thinking, in terms of how these new AUv3 host modules will open up new possibilities.

To be honest, I don't think it opens up new capabilities that you couldn't already do with input and output from miRack in AUM or other hosts. It's a more direct experience though, and different ways of doing things can inspire new ideas.

Sometimes perceptually, not wiring apps together in different ways makes things clearer. Say you have a miRack module such as Topograph. You can either wire it up to a Midi Trigger Out module and send it through AUM's routing matrix to another app, or you can host it in miRack and wire directly to the app. Neither is much different, but just having it right there in the patch can be nice. Same for audio. Does it change what you can do? Not really.

If you're doing a bunch of combining of modules and AUv3's in different ways, juggling your mind between AUM channels, midi routing, FX slots, Busses, etc. can be a conceptually confusing than just re-plugging a few cables within one app. That may help encourage more experimentation. But in the end, it's all just routing of audio and midi no matter how you slice it.

The control surface module is going to be the bigger enabler I think.

HotStrange

@wim said:

@Kashi said:
Am curious to hear what people are thinking, in terms of how these new AUv3 host modules will open up new possibilities.

To be honest, I don't think it opens up new capabilities that you couldn't already do with input and output from miRack in AUM or other hosts. It's a more direct experience though, and different ways of doing things can inspire new ideas.

Sometimes perceptually, not wiring apps together in different ways makes things clearer. Say you have a miRack module such as Topograph. You can either wire it up to a Midi Trigger Out module and send it through AUM's routing matrix to another app, or you can host it in miRack and wire directly to the app. Neither is much different, but just having it right there in the patch can be nice. Same for audio. Does it change what you can do? Not really.

If you're doing a bunch of combining of modules and AUv3's in different ways, juggling your mind between AUM channels, midi routing, FX slots, Busses, etc. can be a conceptually confusing than just re-plugging a few cables within one app. That may help encourage more experimentation. But in the end, it's all just routing of audio and midi no matter how you slice it.

The control surface module is going to be the bigger enabler I think.

Is the surface control module gonna be similar to surface builder from 4pockets? I haven’t had a chance to mess with it yet.

Or is it a control surface just for the synths you build in MiRack?

mifki

It shouldn't be like that, thanks for pointing out about the host modules.

Or is it a control surface just for the synths you build in MiRack?

Yes it's for building custom front panels for miRack patches so that when you load them in AUv3 mode, you see only the controls you need and not the entire patch.

wim

@HotStrange said:
Is the surface control module gonna be similar to surface builder from 4pockets? I haven’t had a chance to mess with it yet.

Early iteration, but here's the idea:
https://forum.audiob.us/discussion/comment/1260346/#Comment_1260346

HotStrange

@wim said:

@HotStrange said:
Is the surface control module gonna be similar to surface builder from 4pockets? I haven’t had a chance to mess with it yet.

Early iteration, but here's the idea:
https://forum.audiob.us/discussion/comment/1260346/#Comment_1260346

Thanks I saw that but haven’t had time to watch the video yet. Will check it out when I get time.

sevenape

@mifki said:
It shouldn't be like that, thanks for pointing out about the host modules.

Or is it a control surface just for the synths you build in MiRack?

Yes it's for building custom front panels for miRack patches so that when you load them in AUv3 mode, you see only the controls you need and not the entire patch.

This is gonna be a literal game changer! Can't wait to see the weird and wonderful boxes people come up with

mifki

I'm now figuring out how presets are going to work. The idea is of course to be able to create presets for such custom modules (or what's a better way to call them as they're not quite modules anymore) which will be accessible just like presets normally are an AUv3 plugin.