KVR Audio

DrMEM · Post by **DrMEM** » Mon Apr 13, 2020 1:46 am

waltercruz wrote: Sun Apr 12, 2020 7:00 pm
dionenoid wrote: Thu Apr 09, 2020 12:09 am
Every plug-in that has a bit of latency will cause Unify to play with more and more delay in your daw. For fun try adding Pro-L2 and Soothe to the master layer. Totally unplayable.
Well, Pro-L is a mastering limiter, so adds a lot of latency. It's not meant to be used on realtime playing.

It's not just about playing, it's also about programming. If you draw a part on the grid it should play back on the grid.

getdunne · Post by **getdunne** » Tue Apr 14, 2020 2:22 am

I appreciate the discussion about latency, and I understand the issues pretty well at this point. Adding latency compensation is on my to-do list.

emasters · Post by **emasters** » Thu Apr 16, 2020 5:13 am

Small feature request - replace the current plugin scanner. Specific requirements: (1) make it go fast; (2) doesn't rescan plugins that have already been scanned and haven't changed; (3) correctly add plugins in Unify, that work in other hosts but fail in Unify (E.g., Kontakt.vst OS X); (4) offer to only add new plugins without rescanning every plugin already scanned (Waveform from Tracktion Software uses the same 3rd party scanner Unify uses, and it does this). I know you've put time into improving the scanner and appreciate that. But having a large number of plugins, it's such a time-sink. I had two new VST plugins to add today. I've spent 2 hours trying to get Unify to get through my VST plugins (AU and VST3 work better). It's agony -- I have yet to get it to complete. It continually restarts, I have to kill it because it gets stuck, many "ok" plugins get red-listed. Is there no other 3rd part scanner you could integrate that would work reliably and quickly?

psynical · Post by **psynical** » Thu Apr 16, 2020 6:14 am

emasters wrote: Thu Apr 16, 2020 5:13 am Small feature request - replace the current plugin scanner.

in pretty much every demo they've done with the plugin scanner, they always demonstrate that you can drag and drop plugins to get around the scanning process.

emasters · Post by **emasters** » Thu Apr 16, 2020 5:12 pm

psynical wrote: Thu Apr 16, 2020 6:14 am
emasters wrote: Thu Apr 16, 2020 5:13 am Small feature request - replace the current plugin scanner.
in pretty much every demo they've done with the plugin scanner, they always demonstrate that you can drag and drop plugins to get around the scanning process.

Yup - and that's where I'm headed. Will work better here.

getdunne · Post by **getdunne** » Thu Apr 16, 2020 7:01 pm

emasters wrote: Thu Apr 16, 2020 5:13 am Small feature request - replace the current plugin scanner. Specific requirements: (1) make it go fast; (2) doesn't rescan plugins that have already been scanned and haven't changed; (3) correctly add plugins in Unify, that work in other hosts but fail in Unify (E.g., Kontakt.vst OS X); (4) offer to only add new plugins without rescanning every plugin already scanned (Waveform from Tracktion Software uses the same 3rd party scanner Unify uses, and it does this). I know you've put time into improving the scanner and appreciate that. But having a large number of plugins, it's such a time-sink. I had two new VST plugins to add today. I've spent 2 hours trying to get Unify to get through my VST plugins (AU and VST3 work better). It's agony -- I have yet to get it to complete. It continually restarts, I have to kill it because it gets stuck, many "ok" plugins get red-listed. Is there no other 3rd part scanner you could integrate that would work reliably and quickly?

Thank you for the feedback. Unfortunately this is not a "small" request.

I don't know of any way to make the scanner faster. It must at least check the date of every file to see if it has changed.
It does not re-scan previously-registered plug-ins. It just displays the name and moves on.
If there were a single general solution, I would have implemented it already. At this point we have to track down failures one by one.
See #2.

Some additional thoughts:

Once you have performed one full scan, there's no need to scan again. It's easier and quicker to register new plug-ins one at a time; see https://pluginguru.net/unify/manual/dok ... l_plug-ins.
Some red-listed items may be 32-bit versions of plug-ins you also have in 64-bit form. Provided the 64-bit versions register correctly, you can ignore the red 32-bit ones (or better yet, delete them).
Individual registration often works when scanning fails. I have no idea why.
I know of no "third party scanners". Unify is built using the JUCE framework and uses their scanning code. Tracktion also uses JUCE; hence the similarity. I just run it in a separate process, restarting it automatically when it crashes.

