miRack by mifki Limited - Live!!!

Yalexein

I agree with you!

@espiegel123 said:
@mifki: the AU is working well.

I have a wish.. that there be a persistent option one can set to disable making cable connections. Too often, I accidentally disconnect a cable while trying to either scroll or turn a knob. With no undo , it can be troublesome re-wiring in a complex patch. My personal preference would be to have the ability to make wiring changes be off when opening existing patches with an easy way to turn them on.

cian

Fairly sure turn off cables does this.

Yalexein

@cian said:
Fairly sure turn off cables does this.

Yep, if I remember correctly you cannot edit cables in that mode.

Clueless

AUv3? Oh, nice. That beat VCV which might take much longer to become a plug-in.
That also mean polyphonic patches are possible as well (so one voice per instance).
Anyone know if such a multi patch can be saved and reloaded in NS2?
Since it does layers/groups i wonder if i could save that as kind of polyphonic synth patch.

Yalexein

I do not see how. You will have unison. Just auv3 and polyphony and mirack is complete for me.

@Clueless said:
AUv3? Oh, nice. That beat VCV which might take much longer to become a plug-in.
That also mean polyphonic patches are possible as well (so one voice per instance).
Anyone know if such a multi patch can be saved and reloaded in NS2?
Since it does layers/groups i wonder if i could save that as kind of polyphonic synth patch.

espiegel123

@Jocphone said:

@espiegel123 said:
@mifki: the AU is working well.

I have a wish.. that there be a persistent option one can set to disable making cable connections. Too often, I accidentally disconnect a cable while trying to either scroll or turn a knob. With no undo , it can be troublesome re-wiring in a complex patch. My personal preference would be to have the ability to make wiring changes be off when opening existing patches with an easy way to turn them on.

You know about hiding cables in the tool menu?

THANKS! I had forgotten about it and didn't realize that it was persistent.

cian

Audible Instruments modules (the mutable instruments modules basically).

Think there's another one, but those give you plenty to being get on with. The Mutable Instruments oscillators are all really good.

Clueless

@Yalexein said:
I do not see how. You will have unison. Just auv3 and polyphony and mirack is complete for me.

@Clueless said:
AUv3? Oh, nice. That beat VCV which might take much longer to become a plug-in.
That also mean polyphonic patches are possible as well (so one voice per instance).
Anyone know if such a multi patch can be saved and reloaded in NS2?
Since it does layers/groups i wonder if i could save that as kind of polyphonic synth patch.

Splitting midi channels and using an MPE controller f.e. or using software which make kind of round robin midi channel for each voice or just send next voice to next midi channel etc.
There are different ways.
I see no limitations in mono synths these days.
Even sometimes prefer playing 4 mono voices like a poly since also the FX can be polyphonic here.

aplourde

@mifki said:

@cian said:
Does the new AU3 do MIDI out? As an AU3 for audio is already going to be huge, but MIDI out (and dare one ask multi-audio) would make this enormous

MIDI out and multichannel audio will come separately. I know I promised them long time ago, but as I was also saying, I wanted to release stuff like AUv3 first so that I can work on smaller things without worrying I have a big uncertain task in front of me.

Fantastic news! Looking forward to the journey ahead!

@espiegel123 said:

@Jocphone said:

@espiegel123 said:
@mifki: the AU is working well.

I have a wish.. that there be a persistent option one can set to disable making cable connections. Too often, I accidentally disconnect a cable while trying to either scroll or turn a knob. With no undo , it can be troublesome re-wiring in a complex patch. My personal preference would be to have the ability to make wiring changes be off when opening existing patches with an easy way to turn them on.

You know about hiding cables in the tool menu?

THANKS! I had forgotten about it and didn't realize that it was persistent.

I would still love a way to lock the cables while still seeing them. Especially when you're playing a patch or trying to debug, seeing the connections is crucial to understanding what's going on.

That said, what I really want is undo! And most importantly, the ability to save or not save a patch when exiting, so I can bail on a patch if I completely screw it up and don't have to worry if I remembered to make a duplicate first!

aplourde

@Clueless said:

@Yalexein said:
I do not see how. You will have unison. Just auv3 and polyphony and mirack is complete for me.

@Clueless said:
AUv3? Oh, nice. That beat VCV which might take much longer to become a plug-in.
That also mean polyphonic patches are possible as well (so one voice per instance).
Anyone know if such a multi patch can be saved and reloaded in NS2?
Since it does layers/groups i wonder if i could save that as kind of polyphonic synth patch.

