miRack by mifki Limited - Live!!!

espiegel123

@mifki said:
Brace yourself for the next update. There was a danger of Apple removing the app without looking at the facts, so we’ve reached a compromise with Wes, and Fundamental modules will not be available in miRack but will continue to function in existing patches without panels and controls, until replaced. I hope this is the last time I hear from those two.

Apart from this, I added Submarine modules - a big collection of modules for signal processing and visualisation (a very good replacement for the Fundamental scope) plus phased oscillators.

Also this update preserves information about missing modules, so that if you open a patch with modules not available in miRack and save it, the modules will not disappear.

Will there be modules that replace the functionality provided by the fundamentals modules like the Attenuverters and what-not?

mifki

@palms said:
I wonder if I'm an outlier, but I've never used those much anyhow. too vanilla for my tastes. The only one of them that I use on the regular is the scope

Yeah I was adding these Submarine modules and thinking that there’s so many sensible and friendly developers and their modules. Surely the removal is a problem for people with existing patches, and I apologise for this, but shouldn’t be a problem for new patches.

mifki

@espiegel123 said:

@rs2000 said:

@gonekrazy3000 said:

@mifki said:
I guess for some, modular is just a way to build some custom "device" and then use it like any other effect or generator plugin.

This is exactly what modular is to me.

This is what Audulus does for me because of its more flexible design.
miRack is more like an independent, sometimes sequenced, instrument to me.
That's why I find an audio recorder/player to record loops inside the app essential.

Now, that miRack has Audiobus compatibilit, I don’t see the need for an internal recorder. It is easy enough to send miRack’s output to a lightweight recorder. I’d much rather see Vitaly spend his time implementing stuff we can’t already do.

I think the idea was to have a recorder that can be triggered with a signal inside the patch. Audiobus solved the recording problem for now, but such a module still will be useful I guess.

[Deleted User]

@espiegel123 said:

@rs2000 said:

@gonekrazy3000 said:

@mifki said:
I guess for some, modular is just a way to build some custom "device" and then use it like any other effect or generator plugin.

This is exactly what modular is to me.

This is what Audulus does for me because of its more flexible design.
miRack is more like an independent, sometimes sequenced, instrument to me.
That's why I find an audio recorder/player to record loops inside the app essential.

Now, that miRack has Audiobus compatibilit, I don’t see the need for an internal recorder. It is easy enough to send miRack’s output to a lightweight recorder. I’d much rather see Vitaly spend his time implementing stuff we can’t already do.

This is still needed for other users.

[Deleted User]

@mifki said:

@espiegel123 said:

@rs2000 said:

@gonekrazy3000 said:

@mifki said:
I guess for some, modular is just a way to build some custom "device" and then use it like any other effect or generator plugin.

This is exactly what modular is to me.

This is what Audulus does for me because of its more flexible design.
miRack is more like an independent, sometimes sequenced, instrument to me.
That's why I find an audio recorder/player to record loops inside the app essential.

Now, that miRack has Audiobus compatibilit, I don’t see the need for an internal recorder. It is easy enough to send miRack’s output to a lightweight recorder. I’d much rather see Vitaly spend his time implementing stuff we can’t already do.

I think the idea was to have a recorder that can be triggered with a signal inside the patch. Audiobus solved the recording problem for now, but such a module still will be useful I guess.

The recorder module would benefit from Record syncing to the BPM so a perfect 4, 8, 16 etc.. bar loop can be generated. The standalone version of Reslice does this beautifully.

NoiseFloored

When miRack was released, I immediately noticed blatant commercial infringement of Fundamental panels from Grayscale

Most of the reasoning regarding miRack stems from this assertion. From what I remember of the first release, I'd say the Grayscale panels> @mifki said:

@espiegel123 said:

@rs2000 said:

@gonekrazy3000 said:

@mifki said:
I guess for some, modular is just a way to build some custom "device" and then use it like any other effect or generator plugin.

This is exactly what modular is to me.

This is what Audulus does for me because of its more flexible design.
miRack is more like an independent, sometimes sequenced, instrument to me.
That's why I find an audio recorder/player to record loops inside the app essential.

