@aMUSEd wrote:
Maybe it’s a Vanguard thing – I’m not seeing it either – had a fairly intensive project with Alchemy and tried deleting all the automation but it made no difference to the cpu hit.
That is my guess too or that it is one of the other vst’s i have in that song.
I will do some more testing to see where the problem is 😀
@Conquistador wrote:
Not seeing a x3 increase in CPU here. Just tried to automate a parameter in Trilogy. 10 -12 % fluctuation in Windows task manager (Max). Perhaps it is Plugin specific.
Running Vista SP2. Final not beta.
Thanks for testing it 😀
I am using XP SP3 and i also encounter allot of random crashes with this version for some strange reason.
Thanks 😀
I love the new navigator window.
I have also found a bug….
If you add automation to a track the cpu usage gets 3Doubled.
The song i was working on uses 7-9% in windows taskmanager but when i added automation to the filter cutoff on a track with Vanguard the cpu usage went up to 30%.
When i deleted the automation track it went down to 9% again.
You will be missed M8.
Hope you get your problems sorted out and that you will come back again soon..
Wish you the best of luck on your journey 😀
Take Care.
@Zynewave wrote:
I’ve uploaded an .exe beta 2.12. Could some of you that had the crash problem with 2.11 please try this beta and report if it works.
The new beta 2.12 work great here with XP SP3 😀
I just tried the exe test version now and i get the same error.
I use Windows xp with SP3 😀
@druid wrote:
So, if I install 2.11, it crashes. If I install 2.10 over the top, 2.10 crashes as well. I could try 2.09 and 2.08 etc over the top as well, if you were curious :P. But, if I remove it all, install 2.10 fresh, it works. I have not put back in my podium.ini at all since trying these things.
Same thing happened to me when i installed V2.10 over V2.09.
I had to remove V2.09 before i installed V2.10 to make it work properly.
Same here on a fresh install of 2.11.