AVStoDVD Support Thread

[_MrC_]

Yes, of course, 2.7.2



Bye

[davexnet]

Hi MrC,
I found something unexpected with 2.7.2 -
I added a movie, edit/title and looked at the video tab.
Video avg bitrate had been reduced to approx. 6400 (as is normal per the length of the movie).

However, I deselected "auto video setup" followed by "auto bitrate calculation" and the
"Video Avg Bitrate" immediately jumped to 8500, the "Higher Avg Bitrate" from the Preferences.

Never seen it do that before.

I normally do the above before I use trim, because I want to check the quality at the calculated bitrate.
thanks,
Dave

[_MrC_]

Dave, thanks for the reporting.

See if this hotfix solves the issue.



Bye

[davexnet]

Dave, thanks for the reporting.

See if this hotfix solves the issue.



Bye

That seems to have fixed it .
thanks you -
Dave

[JohnnyBob]

I haven't had a chance to look at the new version yet. Do I install it over the top or must I uninstall the prior version first? Naturally I want to keep all of my prior settings if possible. (Windows XP)

I'd also like to report (again) about a spontaneous change in the Advance Project Settings which happened during a conversion run with the prior AVStoDVD 2.7.1 version. I know that I definitely did not do this with an accidental mouse click nor a keyboard mishap. I didn't even have access to the main AVStoDVD window during the conversion, but then when it appeared afterwards this box was checked. Something must have done it automatically during the conversion process. I wasn't doing anything unusual, just converting an .avi as I've done many times before, which usually doesn't cause this to happen. My only clue is that it reported some kind of error during the audio conversion and asked me if I wanted to use a different backup process/program (or some such), to which I agreed (because I had no idea what was correct). Graphics below: AVS-settings, AVS-audioerror

[_MrC_]

@JohnnyBob

very very strange. Make sure that the Windows registry key HKEY_CURRENT_USER\Software\AVStoDVD\DefaultEditEncoderParams is set to 0.



Then open again AVStoDVD and verify that the option is unchecked.



Bye

[JohnnyBob]

Yes, that registry key is set to 0, but the box is still checked in the AVStoDVD window. Note that I still retain the original AVDtoDVD window from that conversion run, haven't closed/reopened it, etc.

P.S. Then... I closed the AVStoDVD window, reopened it, and that box remains checked. The registry key changed itself in the process, was then set to 1.

[_MrC_]

Ok, operation "tabula rasa":

1. Uninstall AVStoDVD
2. Delete the main registry key HKEY_CURRENT_USER\Software\AVStoDVD (if still present)
3. Reinstall AVStoDVD using the 2.7.2 installer



Bye

[JohnnyBob]

OK, I uninstalled AVStoDVD 2.7.1 with Revo Uninstaller (advanced mode) which also deleted that and another registry key. However it's not a complete/clean uninstall. Several of the subsidiary programs that were installed by the AVStoDVD 2.7.1 installer remain: AviSynth 2.5, ffdshow v1.2.4422 [2012-04-09], Haali Media Splitter, possibly others but that's all I can find offhand. Can I keep them and hopefully their settings? Or should they also be uninstalled before doing the 2.7.2 reinstall?

P.S.
I notice that the following registry keys also still remain:
HKEY_CLASSES_ROOT\Applications\AVStoDVD.exe
HKEY_CLASSES_ROOT\Applications\AVStoDVD.exe\shell\ open
HKEY_CLASSES_ROOT\Applications\AVStoDVD.exe\shell\ open\command
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Applets\Regedit
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\ComDlg32\OpenSaveMRU\exe
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileExts\.a2d\OpenWithList
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileExts\.avi\OpenWithList
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileExts\.IFO\OpenWithList
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileExts\.log\OpenWithList
HKEY_USERS\S-1-5-21-4051261723-1042136901-3048713622-1003\Software\Microsoft\Windows\CurrentVersion\Exp lorer\FileExts\.mkv\OpenWithList
HKEY_USERS\S-1-5-21-4051261723-1042136901-3048713622-1003\Software\Microsoft\Windows\CurrentVersion\Exp lorer\FileExts\.MOV\OpenWithList
HKEY_USERS\S-1-5-21-4051261723-1042136901-3048713622-1003\Software\Microsoft\Windows\CurrentVersion\Exp lorer\FileExts\.mp4\OpenWithList
HKEY_USERS\S-1-5-21-4051261723-1042136901-3048713622-1003\Software\Microsoft\Windows\CurrentVersion\Exp lorer\MenuOrder\Start Menu\Programs\AVStoDVD
HKEY_USERS\S-1-5-21-4051261723-1042136901-3048713622-1003\Software\Microsoft\Windows\CurrentVersion\Exp lorer\RunMRU
HKEY_USERS\S-1-5-21-4051261723-1042136901-3048713622-1003\Software\VFPlugin

