Vegas 10 Sony AVC Encoder Bug

amendegw wrote on 10/15/2010, 1:53 PM

Okay, folks I'm busy finding bugs. Luckily, none seem to be too serious. Can others reproduce this bug? If so, I'll file an incident report.

1) Open Vegas 10.0a
2) File -> New
3) Click the "Match Media Settings" icon. Navigate to a 30fps (not 29.97) fps .MOV clip. Click "OK"
4) Drag a 30fps .MOV clip to the timeline
5) File -> Render As
6) Select the Sony AVC encoder.
7) Select the Internet 16:9 1280x720-30p Template.
8) Click "Custom"
9) Change "Frame Rate" from "29.970 (NTSC)" to "30.000" and click "OK"
10) Click "Save" to render the project.
11) Vegas reports an undetermined error.
.
If someone needs a 30fps .MOV clip to duplicate this problem. Right click here, and "save target as". It's a clip created from my Canon SD960 IS. However, I would be interested 30fps clips created in other cameras also create the problem.

This test was done in Vegas 10.0a, 32bit & I have Quicktime 7.6 Installed.

This same scenario results in a good render using the MainConcept encoder. Furthermore, this test reported no errors using Vegas 9.0e.

...Jerry

Comments

LoTN wrote on 10/15/2010, 3:01 PM

Same here.

R0cky wrote on 6/20/2011, 10:33 AM

What about 1280x720-50p? I try to render to that (it's a legal bluray format) and I get the unspecified error message. Anyone else? The MC AVC encoder does fine with the same render settings though it is incredibly slow.

rocky

amendegw wrote on 6/20/2011, 10:57 AM

I can't help you re: the 50p question, but since this thread has been resurrected, I thought I would add the documentation this was submitted to SCS first on 10-15-2010 (10.0a) and resubmitted on 01-04-2011 (10.0c). Both were acknowledged as a "bug".

...Jerry

Christian de Godzinsky wrote on 6/20/2011, 11:33 AM

Worrying to see that SCS considers the keyframe timeline bug as "solved" - among the others, even if not! The keyframe bug just bit me badly (in VP10d) that you also have on your list of "solved questions"...

Christian

amendegw wrote on 6/20/2011, 11:51 AM

Christian,

I think we're talking about two different bugs. I believe the one I reported has, indeed, been solved. Click HERE.

...Jerry

Christian de Godzinsky wrote on 6/20/2011, 12:14 PM

Hi Jerry,

OK, thanks for pointing that out, I'm referring to something else. HOWEVER, the annoying bug shown in the video clip IS STILL THERE in VP10d!!! I can see the same behaviour, the timeline marker moving into the FX track headers, and area where it should not go. The timeline should scroll sideways - automatically if you do that, but it does not!. Something is really broken here.

So we have at least TWO keyframe related bugs that needs to be fixed! They even might be somehow related. Frustrating.... especially when some basic functionality gets s*****d up that worked OK before...

Christian

amendegw wrote on 6/20/2011, 12:34 PM

"HOWEVER, the annoying bug shown in the video clip IS STILL THERE in VP10d!!! I can see the same behaviour, the timeline marker moving into the FX track headers, and area where it should not go."Very, Very strange, because it appears fixed in my 10.0d 64bit. Can we get some other testers here? Edit: Just so there's no confusion, can others duplicate the following problem in 10.0d? Click HERE.

...Jerry

Christian de Godzinsky wrote on 6/20/2011, 1:03 PM

Hi again,

OK, sorry for the unintentional confusion, the timeline marker cannot be anymore dragged into the FX label area. My apologies. However you can still drag -select into that region, see pic below:

If I continue to drag to the left, I can continue dragging outside the window, the light blue active region clips correctly at the window border, but the time value continue to decrease as far as I drag into the desktop. I can do the same thing dragging to the right. I can drag as far as there is desktop space and the time field increases as far as I can drag... I can barely accept that this is intentional behaviour?

And my humble opinion is that if I have "Sync Cursor to Media Timeline" -button activated, the timeline in the FX window should scroll accordingly... that would at least be very handy... SCS needs to work still on this, in addition to the keyframe display update problem...

Christian

johnmeyer wrote on 6/20/2011, 3:20 PM

Wow, did this thread ever get hijacked!! The keyframe issue has nothing whatsoever to do with AVC encoding. It would be helpful to keep the discussion of this issue in the other thread.

FWIW, I can reproduce the keyframe problem in 10.0a. However, since it sounds like it has been fixed in 10.0d, why spam other people's threads and continue to talk about it?

amendegw wrote on 6/20/2011, 3:32 PM

Ha! I guess I contributed to the hijack of my own thread. I think what really got lost in the shuffle was bastinado's question posted this morning (which is not off topic):

"What about 1280x720-50p? I try to render to that (it's a legal bluray format) and I get the unspecified error message. Anyone else? The MC AVC encoder does fine with the same render settings though it is incredibly slow."

I don't have an answer to this, but hopefully others can help him.

...Jerry

johnmeyer wrote on 6/20/2011, 5:51 PM

"What about 1280x720-50p? I try to render to that (it's a legal bluray format) and I get the unspecified error message. Anyone else? The MC AVC encoder does fine with the same render settings though it is incredibly slow."I didn't see any preset for this, but I created the following one for the Sony AVC encoder. I put some HDV on the timeline and then rendered in 10.0a and it worked fine. Of course I was using 29.97 interlaced (60i) as the source rather than 50i or 50p, so perhaps that makes a difference.

[edit] I just looked at the original post again and noted that the source file was and MOV file. I am always suspicious of anything that uses QuickTime, and I assume that some form of QuickTime must be installed for Vegas to read this file. One test would be to render this to an intermediate (Cineform, MXF, Lagarith, HuffYUV, or uncompressed) and then render that to Sony AVC.

Robert Johnston wrote on 6/20/2011, 10:46 PM

I get the error if I use 50 fps. No error if I use 59.94 fps.

Marco. wrote on 6/21/2011, 12:20 AM

When rendering to 720p50 which data rate did you use? The error might occur because of exceeding a certain data rate limit.

Robert Johnston wrote on 6/21/2011, 12:52 AM

I tried various data rates down to 768,000. Tried different profiles, all worked with 59.94 fps.

What worked with 50 fps was the MVC format, which I read is backwards compatible with h.264/AVC. With MVC, you can get an elementary video stream in a .avc file. You could render an ac3 audio file in a separate render. Then mux the avc and ac3 with tsMuxer to an m2ts.

My source video, BTW, was from a Kodak PlayTouch (Zi10). 720P60. AVC/AAC MP4.

R0cky wrote on 6/21/2011, 8:54 AM

I was starting with a 1280x720-25p h.264/mp4 and rendering to 10 Mbps 1280x720-50p when I got the error.
rocky