Now, that miRack has Audiobus compatibilit, I don’t see the need for an internal recorder. It is easy enough to send miRack’s output to a lightweight recorder. I’d much rather see Vitaly spend his time implementing stuff we can’t already do.

I think the idea was to have a recorder that can be triggered with a signal inside the patch. Audiobus solved the recording problem for now, but such a module still will be useful I guess.

Yes, the various Nysthi samplers (Simplers, Simpliciter, MusicalBox, Sussudio) are pretty great so anything that could replace those would be appreciated

rs2000

d> @[Deleted User] said:

@mifki said:

@espiegel123 said:

@rs2000 said:

@gonekrazy3000 said:

@mifki said:
I guess for some, modular is just a way to build some custom "device" and then use it like any other effect or generator plugin.

This is exactly what modular is to me.

This is what Audulus does for me because of its more flexible design.
miRack is more like an independent, sometimes sequenced, instrument to me.
That's why I find an audio recorder/player to record loops inside the app essential.

Now, that miRack has Audiobus compatibilit, I don’t see the need for an internal recorder. It is easy enough to send miRack’s output to a lightweight recorder. I’d much rather see Vitaly spend his time implementing stuff we can’t already do.

I think the idea was to have a recorder that can be triggered with a signal inside the patch. Audiobus solved the recording problem for now, but such a module still will be useful I guess.

The recorder module would benefit from Record syncing to the BPM so a perfect 4, 8, 16 etc.. bar loop can be generated.

Exactly!!

mifki

In-app recorder/player modules will be added, that's for sure. Actually the only difficulty here is file management. iOS 13 added a possibility to let user select a folder (previously only file selection was possible). Still, I need to investigate first how the existing recorder modules manage files, especially if the recording will be triggered automatically and there will be a lot of files created. Should it just append to the chosen folder and it's up to the user to manage? Or should records be kept per patch/per module? Let me know if you have any ideas.

rs2000

@mifki said:
In-app recorder/player modules will be added, that's for sure. Actually the only difficulty here is file management. iOS 13 added a possibility to let user select a folder (previously only file selection was possible). Still, I need to investigate first how the existing recorder modules manage files, especially if the recording will be triggered automatically and there will be a lot of files created. Should it just append to the chosen folder and it's up to the user to manage? Or should records be kept per patch/per module? Let me know if you have any ideas.

I would say: Name them by date, then recording number. About the folder - I'm split about how to do it best.
Rerording in per-patch folders named after the patch sounds like a good and better-structured idea.
Something like ./MyGreatGroovePatch/Recordings/20191025-104259-01.wav

Another option would be one folder (./Recordings) and add the patch name in front of the above filename.
Easier for cleaning up stuff if necessary, and faster to find the latest recorded files even if I just forgot the patch name.

I suppose the one-folder solution would be easier to handle and fewer questions asked.

dendy

There was a danger of Apple removing the app without looking at the facts, so we’ve reached a compromise with Wes

@Vortico Ok i promise from now i will spread huge bad words of mouth about you and wess and about whole VCV rack project... by this you got serious enemy in me. Probably it means nothing for you, just saying...

TheOriginalPaulB

@dendy It’s not worth it, just let it go. Nothing you do will make those two better human beings...

Pierre118

@dendy Don't react as a little child. They won this battle but not the war............

mifki

@jipumarino said:

When miRack was released, I immediately noticed blatant commercial infringement of Fundamental panels from Grayscale

Most of the reasoning regarding miRack stems from this assertion. From what I remember of the first release, I'd say the Grayscale panels

The message looks um unfinished, but the reasoning comes from his understanding of "graphics" copyright as including the component locations. While this is a valid option, in our case they're technically separate and the text said "graphics is 'res' folder is copyrighted". It was clear to me that I could use the same layout, while it was clear to him that this made all my graphics, even new, "gradually derived" from his. The App Store complaint process doesn't involve a third-party so with the different understanding of the basic terms it was a dead end. It would've been better if he had not lied from the beginning and stated clearly the problem and what he wanted, but it doesn't matter anymore.

[Deleted User]

@dendy said:

There was a danger of Apple removing the app without looking at the facts, so we’ve reached a compromise with Wes