Leave them, or what...?

[davexnet]

OK, I uninstalled AVStoDVD 2.7.1 with Revo Uninstaller (advanced mode) which also deleted that and another registry key. However it's not a complete/clean uninstall. Several of the subsidiary programs that were installed by the AVStoDVD 2.7.1 installer remain: AviSynth 2.5, ffdshow v1.2.4422 [2012-04-09], Haali Media Splitter, possibly others but that's all I can find offhand. Can I keep them and hopefully their settings? Or should they also be uninstalled before doing the 2.7.2 reinstall?

P.S.
I notice that the following registry keys also still remain:
HKEY_CLASSES_ROOT\Applications\AVStoDVD.exe
HKEY_CLASSES_ROOT\Applications\AVStoDVD.exe\shell\ open
HKEY_CLASSES_ROOT\Applications\AVStoDVD.exe\shell\ open\command
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Applets\Regedit
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\ComDlg32\OpenSaveMRU\exe
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileExts\.a2d\OpenWithList
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileExts\.avi\OpenWithList
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileExts\.IFO\OpenWithList
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\FileExts\.log\OpenWithList
HKEY_USERS\S-1-5-21-4051261723-1042136901-3048713622-1003\Software\Microsoft\Windows\CurrentVersion\Exp lorer\FileExts\.mkv\OpenWithList
HKEY_USERS\S-1-5-21-4051261723-1042136901-3048713622-1003\Software\Microsoft\Windows\CurrentVersion\Exp lorer\FileExts\.MOV\OpenWithList
HKEY_USERS\S-1-5-21-4051261723-1042136901-3048713622-1003\Software\Microsoft\Windows\CurrentVersion\Exp lorer\FileExts\.mp4\OpenWithList
HKEY_USERS\S-1-5-21-4051261723-1042136901-3048713622-1003\Software\Microsoft\Windows\CurrentVersion\Exp lorer\MenuOrder\Start Menu\Programs\AVStoDVD
HKEY_USERS\S-1-5-21-4051261723-1042136901-3048713622-1003\Software\Microsoft\Windows\CurrentVersion\Exp lorer\RunMRU
HKEY_USERS\S-1-5-21-4051261723-1042136901-3048713622-1003\Software\VFPlugin

Leave them, or what...?

It's safe to leave them, will not interfere with any re-installation.
Those other apps you mentioned, FFDshow,etc,etc. All have there own uninstallers in
control panel/add remove programs (as does AVStoDVD itself)

[JohnnyBob]

