miRack — now AUv3! — for Beginners

hghon

>

@hghon said:
I didn’t explain what I meant correctly. I meant send/receive within patches instead of cables that stretch 3 rows and 10 modules across large patches 😄 if the patches are large enough say I want to connect my clock to another module some distance away, send/receive ports would sort that out without having to lock and hide all cables

Yeah that's how I understood it myself initially, yes, that's a good idea, I'll add it to my list.

Great 👍 thanks @mifki

dendy

@auxmux said:
@mifki Great to see the AU host beta. It would be awesome if there was clock input option for fx, and also a way to trigger notes such as for drum machine AUs.

yeah midi clock input is good also for instruments, you can have LFO bpm synced in synths

mifki

@auxmux said:
@mifki Great to see the AU host beta. It would be awesome if there was clock input option for fx, and also a way to trigger notes such as for drum machine AUs.

Yep, I'll add the clock input. As for the note inputs, I'm leaning towards using the standard MIDI I/O modules for that (i.e. for everything other than the most important MIDI inputs), there will just be an option to choose any of the Host modules alongside other MIDI interfaces to send to/receive from, that'll ensure the same functionality is available everywhere.

ronnieb

@mifki said:

@auxmux said:
@mifki Great to see the AU host beta. It would be awesome if there was clock input option for fx, and also a way to trigger notes such as for drum machine AUs.

Yep, I'll add the clock input. As for the note inputs, I'm leaning towards using the standard MIDI I/O modules for that (i.e. for everything other than the most important MIDI inputs), there will just be an option to choose any of the Host modules alongside other MIDI interfaces to send to/receive from, that'll ensure the same functionality is available everywhere.

Just want to make sure I’m not missing something, at the moment there is no way to start an Auv3’s sequencer until the clock input is added right?

I’m super excited to throw koala in mirack to record, chop and organise loops and ideas. It will be an incredible combo once the clock input is added.

Also, separate but related question, does mirack have latency compensation?

HotStrange

@ronnieb said:

@mifki said:

@auxmux said:
@mifki Great to see the AU host beta. It would be awesome if there was clock input option for fx, and also a way to trigger notes such as for drum machine AUs.

Yep, I'll add the clock input. As for the note inputs, I'm leaning towards using the standard MIDI I/O modules for that (i.e. for everything other than the most important MIDI inputs), there will just be an option to choose any of the Host modules alongside other MIDI interfaces to send to/receive from, that'll ensure the same functionality is available everywhere.

Just want to make sure I’m not missing something, at the moment there is no way to start an Auv3’s sequencer until the clock input is added right?

I’m super excited to throw koala in mirack to record, chop and organise loops and ideas. It will be an incredible combo once the clock input is added.

Also, separate but related question, does mirack have latency compensation?

You mean to start an AUV3s internal sequencer?

auxmux

@HotStrange said:

@ronnieb said:

@mifki said:

@auxmux said:
@mifki Great to see the AU host beta. It would be awesome if there was clock input option for fx, and also a way to trigger notes such as for drum machine AUs.

Yep, I'll add the clock input. As for the note inputs, I'm leaning towards using the standard MIDI I/O modules for that (i.e. for everything other than the most important MIDI inputs), there will just be an option to choose any of the Host modules alongside other MIDI interfaces to send to/receive from, that'll ensure the same functionality is available everywhere.

Just want to make sure I’m not missing something, at the moment there is no way to start an Auv3’s sequencer until the clock input is added right?

I’m super excited to throw koala in mirack to record, chop and organise loops and ideas. It will be an incredible combo once the clock input is added.

Also, separate but related question, does mirack have latency compensation?

You mean to start an AUV3s internal sequencer?

Yes, that's correct. Sequencers like Drambo and others won't work without clock input.

auxmux

@mifki said:

@auxmux said:
@mifki Great to see the AU host beta. It would be awesome if there was clock input option for fx, and also a way to trigger notes such as for drum machine AUs.

Yep, I'll add the clock input. As for the note inputs, I'm leaning towards using the standard MIDI I/O modules for that (i.e. for everything other than the most important MIDI inputs), there will just be an option to choose any of the Host modules alongside other MIDI interfaces to send to/receive from, that'll ensure the same functionality is available everywhere.

Ah, perfect, that would be great, thanks!

HotStrange

@auxmux said:

@HotStrange said:

@ronnieb said:

@mifki said:

@auxmux said:
@mifki Great to see the AU host beta. It would be awesome if there was clock input option for fx, and also a way to trigger notes such as for drum machine AUs.

