View Full Version : Vegas Pro 12 (all builds) MPEG encoding bug


Juris Lielpeteris
February 2nd, 2013, 02:40 AM
Take care, Vegas 12 have MPEG HD for Blu-ray encoding bug!
Original SMPTE Bars (NTSC):
http://s017.radikal.ru/i413/1302/02/4165e0df2a88.jpg
Encoded in Blu-ray 1920x1080-60i, 25 Mbps video stream
http://s05.radikal.ru/i178/1302/17/f5a3123a6e24.jpg
Encoding in PAL gives the same picture
Encoding in XDCAM HD 422 or XDCAM EX looks fine
Encoding with older versions of Vegas also looks fine.

Christopher Young
February 3rd, 2013, 12:39 AM
Agreed! Seeing same problem her in PAL BD render. Have you filed a bug report with Sony?

Chris Young
CYV Productions
Sydney

Juris Lielpeteris
February 3rd, 2013, 05:53 AM
Not yet, this month I am installing some workstations with Vegas Pro 12 in Latvian TV.

Eric Olson
February 3rd, 2013, 07:31 PM
Not yet, this month I am installing some workstations with Vegas Pro 12 in Latvian TV.

Does the bug go away in 32-bit float mode? In 8-bit mode, all conversions between computer RGB and studio RGB levels need to be explicitly specified. This appears to be a design decision made because of the limited dynamic range of any type of 8-bit image processing. Try inserting Sony Levels somewhere in your Video Output FX filter chain and select either the Computer RGB to Studio RGB preset or the Studio RGB to Computer RGB preset as appropriate.

Juris Lielpeteris
February 3rd, 2013, 08:07 PM
Does the bug go away in 32-bit float mode?Bug is exactly the same in 32-bit floating point video levels mode and similar in 32 bit full range mode. I never use Computer RGB levels, because they are not compatible with broadcast standards.

Eric Olson
February 3rd, 2013, 10:41 PM
Bug is exactly the same in 32-bit floating point video levels mode and similar in 32 bit full range mode. I never use Computer RGB levels, because they are not compatible with broadcast standards.

Looking at the images again, I see that the white and black levels are okay, so never mind my suggestion about swing levels. The errors in the colors seem too big to be simply quantization errors. Maybe this is the result a Rec601 versus Rec709 mixup.

Juris Lielpeteris
February 26th, 2013, 03:19 PM
I got a reply from the SCS, but unfortunately without a solution, just a recommendation to check whether I really have installed the latest version of Vegas Pro...

Juris Lielpeteris
March 4th, 2013, 03:13 PM
Long-term correspondence with SCS continues to provide no improvement.

Gerald Webb
March 5th, 2013, 04:13 AM
Juris,
Do you really, really have the latest version installed. Have you checked again? lol.
Sorry, have to laugh, tech support at its best.

Juris Lielpeteris
March 5th, 2013, 10:53 AM
Since 2002, I am a registered user of SonicFoundry Vegas (v3.0), but so far I have never had need to use the help from the SCS support. However, I know how to find find the About screen :D

Juris Lielpeteris
March 18th, 2013, 07:33 AM
SCS acknowledged that the problem exists:
This is now listed in the known issue database to be resolved in a future application update. Thank you for reporting this issue.

Juris Lielpeteris
July 24th, 2013, 07:26 AM
The bug is fixed in a build 670 :)
Fixed a bug when rendering MainConcept MPEG-2 files that caused YUV color values from the source file to be changed in the rendered file.

Christopher Young
July 25th, 2013, 10:49 AM
Thx for the heads-up Juris. It took them some time though!

Chris Young
CYV Productions
Sydney