I'm still hesitating because the AVStoDVD 2.7.2 installer provides a later version of ffdshow, but doesn't detect/offer to update the older version from my prior installation. So I'm wondering if I should uninstall the older ffdshow first, or check the box and install the new version on top of the old(?). I'll also need to do some research first to try to find any special settings which I might have made (but can't remember)...

P.S. researched and found my references/notes to the special settings required in ffdshow, so will uninstall it first as the cleanest way...

[davexnet]

Are you sure the installation doesn't respect the existing install of FFDSHOW? It always used to.
If it's true, uninstall the old FFDshow first - as you say, then install the A2D package.

[JohnnyBob]

Are you sure the installation doesn't respect the existing install of FFDSHOW? It always used to.
If it's true, uninstall the old FFDshow first - as you say, then install the A2D package.

Don't know what you mean by "respect"... Apparently it was going to leave the old version of ffdshow untouched, but I didn't try it. I decided to uninstall old ffdshow first, then the AVStoDVD installer installed the new version OK. The only trick for me was finding/remembering several custom settings I had made to ffdshow, so I could reenter them into the new version.

Seems to have gone OK. Hotflix applied too.

The only GUI differences I've noticed in 2.7.2 offhand are:
--the option to save a log file automatically disappeared from Preferences > Misc
--my custom path for Menu Templates won't stick and always reverts to the default location on C-drive

Haven't tried a conversion with 2.7.2 yet...

[davexnet]

"respect" means pretty much how you described it. It means it doesn't blindly overwrite it,
but asks you what you want to do or just ignores it and moves onto the next thing.

Your custom setting for paths doesn't stick? Did you remember to select the "save settings as default"
in the lower part of the preferences box?

I'm not sure if the the new FFDshow offers anything particularly relevant to us or not.
I'm still using the older version (1244 ?) myself.

[JohnnyBob]

...Your custom setting for paths doesn't stick? Did you remember to select the "save settings as default" in the lower part of the preferences box? ...

Yes, of course. The Menu Templates path will not stick, reverts to default location on C-drive. The other paths stick OK.

[_MrC_]

1.3.4500 ffdshow release note from official download page:

This is a small update to the 1.2.4422 release. The Intel QuickSync decoder has been updated and a few subtitle bugs have been fixed.

No big impacts on AVStoDVD.

@JohnnyBob

you are right, the Menu Template path customization is broken. Have to fix it. What about the 'Edit Encoders Command' issue?



Bye

[JohnnyBob]

I've only run 1 conversion with the new AVStoDVD v2.7.2 so far, a .mkv conversion, and the "Edit Encoder Command Parameters at runtime" checkbox was *not* checked afterwards. That anomaly has only happened about 1 time per 10 conversions in the past so might be difficult to troubleshoot.

My only hunch comes from playing around with the main AVStoDVD window and clicking various places with the mouse, I notice a possible GUI graphics involvement. That checkbox can be selected by clicking anywhere along that line to the right, within the area approximately enclosed in the red rectangle (see picture below). It would be more precise to limit the active clickable area to be within the checkbox's xy coordinate perimeters, a much smaller area.

[Seeker47]

@JohnnyBob,
You could always try the "No Install" (i.e., portable) edition: No Registry keys should be involved there, just make a desktop shortcut for it, and off to the races. Nothing to uninstall, either. That's pretty much all I've been running since something like v. 267, and I have not noticed any significant UI issues, or diminution of the job results. And anything that was glitch-laden with the installed versions (some MKVs that were stuffed certain ways, some AVC encoded things, certain sub files) remained as before.

@_MrC_,
You never commented to my query, "Is there any downside to going with the portable versions ?" If there are, I haven't really noticed them.

[_MrC_]

@JohnnyBob

ok, I will reduce the clickable area

@Seeker47

the differences between the "Installer" package and the "NoInstall" are that "NoInstall" does not have:

- installer routine
- AviSynth
- ffdshow
- Haali Media Splitter
- Visual Basic runtime libraries

everything else is the same, included the registry key usage. Take note that the "NoInstall" package is not called "Portable" because it does not 100% fullfill the "Portable" specs.



Bye

[Seeker47]

@Seeker47

the differences between the "Installer" package and the "NoInstall" are that "NoInstall" does not have:

- installer routine
- AviSynth
- ffdshow
- Haali Media Splitter
- Visual Basic runtime libraries

everything else is the same, included the registry key usage. Take note that the "NoInstall" package is not called "Portable" because it does not 100% fullfill the "Portable" specs.

O.K., but isn't AVS still making use of those items if they are present elsewhere on your system ? Otherwise, it's odd then that I had not noticed a difference in terms of basic functionality.
Any reason you could not have the latter four items be part of the NoInstall package, getting it much closer to truly portable status ?

[davexnet]

Portable means the program runs right out of its folder, no Windows installation necessary.
This is not possible for everything, some programs (such as the four you mention) need to be installed
since Windows sets the files in their correct locations, and creates the necessary registry entries
so they work, etc,etc. Because of this "setup" dependency, they can never be "portable".

This is more Windows 101 than anything to do with those specific programs.

[NoCode2112]

I've had AVSToDVD on my old computer for a a few years, but just got a new computer and installed it on this one. But for some reason the last two Output options, ISO UDF Image and Burn DVD, are both grayed out. I've tried Google searches, figuring it was some simple Options thing I needed to do, or that maybe newer versions of AVSToDVD require you to pay for the program in order to actually burn a DVD. But I didn't find anything. I've been looking around in the program trying to find some way to fix it, and no luck there either. Maybe I'm missing something. I've uninstalled and reinstalled all components several times, with the same result. Thanks in advance for any help I can get.

[davexnet]

I've had AVSToDVD on my old computer for a a few years, but just got a new computer and installed it on this one. But for some reason the last two Output options, ISO UDF Image and Burn DVD, are both grayed out. I've tried Google searches, figuring it was some simple Options thing I needed to do, or that maybe newer versions of AVSToDVD require you to pay for the program in order to actually burn a DVD. But I didn't find anything. I've been looking around in the program trying to find some way to fix it, and no luck there either. Maybe I'm missing something. I've uninstalled and reinstalled all components several times, with the same result. Thanks in advance for any help I can get.

The program uses IMGBURN, you may need to install it manually.

[NoCode2112]

The program uses IMGBURN, you may need to install it manually.

I'll try that. Because it looks like I don't have that program on my computer. I didn't install anything manually the first time I did on my last computer, so I assumed all components were included. Maybe it was already on my last computer or something.

[NoCode2112]

OK, that did do it davexnet. Appreciate your help sir.

[davexnet]

OK, that did do it davexnet. Appreciate your help sir.

You're welcome.

[Seeker47]

Portable means the program runs right out of its folder, no Windows installation necessary.
This is not possible for everything, some programs (such as the four you mention) need to be installed
since Windows sets the files in their correct locations, and creates the necessary registry entries
so they work, etc,etc. Because of this "setup" dependency, they can never be "portable".

This is more Windows 101 than anything to do with those specific programs.

I've seen some portable programs that make use of "pseudo" Registry entries (within the portable app's own tree structure) that engage at runtime and seem to fake out the requirement for this. And they run just fine -- from a thumbdrive, etc. Even where the thumbdrive boots up a Bart PE type of environment.