Yep, I'll add the clock input. As for the note inputs, I'm leaning towards using the standard MIDI I/O modules for that (i.e. for everything other than the most important MIDI inputs), there will just be an option to choose any of the Host modules alongside other MIDI interfaces to send to/receive from, that'll ensure the same functionality is available everywhere.

Just want to make sure I’m not missing something, at the moment there is no way to start an Auv3’s sequencer until the clock input is added right?

I’m super excited to throw koala in mirack to record, chop and organise loops and ideas. It will be an incredible combo once the clock input is added.

Also, separate but related question, does mirack have latency compensation?

You mean to start an AUV3s internal sequencer?

Yes, that's correct. Sequencers like Drambo and others won't work without clock input.

Gotcha. Just wanted to make sure. I’m looking forward to it being implemented.

Wrlds2ndBstGeoshredr

@auxmux said:
@mifki Great to see the AU host beta. It would be awesome if there was clock input option for fx, and also a way to trigger notes such as for drum machine AUs.

I would hope a modular AU host allows CV access to the exposed parameters in the AU app.

bygjohn

@Wrlds2ndBstGeoshredr said:

@auxmux said:
@mifki Great to see the AU host beta. It would be awesome if there was clock input option for fx, and also a way to trigger notes such as for drum machine AUs.

I would hope a modular AU host allows CV access to the exposed parameters in the AU app.

Now that would be really something. It’ll be interesting to see if I end up using AUv3s hosted in MiRack or carry on using MiRack multi in/out within AUM. I suspect mostly I’ll keep using things as they currently are because of AUM’s routing capabilities etc, but I could see me doing things the other way round in some circumstances.

auxmux

@Wrlds2ndBstGeoshredr said:

@auxmux said:
@mifki Great to see the AU host beta. It would be awesome if there was clock input option for fx, and also a way to trigger notes such as for drum machine AUs.

I would hope a modular AU host allows CV access to the exposed parameters in the AU app.

It does.

mifki

@bygjohn said:
Now that would be really something. It’ll be interesting to see if I end up using AUv3s hosted in MiRack or carry on using MiRack multi in/out within AUM. I suspect mostly I’ll keep using things as they currently are because of AUM’s routing capabilities etc, but I could see me doing things the other way round in some circumstances.

On this topic, there's a problem here. As you know, miRack doesn't have transport controls, global BPM, time signature - the stuff a DAW has. While AU sequencers need this (communicated via AU API) and not just a MIDI clock input to work. Unless I find a very elegant way to integrate all that into the modular world, I'm not too keen on turning miRack into a DAW. But rather I'm working on improving how it's used inside other hosts (think customisable control UI for patches in AU mode and better preset management).

@ronnieb said:
I’m super excited to throw koala in mirack to record, chop and organise loops and ideas. It will be an incredible combo once the clock input is added.

What workflow did you have in mind? I'm not a Koala expert, but it looks like unlike other plugins, it does allow to decouple its transport from a host when in AU mode (in its settings) and its sequencer can be controlled with just MIDI once I add start/stop inputs (but it doesn't care about MIDI clock). And you can definitely trigger playback or recording of individual samples, which together with CV control for Koala effects makes it pretty awesome inside miRack already.

tyslothrop1

Au-hosting, cool! Can you host Aus with multiple ins and outs? Would be cool to host several MIRacks and have one for all modulations you commonly use, one for synth voices and another for FX, for example. Could keep things nice and tidyband you could drag in a whole racks you saved before. Would be awesome if the user could manually label in- and outputs.

hghon

@mifki said:

@ronnieb said:
I’m super excited to throw koala in mirack to record, chop and organise loops and ideas. It will be an incredible combo once the clock input is added.

What workflow did you have in mind? I'm not a Koala expert, but it looks like unlike other plugins, it does allow to decouple its transport from a host when in AU mode (in its settings) and its sequencer can be controlled with just MIDI once I add start/stop inputs (but it doesn't care about MIDI clock). And you can definitely trigger playback or recording of individual samples, which together with CV control for Koala effects makes it pretty awesome inside miRack already.

That’s exactly what I’ve been thinking about, simply loading Koala and trigger its pads with miRack’s various sequencers, CV control and send the multiouts into miRack’s mixers

mifki

@tyslothrop1 said:
Au-hosting, cool! Can you host Aus with multiple ins and outs? Would be cool to host several MIRacks and have one for all modulations you commonly use, one for synth voices and another for FX, for example. Could keep things nice and tidyband you could drag in a whole racks you saved before. Would be awesome if the user could manually label in- and outputs.

There will be module for this (i.e. some time soon) to load patches as a module, basically what you say but without the AU overhead.

tyslothrop1

@mifki said:

