scene selection menu...strange...

mrAndress wrote on 2/23/2003, 5:35 PM
Hi,
I have an mpg-movie, size 237,5 MB, created in Vegas4. I have a "play"-option on my menu. Works fine.
I also have about 40 chapter points in this movie, imported from Vegas.
Total size for all material on this DVD is correctly reported as being 1.4 GB.

I right-click the movie and select "insert scene selection menu". It looks fine but it now reports total size to be 10.4 GB!
When checking "Optimize DVD" I can see 40 new instances of this mpeg-clip, each being 237,5 MB.

What is going on here. Plz help.

Comments

Clyde200 wrote on 2/23/2003, 6:12 PM
Hey ! Same thing here. Earlier today in fact. But the next time I tried (after a re-boot) everything was OK. Now If I could just get DVDA to not burn a coaster or write a burnable project OR write a file AT ALL I'd be happy.
jon_w wrote on 2/23/2003, 10:30 PM
I have the same problem and a reboot doesn't fix it.
I have one 2.4 gig mpg. I dragged that onto the main menu, then went in and added chapter points. When I added a schene selection menu item, the size of my output became 2.4 x the number of chapters I have (plus menu media.)
rstein wrote on 2/23/2003, 11:33 PM
I saw that too.

The thing that definitely broke it for me was using .AC3 audio on the menus. That's guaranteed to cause DVDA to overestimate your space needs and refuse to prepare.

DVDA is kind of picky and a bit flaky, but I have confidence that SF will get these anomalies cleaned up forthwith!

Bob.
SonySDB wrote on 2/24/2003, 8:36 AM
mrAndress, can you please check to make sure you're email address is correct (click on the "Edit Account" above)? I tried to send you an email, however, it returned as undeliverable. I'd like to take a look at your DVD-A project file. Hopefully, this will help us determine the cause of your problem.
SonySDB wrote on 2/24/2003, 8:46 AM
rstein,

What was the duration and estimated size of the menu before the audio was added? This can be determined in the Optimize DVD dialog (File | Optimize DVD...). What was the duration and estimated size of the menu after the audio was added?

If the length of the menu (i.e. duration) is increased, this will increase the length of the video that needs to be rendered.
jon_w wrote on 2/24/2003, 9:16 AM
I can send you mine if you want it SonicSDB, just give me an email address.
SonySDB wrote on 2/24/2003, 10:24 AM
After examining jon_w's project, we determined this is caused by not having any audio associated with the video. Currently, if your video doesn't have any audio associated with it, it is considered a separate media asset. This is a bug in our logic.

One workaround is to add a short audio file of silence to the video.

For example...
1. Render a short audio file of silence in Vegas
2. Delete the Scene Selection menu
3. Double click to enter the main video
4. Add the short audio file of silence as the audio in the Media Properties
5. Go back to menu
6. Select link to main video and choose Insert | Scene Selection Menu...
jon_w wrote on 2/24/2003, 10:30 AM
I did intend to have audio associated with my project, actually, I can't figure out where it went. The mpeg file I was working with was rendered from VV4. In VV4 there was an audio track. When I look at the mpeg in PowerDVD now there's no sound. I'll have to go back to VV4 and see if I can figure out why it didn't include my audio.

Thanks
Jon
SonySDB wrote on 2/24/2003, 10:35 AM
If you used the "DVD Architect NTSC video stream" template, it will only render the video (i.e. no audio). It is recommended that you render your audio separately as AC-3 or PCM (WAV, 48,000 Hz, 16bit, stereo).
rstein wrote on 2/24/2003, 10:52 AM
SonicSDB,

In my case, I had a small audio clip (a few seconds, really) that I rendered from the sound track of the main video. I rendered it as an .AC3, then put it on the menu as the audio loop. What was confusing, IIRC, is that on the optimization screen, it made it appear that the main video was being calculated twice, and thus DVDA would not prepare the DVD this way.

Rendering the audio clip for the menu to a .wav solved the problem. I think this is a known bug.

Bob.