Meta Morph : Share your patches

Eigenharp
1

A topic to share your patches, you can just attach your vcv presets to your replies here.

I’d suggest for each patch you include:
Brief Description
Which Eigenharp it was created for.
any 3rd party modules used, beyond VCV and Meta Morph.

the 3rd party module list is important!
unfortunately, if a preset includes 3rd party modules you don’t have installed, VCV simply removes the module from the patch. so the patch wont work, and the user is given no indication as to why.
this is why tutorial/demo patches will only use Factory modules to avoid this ‘extra step’

Contributions
The release also includes a few demo and tutorial patches (see post below).
It would be great to extend these over time, so if you create something thats interesting that we could include let us know. Below, I detail some guidelines for these patches.

Housekeeping Rules.

  • Keep an eye on the size of the patch before uploading
    we have limited space on the server, if these patches take up too much space. we will have to remove.
  • Don’t include samples
    we don’t have resources to look for copyrighted material etc.
1 Like
2

Patches included with the Meta Morph release.

you will find in the
~/Documents/Rack2/plugins-mac-arm64/MetaMorph/res/patches
or
~/Documents/Rack2/plugins-mac-x64/MetaMorph/res/patches

vcv tip: right click on module, and you can open the modules plugin folder !

the tutorial and core demo patches do not need any third party modules, and will work on VCV Rack free - you WILL need to set your audio device onto the AUDIO module.

please let me know if you have any issues with these patches, or if I accidentally include a module I shouldn’t :laughing:

Included tutorial patches

Brief Description:
Patches that show how to use the Meta Morph modules, and contain ‘notes’ to help explain how the patch works.

you should review each module in turn , so 1-simple first, then 2-, 3- etc.
as they build on the previous patch, and do assume you understand these.

Eigenharps : ALL
3rd Party modules : None
Files : see directory : res/patches/tutorial

Included core demo patches

Brief Description:
More advanced patches that assume you have worked through the tutorial patches.
The main focus is on combining modules in different ways, whereas the tutorial patches try to focus on one module at a time

Eigenharps : varies, see filename.
patches for specific eigenharps will contain its name in the filename
3rd Party modules : None
Files : see directory : res/patches/demos

Included adv demo patches

Brief Description:
These are patches that use 3rd party modules, so we get a bit more flexibility in sounds.
Often the name of the file will show which modules it focuses on, or if its for a specific eigenharp.

Eigenharps : varies, see filename.
3rd Party modules :

  • Vult (Free)
  • Audible Instruments

Files : see directory : res/patches/demos

Community involvement

If you would like to help new users, please consider creating new demo and tutorial patches similar to those above.
a few guidelines

  • includes one (or more) NOTES module to explain what the patch does/how it works.

  • tutorials
    only use Fundamental modules, so will work out of the box with VCV Free
    try to focus on ONE feature, you can refer to the tutorials for ‘pre-requisites’, so you don’t have to explain everything from scratch.
    try to keep patch complexity down, so that users can follow along

  • core demos
    are more complicated patches that combine different ideas.
    only use Fundamental modules, so will work out of the box with VCV Free

  • adv demos
    are more complicated patches that user (free) 3rd party modules. gives us a space to have some more interesting demos and sounds , that’d be hard to achieve with only Fundamental.
    however, as VCV does not allow for ‘auto downloading’ of required module, we will use a restricted set, which Ive listed above. we may add to this overtime.

1 Like
3

14 virtual columns for Pico

This preset repurposes the bottom four keys of the Pico to retune the other twelve in a way that it occurs as if the Pico had additional columns left and right of actual ones in order to play scales over several octaves.

Eigenharp : Pico

3rd Party modules : Valley Plateau (optional)

Files

Pico14Columns.vcv (2.9 KB)

updated to work with RC2

2 Likes
4

Pico Brass

Brass sound with character (WIP)
v0.1 added a Sum module to manage polyphony.

Eigenharp : Pico

3rd Party modules : Plateau (Free)

VCV Library - Valley Plateau)

Files

Pico-Brass+octave change via buttons v0.1.vcv (2.9 KB)

4 Likes
5

Nice patch Antonio! (The reverb is here in case someone needs a link: VCV Library - Valley Plateau)

2 Likes
6

Pico Orient Piano

Used Karplus Strong for resembling a Piano (WIP)
v0.1 added a Sum module to manage polyphony.

Eigenharp : Pico

3rd Party modules :

Bacon Music KarplusStrongPoly
Bogaudio VCF
Bogaudio OFFSET
Valley Plateau

Files

Pico-Orient Piano+octave change via buttons v0.1.vcv (2.7 KB)

2 Likes
7

Was wondering how feasible would it be to port Meta Morph to mirack ? Is libpico still a binary blob that runs only on specific platforms ?
Connecting the Pico to an iPad would be so nice but I assume there must be some roadblocks in iOS…

8

I wouldn’t count on it as Apple is not allowing apps that can download plugins. (So if at all then VCV would have to be compiled with a set of plugins statically built in).
Android 16 supports full Linux applications now with the Terminal app. So technically it should be possible to install VCV. No clue about latency though (probably depends on the specific phone)

9

I was referring to miRack (https://mirack.app) which is a VCV rack port that indeed comes with the modules pre-built.

1 Like
10

as @NothanUmber , this cannot run ‘downloadable’ custom modules, only modules that are pre-packaged, so you’d have to port meta module and then get mi-rack to release a version with them incorporated…

however, this is a moot point - as technically, its also not going to work anyway.
libpico is not really the issue, alongside this you need the usb layer, and eigenharps use a custom usb protocol, so would need a custom usb driver.
Adding an iOS driver to support them would be a huge undertaking, and very likely require some kind of Apple licensing - so it’s really a non-starter.

so unfortunately, Android is the better option, as its open.
the linux version uses libusb, which ‘theoretically’ supports android as well.
so (again) theoretically the code is pretty portable to android - in practice, its bound to have quirks, and as we saw with rPI may have issues with some devices- also performance would be an open question.

however, unfortunately… given the ‘controversy’ surrounding miRack, I dont believe anyone has dared to try to create an android port of vcv.
so as Ferdinand mentions, probably the only route would be to run Linux on the tablet, but what the performance would be like is anyones guess (depends on tablet I guess)

the only good side of that being, meta module should just compile, as its just another linux target, and there is already aarch-64 support, which is very likely modern android tablets supporting Linux would use.

one final ‘but’… vcv rack devs have never really been into touch screen support. so unless things have changed, the touch screen support is a bit ‘meh’.

overall, it certainly something someone could have a go at, if they have the hardware available, and some dev experience to do it.

though, personally, Id not advise buying a tablet just for this, as its possible you’d hit a roadblock or find the performance is just not good enough to be usable.

2 Likes
11

Thanks for the detailed explanation, it all makes sense, I’ll stick to my Macbook (or perhaps dig up an old raspberry pi at some point) :slight_smile:
I wasn’t aware of the controversy with miRack but I assume it has to do with modules being included without the author’s consent…

12

yeah, it was all a bit messy…

basically, it was early days , and vcv dev were not happy about it. however, the code license allowed, but they argued the artwork for panels did not.

it kind of divided the community a bit, as many wanted vcv on iOS, and devs had made it very clear they had zero interest in this - so as you can imagine, some thought it was ‘fair game’, but others thought this was up to the vcv devs.

this, unsurprisingly, prompted the source code license to later be modified for new versions. - which kind of put miRack into a bit of a deadend.

but yeah, fundamentally, if you want to do a project like this, its best to get the blessing of the original dev - even if legally you dont need to :wink:

3 Likes