@tyslothrop1 said:
Au-hosting, cool! Can you host Aus with multiple ins and outs? Would be cool to host several MIRacks and have one for all modulations you commonly use, one for synth voices and another for FX, for example. Could keep things nice and tidyband you could drag in a whole racks you saved before. Would be awesome if the user could manually label in- and outputs.

There will be module for this (i.e. some time soon) to load patches as a module, basically what you say but without the AU overhead.

Ooh, even better

Kashi

@hghon said:

@mifki said:

@ronnieb said:
I’m super excited to throw koala in mirack to record, chop and organise loops and ideas. It will be an incredible combo once the clock input is added.

What workflow did you have in mind? I'm not a Koala expert, but it looks like unlike other plugins, it does allow to decouple its transport from a host when in AU mode (in its settings) and its sequencer can be controlled with just MIDI once I add start/stop inputs (but it doesn't care about MIDI clock). And you can definitely trigger playback or recording of individual samples, which together with CV control for Koala effects makes it pretty awesome inside miRack already.

That’s exactly what I’ve been thinking about, simply loading Koala and trigger its pads with miRack’s various sequencers, CV control and send the multiouts into miRack’s mixers

This sounds very cool indeed

mifki

@lazyass said:
something similar to CV-Map, Macro, Mirror, and Strip to enhance MiRack's capabilities?
P.S. Not a feature request, just asking

Why not, it's a good feature request and I have something like that in mind for a long time.

@mifki said:
On this topic, there's a problem here. As you know, miRack doesn't have transport controls, global BPM, time signature - the stuff a DAW has. While AU sequencers need this (communicated via AU API) and not just a MIDI clock input to work. Unless I find a very elegant way to integrate all that into the modular world, ...

Actually, I think I have a good idea how to do this.

hghon

@mifki said:

@mifki said:
On this topic, there's a problem here. As you know, miRack doesn't have transport controls, global BPM, time signature - the stuff a DAW has. While AU sequencers need this (communicated via AU API) and not just a MIDI clock input to work. Unless I find a very elegant way to integrate all that into the modular world, ...

Actually, I think I have a good idea how to do this.

Never in doubt 😄

bygjohn

@mifki said:

@bygjohn said:
Now that would be really something. It’ll be interesting to see if I end up using AUv3s hosted in MiRack or carry on using MiRack multi in/out within AUM. I suspect mostly I’ll keep using things as they currently are because of AUM’s routing capabilities etc, but I could see me doing things the other way round in some circumstances.

On this topic, there's a problem here. As you know, miRack doesn't have transport controls, global BPM, time signature - the stuff a DAW has. While AU sequencers need this (communicated via AU API) and not just a MIDI clock input to work. Unless I find a very elegant way to integrate all that into the modular world, I'm not too keen on turning miRack into a DAW. But rather I'm working on improving how it's used inside other hosts (think customisable control UI for patches in AU mode and better preset management).

I’m entirely happy with it not being a DAW, just getting a little carried away about possibilities!

The ability to load patches in as modules sounds fantastic, by the way.

Thank you for your continued work on this.

Carnbot

@mifki said:
On this topic, there's a problem here. As you know, miRack doesn't have transport controls, global BPM, time signature - the stuff a DAW has. While AU sequencers need this (communicated via AU API) and not just a MIDI clock input to work. Unless I find a very elegant way to integrate all that into the modular world, I'm not too keen on turning miRack into a DAW. But rather I'm working on improving how it's used inside other hosts (think customisable control UI for patches in AU mode and better preset management)

I agree with this
Thanks for the continuing updates! It's nice to see that miRack as an AU host is coming, but I would prefer custom Ui too and more modules rather than emphasis on a mirack-DAW. I think it might depend on how CPU intensive it is in comparison to hosting AU in other hosts, and stability of course. Look forward to trying it.

I do get quite a lot of crashes with miRack recently, I hope you're getting my crash reports.

Synthi

Hi @mifki ! Awesome new features coming, thanks a lot!
Been testing yesterday and I get huge difference when using standalone vs AUv3 hosted on. AUM. The Nysthi simpliciter seem to be the cultprint: same patch using standalone CPU consumption 2% , AUv3 in AUM 86% and peaking to max…Maybe you could check while you are on it??
Thanks!🙏🏻😍

mifki

@Carnbot said:
I do get quite a lot of crashes with miRack recently, I hope you're getting my crash reports.

Yes, I'm having a look at the crashes for the next update.

@Synthi said:
Hi @mifki ! Awesome new features coming, thanks a lot!
Been testing yesterday and I get huge difference when using standalone vs AUv3 hosted on. AUM. The Nysthi simpliciter seem to be the cultprint: same patch using standalone CPU consumption 2% , AUv3 in AUM 86% and peaking to max…Maybe you could check while you are on it??
Thanks!🙏🏻😍