@Vortico Ok i promise from now i will spread huge bad words of mouth about you and wess and about whole VCV rack project... by this you got serious enemy in me. Probably it means nothing for you, just saying...

This is terrible, im really shocked by some of your comments lately. Old dendy come back please.

[Deleted User]

@mifki said:
In-app recorder/player modules will be added, that's for sure. Actually the only difficulty here is file management. iOS 13 added a possibility to let user select a folder (previously only file selection was possible). Still, I need to investigate first how the existing recorder modules manage files, especially if the recording will be triggered automatically and there will be a lot of files created. Should it just append to the chosen folder and it's up to the user to manage? Or should records be kept per patch/per module? Let me know if you have any ideas.

I think when the recording is complete mirack should open the option to save to any folder you wish and automatically have the patch name plus the BPM for the file. I believe if you record more than one file from the same patch then ios will add an extra identifier. Ill pm the reslice filing method.

Vortico

@dendy said:
@Vortico Ok i promise from now i will spread huge bad words of mouth about you

Wes (Grayscale) is a contractor, not an employee, of VCV. His actions/opinions are his own, and the dispute was between him and Vitaly.

mifki

@Vortico said:

@dendy said:
@Vortico Ok i promise from now i will spread huge bad words of mouth about you

Wes (Grayscale) is a contractor, not an employee, of VCV. His actions/opinions are his own, and the dispute was between him and Vitaly.

When he requested the removal of the Fundamental plugin, he said "and with Andrew as the developer", and "we simply don't want them included".

Vortico

I agree with his wishes because he designed Fundamental/Component Library and should decide how his work is used. If someone used your own designs commercially, you'd feel the same way.

mifki

Ok, it’s neither place nor time to go over all this again.

Vortico

Agreed, but I'm here if the need to defend myself arises, such as when someone threatens defamation against me for a dispute I am not even a part of.

david_2017

So cool to hear it’s finally over and you guys found a solution to live by. Wow. Great days ahead... 💪🏼 miRack rock 👊🏼😎

OnfraySin

So, perfect!! I don’t use Fundamentals and I don’t want anything about Grayscale on my iPad.

OnfraySin

@Vortico said:
Agreed, but I'm here if the need to defend myself arises, such as when someone threatens defamation against me for a dispute I am not even a part of.

Yeah, the same happen to Vitaly on Vcvrack forum. He can defend herself there.

OH WAIT, NO

[Deleted User]

@Vortico said:
Agreed, but I'm here if the need to defend myself arises, such as when someone threatens defamation against me for a dispute I am not even a part of.

What about allowing Vitaly to defend himself on your forum? maybe you could reverse that decision as a sign of moving forward?

mifki

Defamation! That's the legal term I was trying to recall, thanks!

Vortico

I'll consider it, but right now I see this drama as a result of the existence of miRack, not VCV's existence, so I believe discussions about miRack belong on miRack threads and communities. The VCV communities are specifically for discussion, support, ideas, patches, music, and development for VCV, not miRack.

rs2000

@OnfraySin said:

@Vortico said:
Agreed, but I'm here if the need to defend myself arises, such as when someone threatens defamation against me for a dispute I am not even a part of.

Yeah, the same happen to Vitaly on Vcvrack forum. He can defend herself there.

OH WAIT, NO

@[Deleted User] said:

@Vortico said:
Agreed, but I'm here if the need to defend myself arises, such as when someone threatens defamation against me for a dispute I am not even a part of.

What about allowing Vitaly to defend himself on your forum? maybe you could reverse that decision as a sign of moving forward?

Although I have to say that the best way to move forward would be ... erm ...
to move forward?
Developers are a rare species and they should rather be able to use their intellect for as much constructive and creative use as possible, with our full support.
Both Andrew and Vitaly have done a great job and they've made many modular-loving people happier.

[Deleted User]

Thanks for considering it. Maybe in the future.

hansjbs

Moving from this is the best medicine. Good luck to all parties involved in this situation. Keep making great tools for music!!

Jocphone

Glad you found a way round the trouble @mifki

On another note do you ever see the possibility of miRack becoming universal?