Autocalc Video Memory

AVsupport wrote on 5/14/2018, 8:23 PM

Personally, I'm suss on how VP deals with VRAM.. indication is that:

[internal] Preference 'Autocalc Video Memory - 64Bit' cannot be set to 'TRUE' even though the actual default is 'TRUE'. Value is always 'FALSE'. Even when you try to change by hand. Go figure..

PS I had originally posted this in the 321 thread but got buried..I believe this might well be a bug or indication of one elswhere.. /edit and I cannot find this in the Known Issues list

Comments

Grazie wrote on 5/14/2018, 9:51 PM

NB:As usual you do this at YOUR OWN RISK!

Try this obvious re-re-setting:

1) Delete FALSE

2) APPLY

3) Again type FALSE and APPLY

4) EXIT and Close VP

5) Reopen VP

6) Delete FALSE and now type TRUE

7) APPLY and exit

What happens?

AVsupport wrote on 5/14/2018, 10:05 PM

@Grazie you cannot do 1) Delete FALSE and 2) APPLY as it won't store an empty / invalid command. It will always result in FALSE (..have you tried this yourself, or are you just guessing for a workaround?)

Grazie wrote on 5/14/2018, 10:25 PM

Yes I know that’s what will happen.

I hadn’t tried with this particular field, no, but I had had success with another Field so I wished to assist you with the experience I had. However, have you tried carrying on?

Grazie wrote on 5/14/2018, 10:29 PM

Oh, here’s a thought, if you have ANOTHER installed version of VP try that?

Kinvermark wrote on 5/14/2018, 10:31 PM

Why assume it is a bug? After all, it is in the internal prefs ,which are not normally accessible by users. The programmers may have very good reasons to disable this - messing around here seems ill advised.

Grazie wrote on 5/14/2018, 10:40 PM

@Kinvermark : Quite. My invitation to check this on another VP installed version could demonstrate convergence of the engineers protection of us dabbling about. Could be, and this IS a guess that there are OTHER Fields that cannot be changed. And here I am guessing 😉

AVsupport wrote on 5/14/2018, 10:42 PM

@Grazie, this not possible with VP14 either. @Kinvermark, maybe I should call it 'Not Working'. I am trying to find out why my 6GB video memory won't get used by Vegas. Hence I'm 'probing'.. /EDIT: if this feature is already in an internal - not visible folder-; so why would a developer 'disable' the feature if no one could/should get to it..makes not a lot of sense..

Grazie wrote on 5/14/2018, 10:53 PM

@Grazie, this not possible with VP14 either.

Thanks for testing. Looks like, and I AM guessing here, is that we aren’t meant to alter it 😉

if this feature is already in an internal - not visible folder-; so why would a developer 'disable' the feature if no one could/should get to it..makes not a lot of sense..

@AVsupport : Now THAT’S a good question.

Kinvermark wrote on 5/14/2018, 11:49 PM

Maybe just one more "safety" level. E.g. tech support may need to modify a users internal prefs, but some are just "no go" areas for them too. Anyway, no harm in you messing with your own system as long as you accept the risk... but most users shouldn't be doing this.

Grazie wrote on 5/15/2018, 12:03 AM

Anyway, no harm in you messing with your own system as long as you accept the risk... but most users shouldn't be doing this.

@Kinvermark : Sure..... However, and here I make reference to the previous 16 years I’ve spent on “this” Forum and elsewhere, visiting SONY at their many Tradestands from London to Amsterdam, if a User has the hardware or software that he/she wants to use in conjunction with Vegas/ACID/SF why won’t the products support it? And yes, I know the answer to that one, however, it’s all about managing the expectations of the Users. But hey, I can only guess (😉) why that is.

AVsupport wrote on 5/15/2018, 12:26 AM

Yes I think I am fully aware of my actions..and hopefully some of those findings might contribute for a better smoother bug free end product

NickHope wrote on 5/15/2018, 2:16 AM

I can't change "Autocalculate Video Memory (64-bit)" to TRUE in VP12, 13, 14 or 15. It doesn't exist in VP10, but "Autocalculate Video Memory" does, and I can't change that to TRUE either.

AVsupport wrote on 5/15/2018, 2:52 AM

So I wonder how does VP know how much VRAM to use if it can't calculate it? autopilot? or work in progress? Thanks for checking Nick!

VEGASDerek wrote on 5/15/2018, 9:01 AM

This internal preference is handled in an unusual way. The default is indeed TRUE, which, on the initial launch of the application, will calculate the total memory on the system and then store that value. Once that calculation occurs, the internal preference will automatically switch itself to FALSE, to ensure this calculation does not occur on future launches of the application (which generally is not necessary). Setting it to TRUE again will cause Vegas to recalculate the number again in the next launch of the application as will doing a full reset of the preferences.

The value calculated is primarily used for the Dynamic RAM Preview feature.

AVsupport wrote on 5/15/2018, 4:23 PM

Thank you for the insight @VEGASDerek ! Guess I can leave that one alone... Is there anywhere else where I can check how much VRAM VP is actually allocated?

VEGASDerek wrote on 5/15/2018, 4:43 PM

I misspoke initially saying that this was a video memory calculation. This is the cpu memory which is being calculated and a determination on how much of it should be allocated for Dynamic RAM Preview.

To my knowledge, no user facing property exists to show how much VRAM is being used. This is not my area of expertise so I may be wrong.

AVsupport wrote on 5/15/2018, 5:12 PM

Yes, it was the Video Memory allocation I was after.. [searching: 'MEM'] I was under the impression the dynamic RAM allocation happens elsewhere, like in the 'RAM Preview Limit' setting [searching: 'RAM']

feeling a little none-the-wiser..if its true if it is indeed CPU RAM then 'Autocalc Video Memory' is probably not such a great (ie potentially misleading) descriptor..sorry Derek, may have to remove that 'solution' tag for the time being..