Please clarify exactly what you mean when you say "I have to kill it because it gets stuck". Some plug-ins take an astoundingly long time to scan (again, I don't know why), but the scanner eventually gets past them. If you've found one that truly locks it up tight, please let me know.

emasters · Post by **emasters** » Thu Apr 16, 2020 8:41 pm

getdunne wrote: Thu Apr 16, 2020 7:01 pm
emasters wrote: Thu Apr 16, 2020 5:13 am Small feature request - replace the current plugin scanner. Specific requirements: (1) make it go fast; (2) doesn't rescan plugins that have already been scanned and haven't changed; (3) correctly add plugins in Unify, that work in other hosts but fail in Unify (E.g., Kontakt.vst OS X); (4) offer to only add new plugins without rescanning every plugin already scanned (Waveform from Tracktion Software uses the same 3rd party scanner Unify uses, and it does this). I know you've put time into improving the scanner and appreciate that. But having a large number of plugins, it's such a time-sink. I had two new VST plugins to add today. I've spent 2 hours trying to get Unify to get through my VST plugins (AU and VST3 work better). It's agony -- I have yet to get it to complete. It continually restarts, I have to kill it because it gets stuck, many "ok" plugins get red-listed. Is there no other 3rd part scanner you could integrate that would work reliably and quickly?
Thank you for the feedback. Unfortunately this is not a "small" request.

I don't know of any way to make the scanner faster. It must at least check the date of every file to see if it has changed.

It does not re-scan previously-registered plug-ins. It just displays the name and moves on.

If there were a single general solution, I would have implemented it already. At this point we have to track down failures one by one.

See #2.

Some additional thoughts:

Once you have performed one full scan, there's no need to scan again. It's easier and quicker to register new plug-ins one at a time; see https://pluginguru.net/unify/manual/dok ... l_plug-ins.

Some red-listed items may be 32-bit versions of plug-ins you also have in 64-bit form. Provided the 64-bit versions register correctly, you can ignore the red 32-bit ones (or better yet, delete them).

Individual registration often works when scanning fails. I have no idea why.

I know of no "third party scanners". Unify is built using the JUCE framework and uses their scanning code. Tracktion also uses JUCE; hence the similarity. I just run it in a separate process, restarting it automatically when it crashes.

Please clarify exactly what you mean when you say "I have to kill it because it gets stuck". Some plug-ins take an astoundingly long time to scan (again, I don't know why), but the scanner eventually gets past them. If you've found one that truly locks it up tight, please let me know.

Thanks Shane - clearly I need to be individually adding new plugins without rescanning. Helpful to understand JUCE is the framework and it could very well be that the some of the plugins are taking an astoundingly long time to scan. I think the answer for me is to manually add plugins going forward and avoid rescanning.

grdh20 · Post by **grdh20** » Thu Apr 23, 2020 2:59 pm

manually adding plugins for me isn't going to work. I move so many plugins and updates in and out over the course of a month, that I couldn't possibly remember which is which. can't Unify be set to just scan the newly added ones when open just like Logic does for instance?

getdunne · Post by **getdunne** » Thu Apr 23, 2020 8:09 pm

grdh20 wrote: Thu Apr 23, 2020 2:59 pm manually adding plugins for me isn't going to work. I move so many plugins and updates in and out over the course of a month, that I couldn't possibly remember which is which. can't Unify be set to just scan the newly added ones when open just like Logic does for instance?

Unify's plug-in scanner DISPLAYS the names of all plug-ins, as it checks to see if they have changed. The names zip by very quickly, because it does not attempt to LOAD each plug-in if it hasn't changed. It should only slow down when it hits plug-ins it hasn't seen before, because it actually has to load them to get additional information.

Logic does the same thing; it just doesn't display anything unless it finds new plug-ins. However, it also forces you to wait until it's done before you can use the program, which ours does not. Ours runs as a separate process, so you can just let it run in the background while you use Unify.

Most of the time, you won't need to re-scan plug-ins after simply installing an update. As long as the plug-in file is still in the same place, and its name hasn't changed, you're good to go.

Kalamata Kid · Post by **Kalamata Kid** » Thu Apr 30, 2020 3:52 am

Do Unify users use it on all the instrument tracks?
Or just in the tracks that my be a bit more complex?

BTW Unify 1.1 out soon?

mrsugmad · Post by **mrsugmad** » Thu Apr 30, 2020 4:01 am

Kalamata Kid wrote: Thu Apr 30, 2020 3:52 am Do Unify users use it on all the instrument tracks?
Or just in the tracks that my be a bit more complex?

BTW Unify 1.1 out soon?

It was mentioned that 1.1 will come out in May....

getdunne · Post by **getdunne** » Thu Apr 30, 2020 2:42 pm

May is the goal, yes, but Unify v1.1 has many changes, yielding new features but also new bugs. We won't release until it's working acceptably and has survived a few weeks of beta testing (which has already begun).

iPlogger · Post by **iPlogger** » Fri May 01, 2020 3:50 am

Kalamata Kid wrote: Thu Apr 30, 2020 3:52 am Do Unify users use it on all the instrument tracks?
Or just in the tracks that my be a bit more complex?

I find Unify is useful to use no matter how simple or complex the sound is. With the assignable/programmable macro knobs, even a single VST can make Unify useful. Unify also provides great tools for limiting values such as velocity and has really nice curve features. I recently used that for a piano so I wouldn't go over a certain velocity and drew a curve that was really just what I needed.

Unify is also a sound library so you can easily call up sounds. One area I've found difficult with my DAW. Which may be that I just don't know how to do that.

All that to say, I think Unify is useful even for less complex sounds. I have made so many instrument racks in Ableton Live and I do still use those. But I hope to eventually convert my Racks to Unify.

Kalamata Kid · Post by **Kalamata Kid** » Fri May 01, 2020 6:34 am

Thanks.
That answered my question.
So even if only one VSTi is used still better to use it inside Unify.

I like to use midi fx and Unify will certainly make it easier to do so.

FlyingWithoutTickets · Tue May 12, 2020 9:50 am

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

I made an account just to come help you all out with the VST Scan Hang issues.

So, I ran across this issue with Ableton/Installing Odesi a while back and I think this might help anyone trying to load large VST libraries into any DaW or tool like Unify...

I had a few free Vst's that I got off Plugin Boutique that kept crashing,
so I searched out this tool that scans VST's..
It's a bit old school, but it helped me get out of that pickle.

https://vb-audio.pagesperso-orange.fr/u ... canner.htm (https://vb-audio.pagesperso-orange.fr/us/resources/vst_scanner/vst_scanner.htm)

Hopes this helps..

Unify by PluginGuru; The next big thing?