UVI Quadra Muted n Harmonics Library - Typos!

Posted by: @despondo

Hopefully @getdunne can run a batch on these to fix them. 🙂

Well, there's no way to write a program that will magically recognize and fix these kinds of language errors. However, I noticed that the same garbled comment appears to exist in just about all the patches. I considered trying to reword it, then realized it's not even sensible advice.

• It would make far more sense to use Unify's macro knobs to control Falcon's parameters; MIDI learn isn't needed.
• If the only parameters to be changed are volume and pan, you can do that in Unify itself; every layer has level and pan controls.
• The simplest approach is just to delete the patch comments entirely.

Consider the updated "no-comment" versions of the UVI Falcon Quadra Muted n Harmonics Unified patches here: https://www.dropbox.com/s/hr55wc9ltjy63r1/UVI%20Falcon%20QMH%20patches.zip?dl=0

For reference, the Unify batch tools Python scripts, in particular batch-unpack.py and batch-repack.py, can be used for such changes.

1. Run batch-unpack.py to convert all the .unify patch files to plain-text .xml files.
2. Make a custom script to change whatever you need in all the .xml files (see example below).
3. Run batch-repack.py to convert all the modified .xml files back to .unify files.

I modified the existing batch-rename.py script to yield the following, which I called batch-nocomment.py:

import os

def clearComment(xmlFile):
    infile = open(xmlFile, 'r')
    xml = infile.read()
    infile.close()
    
    # isolate the patch comment text
    commentStart = xml.find("comment=") + 9
    commentEnd = xml.find('"', commentStart)
    
    # rewrite the XML patch, substituting the modified comment tag
    outfile = open(xmlFile, 'w')
    outfile.write(xml[:commentStart] + xml[commentEnd:])
    outfile.close()

for xf in os.listdir('XML'):
    if xf.endswith('.xml'):
        clearComment(os.path.join('XML', xf))

I have just added this new script to the repository on GitHub.

Hi Shane,

Thanks for writing out this for reference. I did not make these patches, but noticed the weird text. Hopefully the original creator of these will also see your post and use it for future patches. Anyway, nice to have some ways to address these kinds of issues. 😉