mp3jrick
That is what I did, but not the point I was making.
This discovery was made months ago and the setting was changed then.
I've opened it many many times and done gigs without incident until yesterday.
I'm just not understanding how it could have changed back unless it was in the course of an update because I certainly wouldn't have done this.
The other thing is how the setting is determined.
Its supposed to limit the memory draw so there is head room to prevent what is happening here.
With a 512 card, why is it choosing 488 as the limit being 85% of the available memory instead of half which is working fine and apparently sufficient?
This discovery was made months ago and the setting was changed then.
I've opened it many many times and done gigs without incident until yesterday.
I'm just not understanding how it could have changed back unless it was in the course of an update because I certainly wouldn't have done this.
The other thing is how the setting is determined.
Its supposed to limit the memory draw so there is head room to prevent what is happening here.
With a 512 card, why is it choosing 488 as the limit being 85% of the available memory instead of half which is working fine and apparently sufficient?
geposted Sun 18 Nov 18 @ 2:15 pm