Just found another issue with highlight colors for the menus. I only tested the "Menu in Black" and the "Blue Rain" template. I chose "Text based, 4:3, Static", the HL colors are yellow for selection and red for playback.

The colors I get are different. It is Red for selection and some other very bright color for playback. I tried all my software players (PowerDVD, MPC-HC and VLC) and also my old and trusted Cyberhome standalone DVD player. The colors are the same with all the players.

This issue probably has been there for a while. I rarely use menus with A2D at all, so I never noticed it.

Cheers
manolito

//EDIT//
Did a couple more tests on this issue...
It doesn't matter which template I select, if I choose Static or Motion, 16:9 or 4:3, Text Based or Thumbnails in the Menu Layout window. The result is always the same: The selected colors for Selection and Play are ignored.

As usual I could not test if the subtitle colors have survived the fix for the menu highlight colors, but the menu colors sure do work correctly now. And the Preferred DS Codecs setup is translated now. Looks like a candidate for the next stable build to me.

BTW (even if it is a little late) a Happy New Year to all of you guys (and girls)...

Just a quick question about the mscomctl_reg.bat in the AVStoDVD\Lib folder for users of the noinstall version:

I noticed that you added a new version of this batch file which first checks if the OS is 32-bit or 64-bit and then unregisters/reregisters the OCX file in the appropriate folder. The older version of the batch file just blindly used the OCX file in the AVStoDVD\lib folder.

Could there be a conflict for users of the noinstall version if the VB runtimes have never been installed before? This would mean that the file MSCOMCTL.OCX would not be present neither in System32 nor in SysWOW64. So the batch file would fail unregistering/reregistering the file. Shouldn't the OCX file from the AVStoDVD\Lib folder first be copied to the appropriate system folder before trying to unregister/register it if it is not already present in this folder? So the batch file should look like this:

If you run the batch file without elevation, then the command to copy the ocx into the system folder will fail and the regsvr32 registration process will fail as well.

If you run the batch file elevated (run as admin), then regsrv32 is executed, but the command prompt will start from %windir%\System32 and the copy command will not work because you lose the starting folder info.

In the mscomctl.ocx section of the readme.txt file I have inserted the note to manually copy the mscomctl.ocx file to %syswindir%, then to run the mscomctl_reg.bat file

First of all the way to check if the current OS is 32-bit or 64- bit is a hack (which does work though...).

The reg key "HKLM\Hardware\Description\System\CentralProcessor\0" returns the hardware CPU properties, not the installed OS properties. I tested it under a 64-bit CPU with Win7-32bit installed, and yes, the reg entry does have "x86" in it. Having Win7-64bit installed under the same CPU there is no "x86" string in this reg key. So the routine does work, but it is not very clean.

And I also tested my modified "mscomctl_reg.bat" under Win7, and it did work without problems. Of course I always work under the main admin account, and one of the first things after installing Win7 is always to disable UAC. Double-Clicking the batch file in Explorer (after deleting the already present OCX file in the SysWOW64 folder) resulted in copying the OCX file from the A2D\Lib folder to SysWOW64 and registering it without any problems.

But of course other users will have set up their OS differently, and someone who prefers the noinstall version will most likely have the knowledge to get the mscomctl.ocx registered...

//EDIT//
I just noticed that my plugin versions you are hosting at SourceForge are getting a little old...
I do update the plugins regularly, and I started uploading them to VideoHelp because they do not delete the files after some time. I always publish the current link in this post:https://forum.doom9.org/showthread.p...58#post1814958

Maybe you could just publish the URL of this post at SourceForge. This way I would not have to nag you to update your SourceForge download page...

Now the alternative normalizing modes also work for MP2 and WAV output. The exception is the Upmix mode which only works for AC3 output. I suppose that 6-ch MP2 and WAV streams are illegal for DVD (not sure, but AVStoDVD allows upmixing only for AC3).

//EDIT//
Just checked Wikipedia for DVD specs, looks like 6-ch MP2 and 6-ch PCM audio streams are part of the DVD standard. But I can only start supporting it when AVStoDVD allows upmixing MP2 and WAV audio. It doesn't make much sense anyways...
//END EDIT//

Also fixed the FFmpeg command line parsing, it won't choke any more when there is another parameter in front of the input parameter.