When I unzipped it just created a xxx.mrk file which I could open easily in miRack. Later when I was experimenting, I was also able to unzip the mrk file itself, which revealed the patch file.

Weird, that feels like some kind of chicken and egg loop!

1 Like

Yes one of the best parts of when I first got vcv. Also great for experimenting with modules you may not have in your hardware rig.

1 Like

On my iPad I wasn’t able to upload just the .mrk file, it just kept saying sorry you must provide a file to upload, I tried drag and drop as well as selecting from the files app. If you have an older version of iOS running on your iPad that doesn’t let you download Zip files, you can install something like the Goodreader app, and Safari will then allow you to download the Zip file and open in Goodreader. From within Goodreader you can then unzip it and open in miRack.

1 Like

Some apps automatically unzip a file, so Chrome might be doing that, then when you uncompressed it you would be uncompressing the .mrk file rather than the .zip file. If the file already has the little ā€œmiā€ icon on it, there’s no need to uncompress it. Also if you long press it, you get the option for ā€œinfoā€, clicking that will give you the full filename, so you can see if it is a .zip or .mrk file.

I was playing around this morning patching elements and clouds on miRack. The JW modules XY pad is great on the iPad. If you haven’t checked it out it’s loads of fun.

2 Likes

Looks like miRack is now on patchstorage:

https://mifki.com/blog/mirack-on-patchstorage/

8 Likes

Was just last night wondering how long that’d take. Good news then.

1 Like

New updates to miRack, including new modules and the ability for modules to contain manuals.

https://mifki.com/blog/mirack-version-1-06-is-out/

4 Likes

My favorite reverb! (Valley Plateau)

3 Likes

Yeah. I think I recall you mentioning it.

1 Like

yeah! they put MI Grids up too! (a port)
has anyone gotten braids macro osc to be able to get into vca mode? i cant get it to leave oscillator mode.
its funny, braids is my favorite drum module and if i could get it going, now i can have 10 of them!
but i’m stuck.

Nice. I hadn’t noticed that.

1 Like

The grids module is not in the other mutable clone’s folder, it’s more at the bottom of the list. Lotsa new stuff!
My iPad Pro is running a buffer of 128, for example. It’s cool. I ran a bunch bunch of stuff and was at like 12% cpu, so this could get much more complex.

My dream is for MiRack to have samplers. Plzzzzzz.

Ah, this is brilliant - I wish I had read this post before I spent a few hours making a very feeble single voice bleeping patch! Thanks for sharing, everyone - it’s incredible useful to help me get my head around how it all works.

1 Like

Oh, cool. I wonder why it’s not in the Mutable clone folder. Thanks.

I’m going to post these two items here (first, a message from the creator of VCV Rack, the code of which miRack is based on, who is talking about his licensing arrangement; the other from the creator of miRack, in response to the circumstances that the VCV Rack creator is describing) because they’re directly related to the development of miRack. I will ask two things:

  1. Maintaining Focus: If we end up in a lengthy discussion about the subject of licensing and ethics in coding, let’s split it into a separate Lines thread.

  2. Being Patient: Given that discussions about these topics have, historically, at times gotten testy, I’ll also ask that people be patient with each other if you experience disagreement.

These are the two pieces:

https://community.vcvrack.com/t/postmortem-on-racks-gpl-relicensing/

https://mifki.com/blog/a-public-statement-on-the-hostile-actions-of-wes-milholen-grayscale-towards-mirack-project/

6 Likes

Damn. As much as I enjoy miRack, I’m now not very happy to know I supported it financially, the whole mess being a bit complex :frowning:

I know very little about this and am very much on the periphery having never used VCV and only used miRack for a short period of time (thus far). That said, my observations are simply that the accounts from Andrew and Vitaly are contrasting, to say the least, making it impossible to really discern the ā€œtruthā€ (a problematic term, obviously, when such emotive issues as perceived intentions are involved). As with most scenarios, it’s easy to imagine that the truth lies somewhere between the two (somewhat conflicting) reports, but perhaps the truth is less important than the fact that the relationship between the two forks is now probably irreparably damaged.

I am inclined to share Andrew’s point of view.

I also find it disingenuous for Vitaly to accuse Grayscale of ā€œharming the whole VCV Rack communityā€ given the significant contribution to the success of VCV that Wes’s efforts represent.

I also regret purchasing miRack and I really hoped Vitaly had made better effort to collaborate in good faith when I did so. I now realize this hope was misplaced.

But VCV will emerge from this stronger and more capable of defending itself against commercial fragmentation.


The really frustrating thing about this, is that it’s really Apple’s licensing that is causing a problem here. We just want a tablet version of VCV. If Apple had a more open ecosystem, I have zero doubt that Andrew would happily provide such a version. Guess there’s always Windows!

5 Likes