PreRender is Excellent - Build Ram Preview stops at less than 8%. Why?

Grazie wrote on 8/17/2019, 1:43 AM

I've set BRP very, very high, 20gb and I only get 20 frames processed. Why? - Oh yeah, originally had BRP set at 200mb and got 4 frames.

Project: 1080p 30fps

Duration: 6 seconds.

Two Tracks:

T1 - TEXT Alpha - GenMed Legacy Text (FIRE) + Particle Illusion (Smoke and Flames Looks gorgeous! Flames and smoke . . . )

T2 - "Elephants" MP4 1080p 30fps + ColorFast2 (nice!)

Not getting anywhere near the full usage of all the RAM I throw at this piece. Why?

Comments

Marco. wrote on 8/17/2019, 3:16 AM

Maybe one of you RAM modules is defect. Any chance to check?

Grazie wrote on 8/17/2019, 3:40 AM

Any chance to check?

@Marco. Thank you. How?

 

wilvan wrote on 8/17/2019, 4:05 AM

I noticed here that having both GPU=ON and lots of dynamic RAM dedicated are not a good match . In SONY's vegas pro 13 I standard have 48 GB ( out of 128 GB ) dedicated for dynamic RAM and have GPU=OFF . Works fine and fast when making small changes and quickly run dynamic ram preview to almost immediately see the final result real-time. You could maybe give it a retry with same 20 GB and GPU=OFF . Would be interesting to see whether that improves the dynamic RAM use . Just a suggestion only

 

Sony  PXW-FX9 and 2 x Sony PXW-Z280  ( optimised as per Doug Jensen Master Classes and Alister Chapman advices ) Sony A7 IV
2 x HP Z840 workstations , each as follows : WIN10 pro x 64 , 2 x 10 core Xeon E5-2687W V3 at 3.5 GHz , 256 GB reg ECC RAM , HP nvidia quadro RTX A5000 ( 24GB ), 3 x samsung 970 EVO Plus 1TB M.2 2280 PCIe 3.0 x4  , 3 x SSD 1TB samsung 860 pro , 3 x 3TB WD3003FZEX.
SONY Vegas Pro 13 build 453  ( user since version 4 ) , SONY DVDarch , SONY SoundForge(s) , SONY Acid Pro(s) , SONY Cinescore ( each year buying upgrades for all of them since vegas pro 4 )
(MAGIX) Vegas pro 14 ( bought it as a kind of support but never installed it )
SONY CATALYST browse 
Adobe Photoshop  CC 2025
Adobe After Effects CC 2025 & Adobe Media Encoder CC 2025
Avid Media Composer 2024.xx ( started with the FREE Avid Media Composer First in 2019 )
Dedicated solely editing systems , fully optimized , windows 10 pro x 64 
( win10 pro operating systems , all most silly garbage and kid's stuff of microsoft entirely removed , never update win 10 unless required for editing purposes or ( maybe ) after a while when updates have proven to be reliable and no needless microsoft kid's stuff is added in the updates )

Grazie wrote on 8/17/2019, 4:32 AM

@wilvan - I’ll have a go. Thanks.

Grazie wrote on 8/17/2019, 4:43 AM

@wilvan - Nope, made no difference, still only a handful of RAM Built Frames.

Marco. wrote on 8/17/2019, 4:53 AM

@Grazie
"Thank you. How?"

Press "Windows+R".
In the command type "mdsched" and press Enter.
Let your system restart to start the scan process (which will take very long).
Then see the log generated.

Grazie wrote on 8/17/2019, 5:43 AM

Let your system restart to start the scan process (which will take very long).

@Marco. How long? More than 3 hours? 6 hours?

Then see the log generated.

@Marco. OK. What would I see if there was an issue?

 

Marco. wrote on 8/17/2019, 5:44 AM

I can't tell. After the restart mine just says there is no error.

Grazie wrote on 8/17/2019, 5:47 AM

I can't tell. After the restart mine just says there is no error.

@Marco. So, I’d only see “no error” if there wasn’t an issue. Presumably I’d get a thorough report if there was an error? Perhaps I should do this overnight?

Marco. wrote on 8/17/2019, 5:59 AM

It took about an hour on my notebook.

Grazie wrote on 8/17/2019, 6:32 AM

Press "Windows+R".

@Marco. Oops! What do I do? Windows Icon and type “r”? That’s not working here. Explain please?

Grazie wrote on 8/17/2019, 6:48 AM

@Marco. Working. I didn’t need to type “r”, typed mdsched.

Grazie wrote on 8/17/2019, 8:53 AM

@Marco. No issues reported. It took 2 hours.

Grazie wrote on 8/17/2019, 9:21 AM

Success - I didn't know this, separate BRP:

T2 - Shift+B

then

T1 - Shift+B

Having separated the BRP got me through. The SAME selection but separate BRP didn't remove the previous? Did you know this?