looking at my original yml, which was created (long before any polyphony firmware), im seeing the redundancy there already. no idea how that would have occurred. maybe a bug in the mm hub on export to yml, or in the mm itself. patch originally created within vcv, then revised directly on the mm (with an early(non beta) v2 firmware)
Presumably the Meta ignores that kind of redundant connection so it’s not an issue when it gets generated. I’ve updated the converter to ignore it too — reload and let me know if it works.
the tool seemed to ignore one of the redundant cables, but that left 1 redundant one still on top of the main one. here’s a yml with the 3 stack in case it’s useful:
Hmm that’s weird, it’s working for me. Check the converter page to make sure it says v1.1.12 in the top right corner — maybe you’ve got an old version cached.
unfortunately still getting the error (even after shift+f5, restart chrome). peaking inside the yml created on the mm, that module is listed:
JWModules:Grains
and then creating a patch from scratch in vcv using grains, then exporting the yml file, it’s listed as:
JW-Modules:Grains
i’m noticing that airwindows is not converting properly. i have a yml that’s using the ‘bitshift gain’ airwindows effect, but in the converted vcv file- it switched the module back to the galactic reverb airwindows default.
Huh. When I create a VCV patch containing just the Meta hub and Airwindows, then set Airwindows to BitShiftGain, then export the yml, then convert the yml to .vcv, the Airwindows setting is preserved in the output .vcv file.
Is there anything else in the patch that might be complicating things? Want to send me the .yml?