@jasensmith said:
until I'm done with the hot chick (windows fogged up).
Good one, "windows fogged up" ... PC ...
But seriously, it seems that there is some confusion here:
- I use a Mac
- I use Logic Pro
- I don't use VE
- I use VI like any other plugin (Omnisphere, Play, Zebra, etc)
We seemed to establish already that ...
- authorization on VI and VE is different
- authorization on a Mac and PC is different.
So if you are on a PC or using mainly VE then you don't have to deal with the long authorization process. Again this is not a call for help in trouble shooting. This post was intended to tell VSL that 5 minutes for a plugin authentication every time you start/restart your machine is outrages and gather more support from other Mac/Logic/VI users that are also outraged to show VSL this is unacceptable.
Obviously most VSL users are on a PC or are on a Mac and don't care much about that, so my mission has failed.
PS:
Using Logic in 64bit and having 16GB of RAM seems plenty. But here is the catch where you have to restart from time to time during the day. For example if you are using Omnisphere, Trilian or Play plugins in a Project and browse through lots of sounds (loading one preset after another while overwriting the previous one), then you will see that your 16GB of RAM gets eaten up pretty fast and you reach the 0 bytes physical RAM situation moving into swap space territory. Every time you overwrite a previous preset, OSX doesn't clean out that memory space but keeps some as inactive memory. So once your samples get paged out into swap space memory addressing, performance starts to degrade and it is time for tabula rasa and reboot the machine.
Although 32bit apps imposed the infamous 4GB memory limitation, but at least it also kept you from entering the swap space. This is a little detail that was hidden in the fine print when they sold us the holy land of 64bit apps.
Again this is on a Mac and I don't have any idea if you are dealing with the same RAM fragmentation and swap space issues on a PC.