Notifications
Clear all

UNIFY 1.9.1 Issues

17 Posts
3 Users
0 Likes
193 Views
(@graig)
Active Member
Joined: 3 years ago
Posts: 12
Topic starter  

Hi Shane, I have a few issues with 1.9.1 that I would like to report.

 

1. Unify does not differentiate between BC Patchwork and BC Patchwork Synth Plugin.  The Synth plug populates the audio category , preventing me from using it.  The only solution I have presently is to delete the synth plugin and then rescan for the audio one to show up in fav audio fx correctly.

2.  Whenever I scan/update plugins in the standalone version, the browser fails to replace the older ones, leaving multiple versions in the directory.  This has happened for at least the last two maybe three versions of unify updates.  Reboots and rescans do not change the result of leaving previous versions listed as well.  Solution I have presently is to scan the whole list of my plugins (1000+) then manually delete the doubles or older versions one at a time.  Also for some reason Xfer DJMF filter keeps on showing up double though its listed in one place only (same) if I do a “show in finder” from the Unify browser.  After a delete of the double and a rescan, it shows up twice again but pointing to the same file.

3. Often I notice very high VST2 Unify cpu usage in ableton (4-bars yellow on a given track) when there is a blank instance of unify or even a patch that is disabled ( inside unify I will mute or disable all the audio fx or synths) unify still shows high cpu usage in Live 11.2.10.

4.  Is setting "use fixed buffer sizes" the only solution to use Unify without cpu overload in FL Studio?

I have a collection of screenshots and crash reports to submit but unsure where to send them.  Thanks in Advance.

I am on Catalina 10.15.7 with a 10-core Intel i9K (3.7Ghz), 32GB RAM, etc...

This topic was modified 11 months ago by Graig

   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4368
 

Posted by: @graig

1. Unify does not differentiate between BC Patchwork and BC Patchwork Synth Plugin.  The Synth plug populates the audio category , preventing me from using it.  The only solution I have presently is to delete the synth plugin and then rescan for the audio one to show up in fav audio fx correctly.

Which format are you using: VST, VST3, or AU? I'm using VST on my Windows machine, and I don't have this issue.

2.  Whenever I scan/update plugins in the standalone version, the browser fails to replace the older ones, leaving multiple versions in the directory.  This has happened for at least the last two maybe three versions of unify updates.  Reboots and rescans do not change the result of leaving previous versions listed as well.  Solution I have presently is to scan the whole list of my plugins (1000+) then manually delete the doubles or older versions one at a time.  Also for some reason Xfer DJMF filter keeps on showing up double though its listed in one place only (same) if I do a “show in finder” from the Unify browser.  After a delete of the double and a rescan, it shows up twice again but pointing to the same file.

This is unexpected. There's a chance it might be due to incorrect folder permissions. Please locate ~/Library/Application Support/PlugInGuru and use Get Info in the Finder to check that you have write permission there. Update if not.

If you're going to do a full re-scan anyway, I'd suggest first using the "Clear List" item at the top of the menu on the Operations button at the bottom of Unify's Known Plug-Ins view first. This will remove everything except Unify's own built-in and bundled plug-ins.

3. Often I notice very high VST2 Unify cpu usage in ableton (4-bars yellow on a given track) when there is a blank instance of unify or even a patch that is disabled ( inside unify I will mute or disable all the audio fx or synths) unify still shows high cpu usage in Live 11.2.10.

High CPU usage is usually due to buffer size being too short. Unify can't work efficiently with buffer sizes lower than 128; I recommend 256. What size do you use?

4.  Is setting "use fixed buffer sizes" the only solution to use Unify without cpu overload in FL Studio?

Yes, due to the buffer-size/efficiency issue I just mentioned.

I have a collection of screenshots and crash reports to submit but unsure where to send them.

Zip and attach to a post/comment here, or email to UnifySupport@PlugInGuru.com.

I am on Catalina 10.15.7 with a 10-core Intel i9K (3.7Ghz), 32GB RAM, etc...

