Known and repeatable "issues" in VP9.0b

Christian de Godzinsky wrote on 10/21/2009, 12:34 PM

Hi,

I think its finally time to gather together our experiences, and to create an unofficial list of known and repeatable bugs, still left in 9.0b. In both 32 bit and 64 bit versions.

This has hopefully a dual function; we help SCS to check that their known-bugs-list is up-to-date. Wealso help other serious VP users from unnecessary banging their heads or pulling some hair, by preventing struggles with known issues.

PLEASE - PLEASE, follow these rules: (to keep this thread clean)

1. Give every new issue an new running number (double check that it isreally NEW on this list, and does not exist from before)
2. Do NOT post if you are the only one with this problem (check other threads for other people's similar experiences - then post here)
3. Use a descriptive and short name for the bug
4. Add a short but clear explanation about the circumstances it occurs
5. Please, please - stay on topic, no ranting, no venting, just pure facts
6. Update your system info page and keep the system info there, unless you need to emphasize some technical details
7. You might add also a known work-around, as long as you keep it short and consistent.
8. Follow strictly rules 1 to 8 ;)

I start:

====== LIST OF KNOWN REPEATABLE "ISSUES" WITH VP9.0b (for both 32 and 64 bit versions) ===============

1) The HDV-capture scene detection is still broken (at least since version V7). At the end of each clip there sound might be missing for a coulpe of frames. The video split points are either not correct, there might be at the end of the clip a frame that belongs to the following scene. The only known workaround is not to usethe scene detection, or then use a thid party capture application (like HDVSplit). VP9.0c release finally deserves a FIX!

Christian

PS: I started this thread because I relally like VP very much, and want it to become even better. We, the end users, should have the best experience and most editing hours, so sounding off is important.

EDIT: A good start -thx for the "contributions" so far. Anyone else?

Comments

amendegw wrote on 10/21/2009, 3:40 PM

2) Creating Custom Templates for MainConcept AVC/AAC revert to 192,000bps (video), 6,000 bps (audio) If you create and save a custom template under "MainConcept AVC/AAC", specify a constant bit rate. Then when you reopen the template, the bitrates revert to the minimum values (i.e. 192kbps & 6kbps).

I've reported this to Sony and they have acknowledged that it is a bug and will be fixed.

...Jerry

rs170a wrote on 10/21/2009, 3:46 PM

3) Custom Render presets not showing up.
I have several custom render presets, some created as far back as Vegas 6, that refuse to show up in Pro 9.
For example (Pro 8 vs. Pro 9), MPEG-2 (20 vs. 9), MainConcept AVC/AAC (5 vs. 1), QuickTime (3 vs. 0), and WMV (5 vs. 0).
The only format where all presets were carried over was AVI (14 vs. 14).

Mike

ushere wrote on 10/21/2009, 8:56 PM

4) chromakey selection tool doesn't drag visible rectangle

it's been noted before, (even before 9b), but didn't get fixed.

leslie

Christian de Godzinsky wrote on 10/25/2009, 11:30 AM

Hi,

Thx for your contributions so far. There must be more - so please let them flow in... Here is a abbreviated list of the issues so far:

1) The HDV-capture scene detection is still broken (at least since version V7). At the end of each clip there sound might be missing for a coulpe of frames. The video split points are either not correct, there might be at the end of the clip a frame that belongs to the following scene.

2) Creating Custom Templates for MainConcept AVC/AAC revert to 192,000bps (video), 6,000 bps (audio) If you create and save a custom template under "MainConcept AVC/AAC", specify a constant bit rate. Then when you reopen the template, the bitrates revert to the minimum values (i.e. 192kbps & 6kbps).

3) Custom Render presets not showing up. Custom render presets, some created as far back as Vegas 6, refuse to show up in Pro 9.
For example (Pro 8 vs. Pro 9), MPEG-2 (20 vs. 9), MainConcept AVC/AAC (5 vs. 1), QuickTime (3 vs. 0), and WMV (5 vs. 0).
The only format where all presets were carried over was AVI (14 vs. 14).