[davexnet]

Portable means the program runs right out of its folder, no Windows installation necessary.
This is not possible for everything, some programs (such as the four you mention) need to be installed
since Windows sets the files in their correct locations, and creates the necessary registry entries
so they work, etc,etc. Because of this "setup" dependency, they can never be "portable".

This is more Windows 101 than anything to do with those specific programs.

I've seen some portable programs that make use of "pseudo" Registry entries (within the portable app's own tree structure) that engage at runtime and seem to fake out the requirement for this. And they run just fine -- from a thumbdrive, etc. Even where the thumbdrive boots up a Bart PE type of environment.

You may be right - but then wouldn't you have to contact the authors of FFDshow, Haali, etc,etc in order
for them to create, let alone consider such a version? MrC certainly has control over his own access to the registry,
but in respect to his program only.

[Seeker47]

I've seen some portable programs that make use of "pseudo" Registry entries (within the portable app's own tree structure) that engage at runtime and seem to fake out the requirement for this. And they run just fine -- from a thumbdrive, etc. Even where the thumbdrive boots up a Bart PE type of environment.

You may be right - but then wouldn't you have to contact the authors of FFDshow, Haali, etc,etc in order for them to create, let alone consider such a version? MrC certainly has control over his own access to the registry, but in respect to his program only.

Yes, good point.

[wingfan]

How come static menu (just a picture background) does not work for me? Tried jpg any size really .. same issues. NO menu. Yet motion menu (with video file) works fine!