RAM render falters . . ?

Grazie wrote on 12/16/2004, 12:35 AM
Got a still. Used P/C on it for rotate. I wanna see in preview and set up RAM Prev. Does 2 frames and stops. Duah!? What's that about? RAM allocation 1000mb. I've had this before . ..

TIA

Grazie

Comments

taliesin wrote on 12/16/2004, 1:32 AM
Is it a high def picture? Those pics eat looooooots of Ram ...

Marco
Grazie wrote on 12/16/2004, 1:49 AM
Marco? How do I say this? . . . no. G
taliesin wrote on 12/16/2004, 5:04 AM
Oh ... I just tried using a high res pic, made a rotation of a 360 degree angle in 4 seconds and used ram preview with only 94 MB allocated. It worked fine.

So maybe do you have your loop region set to only two frames (for Ram preview only works on the loop region area)?

Marco
taliesin wrote on 12/16/2004, 5:07 AM
Or maybe it's the file type. I used JPEG, PNG should work as well.

Marco
JJKizak wrote on 12/16/2004, 5:40 AM
There may be something here. I had a still jpg with rotate and P/C applied for about 10 seconds and it stopped the DVD NTSC render cold. Had to remove it then everything OK. Also had composite added.

JJK
Grazie wrote on 12/16/2004, 5:48 AM
Jpeg
Grazie wrote on 12/16/2004, 5:58 AM
Try this one for size ! ! ! !


1/- Put a Jppeg on a t/l

2/- Pan/Crop a couple of rotations

3/- Select Event

4/- Build Ram PV

5/- I get 2 frames.


. .. here's the killer .. . please try it to confirm I'm NOT going bonkers . ..


6/- Copy the same event with the rotations in it.

7/- Paste back somewhere on Time Line

8/ NOW Build Ram PV! .. .

GOT IT!

9/- Go back and try and Build Ram PV . .result? Only 2 frames . .. weird!

Grazie . . taking medication . . .



taliesin wrote on 12/16/2004, 7:33 AM
Step 1 to 4 works fine for me with a 2560x1920 hires pic and 94 MB Ram allocated. Ram rendering makes all the five seconds I used for the event length (5 rotations).

Marco
Grazie wrote on 12/16/2004, 8:26 AM
Yes! Back to normal here too! Well .. when I say normal . ..

Thanks

Grazie
nickle wrote on 12/16/2004, 9:10 AM
I just put a 2592x1728 jpeg on the timeline, rotated it 360 degrees

preview size 720x480 (preview auto) with ram set at "0".

No problems.

I tried messing with ram preview settings before and didn't see any difference in the preview no matter how much ram I set it for.
Grazie wrote on 12/16/2004, 9:48 AM
I haven't got the foggiest idea what was happenning .. Spot checked it for me too . . Grazie . . . Decemebr 16th ? I dunno . . .

Grazie
Chanimal wrote on 12/16/2004, 10:09 AM
I'm sure you've tried this, but it hasn't been addressed. Have you tried reducing the ram preview size to 512 or something smaller (you may not have 1000 meg of actual ram left (even with a lot of RAM (I have 1.5 gig, sounds like you have more)) and it could be going to the virtual drive memory and messing up)?

***************
Ted Finch
Chanimal.com

Windows 11 Pro, i9 (10850k - 20 logical cores), Corsair water-cooled, MSI Gaming Plus motherboard, 64 GB Corsair RAM, 4 Samsung Pro SSD drives (1 GB, 2 GB, 2 GB and 4 GB), AMD video Radeo RX 580, 4 Dell HD monitors.Canon 80d DSL camera with Rhode mic, Zoom H4 mic. Vegas Pro 21 Edit (user since Vegas 2.0), Camtasia (latest), JumpBacks, etc.

nickle wrote on 12/16/2004, 4:43 PM
I just did an experiment

4 tracks of video with a total of 4 2592x1728 jpegs 1 1440x972 and 3 700x400 tga

all pan/crop to rotate 360 degrees.

At 720x480 preview (full) with ram preview at "0" there was a very slight stutter at each 90 degree position.

At 360x240 preview (good) all was perfectly smooth.

At 720x480 draft (full) all was perfectly smooth.

Changing to 128MB or 384MB ram preview made no difference.
Grazie wrote on 12/19/2004, 1:03 AM
Well! I just got/repeated the same 2 frame nonsense. I as doing this to assist our colleague on Pan/Crop . .and I'e been playing with the Ssmotth filter plugs .. .

So, friends, I've repeated it . .. but if I make a "Copy" of the event and Paste someway down the T/L and then RAM buiold Preview it works! .. Weird science.

Grazie

nickle wrote on 12/19/2004, 11:53 AM
There is something weird with ram preview.

Wax wants it set at "0".

Boris wants it set at "0".

Something to do with Vagas caching.

Like I said I saw NO difference, whatever the settings.

I only have 512MB ram so I can only raise it to 384MB, but there is NO difference for me, so I leave it at "0" and haven't had any negative effects.
taliesin wrote on 12/19/2004, 12:14 PM
The difference is: If you set it to "0" then Ram preview is not even available in Vegas.

Marco
Grazie wrote on 12/19/2004, 1:57 PM
Still persistent:

1/- New track

2/- Put in Event

3/- Apply . .anything .. I've used P/C

4/- Highlight, Loop, the whole Event

5/- Tools > Build RAM Preview

. . result . . . ?

6/- RAM starts to build then only 2 frames done .. . .

HOWEVR: Copy the same EVENT and Paste somewhere down T/L and repeat RAM Preview Build - it works!

Again, TIA,

Grazie