I did a quick test and didn't notice any difference between Simpliciter in standalone and AUv3 in AUM. Could you share your patch or a screenshot of it?

Synthi

@mifki said:

I did a quick test and didn't notice any difference between Simpliciter in standalone and AUv3 in AUM. Could you share your patch or a screenshot of it?

Thanks @mifki , here are the screenshots:

Here in miRack standalone:

Here in AUM, you can see there are no other processes, just one channel with miRack inserted:

Also attaching the preset.

Air4 16.4.1

Thanks!!

Synthi

@Synthi said:

@mifki said:

I did a quick test and didn't notice any difference between Simpliciter in standalone and AUv3 in AUM. Could you share your patch or a screenshot of it?

Thanks @mifki , here are the screenshots:

Here in miRack standalone:

Here in AUM, you can see there are no other processes, just one channel with miRack inserted:

Also attaching the preset.

Air4 16.4.1

Thanks!!

Update:
I’ve been testing, first trying in my other iPad (old pro 10’5”) and had the same problem, then disconnecting each cable and looking for a change in CPU.. until I found the culprit: the record button in simplicity! I had it fired by external trigger but pushing manually has the same effect, the CPU consumption goes to the roof for some seconds. If you keep pushing or triggering the button then it stays always on top

mifki

@Synthi
I'm able to repro the same behaviour, however when I use dev tools to measure CPU consumption of AUM and miRack AUv3 processes, it stays pretty much the same when AUM shows high CPU load and when it's not. So I'm not sure what's happening there. Are you having any actual issues other than the numbers shown, audio dropouts, etc.? At the same time, it's very possibly this module isn't quite suitable for such use case, it seems to be recording to disk, not memory, maybe it's related (NYSTHI is closed-source, so I can't see exactly what it's doing).

Carnbot

In this use case with Simpliciter I only find the cpu spiking to be minimal and not really an issue but that might be because I use a large buffer because my ipad is quite old now (2017 pro)

Synthi

@mifki said:
@Synthi
I'm able to repro the same behaviour, however when I use dev tools to measure CPU consumption of AUM and miRack AUv3 processes, it stays pretty much the same when AUM shows high CPU load and when it's not. So I'm not sure what's happening there. Are you having any actual issues other than the numbers shown, audio dropouts, etc.? At the same time, it's very possibly this module isn't quite suitable for such use case, it seems to be recording to disk, not memory, maybe it's related (NYSTHI is closed-source, so I can't see exactly what it's doing).

Hmmm… maybe @j_liljedahl can help with this AUM behavior

dendy

not sure if everybo> @Synthi said:

@mifki said:
@Synthi
I'm able to repro the same behaviour, however when I use dev tools to measure CPU consumption of AUM and miRack AUv3 processes, it stays pretty much the same when AUM shows high CPU load and when it's not. So I'm not sure what's happening there. Are you having any actual issues other than the numbers shown, audio dropouts, etc.? At the same time, it's very possibly this module isn't quite suitable for such use case, it seems to be recording to disk, not memory, maybe it's related (NYSTHI is closed-source, so I can't see exactly what it's doing).

Hmmm… maybe @j_liljedahl can help with this AUM behavior

i think miRack uses multicore , AUM doesn't - maybe that is reason ? Maybe it's just thst AUM process of CPU load measurement gets fooled ?

j_liljedahl

@Synthi said:

@mifki said:
@Synthi
I'm able to repro the same behaviour, however when I use dev tools to measure CPU consumption of AUM and miRack AUv3 processes, it stays pretty much the same when AUM shows high CPU load and when it's not. So I'm not sure what's happening there. Are you having any actual issues other than the numbers shown, audio dropouts, etc.? At the same time, it's very possibly this module isn't quite suitable for such use case, it seems to be recording to disk, not memory, maybe it's related (NYSTHI is closed-source, so I can't see exactly what it's doing).

Hmmm… maybe @j_liljedahl can help with this AUM behavior

I don't know how miRack measures CPU usage, but AUM checks the time it takes for all audio plugins etc to do their thing, and compares it to the duration of the buffer cycle interval. So if you're running with 512 frame buffer size at 44.1kHz sample rate, it means the system must process all audio within a 11.6mS time window. If the processing takes 5.8mS, AUM displays that as "DSP: 50%", etc. Since this value is updated very frequently (86 times per second in this example), AUM takes the peak value since the last second or two.

Now, an AUv3 that records to disk might work well or not depending on how it's implemented. If it's doing actual disk writes from the audio processing thread, it's a big no no.