Splitting midi channels and using an MPE controller f.e. or using software which make kind of round robin midi channel for each voice or just send next voice to next midi channel etc.
There are different ways.
I see no limitations in mono synths these days.
Even sometimes prefer playing 4 mono voices like a poly since also the FX can be polyphonic here.

There are definitely advantages to running polyphonically in one instance because all the voices can interact with each other. In fact, I'm less interested in the porting to AU than I am in multiple outputs. For me, I want everything in one instance so modulations can affect multiple voices; voices can affect each other, etc.

dendy

@mifki

any chance to add those modules to miRack ? Blamsoft made some cool iOS plugins so i guess in theory they should be opened for porting VCV modules to miRack

https://blamsoft.com/vcv-rack

also this would be lovely addition:
https://library.vcvrack.com/LindenbergResearch (especially this one https://library.vcvrack.com/LindenbergResearch/DIODE_VCF )

reasOne

that blamsoft wave is amazing

cian

More filters would definitely be good. Also maybe a decent delay. Maybe I've missed it, but none of the delays seem that great atm.

auxmux

Loving this beta!

bobbfett

Was it an open beta, how do I get hold on it. I own the main version and have testpilot.
Br Bob

Yalexein

Yep I would like to offer help too. I am using miRack a lot in this period.

Gavinski

I'd also like to be on this beta, am also an existing (though beginner) user.

philowerx

Are there any other beta testers using BM3? Seems the AU parameter automation is a bit NS2 centric at this point in time. In general with AU automation with NS2 you have to decide which parameter you want to use beforehand where with most AU apps in BM3 you just tweak a knob or slider and it’s automatically assigned at that point with no limit to the number of AU apps available parameters as opposed to NS2 8 AU parameter limitation. Also miRack knob movement playback is not reflected in BM3.

mifki

There's nothing NS2-specific, but yes, parameter automation in miRack is a bit different from other AU plugins because the parameters are not static and depend on a patch.

Instead of exposing all of them (more on this below), miRack currently exposes 10 AU parameters, and you can map each to one or more actual module parameters (knobs). After that, you should be able to automate movement of these knobs in any DAW, or the other way round, move the assigned knobs to record automation.

