OK, 1 Swallow don't make a Summer, but.. . . . .

Grazie wrote on 1/12/2012, 4:07 AM

So, experimenting since 3:30am this morning.

In VP10-32 I'm getting crashes and so on. In desperation I want to check a section of titles+Cinescore+mixed compositing - all-in-all about five Tracks of Intro, runtime, about 10 seconds. No biggie.

Shift+B ain't big enough I then increase from 64mb to 100mb. I get more on the T/L - nothing new there. But I still want a bigger slice to check. I up the RAM to 200mb and get the warning about exceeding what could be available. Yeah yeah . . . Oh, ok, let's see how much I have available? 1.5gb . . . . ok . . ? Off I go and get a bigger slice of RAM-pie and yes, I get a longer view . . . nice.

My next crash is a bit more illuminating:

"OUT OF MEMORY"! What??!?

I then prune everything down to bare bones: Zap media away; use my minimalist Windows Layout and disable "Media Mangler" . . . .

OK, I recheck and reopen . . . 1.5gb . . ..

Now I start thinking sideways. Er, Grazie, how about ditching 32 and go into 64?

Well, I have to say, so far so good.

Here's the thing: IS there a natural ceiling to 32bit that when what I'm doing just wont play ball? IS/are there projects that NOW have to go into 64bit? And this is JUST to access more RAM=memory? 32bit says 1.5gb, I understand that, 64bit says 15gb. Now, tell me that that is and has NOW become important for the Project I'm doing? If that's so, I'll go away and lick my wounds.

Is it as simple as that?

And still stable . . . . . one Swallow etc . . .

Cheers - and thanks for putting up with me.

G

Comments

farss wrote on 1/12/2012, 6:20 AM

"IS/are there projects that NOW have to go into 64bit?"

IF you mean just the project data itself then possibly based on what I've heard from Avid. They we forced into 64bit because they were finding more and more users were having split large projects into "reels" just to ge the project data to fit into RAM.

Just how well that may translate into Vegas I don't know but Vegas projects cand be way more complex than what I'd imagine a typical movie edit is.
On the other hand Avid's systems use a LOT of metadata.

Make of it that what you will and I have run projects withe between 3,000 and 10,000 events in V9 and not had a problem but they were primarliy audio events. Here's a though, how big is your project file?
Keep in mind that your project file is packed binary and may use a lot more RAM once unpacked.

And up against all that is that if Vegas has a memory leak or memory management problem then simply having more RAM for it to run amok in means it may never hit a hard stop and cause Windows to shut Vegas down.

Bob.

ritsmer wrote on 1/12/2012, 8:53 AM

32bit? 64 bit?

Once upon a time more or less everybody saw the limitations of 32 bit programs giving instability and crashes.
AFIK it was a question of Windows ability to assign large amounts of memory.
One of the first programs that could not work reliably under a 32 bit Windows was Microsofts own Flight Simulator.
Then some bright users invented a method to make Windows assign the needed memory in a more reliable way - and that helped the Flight Simulator and other programs.
In this forum a bright user introduced this method - which has helped several users since - and which made it possible for them to use their 32 bit hardware in the beginning of the HD era.

At that time I dubbed that method : "The Blink3times 2 GB hack" after the user who introduced it here.

Conclusion: If you must run at 32 bit then apply the 2 GB hack (search for it in this forum) - else install and enjoy the 64 bit versions of your software.

amendegw wrote on 1/12/2012, 9:39 AM

Ha! Don't ask me how I came across it, but I just ran into the following post from over 5 years ago [chuckle]

...Jerry

Grazie wrote on 1/12/2012, 10:36 AM

Jezzer! I remember it very well!! Lol!

Just for the record, and to claw back some of my IT-cred, there ain't no 64bit version of CineScore. SONY stopped developing it back in 32bit.

G