Plugins scanning in T7 - mac: just awful.
- KVRian
- 599 posts since 8 Apr, 2014 from USA
-
- KVRist
- 212 posts since 4 Nov, 2004 from France
@gesslr
--------------
Thanks a lot for the app 'auganizer'. I will download the demo and see if it runs with T7...
Lutin mutin.
--------------
Thanks a lot for the app 'auganizer'. I will download the demo and see if it runs with T7...
Lutin mutin.
-
- KVRAF
- 1790 posts since 30 Dec, 2012
Thanks guys, we're taking a look into this. It shouldn't take hours to scan plugins and hasn't done in the past. It looks like it may be an El Capitan related issue. On our Yosemite test machine NI plugins take a second or two each to scan which is normal.
- KVRian
- 599 posts since 8 Apr, 2014 from USA
Thank you. It took me most of last night to rescan all of my plugins. Quite a few start, stop, relaunches in there.
In case you are interested, here is everything in my VST folder that failed....
Some are alphas (the ImageLine stuff) and is to be expected; the IRCAM and Flux stuff have failed elsewhere too....
In case you are interested, here is everything in my VST folder that failed....
Some are alphas (the ImageLine stuff) and is to be expected; the IRCAM and Flux stuff have failed elsewhere too....
You do not have the required permissions to view the files attached to this post.
-
Robert Randolph Robert Randolph https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=7328
- KVRAF
- 2226 posts since 25 May, 2003 from Saint Petersburg, Florida
FWIW, I am using El Cap.dRowAudio wrote:Thanks guys, we're taking a look into this. It shouldn't take hours to scan plugins and hasn't done in the past. It looks like it may be an El Capitan related issue. On our Yosemite test machine NI plugins take a second or two each to scan which is normal.
Is there any info I can get you guys to make this easier to debug?
-
- KVRAF
- 2464 posts since 9 Oct, 2008 from UK
Ah, so it's a Mac feature! I feel quite left out!dRowAudio wrote:Thanks guys, we're taking a look into this. It shouldn't take hours to scan plugins and hasn't done in the past. It looks like it may be an El Capitan related issue. On our Yosemite test machine NI plugins take a second or two each to scan which is normal.
[W10-64, T5/6/7/W8/9/10/11/12/13, 32(to W8)&64 all, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.
-
- KVRist
- 301 posts since 9 Sep, 2005 from Washington State. USA
Yep, I'm running Yosemite, and on my old mid-2009 MacBook Pro I did a complete rescan in under a minute. (So this would seem to be another Apple upgrade 'feature').
iMac (Retina 5K, 27-inch, 2017), 4.2 GHz Intel Core i7
Radeon Pro 580 8 GB
Focusrite Scarlett 4i4 3rd Gen
Waveform 11 Pro/Studio One Pro 3.5
Radeon Pro 580 8 GB
Focusrite Scarlett 4i4 3rd Gen
Waveform 11 Pro/Studio One Pro 3.5
- KVRian
- 599 posts since 8 Apr, 2014 from USA
I'm on Yosemite too.
-
- KVRist
- Topic Starter
- 260 posts since 23 Oct, 2004
Hate to say but i am on 10.10.5 and i started this scan issue topic.dRowAudio wrote:Thanks guys, we're taking a look into this. It shouldn't take hours to scan plugins and hasn't done in the past. It looks like it may be an El Capitan related issue. On our Yosemite test machine NI plugins take a second or two each to scan which is normal.
So i assume it's not (specifically) El Cap related...
Rob van Hees
-
- KVRAF
- 1790 posts since 30 Dec, 2012
We've spotted one thing that could be slowing down the scan (and yes, it's not El Cap specific).
When the new version is available later this week hopefully please try it and feedback here. Thanks!
When the new version is available later this week hopefully please try it and feedback here. Thanks!
-
- KVRAF
- 1790 posts since 30 Dec, 2012
FYI guys, we've release a beta version with some scanning improvements that might help.
If you want to give it a go and let us know if it helps any feedback would be much appreciated.
If you want to give it a go and let us know if it helps any feedback would be much appreciated.
-
- KVRist
- 377 posts since 17 Mar, 2010
Definitely appreciate the focus here by Tracktion team. However, build 26 is a step backward (at least for me on OS X 10.9.5). The AU scanning is fast and works as expected. But VST plugins are scanning very, very slowly -- and it's rescanning all of them every time. A thought/suggestion -- Steinberg does scanning with Cubase in a simple, effective way. They have two preference files -- scanned plugins and "blacklist" plugins that didn't pass the validation process. If a plugin hasn't changed (e.g., date modified check), and it's in one of those two files, don't rescan it. The nice thing about that approach, as a user, one can delete the blacklist file to control what get's rescanned. I know Tracktion has the equivalent in the plugin list (white ok, red fail) -- but it doesn't seem to consistently use that list to determine what plugins have changed. I appreciate that the initial scan with any DAW will likely be time consuming and unpleasant. But after that, it should be quick and efficient. I think I'll bail at this point with VST scanning, as it's only 6% done (15 minutes into it), and I'll just have to do it again at some point in the near future. Sigh...
-
- KVRAF
- 1790 posts since 30 Dec, 2012
The VST scan definitely shouldn't be rescanning the plugins every time. It has to look at the files to see if the modification times are different but if they're not it will definitely just skip it. I have several hundred VSTs and when I do a scan now it takes about 2 seconds.
We also have a set of blacklisted files which gets created if plugins crash whilst being scanned. These are not even attempted to scan until you delete the blacklisted entry so shouldn't affect scan times at all.
It seems like there is something strange going on with your machine and VST plugins, there shouldn't be a huge difference between AU and VST scan times, we check the same things for each. Do you perhaps have them on an external drive or could there be something modifying the files slightly such as a backup program? At this point I'm struggling to see what could be different between our machines..
We also have a set of blacklisted files which gets created if plugins crash whilst being scanned. These are not even attempted to scan until you delete the blacklisted entry so shouldn't affect scan times at all.
It seems like there is something strange going on with your machine and VST plugins, there shouldn't be a huge difference between AU and VST scan times, we check the same things for each. Do you perhaps have them on an external drive or could there be something modifying the files slightly such as a backup program? At this point I'm struggling to see what could be different between our machines..
- KVRian
- 599 posts since 8 Apr, 2014 from USA
Hmmm....could you tell me how or why a back up program would modify the files such that it might trigger unnecessary scanning? This may apply to me too.
Thanks.
Thanks.