This is important to know. We are still battling CPU spiking issues on M1 Pro/Max/Ultra chips, but I'm not aware of any such issues on any Intel chip.


The above are not intended to be "final" answers. They're just initial thoughts to begin further discussion.

You have raised multiple, probably unrelated issues here. It might be better to start a new Forum topic for each.

 


   
ReplyQuote
(@graig)
Active Member
Joined: 3 years ago
Posts: 12
Topic starter  

Posted by: @getdunne

Which format are you using: VST, VST3, or AU? I'm using VST on my Windows machine, and I don't have this issue.

 

I use VST2 exclusively.
Posted by: @getdunne

This is unexpected. There's a chance it might be due to incorrect folder permissions. Please locate ~/Library/Application Support/PlugInGuru and use Get Info in the Finder to check that you have write permission there. Update if not.

If you're going to do a full re-scan anyway, I'd suggest first using the "Clear List" item at the top of the menu on the Operations button at the bottom of Unify's Known Plug-Ins view first. This will remove everything except Unify's own built-in and bundled plug-ins.

 

thanks. I will try this and report back.

Posted by: @getdunne

High CPU usage is usually due to buffer size being too short. Unify can't work efficiently with buffer sizes lower than 128; I recommend 256. What size do you use?

 

I rarely use 128. My minimum is usually 256 or 512 on heavy sessions.  I have emailed you some reports, thanks for your time and the genius that is Unify!

 

This post was modified 11 months ago by Graig

   
ReplyQuote
(@graig)
Active Member
Joined: 3 years ago
Posts: 12
Topic starter  

Posted by: @getdunne

This is unexpected. There's a chance it might be due to incorrect folder permissions. Please locate ~/Library/Application Support/PlugInGuru and use Get Info in the Finder to check that you have write permission there. Update if not.

Just checked my permissions and I have read/write set as (Me) already.

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4368
 

@graig Could you please zip and attach your PluginList.xml file? You'll find it in ~/Library/Application Support/PlugInGuru. (That's your own ~/Library folder, not the system /Library.)


   
ReplyQuote
(@graig)
Active Member
Joined: 3 years ago
Posts: 12
Topic starter  

Posted by: @getdunne

@graig Could you please zip and attach your PluginList.xml file? You'll find it in ~/Library/Application Support/PlugInGuru. (That's your own ~/Library folder, not the system /Library.)

 

Here you go, thank you.

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4368
 

@graig

Thank you for the XML file. I'm writing some custom Python code to analyze it, because it's so large. So far I've found only one duplicate, an effect VST called elysia phils cascade. Are you aware of other duplicates I should look for?

You have a lot of Waves plug-ins. Waves is one of very few companies that packages large groups of plug-ins into a single VST or VST3 "shell". This might be affecting Unify's ability to detect duplicate entries (but I doubt it).

