Bug in Custom Template for AVC/ACC

jej wrote on 10/4/2009, 7:32 AM

it appears to be a graphic bug...

attempt to render an mp4 (Mainconcept AV/AAC) file from the timeline. On the audio tab choose something other than 6,000 Bit rate (bps), move to another tab and then back to the audio tab.

For some reason on my system it reverts back to 6,000; however if I press OK in the description box it says Audio: 256Kbps the choice I'd made....

so I don't believe this is critical, just an annoyance,

Comments

obliterated wrote on 10/22/2009, 7:26 PM

I heva the same thing on both my machines (laptop for on-the-fly work and my main workstation at home).

Regardless of what it says in the description box, it sounds like the audion's only getting a 6K bit rate, as there're all kinds of audio artefacts introduced when I render without first going in and adjusting it up from the 6K. I usually run about a 96K bit rate with a 44K sample rate and that gives acceptable results for online use. (obviously that's far too low for offline, high quality use - something like 2.1M would be more appropriate for a stereo soundtrack sampled a 44.1K/24bit, but that's just way too heavy for online.

amendegw wrote on 10/23/2009, 3:38 AM

I reported this bug to Sony (note: the problem also occurs when setting the Constant Bit Rate under the video tab - reverts to 192,000). Here's their response:

Incident: 091015-000056
"Thank you for contacting Sony Creative Software. Our Development team has identified this functionality as a bug at this time and are currently working on providing a resolution at this time. We anticipate a fix for this functionality in an upcoming release of the Vegas Pro software."

...Jerry

1marcus4 wrote on 11/6/2009, 10:55 AM

Just to confirm this doesn't appear to be fixed with v9.0c. Whatever I do I can't render using the CONSTANT BITRATE setting with the MainConcept AVC/AAC option. I have to use the Sony option if I require CBR.

Also, when using the VARIABLE BITRATE setting with the MainConcept AVC/AAC option the QT Player 'seek' function's response time is ridiculously slow and unusable. I understand this was not true in v9.0b.

Mark

amendegw wrote on 11/6/2009, 11:16 AM

Yeah, it looks like they fixed the problem with the audio bit rate, but not the video bit rate.

...Jerry

amendegw wrote on 11/21/2009, 8:16 AM

Okay, as I mentioned in an earlier post, Sony seemed to acknowledge this problem and promised it would be fixed in 9.0c. That didn't happen. Maybe they didn't understand my description. So, I've put together a Hypercam presentation to document exactly what the problem is. I think this is about as clear as I can document the problem. So, I thought I'd give this forum a shot at it, before I re-opened my problem report with a link to this URL (obviously better watched FullScreen & HD).

...Jerry

Edit: Maybe I should mention, the rendered output is, indeed, 6Mbps, despite the indicated 192,000 bps.

Andy_L wrote on 11/21/2009, 4:54 PM

I applaud your effort. I wish SCS put in as much time actually fixing the problem!