AC3 audio on a Menu

MHampton wrote on 2/25/2003, 2:01 PM
Thought I'd try something for fun. I just did a project of a musical for my church and I thought it would be nice to have a running clip of music behind the main menu. In Vegas 4 I took 10 sec clips from each song and spliced them together putting a nice fade betweent them. I then rendered it as AC3 output so that DVDA wouldn't have to recompress the file.

Then when I went to create the DVD, DVDA complained that the menu was over 1gig in size! The ac3 file was only 3meg while the WAV file I created from the exact same project was 31meg, yet when I replaced the ac3 file with the wav file, DVDA quit complaining and created the DVD just fine, recompiling the WAV into AC3 for the DVD.

I know there is a bug with 16:9 video in DVDA, but I hadn't heard anything about this.

Comments

sms wrote on 2/25/2003, 3:13 PM
I received the 1 gig message on a project of mine but this is what happened. Some how the link I was using on that menu page was being counted twice. When I looked at the project with "optimize DVD" the size of menu page 3 was a little larger than the mpeg2 file that the menu linked to. I'm not sure how I made the mistake on the menu page but all I had to do was delete the link and create it again.
SonySDB wrote on 2/26/2003, 10:08 AM
This is a known issue that will be fixed in the next update. For now, there are two workarounds:

1. Don't use source audio in a menu that won't recompress. In the file Optimize DVD dialog, make sure there is no check mark beside the audio for the menu.

or;

2. Make sure the source thumbnail file for all links on the menu is shorter than the menu. The thumbnail can be set on the object properties page for each link. Ideally, set this to a still image (e.g. jpg). However, if you want an animated thumbnail use a thumbnail video that is shorter than or equal to the menu length.
Finatic wrote on 3/11/2003, 11:22 AM
Hello SF Tech,

Thanks for the response, I previously read that post but wasnt quite sure what to make of it.

as for issue 1, i am importing AC3 files rendered using the Vegas 4 AC3 5.1 Surround Template and that results in a huge file size. if i change it to just AC3 Stereo then the file reduces considerably but still seems rather large (130 meg from an original 13 meg file)

as for issue 2, i would prefer an animated thumbnail, how do i insure the thumbnail animation is shorter than the menu length? i see where i can determine where the animation begins but how do i make it stop after say 15-20 seconds.

i am rendering my project and the encoding times are huge! each menu page is taking over 5 hours to render, probably because the thumbnails are encoding from the start point of the animation to the end of the file, and with a 2 hour video i can see where that would result in a long render time.

otherwise i am extremely happy with Vegas 4 + DVD Architect, hats off to Sonic Foundry from this FORMER Premiere user. i attended the '02 WEVA EXPO and took the Intro to Vegas Video course and it changed how i look at editing and SO LONG PREMIERE!!! (and good riddance!)

Thanks for the forum support, I look forward to solving my problem.
SonySDB wrote on 3/11/2003, 12:08 PM
First, the problem is only with calculation of the menu size. This will not effect how long the actual render takes.

If the audio is being recompressed then, the menu size estimate should be correct. This is the easiest workaround to the problem.

I assume your original 13 MB file is the AC-3 audio file. But the menu size also includes the video. So, 130 MB sounds about right. You can reduce this by adjusting the video bitrate for the menu in the Optimize DVD dialog (File | Optimize DVD...).

To ensure the thumbnail animation is shorter than the menu length (i.e. the other workaround to the problem):

1. Determine the menu length. This can be found on the properties page of the menu.
2. Select the menu item
3. Go to the Object Properties page
4. Find the path to the thumbnail (under the label "Thumbnail")
5. Using the path, find and click on the file in the media explorer at the bottom of the app.
6. The video and audio properties for the file will be displayed in the media explorer. It will include the video length (i.e. length of the thumbnail source).
7. If the thumbnail source is longer than the menu length, then render a new thumbnail video in Vegas that is the length of the menu (using the original thumbnail as the source) and set it as the new thumbnail video.

Repeat for each menu item in the menu.
PeterWright wrote on 3/12/2003, 5:32 AM
SonicSDB, This concept of Menu length is something I'd like to get to grips with - there's no explanation I can find in the Manual, so could you either explain the idea or point me to some reading.

I suspect I'm wasting lots of space by not limiting either motion menus or background audio, but I'd like to find out how it all works, e.g. if the same video or audio is used more than once, does that double the space or can both instances reference the same file?

thanks for any clarification.

peter
SonySDB wrote on 3/12/2003, 8:21 AM
Menus, picture slideshows and audio compliations are not combined. However, videos (i.e. Insert | Media...) will only be added once for all instances that have the same source video and audio.

The best way to determine the space used by menus, videos, picture slideshows, and audio compliations is to go to the Optimize DVD dialog (File | Optimize DVD...). Each item in the "Individual media assets" list will only be added once to the DVD. Each item's estimated size on the DVD is also given. If you select a video in the "Individual media assets", the details will show how many times this video is referenced (i.e. number of instances) by the project.
Finatic wrote on 3/13/2003, 11:41 AM
I will agree that the DVD-A manual SUCKS, no details at all there. One can read that whole manual in a matter of minutes and still be no closer to a solution.

From what I can gather about adding AC3 audio for background sound in a menu is that your chapters are indexed on the main MPEG file and by adding the AC3 in the background each motion button then each motion button will encode itself from the chapter point to the end of the MPEG file.

The workaround as I understand it is, that instead of accepting the motion buttons that are created by the program itself, you get rid of those and make your own buttons with the length of the animated clip being dependent on the length of the background audio clip.

For example, if your project has 6 animated menu buttons with a background audio clip running 2min 30sec then you have to go back to Vegas 4 and make individual motion buttons that begin from the start of your chapter point and run for the same 2:30

This doesnt sound too encouraging though as I have a music project I am working on with that has a total of 7 menu pages with around 40 or so musical numbers, so I am now faced with the choice of either having to make 40 individual motion button clips or blow off motion buttons and have still frame buttons. I thought one of the benefits of DVD-A was the ease of use to make a motion button but that doesnt seem to be the case.

Am I way off base here SoFo Tech? I know whenever postings are made about AC3 audio on menu clips we are always directed back to a previous thread but even that is a bit confusing....

SonySDB wrote on 3/13/2003, 12:13 PM
The problem is the estimate size of a menu may be too large if (and only if) the audio for the menu is not being recompressed. Two workarounds to the problem are 1) make sure the audio for your menus is being recompressed OR 2) make sure your thumbnail videos are shorter than the menu length.

The reason this isn't talked about in the manual is because it's not expected behavior (i.e. a bug). This will be fixed in the update (i.e. no workaround necessary after the update).

In your situation, I'd suggest workaround #1 (or wait for the update).