Choppy Preview even with HUGE spec PC +64bit Mod

IanH wrote on 7/9/2011, 6:09 AM
Hi all, I'm using VMS 10 and I realise there's some issues with the Preview but even my huge spec PC can't run it smoothly

Intel i7 2600k @ 4.6Ghz (8 cores with hyperthreading)
120GB Vertxe 3 SSD (550mb read/write)
16GB XMS3 RAM
Nvidia 580GTX GPU (512 CUDA)

Now this thing can fly through intense FPS games @ 1920x1080p no problem yet can't even do 1fps on the preview when 2 or more layers need previewing and it's making my attempts at Transitions very difficult as I'm having to VRAM buffer every transition just so I can watch the transition effect in realtime..

My VMS settings are - 64bit mod enabled, Eugenia's settings guide followed & Preview window at "Preview Half".

Any ideas other than VMS 11 or a 2nd monitor (I don't want to spend any more)?

Cheers.........................................................IanH

Comments

Markk655 wrote on 7/9/2011, 11:27 AM
Did you check if there is anything else running in the background which isn't needed? For example, is your PC indexing files while trying to preview? virus checking?

I'm assuming that you editing mp4, avchd or avchd lite. Is that correct?

A good test would be download the VMS11 trial and see if the behavior is improved. If it doesn't help, then there is something in your PC bogging down VMS. I edit 1920x1080 on a Core 2 Duo 2.66GHz/4 GB RAM/Nvidia GT240/32 bit Vista. For me 1 crossfade (in 1 track) for 2 1920x1080 AVCHD files in VMS 10 goes to a low of ~5 fps in preview (auto; with adjust size/quality for optimal playback checked). In VMS 11 it goes down to a minimum of ~10 fps.However, VMS 11 is much better at previewing the unchanged part of a clip.

When you say you followed Eugenia's guide, are you referring to her "rendering for HD Vimeo" guide or her guide on use of proxy files?

Eugenia wrote on 7/9/2011, 12:12 PM
For h.264 Mpeg4/avchd footage, is best to upgrade to VMS11. You could have bought a cheaper PC and save that $65 required to upgrade. You can install the trial version in parallel to test it.

You can be in preview/auto (no need for preview/half), and as long as:
1. Your project properties are set correctly to mirror your footage's properties.
2. You have no plugins on your events in the timeline loaded
then preview will be real time.

For plugins you must do them at the very end, when the editing has finished. At that point it doesn't matter if it's real time or not. Plugins and most transitions are never real time anyway, no matter what spec PC you got.
musicvid10 wrote on 7/9/2011, 12:17 PM
"yet can't even do 1fps on the preview when 2 or more layers need previewing and it's making my attempts at Transitions very difficult as I'm having to VRAM buffer every transition just so I can watch the transition effect in realtime.. "

You see, your layers and transitions and effects don't exist as video files, but are merely a set of instructions that must be rendered in real time in order to preview, unless you pre-render them by one means or another.

So the preview fps is entirely dependent on your system's ability to crunch all those numbers in real time. The things that help, as have been detailed many times before, are to Match Project to Media Settings, turn off preview enhancements, and use an intermediate render to take the load off your CPU.


You left out one critical piece of information, that being your source footage, but In the case of AVCHD or DSLR, with GOPs 200-400 frames in length and various flavors of b-frames sprinkled throughout, it's a wonder they preview at all, even without effects and transitions.

Right now, I understand VMS 11 is doing better with this than Vegas Pro 10, which costs several hundred dollars more.
IanH wrote on 7/10/2011, 7:28 AM
Boy do I feel like a dumbass now - Found the issue after checking my source footage for you guys/gals. Now, I'm doing a some Rally car for a mates Team so I've got multiple sources of video (for Pic in Pic, in-car, outside etc), PNG's of Racetrack maps and normal JPG Pictures all combined so there's alot of source files to check.

Anyway, as a test I rendered one of the track layouts in 25mbps 1080p to see how it looked (final product is 1080p 8mbps for the Internet but I hit the wrong 1080p) and then I've made a big mistake. Somehow I've deleted the original PNG image of the track and re-added the 1080p movie version instead of the PNG (I haven't a clue how/why etc, must have been tired) which is slowing eveything down, the 25mbps file won't play smoothly even on it's own.

Now I've figured that out I've a play and I've found I can have a maximum of 10 video lines all doing 1080p 8mbps with no slow down in the preview window.

Again, I haven't a clue how/why I've added a 1080p movie of a tiny PNG but at least I've found the issue!
trgtc wrote on 7/10/2011, 5:22 PM
Hi Ian,

When I was using VMS10P, I was also having major problems with the preview (about 3-4 SECONDS per FRAME <-Yes, I said that right) though I never had a problem with VMS9P. I work with 640x480 AVI files from a Canon Powershot S5IS.

A test with the Vegas Pro 10.0d trial showed no problem and the VMS11P trial also showed no problem.

I went through the tech support process and showed them the extent of the problem and Sony, much to their credit Thank You Very Much, upgraded me to VMS11P.

Try the trial version of VMS11 and see if you still have preview problems. Make sure you document everything by shooting video of your screen, so you can show Sony what's going on. If you open a tech support ticket, be patient. It will probably take them upwards of a week to respond initially, but after that their replies should come back within a day.

Good Luck,

Jon
yowzer wrote on 7/16/2011, 7:02 AM
I've found this topic in the knowledgebase (and most links contained therein) to be most helpful.

https://www.custcenter.com/app/answers/detail/a_id/4168/kw/program%20hangs/session/L3RpbWUvMTMxMDgyNDU4Mi9zaWQvVUFEeXA3ems%3D

I have a great computer, but at some point along the timeline, the processing required for a project puts too much demand on the system. There are a bunch of things to help - the best one I've found is dividing the project into smaller projects for rendering separately and importing into one, large final project at the end. But there are many other suggestions - many of which the great members of this site seem to have to suggest all too often for us less-experienced editors.