Two final thoughts:

  1. We generally advise that you perform full plug-in scans only once, and thereafter, register newly-added plug-ins individually (that's a link to the manual; click the words to follow it), to save time and avoid this kind of issue.
  2. We also advise that you scan fully for VST, VST3, and AU plug-ins once, then use the Remove "redundant" plug-ins item on the Operations menu in the Known Plug-Ins View. This will attempt to remove AU plug-ins for which a VST/VST3 is available, and VST3's for which a VST is available, leaving you with a minimal set of "most compatible" plug-ins. Note this may fail in some cases, when the plug-in name and/or vendor name is not identical for different formats, but it works in at least 90% of cases.

These advices notwithstanding, if you are patient enough to help debug this issue, I'd appreciate it.


   
ReplyQuote
(@graig)
Active Member
Joined: 3 years ago
Posts: 12
Topic starter  

Posted by: @getdunne

So far I've found only one duplicate, an effect VST called elysia phils cascade. Are you aware of other duplicates I should look for?

I just did a quick check and XFer DJMF is also still showing up as 1.0.0.5 and 1.0.0.6 though they both point to same latter file. (elysia is showing up dbl as well.)  Just to clarify my original post, I always do a "scan for new or updated plugins" and never a rescan everything when I update or add a new plug.  I will also just drag and drop the new plugin as recommended on the plugins window.

Posted by: @getdunne

You have a lot of Waves plug-ins. Waves is one of very few companies that packages large groups of plug-ins into a single VST or VST3 "shell". This might be affecting Unify's ability to detect duplicate entries (but I doubt it)

I concur.

Posted by: @getdunne

We also advise that you scan fully for VST, VST3, and AU plug-ins once, then use the Remove "redundant" plug-ins item on the Operations menu in the Known Plug-Ins View.

Yes , however in the early days of Unify when there were issues with the VST2 version of Serum, I was forced to create hundreds of patches in AU, and when I originally removed the redunant plugins when the option was added to the plugin scanner, I lost all the patches I had created in the AU since SerumAU was missing.  Any way to add the ability of loading the preset in the available format at time of scan or recall ?  Ive had this issue with a few plugins and have presets spread across multiple formats on a few synths.

Posted by: @getdunne

These advices notwithstanding, if you are patient enough to help debug this issue, I'd appreciate it.

Absolutely, no worries, and thank you for your prompt replies.


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4368
 

Posted by: @graig

I just did a quick check and XFer DJMF is also still showing up as 1.0.0.5 and 1.0.0.6 though they both point to same latter file.

There is only one entry in the XML file for DJMFilter, for v1.0.0.6. Did you scan again since uploading the file? If so, please upload the new file. I'm keen to see exactly what happens.

...to clarify my original post, I always do a "scan for new or updated plugins" and never a rescan everything when I update or add a new plug.

Sorry, I'm the one who should clarify. That's what I mean by doing a "full scan", as opposed to just registering one plug-in at a time.

...in the early days of Unify when there were issues with the VST2 version of Serum, I was forced to create hundreds of patches in AU, and when I originally removed the redunant plugins when the option was added to the plugin scanner, I lost all the patches I had created in the AU since SerumAU was missing.  Any way to add the ability of loading the preset in the available format at time of scan or recall ?  Ive had this issue with a few plugins and have presets spread across multiple formats on a few synths.

You can drag/drop the AU again in after a "remove redundant" operation, to add it back in.

Unfortunately, there is no general way to convert any given plug-in's binary state-data from one format to another. Many recent plug-ins use XML, which is then not too hard to parse out of the format-specific "wrapper" data, but with older plug-ins, this approach may fail because different format-versions of the plug-in actually use save/load slightly different formats. Serum appears to use a true binary format, which is gibberish when I look at it. If it's a huge issue, we can try to reach out to Xfer about it, but note there's a manual approach which works for any plug-in: Load the patch you made with the AU, save it as a preset within the plug-in's own GUI, then swap in the VST and load the new preset in the GUI. Tedious, but effective.

Of course, if you don't need to save your patches with PC users, there's nothing wrong with using AU plug-ins in Unify.

 


   
ReplyQuote
(@graig)
Active Member
Joined: 3 years ago
Posts: 12
Topic starter  

Posted by: @getdunne

There is only one entry in the XML file for DJMFilter, for v1.0.0.6. Did you scan again since uploading the file? If so, please upload the new file. I'm keen to see exactly what happens.

 

 

Strangely, When I booted up yesterday and checked DJMF appeared dbl again.  Upon rescanning it was down to one.  I had not changed anything in the meanwhile.  There is something I read online about Catalina and Permissions not always working as intended though it appears correct.  I have SIP disabled since always, but sometimes , by example, if I want to batch rename files in a folder, certain batch programs (like A  better Finder Rename) will give permission access errors to write(rename) on any internal hard drive, though all my Drives show up with correct permissions in Disk Utility and Show correct Admin and User access (r+w) in all the Get iNfo Dialog boxes ( Drives and Folders INclusive.)  I have even dbl run (apply to enclosed items).  THis is of course not a certainty but something I am suspicious of as potential culprit.  Name Mangler on the other hand does all the batch renaming with no errors in the same locations, so it seems there are more ways than one to attempt to access/write a file.  Hopefully this is not too much off topic, as I wonder if there could be a relationship.

Posted by: @getdunne

Unfortunately, there is no general way to convert any given plug-in's binary state-data from one format to another. Many recent plug-ins use XML, which is then not too hard to parse out of the format-specific "wrapper" data, but with older plug-ins, this approach may fail because different format-versions of the plug-in actually use save/load slightly different formats. Serum appears to use a true binary format, which is gibberish when I look at it. If it's a huge issue, we can try to reach out to Xfer about it, but note there's a manual approach which works for any plug-in: Load the patch you made with the AU, save it as a preset within the plug-in's own GUI, then swap in the VST and load the new preset in the GUI. Tedious, but effective.

 

 

Yes I had realized this and spent a few days converting my hundrerds of AU patches... Not fun lol.   Is there any chance at some point we will be getting a proper patch editor, that will enable us to batch rename edit and reorganize existing patches based on pre-existing criteria or tag words ?  This would be a godsend as this is the most time consuming aspect of trying to manage so many files growing and needing to be recompiled to keep order or refine collections.

 

 

This post was modified 11 months ago by Graig

   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4368
 

Posted by: @graig

Is there any chance at some point we will be getting a proper patch editor, that will enable us to batch rename edit and reorganize existing patches based on pre-existing criteria or tag words ?

Can you point to a plug-in whose preset-manager provides such features? I don't think they're so common as to be required for a GUI to be worthy of the adjective "proper", but maybe I'm missing something.

I'm collecting ideas and suggestions for improvements to Unify's patch management features, but given the economics of this industry, I have to be honest and say it will be a challenge to fund such development.


   
ReplyQuote
(@graig)
Active Member
Joined: 3 years ago
Posts: 12
Topic starter  

Posted by: @getdunne

Can you point to a plug-in whose preset-manager provides such features? I don't think they're so common as to be required for a GUI to be worthy of the adjective "proper", but maybe I'm missing something.

Sorry I just realised my "pre-morning esspresso" wording and did not mean any insult, The browser is awesome! 🙂 I meant that with quite a few other synths, you can just open the folder and rename your presets, or drop/rearrange them into new folders/collections and rescan.  There is no way of doing that with Unify, if I am not mistaken, the links would break.  Each patch, if I, say want to change or add a descriptor would require manual editing/resaving of each preset within Unify making it a very time consuming task.  I have a huge and ever-growing evolving collection of my own creations, needing to get refined just to keep track of where everything is.  Another example would be if I instead of DRUM, I accidentally created 50 patches as Drums, I cannot instantly rename and reorganize files as easily as expected.  I have spent days reorganizing my Unify patches manually, and was just hoping there possibly was a more refined solution for organization on the horizon, especially bulk moving items from one folder to another and recognizing patches whose names have been changed in the finder maybe.

This post was modified 11 months ago 3 times by Graig

   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4368
 

Posted by: @graig

I meant that with quite a few other synths, you can just open the folder and rename your presets, or drop/rearrange them into new folders/collections and rescan.

Ah, thank you for clarifying! I feel your pain, and I can assure you that John does too!

My decision to store patch and library names within the patch files, rather than setting patch name = file name and library name = enclosing folder name has proven to be a very mixed blessing. The advantage is that you can use more characters in patch names--each operating system has its own set of characters that are not allowed in file names--but the drawback is, as you say, that you can't use your Finder/Explorer to reorganize libraries.

I've published a small set of programs that can help a bit with renaming/reorganizing libraries; see https://forums.pluginguru.com/postid/13976/ for download links or https://github.com/pluginguru/unify-batch for open-source code. However, I agree it would be easier if you could do these things manually in Finder/Explorer.

If there is ever a Unify 2.0, this will be one of the main changes.

 


   
ReplyQuote
(@graig)
Active Member
Joined: 3 years ago
Posts: 12
Topic starter  

Posted by: @getdunne

I've published a small set of programs that can help a bit with renaming/reorganizing libraries; see https://forums.pluginguru.com/postid/13976/ for download links or https://github.com/pluginguru/unify-batch for open-source code. However, I agree it would be easier if you could do these things manually in Finder/Explorer.

If there is ever a Unify 2.0, this will be one of the main changes.

 

This is actually helpful, thank you!  Had no clue this existed.  Was also wondering... is there any way currently of linking one of the CC knobs to the instrument velocity curve to control the min/max velocity being fed to the VSTi ?  Ive been trying to figure a way to do this using internal plugs only, maybe i am missing something.  Also is there any way of CCing the ability to patch change within a vsti? so turning the knob would scroll presets in a synth browser if they have the ability built in ?  Havent figured out a workflow for this.  Thanks in Advance.


   
ReplyQuote
Robert.P
(@robert-p)
Reputable Member
Joined: 4 years ago
Posts: 290
 

Posted by: @graig

Also is there any way of CCing the ability to patch change within a vsti? so turning the knob would scroll presets in a synth browser if they have the ability built in ?  Havent figured out a workflow for this.

This can be done with free 3rd party PizMIDI "MidiConverter3" and Unify's CC Rider: Set CC Rider's curve flat-top and use PizMIDI to convert CC message to Prog Change. Map CC Riders "Amount" to your macro knob.

P.S. Or use PizMidi "ProgChange" (you can also map it to your macro knob)


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 4 years ago
Posts: 4368
 

Posted by: @graig

is there any way currently of linking one of the CC knobs to the instrument velocity curve to control the min/max velocity being fed to the VSTi ?  Ive been trying to figure a way to do this using internal plugs only, maybe i am missing something.

This is exactly what Unify's velocity curves are for. Briefly, you can click on the little graph icon near the left-hand side of any INST layer, and edit the velocity curve by dragging the left-hand endpoint up (to set minimum output velocity) and right-hand endpoint down (to set max velocity).

However, your question specifically mentions using a MIDI CC to control the curve, and there's nothing for that currently built into Unify. (Interesting idea, though; I'll think about it and add to the to-do list.) Take a look at the PizMidi Collection of MIDI-effect VSTs. There's one called midiVelocityScale that has parameters Velocity 1 and Velocity 2 which you can link to Unify's macro knobs (which you then assign to CCs) to set velocity limits.

