I think everyone understands your concerns, but in all honesty, SCS is keeping mum about the bug link in the latest versions of VegasPro and DVDAPro.
Part of the reason for that is that several other and completely different serious bugs have appeared in DVDAPro 6 such that it is NOT to be recommended for any serious usage of creating discs.

videoITguy,

where are you getting this recommendation of not using if for serious work from?

I have not seen any official posting about this.

Dave T2

The controversy over DVDA Pro 6 is pretty much moot, if one is not burning "stereoscopic 3D video to Bluray disc."

In fact, that is the only production feature added to that release. Hardly worth the effort considering all the collateral damage being reported. With all the attention being devoted to other authoring solutions, is it possible that 6.0 is Sony's last DVDA release?

DaveT2, from other sources, I am aware that SCS maintains a known issue database- and AFAIK, this is is not available in any public way. What can be really frustrating from the point of accessibility, is we do not know truly how issues come to be posted in that database, and in fact what team at SCS authorizes it - the development team? maybe, or the help desk team ? who knows.

Let's bring on a safe hacker! I realize SCS is really trying to control the bad press, as they so handily had to do near the premature end of the last beta, but this is counterproductive.

I have no issue with full disclosure, but exactly would having access to an issue list do for you, or me, or anyone else.

It won't actually get something specific fixed. Not all issues get fixed. That is reality, for all major software. Everything gets classified and prioritized. Some things just stay down in the queue.

NormanPCN, I appreciate your remarks about all notes in the queue don't get attention - I also familiar with development teams am well aware of this modus operandi. The problem begins to really get ugly when you identify long-term (speaking 8-12 years) development cycles where problems identified early-on don't get fixed while tons of new bugs creep in with added feature sets later-on.

It would appear that problems do have a way of getting lost in the market shuffle forward. Would it not make sense that there be a place where the bug list can be identified and voted on /prioritized by the end user community ? Then if the development team is forced by business issues to go to some other direction, so be the fortunes of the company. I really don't trust the development team to do their own prioritizations behind closed doors without lots of user feedback.

I have also created both some s3D but also 2D projects with Vegas and the DVDA 6, and have not seen that issue yet. Maybe that means nothing, since it can take place with specific hardware/drivers only.

But in addition we have asked here for the official statement if there is one - and I understand that ther seems to be no public statement at all. Fine, even without a public statement there may be an issue.

Simply to write something about an hiden data-base, or bad press, will bring us nowhere. So I really would like to know in more detail with what type of footage, with what workflow this issue can be reproduced - and that is also something that a development team needs: without a repro they can do nothing.

A public feature change and feature request mechanism is good. Smugmug has something like this. You get 15 votes total and put up to three votes per item.

Nobody really publically lists bugs or quirks except open source projects and even then some get ignored. I have reported a couple of Chrome browser display bugs and a couple of years later the pages still don't display properly. I reported an issue with Adobe Bridge in CS5 and it's is still there in CS6. They obviously think it not serious enough to bother. I just avoid that feature.

Nobody is going to hand someone a club to beat them with. Hey, why have you not done something about item 53!

I am sure they (Sony) get plenty of feedback via support requests or by trolling forums. I have submitted a number of feature change requests. It is seriously frustrating to try and get past the support script BS we have to go through. And BS support in general. MBA middle managers are at fault for this, counting the beans to increase margins so they can say look at what I did, now give me a bonus.

As someone very new (1 month) to this video edit hobby for me, I have been spanked and frustrated by Vegas. Mostly GPU related, and entered 4 support issues.

1. Movie Studio 12, render crash with video prefs GPU on. Sony said cannot duplicate. I created a sample project for them to show this. They marked the issue as "Solved" and I bitched out that characterization. They can mark it as not reproducible, open, or whatever, but not solved.

2. Vegas lockout in playback. GPU video prefs on. Again I created a project, 900MB, in the hopes they can reproduce. Did some support BS script right now. I thought I pre-answered all script type try this responses in my initial post but I missed at least one.

3. After upgrading my video card. Main Concept AVC no longer thinks OpenCL is available. Always runs CPU only. Everything else OpenCL in Vegas and other app is fine. Not much hope here I think, since it is not Sony code. No response so far.

4. Titles & Text does not support OpenType fonts with postscript outlines. Legacy Text and ProType do support them. Probably not an implementation issue but rather a silly font enumeration bug. No response so far.

This big issue I have is that these product forums tend to be bitch sessions, and in the internet the squeaky wheel does not get grease. It gets ignored and can cast a shadow on all around it. It is hard enough to knock some sense into corporate support culture.

For those who doubt what the problem is:
http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=848749

Norman, thanks for stating it so clearly. I've learned to expect a lot less from Sony Vegas & a lot of BS on the forum. I think we've reached a dead end. All there is... is problems & features that should have already been fixed or implemented by now.

I come to these forums in hope that there are updates & promises to make Vegas faster & better, but it is the same, nothing as usual.

What they report here seems to be a bug in the luminance and/or color shift with the mpeg2 encoder, used to render with BD-templates. But then this is no bug in the DVDA - neither in DVDA6 or DVDA 5.2 - as I said in the beginning. It is a bug in Vegas then.

The workaround is simple at the moment: use the Sony AVC encoder if you need to render to a Blu-ray template. mpeg2 is outdated anyway. Or use the Mainconcept AVC encoder - it has also BD-templates now.

I would assime that this is something that SCS may correct in the next build of Vegas 12.

I arrived at this thread because I remembered there was supposed to be some bug with DVDA 6.0 compared with previous versions.

As Wolfgang said, the bug was actually in Vegas Pro 12. Allegedly is was fixed in V12 build 670.

Anyone know of other new bugs for 2D DVD or Blu-ray that weren't in DVDA versions 4.5 to 5.2? Hoping I can just have 6.0 on my new PC and not have to keep previous versions.

There was identified as a bug handling audio files when creating menus that require the audio to loop. I think the audio was PCM type, but do not know any more about it as it was identified long ago. For that matter it could have been handling a loop of audio in a 2D menu in a 3D disc, but again not sure.