4) Chromakey selection tool doesn't drag visible rectangle it's been noted before, (even before 9b), but didn't get fixed.

Lou van Wijhe wrote on 10/25/2009, 12:18 PM

5) Files rendered in Pro 9 with Sony AVC cause a buffer underflow error in DVDA. This didn't happen in Pro 8.

Zulqar-Cheema wrote on 10/25/2009, 4:07 PM

6)

when customising keyboard...

select "Ignore event grouping"
pick a new key, " ` " the one to the left of the 1 above the TAB key (UK kbd)
save and SV9a,b 32bit crashes,V8 was fine

Marc S wrote on 10/25/2009, 5:48 PM

7) Save As > Copy media with project > Create trimmed copies of source media = no longer works with HD avis in Vegas 9.

This works perfectly in Vegas 8. Others have reported the same problem but Sony has not ackowledged it to be a problem.

Sebaz wrote on 10/25/2009, 6:32 PM

This is all for the 64 bit version, since I don't think I tried the 32 bit version. Still, in this day and age, a 32 bit version of Vegas doesn't make much sense. Memory is rather cheap, and you don't have to break the piggy bank to get a decent Quad Core CPU. So for me to pay for a new Vegas, it has to be the 64 bit version or nothing.

8) Vegas 9 has had from the first release a bug in AVCHD playback. Most times you hit play on the timeline the footage starts playing at stuttery slow speed and it takes 3 to 5 seconds to speed up to normal speed. That makes it unbearable to edit. Vegas 8 doesn't have this problem, and never had.

9) 64 bit Vegas 9 has the same bugs as 8.1, one being that many times you open the program and when it loads the last project an error pops up saying that the source files can't be found. You have to close Vegas, open it back, and reload the project for it to see the files, which were not moved anywhere in the first place.

10) Other bug in 64 bit V9 carried from 8.1: if you do a pre-render to a module that has a different size than that of the project (say, to 720p to do a faster preview in a 1080i project), it will modify the project properties to the size of the pre-render module, something that doesn't happen in Vegas 8.

11) If you are editing AVCHD 1080i and you pre-render to MPEG-2 1080i, it will only render the parts that have any filters or modifications added to it, but it won't render untouched footage, which is a problem because Vegas doesn't always play AVCHD at full speed even with quad core CPUs.

rs170a wrote on 10/25/2009, 6:38 PM

7) Save As > Copy media with project > Create trimmed copies of source media = no longer works with HD avis in Vegas 9.

Not sure if this is applicable or not but the V9 Pro readme says:

In the Save As dialog, the Copy media with project radio button now copies only media files that are saved outside of the project folder; media files in folders below the project folder are no longer copied.

Mike

Marc S wrote on 10/25/2009, 11:20 PM

Hi Mike,

The problem I'm referring to is different. It happens when you try to make trimmed copies of the source media into a new folder. Works perfectly in V8. Is broken in V9.

wilvan wrote on 10/26/2009, 3:36 AM

Capture video in vista64 ( with or vegas9x32 or vegas9x64 ) writes random pieces files to Harddisk instead of 1 file .
Capturing same video on same system but with vista32 , works .

( same actually in vegas 8 and probably also 7 )

Lou van Wijhe wrote on 10/26/2009, 7:47 AM

Woelf,

Sony Vegas starts a new file whenever there is a frame drop. Couldn't this be the cause of what you have observed?

Lou

wilvan wrote on 10/26/2009, 1:01 PM

Lou , this post is meant for listing failures ( checked , double checked on multiple systems before posting ) .
(Working on workstations lots of power and vegas for about 4 years , never missed a frame with these monsters ,not even with the notebook running only vegas and dvdarch.)
We can discuss this in another post if U want