Build 710 and 714 - bad rendering

Grazie wrote on 9/13/2013, 2:29 AM

What was the Framerate of your original footage.

Grazie

Jan Tkac wrote on 9/13/2013, 3:11 AM

Framerate is the same. It is footage from Nikon D800 set to PAL framerate.
Jan

Grazie wrote on 9/13/2013, 3:19 AM

OK, not 25fps, but I just used one of the CC Templates - Infrared - and rendered 23.976 > HD EX 1920x1080-24p (23.976) and I don't see a change in framerate.

Can you interrogate the Playback rate and see what that says. Mine mirrors the original.

So, in essence, you have 25fps from media thru' Settings > Template render, and all that's changed is the use of the FX. Try a quick experiment and render WITHOUT the FX. What does that give you?

I wondering if the GPU issue is raising its head . . . again?

Grazie

Jan Tkac wrote on 9/13/2013, 4:27 AM

I found source of my problems:
- rendering set to Only CPU generate bad video (in my case size is 51 MB)
- rendering set to Using CUDA generate corect video (size 46 MB)

Jan

Christian de Godzinsky wrote on 9/13/2013, 5:59 AM

Hi,

How come this is a solution? Ticking different options (mainly for render speed optimization) causes the softaware to produce crap output? Doesn't sound very convincing...

In this case - CPU-only produces bad video? This is really alarming. Are you sure? We all know that GPU rendering is still to a major extent dysfunctional - but CPU rendering also? Please check again, we neet to understand what you are experiencing...

Christian

dxdy wrote on 9/13/2013, 7:13 AM

Please run mediainfo on each of the renders ("good" and "bad") and post the results. I wonder if the "bad" one is running a high bitrate that your video player is stuttering on.

Edit - What are your computer specs? What GPU driver are you using?

Jan Tkac wrote on 9/13/2013, 11:23 AM

Hello,

You can see Notable fixes/changes in version 12.0 (Build 710) for many rendering changes:
-Added an Enable progressive download check box to the Video tab of the Sony AVC/AAC Custom Settings dialog to allow your videos to begin playing during download. This check box is available only when rendering to MP4 formats.
-Added support for rendering XAVC MXF and XAVC S MP4 files to a folder on your computer.
-Fixed a bug that could cause a crash when opening the Render As dialog after saving a custom rendering template.
-Fixed a bug that could cause a crash when rendering very large projects to AC-3, ATRAC, FLAC, MP3, and OggVorbis formats on some systems.
-Fixed a bug that could cause selective prerender to fail when rendering using some XDCAM EX templates.

I render video on my notebook HP Pavlion dv7: Intel CORE i7, 6GB RAM, NVIDIA GEFORCE 630M (2GB) Intel(R) HD Graphics 4000, Windows 8 Enterprise and on the actual drivers versions.

I prepared two video files that was rendered from Sony Vegas in a row without any manipulating. Bitrate was variable: Average = 12 Mbps and Max = 24 Mbps.

Documentation:

Bad video: https://dl.dropboxusercontent.com/u/72462364/TestWithoutCUDA.mp4
Correct video: https://dl.dropboxusercontent.com/u/72462364/TestWithCUDA.mp4
Rendering settings: https://dl.dropboxusercontent.com/u/72462364/VegasRenderSettings.png
Project settings: https://dl.dropboxusercontent.com/u/72462364/VegasProjectSettings.png
My computer and Vegas info: https://dl.dropboxusercontent.com/u/72462364/ComputerInfo.txt

Jan

set wrote on 9/14/2013, 1:10 PM

PAL D800 user here too, using VP12 build 714.

I try make an exact project settings and render them with similar MP4 (Mainconcept) render settings, GPU (AMD-ATI) and CPU only.

I found similar issue when having CPU only rendering.

I will post my rendered video soon.

set wrote on 9/14/2013, 6:13 PM

https://www.dropbox.com/sh/3wobnl4hndxmxmn/tQVoifk6E0

ChrisDolan (SCS) wrote on 10/3/2013, 12:01 PM

Vegas Pro 12 build 726 is now available which fixes this bug. Sorry for the delay, but it turned out to be complex under the hood. Here's a little bit of technical detail to help you decide whether you need 726.

The bug affects three areas of Vegas: MainConcept AVC render in CPU-only mode, upload to YouTube, and XAVC-S render. In all three cases, the cause is the same. We upgraded the AVC encoder which started reporting the wrong frame timestamps for B-frames. We missed that new error, and we're putting those incorrect timestamps in the MP4 frame index (the "ctts" box) in the file metadata, so during playback the frames are played in the wrong order. This is an encode bug, not a decode bug, so it affects all playback engines and not just Vegas.

This bug does not affect the MainConcept AVC GPU render (CUDA or OpenCL) because those are completely separate encoders that don't have the timestamp error. We put out this new build because there's no workaround for the bug for the YouTube case -- you can't select GPU mode in that case.

Our fix corrects the timestamp and thus the MP4 frame index.

Thanks to Jan Tkac for reporting this and thanks to "set" for the DropBox files that made the bug more obvious to us.

Former user wrote on 10/3/2013, 12:12 PM

Talk about serendipity...I just did a render this morning, and just for the heck of it, did a separate GPU/CPU render - no reason, just playing. Noticed the different file sizes and then came on and found this thread.

And thanks to Jan for finding the bug and solution, and to Chris for the best SCS support reply I've seen in a long time. It makes a huge difference to know not just what is happening, but why.

Best support community. Ever.

manishved wrote on 1/4/2014, 12:12 PM

I am trying to render a 2.5 hour 3d 1280x720/59.94p project using the Sony MVC/AVC encoder and have the same issue using vegas pro 770. Smaller sizes work fine. Spent over 4 days trying to resolve this issue.
I am on win7 64 bit