Also is there any way of CCing the ability to patch change within a vsti? so turning the knob would scroll presets in a synth browser if they have the ability built in ?

The PizMidi Collection has one plug-in called midiConverter3 to "change and convert between CC, Channel Pressure, Poly Aftertouch, Program Change, Pitch Bend, NRPN/RPN, Note On/Off, and other messages in various ways", and another called midiProgramChange to "send Program Change and/or Bank Select messages".


   
ReplyQuote
(@graig)
Active Member
Joined: 3 years ago
Posts: 12
Topic starter  

Posted by: @getdunne

However, your question specifically mentions using a MIDI CC to control the curve, and there's nothing for that currently built into Unify. (Interesting idea, though; I'll think about it and add to the to-do list.)

Thanks.  I find this useful for Intruments like E Pianos, were the tone differs greatly past a certain range and you can control the min/max velocity "on the fly" ( which is the descriptive I forgot to include before.)  This is achieavable with Abl Live's built-in velocity tool , however if its not too difficult, if could be a fun addition to further control things "on the fly".

Posted by: @getdunne

The PizMidi Collection has one plug-in called midiConverter3 to "change and convert between CC, Channel Pressure, Poly Aftertouch, Program Change, Pitch Bend, NRPN/RPN, Note On/Off, and other messages in various ways", and another called midiProgramChange to "send Program Change and/or Bank Select messages".

Posted by: @getdunne

The PizMidi Collection has one plug-in called midiConverter3 to "change and convert between CC, Channel Pressure, Poly Aftertouch, Program Change, Pitch Bend, NRPN/RPN, Note On/Off, and other messages in various ways", and another called midiProgramChange to "send Program Change and/or Bank Select messages".

Totally forgot about those...cool. thanks.  saves me BC plugnscript time!


   
ReplyQuote
Share: