Hey Dan, feel free to make use of this in any way you like! The repo is here. It started life as a Python script which should still be in there somewhere — I can re-add if not. That’s probably more useful to you than JavaScript.
That would be neat to have it built into the Hub. The really ambitious step would be to finagle the wifi expander to send YAML files back to the computer, at which point you’ve almost got two-way syncing.
Awesome, thanks, I’ll give it a shot when I have a moment…
I actually built something similar with chatgpt last year but struggled with the values (like you did initially, too)
had many projects becoming more important so I’m glad somebody took over the task!
this will help me so much to finetune my mod matrix in MM! Thanks 
Agentic coding! It makes all the difference. Glad this is useful for you.
this recent one i’m trying to convert back to vcv, i’m getting an error “HubMedium/HubMedium not installed” - and it loads of course without the hub so i’m losing all the knob mappings.
i had recently installed the latest version 2.1.6 of the 4ms vcv plugin from github (the one with line break capability in the description area). and also tried the most recent 2.1.7 but seeing this error still.
curious if you might have any clues?
Hmm … seems like the yml is being written incorrectly — it should say 4msCompany:HubMedium but instead it says HubMedium:HubMediumfor some reason. Where did the yml come from? And does it load normally on the MetaModule? And maybe attach it so I can take a look?
the yml is something i created initially last september in vcv, then altered quite a bit directly on the mm. it’s strange, the slug just says HubMedium no single quotes like the rest.
not sure how it would have gotten into that state. but it appears that i can manually edit in the yml HubMedium to ‘4msCompany:HubMedium’ and it seems to work ok
Interesting. I guess it’s somewhere in the patch serialization code in the Meta Hub or MetaModule. But I can add a check so the converter knows to write this to .vcv properly. UPDATE: Done, try uploading the original patch and it should convert properly.
tried on a different yml (also with the HubMedium no single quotes) and didn’t receive the hubmedium error! however this new midi controller based yml im attempting to convert, im getting a message about missing “rack core/cv-midi” message:
was using the cv-midi module on the mm
Hmm … I guess it doesn’t know about the RackCore slug. Try again now.
that seemed to do the trick there, ty!!
one more issue im finding is with the air windows ones, it can’t seem to find them after converting yml-vcv:
Thanks! Fixed now.
now im seeing this error:
!_airwintests.yml (11.4 KB)
edit: seems to be caused byt the underscore in the file name
I think it was the exclamation point, actually. Should work now.
just ran across a couple little discrepancies, on this latest conversion im noticing that the freq knob on that disjoint module is not adhering to the what its mapped mm hub knob is set at. i think the freq knob is reverting to it’s default state. also if there’s if there’s a suggested rate/blocksize set in the yml, the mm hub doesn’t seem to set those values after convering..
The sample rate/block size issue is fixed. That one was interesting – that information is stored in the Audio module for the VCV Rack patch, and the converter wasn’t exporting Audio modules because they’re not saved in the yml. Now whenever there’s a SR or block size set in the yml, we create an Audio module, which lets the SR/block size persist in the Hub.
The Vult modules (yay!) have not yet been added to the table where the converter figures out how to map the values from the yml to VCV. I’ll build a “map a new module” process soon. Update: I have done this and the Vult modules should be working now.
found a strange bug, when i converted a yml, one of the modules had 3 cables running from the same input/output (didn’t know vcv would actually allow that):
Bizarre! Could you share the yml?
Oh I wonder if this has anything to do with polyphony in the new Meta firmware? I’ll see if that changes the yml spec.
