Plugins scanning in T7 - mac: just awful.

Discussion about: tracktion.com
Post Reply New Topic
RELATED
PRODUCTS

Post

T7 on mac, 64bit version:

Scanning my plugins arsenal (AU,VST,VST3) in T7 is just awful.
The scanning process just "hangs" alot.
Have to abort scanning and then re-scan for the scanning proces to move on.
With the many plugins i have this proces is just hilarious. :evil:

Oftopic but ..:
Bought T7 last week, just as it seems a quit revolutionary DAW.

Right away 3 issues:

- After purchase of T7 ultimate bundle, the order seemed to have been pending so i had no accces
to download it, after purchase.
- Also, because of this pending situation, i didn't got a license file.
- Support sent me a license file,but it doesn't work, gives me an error.
- So, ok, then going in Trial mode today , and i experience this plugin scanning issue.

Totally bad first Tracktion impression ; not a happy customer currently.
Wonder if i went on the Tracktion (T7) boat to soon.
Rob van Hees
Top

Post

vanhaze wrote:T7 on mac, 64bit version:

Scanning my plugins arsenal (AU,VST,VST3) in T7 is just awful.
The scanning process just "hangs" alot.
Have to abort scanning and then re-scan for the scanning proces to move on.
With the many plugins i have this proces is just hilarious. :evil:
same here just for the record. it took me nearly a day of stopping and restarting to scan all my plugins and I was left with a list of about 100 vsts that failed. It got worse near the end of the scans for some reason and in the last 20% it was stalling on every single plugin. BUT, if I try and use said stalled plugin, some of them worked ok anyways. But I'm still loving T7 overall...
Top

Post

Plugin scanning on the Mac isn't very good (compared to other hosts) and can be very time consuming. Once the process is initially complete, the incremental scans are better. There are a few plugins that just don't get recognized, and after getting noted as such, get bypassed every time. One thing that would help is after a plugin is initially scanned, don't rescan it again. For example, Waves Mercury VST3 takes 10 minutes to scan on my system. If it only did this once when the Waves plugins are initially updated, it's not great but tolerable. Unfortunately, it rescans every time there-after, which is a big time sink. That said, plugin scanning has improved over time, so hopefully Tracktion develop effort in this area will continue to improve the process.
Top

Post

Thanks guys, for shiming in on this.
I am "glad" that i am not the only one, so it seems...
Rob van Hees
Top

Post

Agreed. It took me a couple passes to get my plugins scanned properly in OS X. The process crashed multiple times... yet if I rescanned, some of them would work!

Some plugins also took FOREVER to scan.
Top

Post

Oh dear.

The plug-in scan only happens when you tell it to, so it's mostly a one-off, except when you want it to look for new ones. If your plug-ins are in different folders, you might try doing it folder-by-folder to see if it gets through it all a bit faster. Perhaps.

Did you get back to Support?
[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.
Top

Post

jabe wrote:Oh dear.

The plug-in scan only happens when you tell it to, so it's mostly a one-off, except when you want it to look for new ones. If your plug-ins are in different folders, you might try doing it folder-by-folder to see if it gets through it all a bit faster. Perhaps.

Did you get back to Support?
Even for a one-off, it took me over an hour to get all my plug-ins scanned.

That's over an hour of being at the computer and killing processes, rescanning, deleting bypassed plugs etc..

Not ideal.
Top

Post

Totally agree here ..
Rob van Hees
Top

Post

Robert Randolph wrote: Not ideal.
Not ideal.
[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.
Top

Post

It is very painful the first time through. FWIW, the incremental scans once you get through that mess are better...
iMacPro 1,1 | 64gb | OSX 10.15.7
http://www.gesslr.com
http://www.storyaudio.com
Top

Post

This is why I don't allow Tracktion to scan all my plugins, for VST2 plugins I point it to just a selection that I have in a separate folder with symlinks in to the plugins I want Tracktion to use. It seems pointless to have it scan them all when so many are duplicated between the 3 formats anyway. For the few that I do need to have in other formats (plugins that have VST3 or AU versions but no VST2) I just drag them directly onto the plugin manager page and they get scanned selectively.
Top

Post

My old MacBook Pro handled everything quickly on my first scan in T7: is that just because it was importing my T6 settings and doing an incremental update?

Tracktion's initial plugin scanning woes have caused headaches since what, T4? I usually avoid playing the 'my other daw...' game, but Studio One, Reaper, MainStage, even Adobe Audition seem to scan all my plugins quickly, with so little drama I'm not even aware of the process. Is there something specific to how Tracktion integrates and tests plugins that makes the task more complicated?
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
Top

Post

Same here than aMUSEd.

And because I'm on Mac, if I have the choice, I scan only the AU plug-ins most frequently used.
If one of them is only available in an other format (VST2 or 3), I drag and drop it directly in.
For me, the advantage is that I have not an enormous list to chose from when I want to put a plug in a track or in a clip.

By the way, I see the scanning process better from T4... I let Jules and the team a bit of time to find the right way. Don't forget that also, the Tracktion DAW comes in the 3 OS : Windows, Mac and Linux, with big changes in short times in the win OS (OS 8, 8,1, 10), in the Mac OSX from Mavericks to El Capitan (sorry, I don't know if it is also the case for Linux).

Ok, ok, my arguments are not very... let say... professional...
But as a very big fanboy since the very early days (T1), I am so happy than Jules and a very small team have had the courage to give a new life to this revolutionary Daw killed by the Mackie company, than I gives big excuses to the TSC team... ;-)

All the best,
Lutin mutin.
Top

Post

Lutin mutin wrote:Same here than aMUSEd.

And because I'm on Mac, if I have the choice, I scan only the AU plug-ins most frequently used.
I would like to do that, some plugins (eg Soundtoys) run better in Tracktion than their VST2 versions, but aupreset support in Tracktion is still crappy and it is easier to create a folder of symlinks to VST2 plugins because you can't have custom AU/VST3 paths like you can VST2 paths.
Top

Post

to aMUSEd

Because you create a symlink, you are right, and I agree with you, of course.

But I don't do exactly like you...
On Mac, when installing the plug-ins, they are automatically stored in the 'components' folder. Ok. And it's the only folder that is scanned when needed. Ok.

I've created an other folder called something like 'other AU components' in witch I drag-and-drop manually all the AU plug-ins I don't use. So, in the 'normal' library folder are only those who I use regularly. And when I scan my AU plug-ins, Logic Pro X or Tracktion, scan only my preferred.
And if I need a specific one (outside the 'official' folder, with a manual drag-and-drop, I put it in the 'official folder' and I make a new scan.
I know that it is not very simple and it is time consuming. But if I have a lot of plug-ins (is a fact), in my regular way to compose music, I have to say that in 90% of the cases, they are always the same plug-ins that I use... as instruments and/or as 'filters'...

My 2 cents...

All the best,
Lutin mutin.
Top
Post Reply

Return to “Tracktion”