To: Vlad
Thanks for your reply....but I think I've discovered what the cause of the problem is.
Shame on me....this is what happens when I try to run your latest version on a slightly underpowered system. When I first bought the AVS Video Editor in 2009, my hardware exceeded its requirements. Now that I've uploaded your latest version, my system's hardware is slightly less than optimum. In my recent project, I apparently jumped the gun, and clicked on the "Create Movie" button before the menu creation routine of the program had finished running (the rotating icon on the preview screen was still present). This evidently resulted in an empty menu file being created. When I repeated the process, this time waiting until the menu had completely finished being created, everything worked fine.
Here's just a thought....if the program's source code is modified to include a "check switch" that would prevent the Create Movie button from being activated until the Menu creation subroutine (or any other program subfunction) has completed execution, it would prevent the type of error that I encountered.
I know....maybe it would just be easier if I upgraded my hardware....and I will....when my budget allows.
As I stated, when I adopted my new methodology everything worked fine....except....(sorry)....
Now that I have a DVD with a working menu, I have noticed a few quirks --
The original camera discs were in the 16:9 format. In the program, the chapter thumbnail images are also shown in 16:9 format, but, on the output DVD, the chapter thumbnail images display in 4:3 squeezed ratio, as if viewing a 35mm anamorphic print.
Also, when using a 16:9 ratio image for the menu background, the program properly displays the entire contents of the picture. However, on the output DVD, the image is obviously "overscanned", and displays less than the complete image. I tested this on my high definition TV and DVD player with an HDMI connection, which I know, from experience with DVD calibration discs, will display the image out to the very last pixel -- no overscan.
Hopefully, these notes will help you in the next release....thanks for listening and your help!