Ridiculous rendering bug (upscaling DV->.MXF)

ReceptorDeceptor wrote on 5/22/2013, 8:38 PM
This has got to be the most ridiculous rendering bug I've encountered in Sony Vegas so far.

Running Vegas 12 Pro Suite.

I'm trying to upscale a NTSC DV file so that it is opened and upscaled into a 1920x1080 @ 24FPS project and then rendered to MXF. There is only one video track, one audio track, one file altogether, no effects in either audio or in the video track, or in master buses. I had to tear my other project apart in order to see what was causing the problem in rendering, and apparently a simple NTSC DV file will do! It plays back just fine, so I don't understand the problem at all.

Rendering starts very nicely, but freezes completely at 2000 frames or sooner. I've tried rendering to different HDD's and just about everything else I could think of (changing the compatibility modes in Win7, rendering just the video track, etc etc), but nothing helps. This is just unacceptable.

I'd highly appreciate all the help I can get, thanks.

Comments

VidMus wrote on 5/22/2013, 8:44 PM
Help us help you by including your system specs and driver versions.

If I use a later Nvidia driver and have certain settings in options I will have this problem on some types of renders.

Need more information please.
ReceptorDeceptor wrote on 5/22/2013, 8:57 PM
Hi there,

OS: Win7 64-bit Professional (EN)
CPU: Intel i7 Core 860K
RAM: 16GB
Graphics card: AMD FirePro V7900
(Driver version 9.3.3.3000)

Sound card: RME Hammerfall DSP + Multiface (ASIO)

Vegas installed on system volume SSD (Intel 520 series).
Source video from external RAID (tried internal drives as well)
Target video to external RAID (tried internal drives as well).

Even if I copy the video to a new project and try rendering to/from a completely different drive, the rendering freezes at no later than @~2000 frames (render time calculator still running, disk I/O & CPU usage by Vegas halts completely). I can watch the video in full quality preview with no problems at all ...

ReceptorDeceptor wrote on 5/22/2013, 9:25 PM
Well, this is interesting.

Should have suspected the usual culprit once again! I set the "Dynamic RAM Preview" amount from the options menu to 0 and now it's rendering. I might have fixed this one by myself after all!

Throughout the years I've tried just about every value (including 0), but lately (= since VP12), preview/editing has been working quite well with GPU acceleration turned on and 16MB as the Dynamic RAM Preview amount (yes, 16MB, not 16GB).

I still wonder why a majority of Vegas problems are related to the RAM preview settings, and especially why the preview RAM amount affects rendering times altogether. Found more talk on this issue from: http://forums.creativecow.net/thread/24/941540

Somehow I would have presumed that Sony would have fixed problems like this a long time ago.
ReceptorDeceptor wrote on 5/22/2013, 9:39 PM
More information on how dynamic RAM preview affects rendering times altogether:

http://forums.creativecow.net/thread/24/941866

Very informative post, check it out if you're experiencing related problems.

PS: Somehow the dynamic RAM preview problem only bugs me when I'm upscaling (NTSC) DV material to 1920x1080 MXF @ 24 FPS. Rendering all kinds of other video material is not an issue. I hope I don't have to do guesswork in the future whether or not to enable dynamic RAM preview and to what amounts.
musicvid10 wrote on 5/22/2013, 10:11 PM
A bit off topic, but I am at a loss -- why are you upscaling SD to 1080p, and NTSC to IVTC?
ReceptorDeceptor wrote on 11/10/2013, 1:32 PM
It was for a 1080p BD-project, you actually get a bit better video quality in the end by upscaling to HD resolution, as long as it's done properly. The frame rate change was because it was intended to have a film-like appearance - the main project consisted of multicamera material (coming from both SD and HD sources) which was edited in/to 1080p IVTC.

http://forums.creativecow.net/thread/24/955774