I will try to simplify this process by requiring to just choose which module parameters to expose, but the last time I tried implementing dynamic parameter list it didn't work. This is also why I can't dynamically expose all patch knobs as parameters (although even if I could I think there's no point as the list would be too big).

philowerx

@mifki said:
There's nothing NS2-specific, but yes, parameter automation in miRack is a bit different from other AU plugins because the parameters are not static and depend on a patch.

Instead of exposing all of them (more on this below), miRack currently exposes 10 AU parameters, and you can map each to one or more actual module parameters (knobs). After that, you should be able to automate movement of these knobs in any DAW, or the other way round, move the assigned knobs to record automation.

I will try to simplify this process by requiring to just choose which module parameters to expose, but the last time I tried implementing dynamic parameter list it didn't work. This is also why I can't dynamically expose all patch knobs as parameters (although even if I could I think there's no point as the list would be too big).

Yes, NS2 is limited 8 user preassigned AU parameters, miRack currently 10.
That’s the beauty of BM3. The AU parameter only populates when you move a
knob or slider and only limited by those exposed per app and if an app is properly programmed all knobs and sliders will move on playback.
Do you have a copy of BM3?

mifki

@philowerx said:
That’s the beauty of BM3. The AU parameter only populates when you move a
knob or slider.
Do you have a copy of BM3?

Yes I do. I guess you're talking about parameters appearing in BM3, but even if not showing them, BM3 already knows about all parameters. When AU instance is created, it must report all parameters it has ("parameter tree"). In case of miRack, this list is not static, it depends on a patch. I wasn't able to get such dynamic parameter tree working (and not sure hosts support them either). That's why miRack currently reports a static list of 10 parameters to host and you have to do the manual assignment. It has nothing to do with a specific host app really.

auxmux

I really like how the parameter selection process is done @mifki. It's very intuitive. I just wish there was more than 10. Though using midi parameters is good workaround.

dendy

@mifki

i like current parameters mapping very much, it's easy, intuitive, fast.. good job !

what i really like is that you can assign multiple parameters on same knob - that is epic, it allows to create very complex mappinx with just one knob altering sound of patch significantly. Instant morphing !!

one idea how make it even more handy - it would be super handy if it will be possíe to define range (min -max) which au parameter knob on each asigned module parameter knob controls

some simple list like this

[parameter knob] [mapped module param] [min] [max] [x]

I see place for this in "Tools" menu... btw [x] would be button for removing that mapping

OnfraySin

@dendy said:
@mifki

i like current parameters mapping very much, it's easy, intuitive, fast.. good job !

what i really like is that you can assign multiple parameters on same knob - that is epic, it allows to create very complex mappinx with just one knob altering sound of patch significantly. Instant morphing !!

one idea how make it even more handy - it would be super handy if it will be possíe to define range (min -max) which au parameter knob on each asigned module parameter knob controls

some simple list like this

[parameter knob] [mapped module param] [min] [max] [x]

I see place for this in "Tools" menu... btw [x] would be button for removing that mapping

I don't like at all this kind of "macro" but you can use TACT-1 module to this.

Multiple outputs and it's done

MadGav

@dendy said:
@mifki

i like current parameters mapping very much, it's easy, intuitive, fast.. good job !

what i really like is that you can assign multiple parameters on same knob - that is epic, it allows to create very complex mappinx with just one knob altering sound of patch significantly. Instant morphing !!

one idea how make it even more handy - it would be super handy if it will be possíe to define range (min -max) which au parameter knob on each asigned module parameter knob controls

some simple list like this

[parameter knob] [mapped module param] [min] [max] [x]

I see place for this in "Tools" menu... btw [x] would be button for removing that mapping

A modular approach to this would be to map to “just a knob” maybe called on offset or fixed value, then use that to modulate other modules. Though this does depend on the other modules having modulation inputs for everything.

dendy

@OnfraySin said:
I don't like at all this kind of "macro" but you can use TACT-1 module to this.

Multiple outputs and it's done

Oooo coool, thanks for tip, will try it

dendy

@MadGav said:
A modular approach to this would be to map to “just a knob” maybe called on offset or fixed value, then use that to modulate other modules. Though this does depend on the other modules having modulation inputs for everything.

Oh yes, this is weak place of method suggested by OnfraySin, it is limited to controls with CV input .. still better than nothing, definitely useable module that TACT-1 !

OnfraySin

@dendy said:

@MadGav said:
A modular approach to this would be to map to “just a knob” maybe called on offset or fixed value, then use that to modulate other modules. Though this does depend on the other modules having modulation inputs for everything.

Oh yes, this is weak place of method suggested by OnfraySin, it is limited to controls with CV input .. still better than nothing, definitely useable module that TACT-1 !

Not a weak place...this is modular!

philowerx

@mifki said:

@philowerx said:
That’s the beauty of BM3. The AU parameter only populates when you move a
knob or slider.
Do you have a copy of BM3?

Yes I do. I guess you're talking about parameters appearing in BM3, but even if not showing them, BM3 already knows about all parameters. When AU instance is created, it must report all parameters it has ("parameter tree"). In case of miRack, this list is not static, it depends on a patch. I wasn't able to get such dynamic parameter tree working (and not sure hosts support them either). That's why miRack currently reports a static list of 10 parameters to host and you have to do the manual assignment. It has nothing to do with a specific host app really.

Bummer. miRack AU support is crippled compared to Ripplemaker and iVCS3.

auxmux

@philowerx said:

@mifki said:

@philowerx said:
That’s the beauty of BM3. The AU parameter only populates when you move a
knob or slider.
Do you have a copy of BM3?

Yes I do. I guess you're talking about parameters appearing in BM3, but even if not showing them, BM3 already knows about all parameters. When AU instance is created, it must report all parameters it has ("parameter tree"). In case of miRack, this list is not static, it depends on a patch. I wasn't able to get such dynamic parameter tree working (and not sure hosts support them either). That's why miRack currently reports a static list of 10 parameters to host and you have to do the manual assignment. It has nothing to do with a specific host app really.

Bummer. miRack AU support is crippled compared to Ripplemaker and iVCS3.

This is not a big issue. miRack is not like other AU. There could be hundreds of parameters depending on the size of the modules in a patch. It makes sense to have limits. Other AUs have a fixed number of defined parameters every time. Once you have a few favorite patches, you can save those configurations with midi or au parameters in AUM. Not a big deal.