AVStoDVD Support Thread

[Danette]

I’ve installed version 2.8.5 on my win 7 64-bit machine. Every attempt to open it results in the warning that mscomctl.ocx is not present or correctly registered. It is definitely present and seems to be registered correctly. I have also installed the visual basic 6.0 runtime libraries. Nothing works. Any ideas?

[manolito]

Could be an older version of mscomctl.ocx which was not unregistered. I found some posts at VideoHelp about this problem:

I moved the file MSCOMCTL.OCX to the Windows/system32 directory and that solved the problem.

Or this post:
http://forum.videohelp.com/threads/313451-BD-Rebuilder-MSCOMCTL-error?p=1949036&viewfull=1#post1949036

Good Luck
manolito

[Mister XY]

I have a small problem with videos in x265 format and chapters. AVS2DVD did not take the chapters from this video source. Under "view source title info" i see the chapter but the chapters did not take this chapters. If i have a x264 source, the chapters are correct.
I have tested it also with a self encodet x265 File. I have encode it in to x265 and also into x264. with x264 i have chapters and with x265 not. Strange

[Danette]

Nothing works:

1) Could be an older version of mscomctl.ocx which was not unregistered.

It is the most recent version (6.1.97.9786)

2) Although I did register the MSCOMCTL.OCX previously, I did so again after your suggestion.

3) Also tried moving the file from the sysWOW64 folder to the System 32 folder, but it is not possible, since the file exists in the sysWOW64 folder, Windows does not allow it to exist in the System 32 folder. As an example, when I move the file from the sysWOW64 folder to the desktop (and it then no longer exists in the sysWOW64 folder) and then try moving it to the System 32 folder, it automatically appears in the sysWOW64 folder and not the System 32 folder.

I’m beginning to wonder if recent Microsoft updates have rendered AVSTODVD useless, as I used a previous version successfully a year ago.

[manolito]

OK, I checked my notebook with Win7-64bit. Latest updates are installed.

I have mscomctl.ocx in my AVStoDVD\Lib folder and in my SysWow64 folder. It is not present in my System32 folder.

The version in the A2D\Lib folder is 6.1.98.34, the version in SysWow64 is 6.1.98.46.

The newer version from the SysWow64 folder is registered, and AVStoDVD 2.85 happily works with this version.


Your version 6.1.97.9786 is hopelessly outdated. I would recommend to unregister all versions first with the "regsvr32 /u" command. Then copy a newer version (the one from the Lib folder) into your SysWow64 folder and register it.


Cheers
manolito

[MrC]

@manolito

thanks for the test, comma bug report and for the updated german translation. Good Xmas gifts indeed! ;)
1.0427 is correct for 24->25 conversion
1.0417 is correct for 23.976 -> 25 conversion
probably noticeable only on very long tracks. Anyway I will fix it.

@Danette

definitively follow manolito's suggestion

@MisterXY

do you have the possibility to update the x265 file anywhere?

;)

Bye

[Mister XY]

@MrC did you mean that i must change my x265 files to x264 files? I got a workaround from user manolito but this is a little bit tricky. But can you also test x265 files with chapters?

[Danette]

Your version 6.1.97.9786 is hopelessly outdated. I would recommend to unregister all versions first with the "regsvr32 /u" command. Then copy a newer version (the one from the Lib folder) into your SysWow64 folder and register it

Thank you.

I had tried that but the installer did not install the MSCOMCTL.OCX file into the AVSTODVD Lib folder (I tried reinstalling several times), nor did it replace the old version in the SysWOW64 folder. I solved it by deleting the older MSCOMCTL.OCX file in SysWOW64 and then uninstalled and reinstalled AVSTODVD, which placed the newer MSCOMCTL.OCX file into both the SysWOW64 and AVSTODVD folders.

AVSTODVD works fine now.

[manolito]

1.0427 is correct for 24->25 conversion
1.0417 is correct for 23.976 -> 25 conversion


Are you sure?
I believe it is the other way around:
1.0417 is correct for 24->25 conversion
1.0427 is correct for 23.976 -> 25 conversion

But then again my math capabilities are limited, am I making a complete fool out of myself?


Whatever, a Happy New Year to everyone...
manolito

[MrC]

1.0417 is correct for 24->25 conversion
1.0427 is correct for 23.976 -> 25 conversion


100% correct

;)

Bye

[Danette]

In the spirit of an all-in-one approach to creating a DVD compliant video (in my case, from an MKV with an m2v stream), is it possible to add custom Avs script within AVStoDVD, such as can be done in software such as MeGUI for MP4? I know I can create a separate Avs output in an AVI and then run it through AVStoDVD, but then that’s an added step.

[Mister XY]

@MrC did you mean that i must change my x265 files to x264 files? I got a workaround from user manolito but this is a little bit tricky. But can you also test x265 files with chapters?

[manolito]

In the spirit of an all-in-one approach to creating a DVD compliant video (in my case, from an MKV with an m2v stream), is it possible to add custom Avs script within AVStoDVD, such as can be done in software such as MeGUI for MP4? I know I can create a separate Avs output in an AVI and then run it through AVStoDVD, but then that’s an added step.

Since AVStoDVD creates an individual input AVS script for every input file (without using a template which a user could modify) I do not see a way to add your custom AVS script without an additional step.

As I see it you can do it in two different ways:
1. Use an AVS script as your input for AVStoDVD. The script might look like this:
{My Source Filter}("{Full Path to the Input File}")
Crop(0,0, -Width % 4,-Height % 4)
ConvertToYV12()
{My custom Filter #1}
{My custom Filter #2}
{My custom Filter #3}

But you will have to edit the script for each different input file and enter the input filespec.


2. Create a template of your custom filters like this:
{My custom Filter #1}
{My custom Filter #2}
{My custom Filter #3}

Save this as an AVS file, then you must edit your script within AVStoDVD for every input file and add these lines right after the "ConvertToYV12()" command:
Last = Video
Import("My_Custom_Filters.avs")
Video = Last


A third way would be to write a wrapper plugin (like my ff_vbr plugin) which intercepts the encoder call and alters the input AVS script before executing the encoder. This would have to be done separately for ffmpeg and HCenc. (I have no intention to do this... :devil: )


Cheers
manolito

[MrC]

@Danette

you can already add an avs script file as input title. AVStoDVD will use the Import() function to load the AviSynth script. Of course, if the script is not DVD compliant, AVStoDVD will add the proper commands to make it compliant. I don't know if this covers your needs, you can try ;)

@MisterXY

Let's try it. Start uploading the x265 file...

;)

Bye

[manolito]

New version of my AVStoDVD plugins:

This time only the Wavi_mod plugin has changed. I added the LoudNorm filter by Kyle Swanson which is part of current FFmpeg versions. Download here:
http://www90.zippyshare.com/v/yQgp0Kmu/file.html

This filter normalizes audio tracks for a target loudness level according to the EBU R128 standard. The difference to using the BS1770Gain routine is that if the gain correction would cause clipping, Loudnorm uses a dynamic correction adding some real DRC plus a fast lookahead peak limiter. I use a LoudNorm wrapper tool called "WinLoudCLI" by Muxson. This tool makes it easy to work in 1-pass, 2-pass or SMART mode, it adds a progress indicator, plus it allows for easy creation of a log file.


Cheers
manolito

[Mister XY]

I hope this sample is good enough.
http://www20.zippyshare.com/v/2SXfFUrK/file.html

[manolito]

Hi Mister XY,

you are right, AVStoDVD seems to be unable to recognize chapters from this file. First I thought that the reason could be that you are cheating a little bit (you muxed a 12sec video track with a 1hour 39min audio track). But when I tested a file with matching track lengths I got the same behavior. Converting the file to AVC video solved the issue.

Until MrC fixes the problem you need to use some workaround. The easiest workaround I found is using "ChapterEditor" by hubblec4. Click the "Convert" tab, load the source MKV and save the chapters to a file using the "Celltimes" format. Select the fps value of the target, not the source. Then import this Celltimes chapter file directly into AVStoDVD.


Cheers
manolito

[Mister XY]

That's was only one movie from many more with this problem.

[hurricane51]

Thank you.

I had tried that but the installer did not install the MSCOMCTL.OCX file into the AVSTODVD Lib folder (I tried reinstalling several times), nor did it replace the old version in the SysWOW64 folder. I solved it by deleting the older MSCOMCTL.OCX file in SysWOW64 and then uninstalled and reinstalled AVSTODVD, which placed the newer MSCOMCTL.OCX file into both the SysWOW64 and AVSTODVD folders.

AVSTODVD works fine now.

Thanks so much for this tip. My AVS2DVD installation works fine now.

[Mister XY]

No solution?

[MrC]

@Mister XY

I apologize for the delay, unfortunately I have very little time for AV stuff in these days. But do not give up, I will try to come back with a reply asap.

;)

Bye

[Mister XY]

Ah thanks for the info.

[MrC]

A new Alpha release is available to download (https://sourceforge.net/projects/avstodvd/files/avstodvd_alpha_beta/AVStoDVD%202.8.6%20Alpha%20170131/).

Change log:

- Some bugs fixed
- Added '-filter:v "setpts=x*PTS"' command flag to FFmpeg Safe Mode video encoding routine in case of PAL SpeedUp or NTSC SlowDown
- Improved troubleshooting of mscomctl.ocx file missing or broken
- LAV Filters updated to release 0.69
- FFMpegSource plugin updated to release 2.22 r1140 (C plugin)

;)

Bye

[manolito]

Mille Grazie for the new version... :thanks:

Did some comprehensive tests, works beautifully:

Mister XY will be happy to hear that chapters in HEVC sources are now recognized correctly.

SpeedUp and SpeedDown when using FFmpeg safe mode now work nicely for both audio and video (Neat trick modifying the vdeo time stamps. I was looking for something like AssumeFPS in FFmpeg without success).

I could not test the new safeguards for mscomctl.ocx because I never had any problems.

The new alpha still comes with a slightly damaged German language file. The correct file is still here:
https://forum.doom9.org/showthread.php?p=1790801#post1790801


Thanks again
Cheers
manolito

[manolito]

And here comes a new version of my Plugins for AVStoDVD...

This time only the Wavi_Mod plugin was updated. No new functionality, I just replaced Aften with FFmpeg for the final encode to AC3.

The only reason was that all the audio experts agree that the AC3 encoder in FFmpeg delivers better quality than Aften. I am not sure if the difference is audible, but whatever, in AVStoDVD we always aim for the highest quality, right?

I took great care to make sure that large 6-ch audio files where the size of the intermediate WAV file is > 4GB are supported. Thanks to tebasuna51 for providing essential help.

Download here:
Link removed, get the file here:
https://forum.doom9.org/showthread.php?p=1801413#post1801413

Cheers
manolito

[MrC]

Thanks manolito for the plugins package update and for the German lang file. I had alreday downloaded it, but never copied from Download folder to A2D Lang folder... my bad...

;)

Bye

[ChickenMan]

Gi'day Manolito, great to see your still active here old friend :)

I recently had to convert a few AVI's to DVD and decided I had better install something to do it. Now on Win10 x64 all my old stuff no longer works. So upgraded my old installation of AVS2DVD to the latest, fixed the mscomctl.ocx registration and did my first conversion, well for a very long time, avi to dvd. All went well as expected, so thanks MrC for continuing to support the program.

Cheers,
cm

[manolito]

Hey ChickenMan,

good to see you again after a long time (last time we talked was in 2014, and before this in 2010)... :eek:

We do go back a long time, I remember you had published a tutorial for DVD2SVCD on another forum (defunkt now, I even forgot the name). This was when I just started with conversions to SVCD (DVD burners were not even available at this time). Man, we've gotten old...

I still have DVD2SVCD on my machine, but not really using it. Generally the DVD format seems to fade quickly, I myself do not use it any more. I used to burn my TV captures to DVD for a long time, but this became unmanageable for the sheer number of disks. I now convert everything to AVC / AAC and copy it to an external HDD, I got a little streaming box (Xtreamer Sidewinder) to watch the stuff. And right now even AVC looks out of fashion, everybody seems to use HEVC.


But yes, AVStoDVD is still fun, I hope that MrC will stick with it for a while. I am also a little bit involved in DVDStyler. My little FFmpeg VBR plugin got so popular over there that Mr. Thuering (the author) decided to integrate it transparently into his software. Now DVDStyler in addition to elaborate menu creation can also do high quality FFmpeg based transcodings.


All my best wishes to you...
Cheers
manolito

[ChickenMan]

Good to hear from you Manolito :) Arr... yes the good old DVD2SVCD days at CDFreaks back in the early days of this century :) Now I'm really starting to feel old !!!!

Like yourself and the low price of hard drive space now compared to those days, its much easier to store your files on a HD and stream them to the TV. Or just get Netflix's or similar :)

Nowadays I spend more of my time involved with the retro computer, Aussie designed & built Microbee.

Keep up the good work :)

Cheers,
cm

[manolito]

Arr... yes the good old DVD2SVCD days at CDFreaks back in the early days of this century :) Now I'm really starting to feel old !!!!


You remember this one?
http://forum.dvdrbase.info/threads/26515-How-to-backup-your-DVD-to-DVD±R

[ChickenMan]

DVDRBase, oh yes, the forum Woody & I started back in 2001. I dont believe it, those tutes are still there !! I dont believe the Forum is still there as well !!!

How things have changed over the years though, we now have the all in one programs, you just install, load in file and click GO ! No fun in that, but we had lots of fun back in those days :)

[manolito]

Changes:

In HCenc_Mod and FFmpeg_VBR you can now add parameters to the AviSynth resizer commands.

Example:
You want to use BlackmanResize, but always with the "taps=5" parameter. Instead of editing the AVS script for every source you can now force using this parameter all the time.


Bug fix for the Wavi_Mod plugin:
If the AVStoDVD temp folder or output folder had spaces in their names, the folder would not be recognized.


Download:
Link removed, see the next post...

Cheers
manolito

[manolito]

Another new version...

While I already was at manipulating the A2D AviSynth script, I decided to take it one step further. Now it is possible to inject your own custom AVS commands into the script. These commands will be imported into the script right after the "ConvertToYV12()" command.

Of course all the filters you call with this method must be present in your "AviSynth\Plugins" folder. And there is one drawback:

The A2D preview will not honor those additional filters. As a workaround you can start the encode and pause it immediately (for FFmpeg press the "Pause" button on the keyboard, in HCenc press the "Suspend" button). Then go to your AVStoDVD Temp folder in Explorer and open the AVS file in a DirectShow media player like MPC or WMP.


Download:
//Link removed//


Cheers
manolito


//EDIT//
Improved filtering of interlaced sources using JDL_UnfoldFieldsVertical and JDL_FoldFieldsVertical by Stickboy. Needs jdl-interlace.avsi and jdl-util.avsi from here: http://www.avisynth.nl/users/stickboy/
Switching to interlaced mode will be automatic

Please redownload...

[manolito]

And another new version of my plugin pack for AVStoDVD:

Until now the Wavi_Mod plugin required that the AVStoDVD executable had to patched. This was very clumsy, and some users had problems with this requirement. So I decided to revamp Wavi_Mod so patching is no longer necessary... :D

Until now I had hacked Wavi.exe to access the parameters issued by AVStoDVD. I moved this to FFmpeg.exe, so now in order to invoke the plugin the audio conversion method must be set to "FFmpeg (AviSynth)" instead of the previous "Wavi + Aften".

Everything else stays the same, there is no new functionality. The "hacked" FFmpeg.exe now works for both FFmpeg_VBR and for Wavi_Mod.

Before installing the new version of Wavi_Mod please uninstall the previous version. Also make sure to replace the patched "AVStoDVD.exe" with the original unpatched version.

Download from here:
Link removed, get it here:
https://forum.doom9.org/showthread.php?p=1814855#post1814855


Cheers
manolito

[MrC]

Just released 2.8.6 Final (https://sourceforge.net/projects/avstodvd/files/avstodvd/AVStoDVD%202.8.6/). No significant changes from latest Alpha, except there's the Installer package.

;)

Bye

[manolito]

:thanks:

[MrC]

AVStoDVD release 2.8.7 Alpha 170810 is available (https://sourceforge.net/projects/avstodvd/files/avstodvd_alpha_beta/AVStoDVD%202.8.7%20Alpha%20170810/)

Changes log:

- Some bugs fixed
- Added support to WebM files (*.webm) as input files, subset of Matroska
- Added warning messages when AVC/AAC title is added and Microsoft DTV-DVD decoders are default codecs
- Added a warning message when input title has a DVD compliant audio track with delay, to force audio re-encode
- Added check of .NET Framework 2 presence in 'Preferences'/'System'/'Software Info'
- Revised video encoder smart selection rationale: no more HCenc VBR 1-pass for multicore CPUs
- Improved handling of "non-mod4" interlaced sources within the AviSynth script generation routine
- LAV Filters updated to release 0.70.2

It is an Alpha release, please advise if you get problems with the new (and old ;) ) features.

;)

Bye

[manolito]

Thanks for the new Alpha... :thanks:

Works nicely here, I found just one minor thing:
For some reason the older slightly broken version of my German language file found its way into the Alpha. The version in the stable version 2.8.6 is the correct one.


Cheers
manolito

[manolito]

Here comes a new version of my plugin package for AVStoDVD:

Only the FFmpeg VBR plugin is affected. After MrC changed this in the latest Alpha:
Revised video encoder smart selection rationale: no more HCenc VBR 1-pass for multicore CPUs

I decided to bring the FFmpeg VBR behavior more in line with the HCenc behavior. It works like this:

Like for HCenc the different encoding modes are automatically selected depending on the video bitrate. The bitrate thresholds are stored in the Registry, and the ff_vbr plugin uses these values just like HCenc. It also uses the High Quality parameters which can be turned on under "Preferences".

The difference to HCenc is that there is an additional "Extreme High Quality" mode which only kicks in if the bitrate goes below the Extreme HQ threshold (can be edited in the batch file) AND the FFmpeg HQ mode is activated.

Of course these automatic mode decisions can be overturned by forcing certain encoding and HQ modes (can be turned on by editing the batch file).

All in all this makes the plugin behavior more consistent with the A2D behavior for HCenc so it is more powerful and also less confusing than it was before.


Another change is that the plugin mode is now shown in the title bar of the encoding window. This kind of makes up for the still missing separate VBR encoding log.


Download here:
https://files.videohelp.com/u/172211/Manolito_s%20A2D%20Plugins.7z

Cheers
manolito



//EDIT//
This kind of makes up for the still missing separate VBR encoding log.
No longer true... :D
The latest version of the FFmpeg_VBR plugin now creates a separate log file in the A2D output folder. Please redownload if you want this feature.

//EDIT2//
Adapted the plugins to the latest AVStoDVD Alpha 171109. The DSS2Mod patch was removed since the latest Alpha uses DSS2Mod by default. Also improved the documentation.

[MrC]

Thanks manolito for the new plugin update and for the German language file advise.

;)

Bye

[manolito]

I have been meaning to compile this little list for a long time, here it is finally. I will try to keep this list current as good as I can...

Since I still use the software on an ancient machine with a non-SSE2 CPU under Windows XP I took special care to point out which updates require newer hardware or software.

Please note that if you want to upgrade you absolutely have to download and use the 32-bit versions of the applications. All 64-bit software cannot be used under AVStoDVD


Here is a list of the AVStoDVD helper applications which can be updated to newer versions. I also tested the compatibility with Win XP and with CPUs without SSE2 capabilitiy (Intel Pentium 3 and older AMD Athlons).

According to the "Requirements" section in the A2D help file an SSE2 capable CPU is required, but I found that this is not necessarily true. The only helper software which requires SSE2 at the moment is LAV Filters, and it can easily be replaced by the slightly older version 0.69.0.85.

.NET Framework 2.0 is only necessary for SubtitleCreator. For users who do not need subtitles .NET Framework is not required for using AVStoDVD.

The Java Runtime Environment (JRE) must be installed for BDSup2Sub. The program was last updated in 2013, but it works flawlessly using the current JRE Version (32-bit of course).


AviSynth:
Version 2.60 is required (the latest 2.61 Alpha also causes no problems).

AVS+ is now supported, but the user is responsible to modify the AVS script to enable multitasking. Only use the latest official version which can be found here:
https://github.com/AviSynth/AviSynthPlus/releases

To enable multithreading the command "Prefetch(n)" must be appended to the AVS script which is created by AVStoDVD (where "n" is the number of prefetch threads). Users of my FFmpeg_VBR and HCenc_Mod plugins have the option to do this automatically.

LAV Filters:
The current LAV versions require Windows Vista or higher. For a non-SSE2 CPU the nightly build 0.69.0.85 is the latest working version, under Win XP the latest working nightly is LAVFilters-0.70.2-16. So you may have to downgrade...

AVSMeter:
The latest AVStoDVD version comes with a modified AVSMeter version which does not check all the autoload plugins. This speeds up the program start considerably. The current official versions have slightly changed calling parameters, so these cannot be used with AVStoDVD.

BatchMux:
Newer versions than version 1.4.1 which is bundled with A2D are NOT compatible.

ColorMatrix:
AVStoDVD ships with the latest Tritical version 2.5. There is a newer version 2.6 from 2018 which adds support for Rec.2020 which is widely used for UHD clips. The latest build by Groucho2004 does not even require a CPU with SSE2 support. Download here:
https://www.mediafire.com/file/aj88vdobroxjbkd/ColorMatrix26.7z/file
If you want to upgrade please use the 32-bit version. Please note that AVStoDVD does not take any action if MediaInfo detects a source with BT.2020 color. You need to manually add ColorMatrix in the "View/Edit Title Settings -> AviSynth" tab and specity 4 for the source format and 2 for the target format.

DGIndex:
The included version 1.58 was recently updated to version 2.0.01. There also is an ICL build 1.58 by Groucho2004 which is slightly faster and works well. Download the file "dgmpgdec158_ICL.7z" from here: https://www.mediafire.com/file/q9d34pu3d2co6px/dgmpgdec158_ICL.7z/file
Extract the files from the archive into the "DGIndex" subfolder, the file "DGDecode.dll" must be extracted into the "Lib" subfolder additionally.
The new version 2.0.01 does no longer work under WinXP and/or a CPU without SSE2 support.

FFmpeg:
The included version 2.2.3 is from 2014 and is slowly getting a little old. For the purpose of AVStoDVD it probably has everything it needs, though...
If you want to upgrade to a later version, there are a few things to keep in mind:

Starting with version 3.1.2 the FFmpeg AVS interface has changed. To work with A2D it is necessary to include the folder "...\AVStoDVD\Lib" in your "PATH" environment variable. It is also recommended to include the folder "...\AviSynth\Plugins" in the "PATH" variable.

Current FFmpeg versions do NOT work under Win XP. Reino (formerly CoRoNe) still builds recent XP compatible versions, get them here:
http://rwijnsma.home.xs4all.nl/files/ffmpeg/

The latest and highly recommended version which works under Win XP and does not require to modify the "PATH" variable is this one from July 2016 by rogerdpack:
https://sourceforge.net/projects/ffmpegwindowsbi/files/2016-07-18/ffmpeg.static.2016-07-18-g450cf40.32-bit.ffmpeg-static-xp-compatible.zip/download
Please note that my latest Wavi_Mod plugin needs (and comes with) a newer FFmpeg version than this one to make the upmix routines work. But this is only for the Wavi_Mod plugin, it has nothing to do with the FFmpeg version which AVStoDVD itself uses.

FFMS2 (FFmpegSource):
AVStoDVD comes with the ffms2 C-plugin for AVS version 2.27 by qyot27. The latest version which works under Win XP is FFMS2 C-plugin r1315+119 version 2.30, It is available for download here:
http://www.mediafire.com/file/oi31n1lcrzdvkno/ffms2_r1315%2B119-avs%2Bvsp_lastxp.7z
This version works nicely under AVStoDVD. One thing I did notice, though, is that it is less tolerant with problematic or broken source files than other ffms2 versions.
The last ffms2 version which does handle problematic sources flawlessly is FFMS2 C-plugin 1140+101 from 2016. Highly recommended. Get it here:
https://forum.doom9.org/showthread.php?p=1783312#post1783312
The current C-plugin versions need at least Windows Vista, get them here:
https://forum.doom9.org/showthread.php?p=1829061#post1829061

Good news for WinXP users (even without SSE2 capable CPUs):
CoRoNe (aka Reino) started to build XP compatible versions of the ffms2 C-Plugins, get them here:
http://rwijnsma.home.xs4all.nl/files/ffms2/
Highly recommended...

Switching from the C-plugin to the Standard-plugin version is possible, but it requires to patch the AVStoDVD executable with a hex editor. I do not see any advantages compared to the C-Plugin, but if you insist, let me know...

One note of caution:
It is NOT recommended to have a different ffms2 version in your "...\AviSynth\Plugins" folder. If you do it is much safer to copy the files ffms2.dll and ffms2.avsi from the AVStoDVD\Lib folder into the AviSynth\Plugins folder.

MediaInfo:
Works up to version 18.05. Later versions are NOT compatible with AVStoDVD..

MKVtoolNix:
The only file from the package which is actually used by AVStoDVD is "mkvextract.exe". The last version which works under Win XP is v29.0.0.

Mplex:
AVStoDVD comes with two different Mplex versions, a "normal" version and a version which requires SSE2. In my experience the SSE2 version has no advantages whatsoever, in my tests it was even slower than the normal version. I recommend to leave everything as it is.

SubtitleCreator:
AVStoDVD comes with the latest stable version 2.2. There is a newer release candidate version 2.3 available, but the author stopped working on it in 2008, so I did not test it under A2D.


All other helper applications are current. Most of them are static, i.e. there will probably be no more updates for them.


Comments and corrections welcome... ;)


Here is the link to the current version of my plugins for AVStoDVD:
https://files.videohelp.com/u/172211/Manolito_s%20A2D%20Plugins.7z

The package consists of FFmpeg_VBR (adds VBR modes for the FFmpeg encoder), Wavi_Mod (offers alternative audio normalizing modes) and HCenc_Mod (users can add custom parameters to HC.ini). The FFmpeg_VBR and HCenc_Mod plugins also allow to automatically enable AVS+ Multithreading using very stable settings, a guide and some additional tools are included.


Cheers
manolito

[Groucho2004]

AVSMeter:
The current versions are NOT compatible with AVStoDVD (different log file format).
I suppose it's the video frame size formatting that has changed? I can revert this (at least in the log file), no big deal.

[manolito]

Sorry I have no idea... :confused:

With AVSMeter 2.6.1 I get an error message complaining that the AVSInfo.log file could not be read. No further explanation what exactly caused the error. Using AVSMeter 2.1.3 users never get to see this log file, so there is no way to compare the two versions.

Whatever, it is not worth the trouble to fix this. For AVStoDVD the old version 2.1.3 works nicely, and since the software is small and portable users can easily keep a current version of AVSMeter in a different HDD folder.


Cheers
manolito

[Groucho2004]

With AVSMeter 2.6.1 I get an error message complaining that the AVSInfo.log file could not be read.It should work again with 2.6.2.

[manolito]

It should work again with 2.6.2.
Yes it does, thanks a lot...

Just one minor catch:
Older versions of AVSMeter could read the previous INI file and take over the settings to the new INI file. This does not work here. If the older INI file from 2.1.3 is still present in the AVSMeter folder then the new version 2.6.2 will crash. No big deal, I just need to tell users to clean the AVSMeter folder completely before upgrading to the latest version.


Thanks again
manolito

[Groucho2004]

Just one minor catch:
Older versions of AVSMeter could read the previous INI file and take over the settings to the new INI file. This does not work here. If the older INI file from 2.1.3 is still present in the AVSMeter folder then the new version 2.6.2 will crash.
That's a very easy fix (already done for 2.6.3).

[manolito]

That's a very easy fix (already done for 2.6.3).
Confirmed...
And :thanks:

[MrC]

A new 2.8.7 alpha release is available to download (https://sourceforge.net/projects/avstodvd/files/avstodvd_alpha_beta/AVStoDVD%202.8.7%20Alpha%20170921/).

Change log (cumulative from 2.8.6):

- Some bugs fixed
- Added support to WebM files (*.webm) as input files, subset of Matroska
- Added warning messages when AVC/AAC title is added and Microsoft DTV-DVD decoders are default codecs
- Added a warning message when input title has a DVD compliant audio track with delay, to force audio re-encode
- Added check of .NET Framework 2 presence in 'Preferences'/'System'/'Software Info'
- Added BDSup2Sub 5.1.2 to improve bitmap-based subs handling (resize and resync). It requires Java Runtime Environment
- Added check of Java Runtime Environment presence in 'Preferences'/'System'/'Software Info'
- Improved support of VobSub subtitles: resize and resync from BD sources is now implemented with BDSup2Sub
- Improved handling of "non-mod4" interlaced sources within the AviSynth script generation routine
- Revised video encoder smart selection rationale: no more HCenc VBR 1-pass for multicore CPUs
- LAV Filters updated to release 0.70.2
- AVSMeter updated to release 2.6.5

;)

Bye

[manolito]

Thanks for the new Alpha...

Did some short tests and found no problems. For the new addition BDSup2Sub I only checked that it runs at all on my ancient computer and that it also works using the current JRE Version 8 Update 144 (32-bit).


Cheers
manolito

[MrC]

Hi manolito, thanks for the feedback on the new Alpha.

I'm planning to alter a bit the routine to select the FPS conversion method, specifically for 30p/60p sources.

Currently, if Pulldown, SelectEven, PAL SpeedUp, NTSC SlowDown are not selected/feasible, then MotionProtectedFPS is used by default (with the option for the user to switch to ChangeFPS or ConvertFPS in Preferences section). MotionProtectedFPS does usually its job nicely, but we know it can introduce edge artifacts.

Nowadays many HD/FullHD sources are 30p and, when output is NTSC, probably the best approach could be to drop few frames (from 30 to 29.97) with ChangeFPS instead of applying motion compensation. Same for 60p sources: first SelectEven than ChangeFPS. Instead for PAL output the frames drop approach from 30p could provoke too much jerkiness.

What do you think? (open question to all Doom9 expert users, of course)

;)

Bye

[manolito]

Hi MrC,
basically I believe that you are absolutely right. My thoughts so far - please keep in mind that I do not know all that much about NTSC...

The MotionProtectedFPS routine is quite deprecated these days. Using MVTools2 the results can be much better, but of course at the cost of a slower speed.

A while ago I stumbled upon a script suggestion by johnmeyer which IMO could beat everything I had seen before. I called it "jm_fps", the name did stick somehow. See here:
https://forum.doom9.org/showthread.php?p=1800439#post1800439

The script defaults work well for most sources except for anime (where you often need a higher block size of 32 and maybe a DCT value of 1). The speed is slower than for MotionProtectedFPS, but still very usable.

There is another approach by MysteryX which is based on this jm_fps script, but adds artifact masking. Still slower, sometimes very useful, sometimes not. I simplified it quite a bit and called it "mx_fps", get it here:
https://forum.doom9.org/showthread.php?p=1805050#post1805050

I also uploaded an ALL In ONE package which you can download from this page.


But still this motion interpolation approach is not for everyone, with some sources it just does not work too well. Another challenge is that today we encounter a lot more different source formats than we did earlier, and getting the best approach to convert these formats to DVD is not easy.

For a 30p source when the target format is NTSC then of course using ChangeFPS would be the preferred choice. If the target format is PAL then the users have to decide if they can live with a lot of dropped frames, or if a motion interpolated conversion is required. The same applies to 60p sources.


Recently here in Germany the switch to DVB-T2 brought some more confusion for me. The video format is now HEVC, it is always progressive at 50 fps. For film sources they just duplicate frames (looks like they first speed up 24fps sources to 25fps and then just duplicate each frame). But for video sources (news, soaps, sports) there are no duplicate frames, the captured clips have 50 unique progressive frames per second. Can we still use SelectEven() for such sources, or is it better to interpolate? And which method is best to convert such sources to 29.97fps for NTSC? Decimate (or convert) to 25p first and then apply NTSC slowdown followed by soft pulldown? Or better interpolate from 50p to 29.97p directly? I have no idea...


Cheers
manolito

[MrC]

Hi manolito,

thanks for the link about the most recent applications of motion interpolation on FPS conversion. I have quickly tested the jm_fps routine and it is very very clean, with acceptable impact on encoding speed. Quite easy to implement into A2D too. I just would find a more "sexy" name, instead of jm_fps.... ;) Do you confirm that fftw3.dll is actually needed only if DCT flag is set to 1? Still not tested mx_fps.

As per the 50p conversion to DVD, if the output is PAL, generally speaking I would go with SelectEven(), it should deliver the smoothest result. If the output is NTSC the decision is much more video content dependant. Will the DVB-T2 standard be @ 50fps in all countries or only in German? If the latter, NTSC output could be irrelevant...

;)

Bye

[manolito]

I just would find a more "sexy" name, instead of jm_fps.... ;) Do you confirm that fftw3.dll is actually needed only if DCT flag is set to 1? Still not tested mx_fps.
For a sexier name I am open to suggestions... :D
It's just that a couple of other folks also have adopted this name, it might get confusing to rename the script now.

fftw3.dll is not needed when DCT is not used (DCT=0), which is the default. Usually DCT=0 works fine, but for some rare (mostly anime) sources DCT=1 gives a much better quality, but at a very very low speed.

The jm_fps script only exposes the framerate to keep it as simple as possible. Maybe I should change the interface to also expose the block size and DCT. These 2 params are the ones a user wants to play with for difficult sources. But this might be beyond the scope of A2D... :devil:

Another thing you want to think about when integrating this into A2D:
For most helper plugins there are "modernized" versions (mostly written by pinterf) which add additional features like new colorspaces, high bitdepth and MT support. All these newer versions require SSE2 so they will not work on my computer. I also find them a little unstable, they are work in progress. The AIO package for mx_fps which I linked to contains older but stable versions of these plugins.


As per the 50p conversion to DVD, if the output is PAL, generally speaking I would go with SelectEven(), it should deliver the smoothest result. If the output is NTSC the decision is much more video content dependant. Will the DVB-T2 standard be @ 50fps in all countries or only in German? If the latter, NTSC output could be irrelevant...

I believe that DVB-T2 will be 50fps only in PAL countries. I really do not like the fact that each European country now uses its own flavor of the standard. Germany was very late to introduce DVB-T2 so they figured to push ahead and use HEVC video and EAC3 and/or AAC-LATM audio. It took me a long time to establish a workflow for my conversions to AVC or DVD which keeps audio in sync.


Cheers
manolito

[MrC]

Rename to MCJMFPS (Motion Compensation John Meyer FPS)? Not so sexier, but more "impressive"... and "expressive"... ;)

About the need of fftw3.dll, since it was not present in my system, I did some tests, and, DCT=0 does not require it. Thus I would update the avsi info section accordingly. And maybe add the DCT flag to the MCJMFPS function. What do you think?

Another small clue when loading RemoveGrain. RemoveGrain.dll needs MSVCR71.DLL in System32/Syswow64, while the monolithic build RemoveGrainS.dll works alone.

In terms of speed, from few 1080p@60 to PAL conversions, I would say that jm_fps (DCT=0) is 1/3 than MotionProtectedFPS and 1/5 than ChangeFPS. What about mx_fps with defaults params? Even slower than jm_fps?

;)

Bye

[manolito]

I did some tests, and, DCT=0 does not require it.

Yes of course, just noticed that my previous post had it the other way around. Getting old...

I would still recommend to copy fftw3.dll into a system folder because for some sources (anime) DCT=0 causes bad artifacts. MysteryX even changed his "normal" preset from DCT=0 to DCT=4 in the latest version of his "FrameRateConverter" plugin.

If you want to have a look at this latest version, see here:
https://github.com/mysteryx93/FrameRateConverter/releases/tag/v1.2
My mx_fps version has many presets removed, all the debug code is gone, I made it compatible with older versions of MaskTools and MVTools, and the user interface exports only the most important parameters (MysteryX hates me for doing this). :devil:

And yes, mx_fps with default parameters is a little bit slower than jm_fps, simply because of the added artifact masking. In most of my tests I found that jm_fps is all I need, but this probably is different for different sources and different users.

The mx_fps version I linked to uses an additional DLL which can build a "stripe mask". This DLL needs SSE2, so I do have an alternative version which has the stripe mask feature removed. Not a big loss, this feature only helps in rare cases IMO.

Meanwhile I updated jm_fps so now it has the two additional parameters "BlkSize" and "Dct". BlkSize can only be 8, 16 or 32. For the possible Dct values see the MVTools documentation. The most useful values are 0, 1 and 4.


Cheers
manolito

[MrC]

AVStoDVD release 2.8.7 Alpha 171109 is out (https://sourceforge.net/projects/avstodvd/files/avstodvd_alpha_beta/AVStoDVD%202.8.7%20Alpha%20171109/)

Change log (cumulative from 2.8.6):

- Added AviSynth plugin DSS2mod to replace DirectShowSource for video frame serving in 'A2DSource.avsi' script
- Added support to WebM files (*.webm) as input files, subset of Matroska
- Added warning messages when AVC/AAC title is added and Microsoft DTV-DVD decoders are default codecs
- Added a warning message when input title has a DVD compliant audio track with delay, to force audio re-encode
- Added check of .NET Framework 2 presence in 'Preferences'/'System'/'Software Info'
- Added BDSup2Sub 5.1.2 to improve bitmap-based subs handling (resize and resync). It requires Java Runtime Environment
- Added check of Java Runtime Environment presence in 'Preferences'/'System'/'Software Info'
- Added 'Smart Selection' option to 'Preferences'/'AviSynth'/'Hard FrameRate Conversion' option (see Help section for more details)
- Added AviSynth script 'MCJMFPS.avsi' for hard fps conversions (thanks to johnmeier and manolito from doom9)
- Dropped AviSynth script 'MotionProtectedFPS.avsi' for hard fps conversions, mainly due to edge artifacts
- Revised other 'Preferences'/'AviSynth'/'Hard FrameRate Conversion' option labels
- Revised video encoder smart selection rationale: no more HCenc VBR 1-pass for multicore CPUs
- Improved support of VobSub subtitles: resize and resync from BD sources is now implemented with BDSup2Sub
- Improved handling of "non-mod4" interlaced sources within the AviSynth script generation routine
- Spun off Preferred DirectShow Codecs Tool in a separate executable file 'A2DCodecs.exe'
- Removed 'Execute AVStoDVD with Elevated Privileges' option in 'Preferences'/'Misc'
- LAV Filters updated to release 0.70.2
- AVSMeter updated to release 2.6.5

Bye

MrC

[manolito]

Thanks for the new build... :thanks:

Did a couple of short test conversions, no problems. The only thing I found is that
- Spun off Preferred DirectShow Codecs Tool in a separate executable file 'A2DCodecs.exe'
this new separate A2DCodecs.exe does not (yet) use the translated strings from the language files... :p


Cheers
manolito

[MrC]

Yes, you are right, I still have to implement the language customization into the new A2DCodecs tool. In the ToDo list before going final with 2.8.7

;)

Bye

[manolito]

Oops, after a few days I did find a bug in the latest Alpha which crashes AviSynth for interlaced sources... :devil:

- Improved handling of "non-mod4" interlaced sources within the AviSynth script generation routine


For "non-mod4" interlaced sources A2D adds the follwing line to the AVS script:
Video = Video.Crop(0,0,-Width % 4,-Height % 4).ConvertToYV12(interlaced=true)

Width and Height are not defined for the implicit "Last" variable at this point, so AVS crashes. The line should instead be:
Video = Video.Crop(0,0,-Video.Width % 4,-Video.Height % 4).ConvertToYV12(interlaced=true)


Cheers
manolito

[manolito]

And here is another bug report for the latest Alpha...

This latest Alpha breaks BatchMux completely (at least for me). Took me a while to find it because the change log did not mention any changes to BatchMux.

The BatchMux log file says that there is no reference to the first video file. The relevant log files are here:
http://www30.zippyshare.com/v/6nkm21Zp/file.html

I then went back to the previous Alpha from 170921, and this version worked using identical settings. Something with the script creation for BatchMux must be broken.


Cheers
manolito

[MrC]

Hotfix 171212 for release 2.8.7 Alpha is available (https://sites.google.com/site/avstodvdmain/AVStoDVD_287_Alpha171212_Hotfix.7z).

It solves the 2 bugs reported by manolito.

;)

Bye

[manolito]

Yes, works beautifully... :D

Now just apply the translated strings to the DS filter setup window, and you have a new stable version... :devil:

Thanks and Cheers
manolito

[MrC]

Yes, agreed. Thanks for the feedback!

;)

Bye

[manolito]

Damn, I spoke too soon... :devil:

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.

The relevant settings are here:
http://www85.zippyshare.com/v/uf1ZfUh4/file.html

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.

[MrC]

Thanks manolito for the new report. I will check what's broken.

;)

Bye

[MrC]

To optimize the subtitles colors I had modified the default DVD palette, which is used also by BatchMux/Muxman to assign the colors to menu highlights.

To fix that, I have completely redefined also the Selection/Play colors list, taken from \AVStoDVD\Menu\HL Colors folders.

;)

Bye

[MrC]

A new 2.8.7 Alpha release is out (https://sourceforge.net/projects/avstodvd/files/avstodvd_alpha_beta/AVStoDVD%202.8.7%20Alpha%20180107/).

Cumulative changes log from 2.8.6:

- Some bugs fixed
- Added AviSynth plugin DSS2mod to replace DirectShowSource for video frame serving in 'A2DSource.avsi' script
- Added support to WebM files (*.webm) as input files, subset of Matroska
- Added warning messages when AVC/AAC title is added and Microsoft DTV-DVD decoders are default codecs
- Added a warning message when input title has a DVD compliant audio track with delay, to force audio re-encode
- Added check of .NET Framework 2 presence in 'Preferences'/'System'/'Software Info'
- Added BDSup2Sub 5.1.2 to improve bitmap-based subs handling (resize and resync). It requires Java Runtime Environment
- Added check of Java Runtime Environment presence in 'Preferences'/'System'/'Software Info'
- Added 'Smart Selection' option to 'Preferences'/'AviSynth'/'Hard FrameRate Conversion' option (see Help section for more details)
- Added AviSynth script 'MCJMFPS.avsi' for hard fps conversions (thanks to johnmeier and manolito from doom9)
- Dropped AviSynth script 'MotionProtectedFPS.avsi' for hard fps conversions, mainly due to edge artifacts
- Revised other 'Preferences'/'AviSynth'/'Hard FrameRate Conversion' option labels
- Revised video encoder smart selection rationale: no more HCenc VBR 1-pass for multicore CPUs
- Revised DVD Menu Highlight colors list (Selection and Play). Now they replicate default DVD palette used in AVStoDVD.
- Improved support of VobSub subtitles: resize and resync from BD sources is now implemented with BDSup2Sub
- Improved handling of "non-mod4" interlaced sources within the AviSynth script generation routine
- Spun off Preferred DirectShow Codecs Tool in a separate executable file 'A2DCodecs.exe'
- Removed 'Execute AVStoDVD with Elevated Privileges' option in 'Preferences'/'Misc'
- LAV Filters updated to release 0.70.2
- AVSMeter updated to release 2.6.5

;)

Bye

[manolito]

Yes, beautiful, grazie mille... :thanks:

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)...

Cheers
manolito

[manolito]

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:
@echo OFF
setlocal

reg Query "HKLM\Hardware\Description\System\CentralProcessor\0" | find /i "x86" > NUL && set OS=32BIT || set OS=64BIT

if %OS%==32BIT set syswindir=%windir%\System32
if %OS%==64BIT set syswindir=%windir%\SysWOW64

IF NOT EXIST %syswindir%\mscomctl.ocx COPY mscomctl.ocx %syswindir%

regsvr32 /u %syswindir%\mscomctl.ocx
regsvr32 %syswindir%\mscomctl.ocx


Cheers
manolito

[MrC]

Good question, manolito. The scenario is complicated by Win7/8/10.

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

;)

Bye

[manolito]

Thanks MrC for the detailed explanation...

But I found that some things are a little different.

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...


Cheers
manolito

[manolito]

Alright, I agree that turning off UAC completely may be a bit much for the average user (although I am a big fan of it)...

I made a new version of mscomctl_reg.bat which should overcome the issues (Stackoverflow is your friend...)

@ECHO OFF
SETLOCAL
REG ADD HKLM /F>nul 2>&1
IF ERRORLEVEL 1 GOTO noAdmin

SET Lib_DRIVE=%~d0
SET Lib_PATH=%~p0
%Lib_DRIVE%
CD "%Lib_PATH%"

REG QUERY "HKLM\Hardware\Description\System\CentralProcessor\0" | FIND /i "x86" > NUL && SET OS=32BIT || SET OS=64BIT

IF %OS%==32BIT SET syswindir=%windir%\System32
IF %OS%==64BIT SET syswindir=%windir%\SysWOW64

IF NOT EXIST "%syswindir%\mscomctl.ocx" COPY mscomctl.ocx "%syswindir%"

regsvr32 /u "%syswindir%\mscomctl.ocx"
regsvr32 "%syswindir%\mscomctl.ocx"
GOTO :EOF

:noAdmin
ECHO This script must run with elevated privileges, so:
ECHO.
ECHO right click on it, choose "run as administrator"
ENDLOCAL
ECHO.
ECHO.
ECHO.
PAUSE


Tested under WinXP and Win7 64-bit with UAC ON and UAC OFF. Works well, no idea about Win8 or Win10 though...

It won't help if a previous broken or incompatible mscomctl.ocx is present. In this case the suggestions in the A2D help file need to be applied.



BTW if you are gearing up for the next stable version please consider using the latest ffms2 by qyot27 from here:
https://forum.doom9.org/showthread.php?p=1829061#post1829061


Cheers
manolito

[MrC]

Thanks manolito for the upgrade to the batch file, brilliant! I confirm it works well under Win10 64bit UAC on. I will add to the final 2.8.7 package. Another credit to you ;)

I will have a look also to latest qyot27 ffms2 release. Thanks.

;)

Bye

[MrC]

Release 2.8.7 Final is out (https://sourceforge.net/projects/avstodvd/files/avstodvd/AVStoDVD%202.8.7/).

Cumulative change log from 2.8.6:

- Added AviSynth plugin DSS2mod to replace DirectShowSource for video frame serving in 'A2DSource.avsi' script
- Added support to WebM files (*.webm) as input files, subset of Matroska
- Added warning messages when AVC/AAC title is added and Microsoft DTV-DVD decoders are default codecs
- Added a warning message when input title has a DVD compliant audio track with delay, to force audio re-encode
- Added check of .NET Framework 2 presence in 'Preferences'/'System'/'Software Info'
- Added BDSup2Sub 5.1.2 to improve bitmap-based subs handling (resize and resync). It requires Java Runtime Environment
- Added check of Java Runtime Environment presence in 'Preferences'/'System'/'Software Info'
- Added 'Smart Selection' option to 'Preferences'/'AviSynth'/'Hard FrameRate Conversion' option (see Help section for more details)
- Added AviSynth script 'MCJMFPS.avsi' for hard fps conversions (thanks to johnmeier and manolito from doom9)
- Dropped AviSynth script 'MotionProtectedFPS.avsi' for hard fps conversions, mainly due to edge artifacts
- Revised other 'Preferences'/'AviSynth'/'Hard FrameRate Conversion' option labels
- Revised video encoder smart selection rationale: no more HCenc VBR 1-pass for multicore CPUs
- Revised DVD Menu Highlight colors list (Selection and Play). Now they replicate default DVD palette used in AVStoDVD.
- Revised 'Force FFmpeg when temp WAV is > 4GB' in 'Preferences'/'Audio' rationale: now it is applied also for 1.0/2.0 channels tracks longer than 3 hours
- Improved support of VobSub subtitles: resize and resync from BD sources is now implemented with BDSup2Sub
- Improved handling of "non-mod4" interlaced sources within the AviSynth script generation routine
- Spun off Preferred DirectShow Codecs Tool in a separate executable file 'A2DCodecs.exe'
- Removed 'Execute AVStoDVD with Elevated Privileges' option in 'Preferences'/'Misc'
- LAV Filters updated to release 0.70.2
- AVSMeter updated to release 2.6.5
- FFMpegSource plugin updated to release 2.22 r1293+111 (C plugin)

;)

Bye

[manolito]

Beautiful, works like a charm... :thanks:


Cheers
manolito


//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.php?p=1814958#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...

[MrC]

Hi manolito, thanks for the kind words and for the constant and professional support.

I'm updating the latest plugin version right now. I don't feel nagged at all ;)

;)

Bye

[manolito]

Found some time today to work on my Wavi_Mod plugin...

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... :eek:
//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.

As usual the download link is at the bottom of this post:
https://forum.doom9.org/showthread.php?p=1814958#post1814958


@ MrC
Maybe now you know what I meant with "nagging" you... :p


Cheers
manolito

[MrC]

@manolito

new Wavi_Mod plugin uploaded @ SF

;)

Bye

[manolito]

Thank you so much...

Cheers
manolito

[ebolaguy]

I tried right clicking on REG_MSCOMCTL.bat and running as administrator
but I keep getting the error message "The module "mscomctl.ocx" failed to load. Make sure the binary is stored at the specified pathor debug it to check for problems with the binary or dependant .DLL files. The specified module could not be found. "

[manolito]

From the AVStoDVD help file:

Anyway, if there is already an old or broken mscomctl.ocx file, the Installer will not overwrite it. In that case AVStoDVD will complain. You have to:

· Delete any previous mscomctl.ocx files in your system folders (e.g. C:\Windows\System32 for Win32 or C:\Windows\SysWOW64 for Win64)
· Run as administrator .\AVStoDVD\Lib\mscomctl_reg.bat file

Have you tried to delete old versions of mscomctl.ocx in System32 and/or SysWOW64 before running the batch file?


Cheers
manolito

[MrC]

AVStoDVD 2.8.8 Alpha 180508 is available to download (https://sourceforge.net/projects/avstodvd/files/avstodvd_alpha_beta/AVStoDVD%202.8.8%20Alpha%20180508/).

Change log:

- Some bugs fixed
- Added 'Audio Peak Level Check' feature in 'Title Edit'/'Audio' section
- Added support to OGG chapters txt format (timestamps) in 'Title Edit'/'Chapters'/'Import Chapters' routine
- Improved 'Title Edit'/'Chapters'/'Export Chapters' routine
- Improved source chapters detection routine (now it works again for IFO/DVD files)
- MKVToolNix updated to release 23.0.0
- MediaInfo updated to release 18.03

;)

Bye

MrC

[manolito]

Thanks MrC for the new Alpha...

Did a few quick tests, this is what I found so far:

I will have to update the German language file, give me a few days.

After a long time you finally managed to break my FF_VBR and WaviMod plugins... :devil:
The audio peak level check will not work if my plugins are installed. The reason is that you use the redirection character in the FFmpeg params. The way I intercept all FFmpeg commands in my plugins requires that I retrieve the original command line. In a batch file there is no way to do this correctly if the command line contains special characters like the pipe character or the redirection character.

So far I do not see any workaround for this. Myself I do not care because I use external tools to analyze my audio sources, and I also pretty much abandoned simple peak normalizing.

For the new chapter import and export routines I did not have the time yet to test them, will do this ASAP.

Cheers
manolito

[MrC]

Hi manolito, of course it did not intend to break the plugins... from my side I will try to find a way to redirect FFmpeg stderr to a VB variable instead of going thru batch text file saving. Not easy, but I will try.

I will wait for your kind german translations.

And please let me know your opinion about the new features (Import OGG Chapters and Peak Level Check).

Thanks for your neverending support.

;)

Bye

[manolito]

Hi manolito, of course it did not intend to break the plugins...

Hi MrC,

of course you didn't, I was trying to be funny... ;)

I tried a few more tricks today, but nothing worked (escaping special characters, using delayed expansion, creating new processes for my batch files). I am just hitting the limitations of batch files, which somehow was to be expected.

What would work is to edit your A2DPeakLevel.bat to call _FFmpeg.exe (the renamed original FFmpeg.exe). But this would mean that you had to integrate a check in A2D if my FFmpeg hack is installed and then call the appropriate executable. Not really desirable...

Anyways, anybody who uses my Wavi_Mod plugin has no need to check the audio peak level from within A2D. And for users who have not installed my plugins it does not matter anyways.

A suggestion:
Currently you employ the AviSynth "Normalize" function after the peak level check. This wastes a lot of time. If the peak level is already known you could use the "AmplifyDB" function instead.


Another unrelated thing for the MCJMFPS.avsi:
According to this post
https://forum.doom9.org/showthread.php?p=1841952#post1841952
the quality improves a little bit after adding these params to the two MSuper calls:
sharp=1, rfilter=4

The lines would then look like this:
super = MSuper(source, hpad = 16, vpad = 16, levels = 1, sharp = 1, rfilter = 4) # one level is enough for MRecalculate
superfilt = MSuper(prefiltered, hpad = 16, vpad = 16, sharp = 1, rfilter = 4) # all levels for MAnalyse

I did a few short tests, I found it hard to see a difference. Maybe you could give it a whirl, you might have better eyes than I do...


Alright, I will report back with more test results.

Cheers
manolito

[manolito]

Alright, here is the updated German language file:
https://files.videohelp.com/u/172211/German.lang.ini.7z

I noticed one small glitch with this entry:
120011 Right-Click to manage Titles

When A2D is started in German then the translation for this entry does not kick in, I see the English text. Clicking "View->Select Language->German" fixes it, now I do see the German translation.


I also played a little with the new chapter import/export routines, but this stuff seems awfully complex, at least when you do not live in NTSC land... :(

What I tried so far was to convert a PAL title with chapters every 3 minutes to NTSC. When I had NTSC SpeedDown activated of course the OGG chapters added about 4sec to every chapter point, I did expect this. But when I imported an OGG chapter file I had saved earlier with chapters at exactly every 3 minutes then I got chapter points with about 40 sec added to every original chapter.

Still Batchmux handled these chapters gracefully. I did not expect this because I know that Muxman refuses to author streams with chapters beyond the video length.

Whatever, I think that some folks from NTSC land will have to join in here to test this new feature.


Cheers
manolito

[Sir Didymus]

<<
...Still Batchmux handled these chapters gracefully. I did not expect this because I know that Muxman refuses to author streams with chapters beyond the video length...
>>

Indeed, this is intriguing...

The total number of chapters identified are reported in the BM log file as: "Segment #... - Total Nr of Chapters --> ...".

Just out of curiosity I browsed a little bit deeper in the C code where the chapter points are validated... Well, plenty of code is present in BM to validate the timecode entries. Believe me, there are many checks (and warnings/errors printed out in case of issues). Nevertheless, there is no explicit validation of the individual time points of the chapter lists against the duration of the related video segments. In other terms, as you are pointing out, the BM session (preparation of the mxp script) should not stop...

It is an intended behavior: in case of problems related to chapter points outside of the range of the video segment duration, the complains are all left to MuxMan...
:cool:

[manolito]

Hi Sir Didymus,

good to see you back here after about 2 years... :cool:

You are right, all credits for handling these out of range chapters go to BatchMux, not to MuxMan.

Did another test which confirmed it. The source file was PAL, length was 6min 10sec. It had chapters at 2:00, 4:00 and 6:00. I exported these chapters to the OGG format. Then fired up AVStoDVD and told it to create an NTSC DVD structure. A2D used soft pulldown (correctly, the source was progressive). Then I imported the previously saved OGG chapters file, and the chapters window told me that I had chapters at 2:30, 5:00 and 7:30.

After the conversion which went without errors I played the DVD, and it had chapters at 2:30 and 5:00. The last chapter at 7:30 had not been included.

Had I tried to mux these chapters only using Muxman then Muxman woud have refused to mux and author this project. So it was really BatchMux which protected Muxman from receiving a chapter point outside of the video length. Very cool...


But of course it is still not correct how A2D handles this case. The whole point of using a chapter file which is based on absolute time stamps (as opposed to frame numbers which need to change with the target FPS) is to be independent of the target FPS. Right now A2D does not handle these OGG chapter files correctly when using pulldown.

In another test I used hard FPS conversion to NTSC with ChangeFPS. This time after importing the OGG chapter file the chapter points were correct. Looks like FPS conversion using pulldown needs to be fixed when importing OGG chapters.


Cheers
manolito

[Sir Didymus]

Hem... No, no... Thanks for the credits, but I think there should be something else in the chain which is filtering out the last chapter.

Possibly it is the analysis and the conversions of AVS2DVD. Please get a look at the input chapter files provided to BM to confirm...
:scared:

About BM I was saying the opposite of your (kind) understanding infact: as far as I can say, BM is NOT checking the duration of the video, so it is not removing the last chapter. If you look at the .mxp (output) file produced by BM, you should be able to see the presence of a scene at the time 7:30.

Cheers,
:)

[manolito]

@ Sir Didymus

Yes, you are correct. I repeated my tests keeping all the temp files, and indeed it was AVStoDVD which removed the last (out of range) chapter from the conversion. BatchMux was called without this last chapter, so MuxMan had no problem. Still this is not the desired outcome, the chapters are not at the positions where they should be...


@ MrC

After some long hours of testing I do know why I had this feeling that implementing OGG chapter import would be a major task... :scared:

AVStoDVD is so advanced now, it offers many methods for FPS conversion, and all of these methods require a different handling of importing OGG chapters which are based on time codes.

From my understanding the goal must be:
When I import an OGG chapter file into A2D, then the chapters must appear at the same position of the video in the conversion result. If A2D does not speed up or slow down the video then the chapters must appear at the same point in time (which is also the same position in the video). But if A2D does speed up or slow down the video, then the chapters should still be at the same position of the video. But of course the time stamps for the chapter points should be different to reflect the now different length of the clip. Do we agree on this?


Alright, I tested most of the possible scenarios with the current Alpha, this is what I found so far:

Test environment:
Source file was a short 6min 9sec clip. I created an OGG chapter file with chapters at 2:00, 4:00 and 6:00 min. From this source clip I made different clips for the different use cases:

PAL progressive (interlaced was not needed, it made no difference)
NTSC with soft pulldown 25 -> 29.97 ("irregular" pulldown)
NTSC with soft pulldown 23.976 -> 29.97 ("regular" 3:2 pulldown)
NTSC without soft pulldown, either hard telecined or pure progressive)

I then loaded the desired source clip into A2D and imported the previously created OGG chapter file.


Results:

PAL to NTSC

Using the default soft pullown:
Chapters were way off. MuxMan did not crash though because A2D removed the out-of-range chapters.

Using hard FPS conversion (either hard telecine or ChangeFPS). Also applies to interlaced sources:
No problem


NTSC to PAL

Genuine 29.97 source without pulldown flags (progressive or interlaced):
A2D uses hard FPS conversion, no problem.

Soft telecined source:
A: Telecined 23.976 -> 29.97

A1: Using DGDecode
Pulldown flags are honored, A2D sees the source as 29.97 and uses hard FPS conversion. Chapter points are correct

A2: Using DSS2Mod with LAVFilters
MediaInfo recognizes the frame rate as 23.976, DSS2 removes the pulldown flags, and A2D will either use PAL speedup or 23.976 -> 25 pulldown. In both cases the chapter points are off (by about 4% with PAL speedup, much worse when using 23.976 -> 25 pulldown).

B: Telecined 25 -> 29.97
MediaInfo does not recognize the pulldown flags. A2D sees the source as 29.97 and will use hard FPS conversion. No problems with the chapter points.


Generally it looks like hard FPS conversions are handled correctly by the current implementation. When soft pulldown or speedup/slowdown gets used then the problems start. There are probably some more use cases which will need special attention, but right now I am not in the shape for more testing (my head is buzzing already...).


Cheers
manolito

[manolito]

A1: Using DGDecode
Pulldown flags are honored, A2D sees the source as 29.97 and uses hard FPS conversion. Chapter points are correct

A2: Using DSS2Mod with LAVFilters
MediaInfo recognizes the frame rate as 23.976, DSS2 removes the pulldown flags, and A2D will either use PAL speedup or 23.976 -> 25 pulldown. In both cases the chapter points are off (by about 4% with PAL speedup, much worse when using 23.976 -> 25 pulldown).


Realizing once again that NTSC is still a strange beast to me... :devil:
What is the "most correct" way to handle a progressive (film) NTSC clip which is encoded at 23.976fps with 3:2 pulldown flags?

In AVStoDVD the different source filters depend on the MediaInfo information. When DGIndex/DGDecode is used then the "Honor Pulldown Flags" option is set. AviSynth sees a 29.97fps clip which looks "interlaced" due to the repeated fields. For fps conversion to PAL framerate A2D uses the selected "hard" conversion method (default is MCJMFPS).

Is this a good way to do it? Or shouldn't DGIndex use the "Force Film" option instead to serve the 23.976 clip without the repeated fields to AviSynth?

//EDIT//
I had falsely assumed that AVStoDVD actively edits DGIndex.ini to make sure that "Honor Pulldown Flags" is set. This is not true, A2D does not touch the "Field Operation" setting. A user can change this setting to "Force Film" before starting AVStoDVD, and this will make sure that only the encoded frames without the repeated fields will be served to AviSynth.
//END EDIT//


The other method using DSS2Mod and LAVFilters also raises a few questions. In this case MediaInfo reports 23.976fps and 3:2 pulldown for the source clip. A2D adds the "fps=23.976" to the DSS2Mod source filter command. Does this command return the correct frames? Without the "fps=23.976" DSS2Mod would return a rate of 29.97 (like DGIndex with "Honor Pulldown Flags"). Is forcing 23.976 in the source filter command the equivalent of removing the pulldown flags? I have my doubts... I am afraid that DSS2Mod first decodes to 29.97 and afterwards just drops frames to reach the specified frame rate of 23.976.

BTW DirectShowSource and FFmpegSource behave the same way as DSS2Mod.


Whatever, I am mighty glad to live in PAL land where I do not have to deal with those things...


Cheers
manolito

[MrC]

Thanks manolito for the German translation and extensive testing. PAL<->NTSC conversions are a nightmare for many reasons, chapters affaire is just the top of the iceberg...

Now I just have to find a couple of hours to go thru your investigations and solve all (?) the possible fps conversion scenarios within the new OGG chapters import routine.

About the Peak Level Check feature, I agree with you that it would better trigger the AmplifyDB() instead of Normalize(). There is also the possibility to move that routine directly in the AviSynth tab > Audio > Amplify Audio option, as preliminary prompt to the user.

;)

Bye

[MrC]

The following hotfix (https://sites.google.com/site/avstodvdmain/AVStoDVD_288_Alpha180522_Hotfix.7z) should solve the chapters import sync issues in PAL<->NTSC conversions. And the Peak Level Check feature now triggers AmplifyDB(). And the 120011 Right-Click to manage Titles translation.

Still to manage the redirection of FFmpeg stderr to a VB variable.

;)

Bye

[manolito]

Thanks MrC, this is a major improvement... :thanks:

The Language file issue is fixed.

For OGG chapter file import for PAl -> NTSC conversions the pulldown issues as well as the speeddown issues are fixed.

For NTSC -> PAL I think that the PAL speedup thing is also fixed, but the whole NTSC -> PAL conversion routine does not work when the source is a progressive NTSC Film clip at 23.976 with pulldown flags (23.976 -> 29.97) added.

This has nothing to do with OGG chapter file import, this problem has been there for a long time. Most folks do not care, because all PAL players can handle NTSC sources these days, no need to convert to PAL.


For the FFmpeg stderr thing I think that it is not so important. I will add a quick batch command to my FFmpeg hack to disable and reenable the hack with one mouse click, so users can easily use the peak level check even when they have my plugins installed.

Right now when the Normalize option is active and the peak level check is performed, users may end up with a "normalize" command followed by a "AmplifyDB" command. After a successful peak level check the "normalize" command should be removed from the AVS script.


Cheers
manolito

[manolito]

the whole NTSC -> PAL conversion routine does not work when the source is a progressive NTSC Film clip at 23.976 with pulldown flags (23.976 -> 29.97) added.


Case studies:

Using DGIndex with "Honor Pulldown Flags" enabled (default):

The stream served to AviSynth will be (pseudo) interlaced. You can either IVTC it (a field matcher followed by a decimator), or you can deinterlace it. Otherwise you will have to treat it as "interlaced".

AVStoDVD does not do anything to such a stream, it falsely treats it as progressive. Any vertical resizing or using a filter with a spatial component will screw up the clip.


Using DGIndex with "Force Film" enabled:

For consistent pulldown flags this would be the correct option. But importing OGG chapter files fails with the current A2D version.


Using DSS2Mod or DirectShowSource or FFmpegSource:

For these source filters AVStoDVD uses the frame rate reported by MediaInfo of 23.976 and inserts this frame rate into the source filter call. MediaInfo also reports 3:2 pulldown flags, but A2D ignores this. So the source filters first serve the 29.97 (pseudo interlaced) stream to AviSynth, then the frame rate parameter causes frame drops to reach the specified frame rate. The result will still have interlaced frames, generally the quality will be pretty bad.

Users could edit the AVS script in A2D and remove the FPS parameters for the source filter. Then the source would be served as 29.97 to AviSynth, but (the same as DGDecode) the resulting (pseudo) interlaced stream is not handled correctly by AVStoDVD.


Cheers
manolito

[MrC]

The problem is there also when the PAL speedup routine is active along with a 23.976 progressive clips with 2:3 pulldown flags. Now I don't check if pulldown flags are present.

In these cases, what about applying the IVTC option (Edit Title > AviSynth > Enhance) to remove the pulldown flags? The output would be a true 23.976 progressive clip, to which we can apply soft pulldown (23.976->25) or 4% speedup. Currently IVTC option is greyed out for everything but 29.97 interlaced, but you can easily tweak the frame rate and scan type clip properties within A2D. And if it works, I can activate IVTC by default for this scenario (input NTSC 23.976 progressive clips with 2:3 pulldown flags, output PAL).

;)

Bye

[manolito]

Currently IVTC option is greyed out for everything but 29.97 interlaced,

Hi MrC,

I have to admit that I did not test the IVTC option at all since it was introduced by the end of 2016. Now that I looked into it I believe you should change some things about it...

Only allowing it for 29.97 interlaced sources is too limited. First of all not all 29.97 interlaced clips are hard telecined, they could just as well be "truly" interlaced without repeated fields. In such cases TFM will fail because there are no fields to match. MediaInfo is no help for hard telecined sources, it won't tell if there are repeated fields.

And then of course applying IVTC is a standard procedure for soft telecined NTSC sources, it should not be greyed out for such sources.

A general remark about the IVTC implementation:
Right now the following lines are present in the AVS script:
Video = Video.TFM.TDecimate
Video = Video.ConvertToYV12()
I believe that the IVTC commands should appear AFTER the ConvertToYV12 command, because TFM and TDecimate both only support YV12 and YUY2. And the commands should be "TFM()" and "TDecimate()", the brackets make it faster.


Now talking about these standard progressive 23.076 NTSC sources which have been encoded with 3:2 soft pulldown. How should A2D treat such clips?

From the Doom9 IVTC tutorial:
IVTC ADVICE

FOR NTSC PEOPLE: FORCE FILM WHEN YOU CAN. IVTC WHEN YOU CAN’T FORCE FILM. DEINTERLACE WHEN YOU CAN’T DO EITHER.

But before digging into this I believe it is necessary to talk about semantics to make the behavior of the different source filters consistent.

For such a clip MediaInfo reports "23.976fps, 2:3 pulldown, progressive". All software players and VirtualDub report 29.97fps. I believe that the MediaInfo fps detection is wrong.

The problem with A2D is that whenever DSS2Mod or DirectShowSource or FFmpegSource is used then the frame rate reported by MediaInfo is included in the call for the source filter. This will give incorrect results. If MediaInfo reports 2:3 pulldown then the frame rate for the source filter call should be 29.97 (or it could be omitted).

The reason for this incorrect behavior is that all the above source filters have no option to remove pulldown flags with a "Forced Film" option like DGIndex. They all honor the pulldown flags and serve a "pseudo-interlaced" output to AviSynth.

DGIndex has a "Forced Film" option. When this option is selected then the pulldown flags are removed and AviSynth gets a progressive 23.976 stream from DGDecode.


IMO the way AVStoDVD should address this difference between source filters is to always set the fps to 29.97 as soon as MediaInfo reports pulldown. This way the behavior of all source filters will be consistent (if the DGIndex field option is left at the default "Honor Pulldown Flags").


Now how can A2D follow the advices from the Doom9 IVTC tutorial? The preferred option is "Force Film". Only DGIndex/DGDecode can do this in A2D, and only if users change the "Field Operation" setting to "Forced Film" before starting AVStoDVD. With the default option "Honor Pulldown Flags" DGIndex/DGDecode will send a 29.97 pseudo-interlaced stream to AviSynth like the other source filters.

The next advice "IVTC if you can't force film" means that A2D should not grey out the IVTC option as soon as MediaInfo reports pulldown.

And the last option "Deinterlace if all else fails" means that A2D should not grey out the "Deinterlace" option if MediaInfo reports Pulldown. Right now deinterlacing is not possible for such sources unless the user changes the title properties from Progressive to Interlaced.



Alright, even more things to consider. All of the above only applies to 23.976 progressive sources with standard 3:2 pulldown. But A2D also supports "irregular" pulldown (23.976 -> 25, 24 -> 25, 25 -> 29.97). For such sources MediaInfo does not report the pulldown. So AVStoDVD will treat it as progressive 29.97 which causes terrible results when applying vertical resizing or spatial filters.

The question is if you want to deal with such "irregular pulldown" sources at all. There is no automatic way to do it since MediaInfo does not recognize the pulldown. Of course using "Forced Film" on such sources is desirable, but only experienced users would be able to detect such a source. IVTC would also work, but not with the default parameters. TDecimate would need custom parameters to retrieve the original frame rate.


Well, this post came out much longer than I anticipated, but the problems are real. No idea how important this stuff is for the "Average Joe" user since converting NTSC to PAL is mostly not necessary for users living in PAL land. And the PAL -> NTSC conversions do already work.


Cheers
manolito

[manolito]

In these cases, what about applying the IVTC option (Edit Title > AviSynth > Enhance) to remove the pulldown flags? The output would be a true 23.976 progressive clip, to which we can apply soft pulldown (23.976->25) or 4% speedup. Currently IVTC option is greyed out for everything but 29.97 interlaced, but you can easily tweak the frame rate and scan type clip properties within A2D. And if it works, I can activate IVTC by default for this scenario (input NTSC 23.976 progressive clips with 2:3 pulldown flags, output PAL).


Sorry I forgot to report my test results for this case in my last post...

Yes, IMO for such sources IVTC should be activated by default - or at least a popup window should appear informing the user of using IVTC or Deinterlace.
I did this, and the video is treated as it should. But OGG chapter import is still broken for this scenario.

My suggestion for how AVStoDVD should treat such sources (NTSC progressive 23.976 with standard 3:2 pulldown flags):

1. Always evaluate the MediaInfo report for Pulldown. If Pulldown is reported then set the fps to 29.97 (ignore the 23.976 MediaInfo report). Also set the title properties to Interlaced.

2. Suggest that IVTC or Deinterlace should be used. If the user decides that he does not want to use any of these then at least A2D will treat the source as "interlaced" to avoid major damage.

This will only work for sources with standard (23.976 -> 29.97) pulldown flags. Irregular pulldown flags are not recognized neither by MediaInfo nor by AVSMeter, so A2D has no way to treat sources with irregular pulldown automatically.

One small inconsisteny I noticed:
If IVTC is checked then A2D of course modifies the AVS script, it also (correctly) removes the "Interlaced Encoding" checkmark from the Video tab. But if "Deinterlace" is activated instead, only the AVS script is edited. Under the Video tab the setting for "Interlaced Encoding" stays active (which is wrong IMO). After applying deinterlacing the encoder should use progressive settings and the output should not be flagged as interlaced.


Now back to the original topic of importing OGG chapter files:

After a lot of additional tests I see the current situation as follows:

1. OGG chapter import ALWAYS works when hard frame rate conversion gets used.

2. PAL to NTSC does work correctly. Using 25 -> 29.97 pulldown works equally well as using NTSC slowdown first and then applying 23.976 -> 29.97 pulldown.

3. NTSC to PAL conversion does NEVER work except when hard frame rate conversion is forced (For progressive sources A2D only offers DGPulldown or PAL speedup by default). I tested IVTCed sources using PAL speedup as well as 23.976 -> 25 pulldown, the chapters were way off in both cases. Finally I used a progressive 23.976 source without soft pulldown, and the results for OGG chapter import were identical to the IVTCed source.

So for NTSC to PAL conversions the OGG chapter import still needs some work...


Cheers
manolito

[manolito]

For the FFmpeg stderr thing I think that it is not so important. I will add a quick batch command to my FFmpeg hack to disable and reenable the hack with one mouse click, so users can easily use the peak level check even when they have my plugins installed.


And here it is:

Toggle_Plugins.bat
@ECHO OFF

REM This batch file toggles the FFmpeg-Mod based plugins for AVStoDVD ON or OFF

REM Both the FFmpeg_VBR plugin and the Wavi_Mod plugin are affected at the same time.
REM To deactivate or activate the plugins separately you need to rename the files
REM "ff_vbr.bat" or "wavi_mod.bat" respectively.


REM You need to use this batch file to deactivate both plugins if you want to use
REM the new "Audio Peak Level Check" within AVStoDVD.

REM ==================================================================================


REG QUERY HKEY_CURRENT_USER\Software\AVStoDVD /v AppPath >"%temp%\$temp.txt"
FOR /F "usebackq tokens=2,*" %%a IN ("%temp%\$temp.txt") DO SET AppPath=%%b
IF EXIST "%temp%\$temp.txt" DEL "%temp%\$temp.txt"
CLS

:toggleRename
IF EXIST "%AppPath%\FFmpeg\ffmpeg.exe" IF EXIST "%AppPath%\FFmpeg\_ffmpeg.exe" GOTO deActivate
GOTO Activate

:deActivate
COLOR 4F
IF EXIST "%AppPath%\FFmpeg\ffmpeg.exe.mod" DEL "%AppPath%\FFmpeg\ffmpeg.exe.mod"
REN "%AppPath%\FFmpeg\ffmpeg.exe" ffmpeg.exe.mod
REN "%AppPath%\FFmpeg\_ffmpeg.exe" ffmpeg.exe
ECHO.
ECHO ÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜ
ECHO Ý ÚÄÄÄ¿Þ
ECHO Ý FFMPEG-MOD PLUGINS ARE NOW DE-ACTIVATED ³ X ³Þ
ECHO Ý ÀÄÄÄÙÞ
ECHO ßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßß
ECHO.
ECHO Both the FFmpeg_VBR and the Wavi_Mod plugins are
ECHO now turned OFF...
ECHO.
GOTO end

:Activate
COLOR 1F
IF NOT EXIST "%AppPath%\FFmpeg\ffmpeg.exe.mod" GOTO Notinstalled
IF NOT EXIST "%AppPath%\FFmpeg\ffmpeg.exe" GOTO Notinstalled
REN "%AppPath%\FFmpeg\ffmpeg.exe" _ffmpeg.exe
REN "%AppPath%\FFmpeg\ffmpeg.exe.mod" ffmpeg.exe
ECHO.
ECHO ÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜ
ECHO Ý ÚÄÄÄ¿Þ
ECHO Ý FFMPEG-MOD PLUGINS ARE NOW ACTIVATED ³ û ³Þ
ECHO Ý ÀÄÄÄÙÞ
ECHO ßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßß
ECHO.
ECHO Both the FFmpeg_VBR and the Wavi_Mod plugins are
ECHO now turned ON...
ECHO.
GOTO end

:Notinstalled
CLS
ECHO.
ECHO ÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜÜ
ECHO Ý ÚÄÄÄ¿Þ
ECHO Ý ERROR FFMPEG-MOD PLUGINS NOT INSTALLED ! ³ ! ³Þ
ECHO Ý ÀÄÄÄÙÞ
ECHO ßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßßß
ECHO.
ECHO You need to install the plugins first before you
ECHO can toggle them ON or OFF...
ECHO.

:end
PAUSE
EXIT


The file can reside anywhere on the HDD, users who want to do an Audio Peak Level Check need to run it before doing so.


Cheers
manolito

[thescrapyard]

I'm trying to add Russian subs to a project, tried extracting them from the source and also just let AVStoDVD automatically do the conversion but both ways come back with a sub error when it tries to add the subs into the output DVD

Also, it forces the subs into the final DVD, but all you get is a row of question marks where teh subs should be when playing the output DVD via PotPlayer, but the source plays the subs perfectly

The extracted subs are in Russian (Cyrillic font ??), maybe thats the issue. If I open the extracted subs .srt file in NotePad ++ the Russian text is all there and perfectly readable Russian characters



Attached is the file I'm trying to add back in as either AVstoDVD internal or as an added subs file. Either way the subs fail and are displayed as nothing but "?????????" on the video

[Groucho2004]

Attached is the file I'm trying to add back in as either AVstoDVD internal or as an added subs file. Either way the subs fail and are displayed as nothing but "?????????" on the video
Approval of the attachment could take a while, why don't you upload it somewhere else?

[MrC]

@thescrapyard

I guess the issue is related to the fact that SubtitlesCreator, the app used to convert from SRT to SUP, accepts only ANSI formatted text. If the input SRT file is formatted in UTF format (and your file should be like that), than A2D converts the content to ANSI. During conversion many special chars are lost, very likely cyrillic chars are lost as well.

BTW to be sure of that guess, let's wait for the russian subs file.

;)

Bye

[Groucho2004]

I guess the issue is related to the fact that SubtitlesCreator, the app used to convert from SRT to SUP, accepts only ANSI formatted text.A program that deals with subtitles and doesn't support UTF-8 is ridiculous.
Isn't there another free program that can do that?

[MrC]

A fresh 2.8.8 release hotfix is available to download (https://sites.google.com/site/avstodvdmain/AVStoDVD_288_Alpha180603_Hotfix.7z). It should address (very likely ;) all) the issues manolito has kindly and with expertise highlighted about NTSC to PAL conversions.

There's also an implementation of FFmpeg stderr capture within VB code. No more need to go thru an external text file.

;)

Bye

[manolito]

It should address (very likely ;) all) the issues manolito has kindly and with expertise highlighted about NTSC to PAL conversions.

Yes, this build does handle ALL the issues about NTSC to PAL conversions when importing OGM chapter files. Beautiful, this must have been a lot of work...

There's also an implementation of FFmpeg stderr capture within VB code. No more need to go thru an external text file.

This feature does not work (yet) when my FF_Mod hack is active. I get an error window telling me
Runtime error 5, Invalid procedure call or invalid argument

Please note that this is not an FFmpeg error, it is an AVStoDVD error message. Running the hacked FFmpeg version with the command line issued by AVStoDVD causes no problems.


Cheers
manolito

[MrC]

This feature does not work (yet) when my FF_Mod hack is active. I get an error window telling me
Runtime error 5, Invalid procedure call or invalid argument

Please note that this is not an FFmpeg error, it is an AVStoDVD error message. Running the hacked FFmpeg version with the command line issued by AVStoDVD causes no problems.

The new VB routine to grab stderr output tries to grab the ffmpeg.exe.mod (renamed to ffmpeg.exe) stderr, but a bat file with exe camouflage has no stderr output.

BTW I have added in the Peak Level Check routine few lines to check if there is _ffmpeg.exe and if yes, then _ffmpeg.exe will be called instead of ffmpeg.exe, only for that scope.

Hotfix (https://sites.google.com/site/avstodvdmain/AVStoDVD_288_Alpha180605_Hotfix.7z)

;)

Bye

[manolito]

BTW I have added in the Peak Level Check routine few lines to check if there is _ffmpeg.exe and if yes, then _ffmpeg.exe will be called instead of ffmpeg.exe, only for that scope.

Thanks MrC for this hotfix, and yes, it does of course fix the issue... :cool:

But I have the feeling that you are not all that eager to employ such workarounds (I wouldn't for sure). In the end it all comes down to another ugly rant about how the FFmpeg devs handle things...

Why in the world can't they just add a "logfile" parameter where users can specify a file location and name just like everybody else does? Instead they use stderr which must be redirected to a file. Even this is not done well, normally one would expect that only errors end up in stderr, the normal progress logging should go to stdout instead. But whatever, these guys will do what they want anyways, maybe they need to do it this way because FFmpeg needs to be multi-platform.

In this special case the executable which actually writes to stderr is the grandchild of the executable which A2D actually calls. Is there a way in VB6 to intercept stderr output of child or grandchild processes? Probably not...

For my audio analyzing needs I usually use BS1770Gain. For decoding it is based on FFmpeg, but it writes its results to a file directly, and it analyzes peak level and BS1770 (EBU R128) levels in one single pass. It is part of my Wavi_Mod plugin.


For the peak level analysis I do have one more request. Right now A2D offers to bring up the audio level to 0dB. If the final result is uncompressed PCM then this is fine. But for MP2 or AC3 output you should never go up to 0dB, a little headroom of at least 1dB is required.

For the old A2D normalizing there is a setting to only normalize to a lower value. But this value is a percentage, while the FFmpeg analysis and the AmplifydB command use Decibels. There is no linear relationship between these two, so it will be difficult to take the percentage (like 0.95) from the A2D audio settings and apply this reduction to the dB value of Amplifydb - like AmplifydB(FFmpeg peak result - 1). Maybe you should give up on the old AviSynth normalize altogether and instead use FFmpeg analysis -> AmplifyDB exclusively.


Cheers
manolito

[manolito]

Two more issues found with the Audio Peak Level detection...
(This time it is not related to the FFmpeg-Mod hack)

1. If a title has more than 1 audio track then after analyzing the second track A2D will throw an error message:
Error 5 Invalid Procedure Call or Invalid Argument

2. If the title has been trimmed using the AviSynth tab then the selection will not be honored by the analysis. FFmpeg will analyze the whole audio track without regard to the selection.


Cheers
manolito

[MrC]

@manolito

the 1st issue has uncovered some weaknesses in general management of multiple audio tracks. A good amount of code lines has been refactored ;) The 2nd issue was way easier to fix.

See the new hotfix (https://sites.google.com/site/avstodvdmain/AVStoDVD_288_Alpha180623_Hotfix.7z).

As you suggested, I'm thinking about to drop classic AviSynth normalization and keep only the Peak Level Check + AmplifyDB routine. That's a more lean approach, I like the idea to drop the normalization option in Edit Title sections... but I would have to drop the normalization option in Preferences too... Still have to digest it ... I'm an old conservative man... and some users with the habit to normalize the world may complain. Do you have any advise?

;)

Bye

[manolito]

Hi MrC,

sorry for the late reply, but I just got back from my annual motorcycle trip. It was Scotland this time, real nice, and we had the greatest weather...

Just did some quick tests with the new hotfix, so far no problems...

There is a small cosmetic thing when detecting the audio peak for 2 audio tracks. The detection works nicely now, and the 2 AVS scripts use the correct gain values. Only under the Audio tab the displayed gain value is always the value of the last detection. Switching to the other audio track has no effect on the displayed gain value (under the AviSynth tab the different gain values are displayed correctly according to the selected audio track). Just cosmetic and probably easy to fix...

The audio range parameters in the detection command also work nicely, even though I do not really understand why the number of audio frames is different from the number of video frames in the trim command.


For the general normalization concept I do not really have any opinion. I suppose that you want to stick with the simple peak normalization (as opposed to ReplayGain or EBU R128 normalization or even Dynamic Range Compression).

In this case AviSynth normalization and peak detection/amplifydb are redundant, I would prefer ditching AviSynth normalizing. Under Preferences you could leave the normalize option, just change the target value from percentage to dB. If the user has normalization ticked under Preferences and does not explicitly do a peak level check then just do the peak check plus amplifydb silently (of course subtracting the target dB which was specified under Preferences). If the user does the peak level check then let the user decide if he wants to alter the gain or not, just like it works now. This should of course override the normalize setting under Preferences.

This should satisfy even users who want to normalize the world... :p But mostly these users do not really understand the concept of normalizing, they falsely assume that peak normalizing will result in a constant loudness.


Thanks again for your work,
Cheers
manolito

[MrC]

Hi manolito,

I'm sure your trip in Scotland was memorable and finding good weather in Great Britain is a nice fluke!

Thanks for testing the new alpha. The cosmetic bug is quickly fixable. We agree that simple peak detection and avisynth normalization are redundant. Very likely I will drop Normalize in Edit Title > Audio. I think the more convenient way is to erase the Normalize option and to move the peak level check in the AviSynth tab, under Amplify Audio option. It will be a bit hidden, but I would say more elegant. Then, as you suggest, I can leave the Normalize option in Preferences > Audio (with a target dB textbox), to trigger the peak level check at runtime during project execution.

I think this approach is more streamlined and fine for standard users. More sophisticated users can still use manolito's ReplayGain or EBU R128 normalization extensions.

;)

Bye

[manolito]

Yes, totally agreed...
Looking forward for the next Alpha.


Cheers
manolito

[manolito]

Here is a slightly updated version of my plugin package for AVStoDVD. The download link is at the bottom of this post:
https://files.videohelp.com/u/172211/Manolito_s%20A2D%20Plugins.7z

Changes:
1. Added a new audio mode to the Wavi_Mod plugin. Now there is a new Dynamic Range Compression (DRC) mode using SoX. The parameters were taken from MkvToMp4 by oreons, I like the results very much. Optional EBU R128 postprocessing is available.

2. Added the file "Toggle_Plugins.bat". By executing this batch file both my FFmpeg based plugins (FF_VBR and Wavi_Mod) can be disabled or reenabled completely with one mouse click.

3. Updated documentation


Cheers
manolito


//EDIT//
Hardened the Wavi_Mod script against file names containing an exclamation mark. Please redownload...

[manolito]

I have a request for changing the handling of FFmpegSource...

It seems that many versions of ffms2 have a problem when fpsnum/fpsden are used to guarantee CFR output. A recent discussion was started here:
https://forum.doom9.org/showthread.php?p=1845939#post1845939

AVStoDVD is only rarely affected, but generally the safest workaround is to abandon the fpsnum/fpsden parameters completely and instead use ChangeFPS following the ffvideosource call. (I know that it was me pushing the use of fpsnum/fpsden, but this was before the issues became apparent).

For AVStoDVD this will require two changes:
1. The A2DSource.avsi must be changed. An updated file is here:
https://www.sendspace.com/file/7b2tux

2. If FFmpegSource is specified under "Preferences" then the A2D executable must be changed like this:
This script line
Video = FFVideoSource("F:\Download\2 source.avi", track=-1, fpsnum=2997, fpsden=100, seekmode=0)
must become this
Video = FFVideoSource("F:\Download\2 source.avi", track=-1, seekmode=0).ChangeFPS(2997, 100)


Cheers
manolito

[MrC]

Thanks manolito for the plugins update and for the suggestion how to improve the handling of FFMS. I will have a look very soon. Meanwhile I have updated a new Alpha (https://sourceforge.net/projects/avstodvd/files/avstodvd_alpha_beta/AVStoDVD%202.8.8%20Alpha%20180706/) with the latest fixes.

;)

Bye

[manolito]

Thanks for the new Alpha,

did a couple of tests already, everything is fine so far...


Cheers
manolito

[manolito]

I found an issue with all versions of ffms2 with AAC-LATM audio streams. Unfortunately this evil audio format is one of the standards for German DVB-T2 broadcasts.

I posted the detailed problem plus a sample file here:
https://forum.doom9.org/showthread.php?p=1846272#post1846272

According to qyot27 a (sort of) working solution would be to index the source manually before calling ffaudiosource. But still the second audio track cannot be accessed.

LAVFilters have no problems with this audio format. But unfortunately AVStoDVD can only access the first audio track with DirectShowSource. For the second audio track ffmpegsource must be used.

I think that only very few users will be affected by this issue, it is probably not worth spending any time to fix it.


Cheers
manolito


//EDIT//
Turned out that it was surprisingly difficult to find a workaround for such sources to make them work in AVStoDVD. It is easy if you only need the first audio track, but if the second track is also needed (and you want audio to be in sync) then only methods which do not use AviSynth for audio seem to work.

Specifying "FFmpeg Safe Mode" under preferences works, but there is no way to process audio. The other option is to use FFmpeg to preprocess the source. I use dmMediaConverter as the front end for FFmpeg. Repacking the source to MKV, using copy mode for video and converting both audio tracks to AC3 did the trick. The front end makes it easy to use built-in FFmpeg audio filters, and the AC3 encoder is first rate. Then feed the resulting MKV to AVStoDVD and use Direct Stream Copy for the audio tracks. This is my preferred method.

[MrC]

I have a request for changing the handling of FFmpegSource...

It seems that many versions of ffms2 have a problem when fpsnum/fpsden are used to guarantee CFR output. A recent discussion was started here:
https://forum.doom9.org/showthread.php?p=1845939#post1845939

AVStoDVD is only rarely affected, but generally the safest workaround is to abandon the fpsnum/fpsden parameters completely and instead use ChangeFPS following the ffvideosource call. (I know that it was me pushing the use of fpsnum/fpsden, but this was before the issues became apparent).

For AVStoDVD this will require two changes:
1. The A2DSource.avsi must be changed. An updated file is here:
https://www.sendspace.com/file/7b2tux

2. If FFmpegSource is specified under "Preferences" then the A2D executable must be changed like this:
This script line

must become this


Cheers
manolito

I have had a quick look to the mentioned thread, and, frankly speaking , I would not alter the current A2D code to deal with similar AVI titles. Also, the approximation to use 2997/100 config should be safer than the more accurate 30000/1001 ;)

I found an issue with all versions of ffms2 with AAC-LATM audio streams. Unfortunately this evil audio format is one of the standards for German DVB-T2 broadcasts.

I posted the detailed problem plus a sample file here:
https://forum.doom9.org/showthread.php?p=1846272#post1846272

According to qyot27 a (sort of) working solution would be to index the source manually before calling ffaudiosource. But still the second audio track cannot be accessed.

LAVFilters have no problems with this audio format. But unfortunately AVStoDVD can only access the first audio track with DirectShowSource. For the second audio track ffmpegsource must be used.

I think that only very few users will be affected by this issue, it is probably not worth spending any time to fix it.


Cheers
manolito


//EDIT//
Turned out that it was surprisingly difficult to find a workaround for such sources to make them work in AVStoDVD. It is easy if you only need the first audio track, but if the second track is also needed (and you want audio to be in sync) then only methods which do not use AviSynth for audio seem to work.

Specifying "FFmpeg Safe Mode" under preferences works, but there is no way to process audio. The other option is to use FFmpeg to preprocess the source. I use dmMediaConverter as the front end for FFmpeg. Repacking the source to MKV, using copy mode for video and converting both audio tracks to AC3 did the trick. The front end makes it easy to use built-in FFmpeg audio filters, and the AC3 encoder is first rate. Then feed the resulting MKV to AVStoDVD and use Direct Stream Copy for the audio tracks. This is my preferred method.

That's weird because it could become a general issue if the AAC-LATM standard will become popular. Do you know if qyot27 has plans to finally fix that?

An actual workaround for A2D could be to demux the 2nd (and above) track when a containing title is added. Not very elegant indeed. By the way I can add an entry to the FAQ/Audio section.

;)

Bye

[manolito]

I have had a quick look to the mentioned thread, and, frankly speaking , I would not alter the current A2D code to deal with similar AVI titles. Also, the approximation to use 2997/100 config should be safer than the more accurate 30000/1001 ;)

I agree, most A2D users will never be affected by this ffms2 issue. BTW is there any situation at all where A2D will issue 1001 as the denominator? Because only then there is a problem. Using 23976/1000 works while 24000/1001 does not.

Whatever, what really bugs me is that there is no error message at all, you only see the problem if you step through the frames. And it must be a pretty stupid error because the old version 2.17 of ffms2 behaves just fine.

That's weird because it could become a general issue if the AAC-LATM standard will become popular. Do you know if qyot27 has plans to finally fix that?

An actual workaround for A2D could be to demux the 2nd (and above) track when a containing title is added. Not very elegant indeed. By the way I can add an entry to the FAQ/Audio section.

;)

Bye

I have no idea if qyot27 cares for this problem at all. ffms2 depends on a couple of external libraries and headers, he has no control over these assets.

Demuxing the 2nd and above audio tracks does not work within A2D. FFmpeg tries to save the AAC-LATM audio tracks as standard AAC tracks, and this is not supported. The demuxed tracks come out totally silent.


Cheers
manolito

[MrC]

BTW is there any situation at all where A2D will issue 1001 as the denominator? Because only then there is a problem. Using 23976/1000 works while 24000/1001 does not.

1001 is never used within A2D code ;)

Demuxing the 2nd and above audio tracks does not work within A2D. FFmpeg tries to save the AAC-LATM audio tracks as standard AAC tracks, and this is not supported. The demuxed tracks come out totally silent.

Got it. Do you have a small sample with AAC-LATM audio track?

Thanks

;)

Bye

[manolito]

Got it. Do you have a small sample with AAC-LATM audio track?

Thanks

;)

Bye

Sure, the link still works...
https://www51.zippyshare.com/v/KY10rZkC/file.html

It is not just this file, it applies to all captured files from stations which use AAC-LATM. About half of the public broadcasters in Germany use this audio format, the other half use E-AC3. Since you fixed A2D recently so it no longer confuses E-AC3 with standard AC3 these captures do work nicely with A2D.


Cheers
manolito

//EDIT//
When I said that mts files with E-AC3 audio tracks work nicely in A2D I forgot to mention that audio delay correction is a little bit tricky with such transport streams (could well be an issue with MediaInfo). The reported delay may be something like -1500 ms for both audio tracks. For a perfect result the delay correction for the first track (the one which is decoded with DirectShowSource) must be disabled. For the second track (the one which gets decoded by ffms2) the delay correction must be applied, but it needs to be reversed. So the "-" sign in the "DelayAudio" command has to be removed.

//EDIT2//
It gets even more confusing. The above behavior only applies when the A2D default settings are used, i.e. DSS2Mod/LavFilters for video, DirectShowSource/LAVFilters for the first audio track and FFmpegSource for the second audio track. If the user forces FFmpegSource for video and audio under "Preferences" then the audio delay correction must be disabled for both audio tracks. Weird...

[MrC]

Sure, the link still works...
https://www51.zippyshare.com/v/KY10rZkC/file.html


Could you upload the file elsewhere? When I click on "Download Now" from zippyshare site, I have to download and install first the app "MessengerTime"... I really don't...

;)

Bye

[manolito]

Sorry for the zippyshare trouble. I always use a custom hosts file from
winhelp2002.mvps.org/hosts.htm
so I never experienced these issues.

You can get the file here:
https://www.zeta-uploader.com/2097415887
and here:
https://we.tl/8EraIY43vo

Let me know if you also need a captured mts file with E-AC3 audio.


Cheers
manolito

[MrC]

Hi manolito, zeta-uploader works ;)

Yes, please, upload the mts with e-ac3 too

;)

Bye

[manolito]

No problem, here it is:
https://www.zeta-uploader.com/2130213520

Unfortunately I could not find a station which broadcasts with 2 different audio languages at the moment.


Cheers
manolito

[MrC]

About the mts with aac-latm, switching to FFmpeg Safe Mode for audio encoding is the better workaround. With FFmpeg Safe Mode the audio delay is ignored, and for this capture is the right thing. Somehow MediaInfo is exposing a wrong delay.

I have found that remuxing the mts to mkv has some benefits: the filesize decreases a lot (padding within the mts?) and FFMS2 is now able to decode the 2nd aac track. In this case, major drawback, the audio delay is messed up even more. Again, FFmpeg Safe Mode with the remuxed mkv works as well.

Still to test the mts with e-ac3

;)

Bye

[manolito]

About the mts with aac-latm, switching to FFmpeg Safe Mode for audio encoding is the better workaround. With FFmpeg Safe Mode the audio delay is ignored, and for this capture is the right thing. Somehow MediaInfo is exposing a wrong delay.

This is what I said in my first post about the problem:
Specifying "FFmpeg Safe Mode" under preferences works, but there is no way to process audio.
This may be all which most users need, but others like me really like to be able to manipulate the audo tracks.

I have found that remuxing the mts to mkv has some benefits: the filesize decreases a lot (padding within the mts?) and FFMS2 is now able to decode the 2nd aac track. In this case, major drawback, the audio delay is messed up even more. Again, FFmpeg Safe Mode with the remuxed mkv works as well.


I agree, I always do this with HEVC transport streams, but mainly for the video track. None of the available source filters does a decent job seeking within such sources. Finding the right cut points when trying to cut out parts is painful. MKV is a much better format to do this.

Great that you found out that ffms2 can decode AAC-LATM when it is in an MKV container, I did not have this situation on my screen. And the messed up audio delay actually is not too challenging. You just need to use the delay value reported by MediaInfo, only reverse the prefix. Just remove the "-" prefix from the "DelayAudio" command.

My take on the whole issue is that such captured transport streams always have non-decodable B-Frames at the beginning. And all the available source filters have different ways how they treat these non-decodable frames. Luckily we only need to deal with DirectShow based source filters and ffms2 (Donald Graft handles such sources differently again).


Cheers
manolito

[manolito]

I am trying to find a fool proof work flow for such captured MTS transport streams which allows me to add audio filters and does not have any audio delay problems. And I believe that I found such a work flow... ;)

These are the steps:
1. Repack the source to MKV while converting the audio tracks to PCM. Here is a universal FFmpeg command line for this task:
ffmpeg.exe -fflags +genpts -y -i "ONE.mts" -map 0:0 -c:v:0 copy -aspect:v:0 16:9 -map 0:1 -c:a:0 pcm_s24le -map 0:2 -c:a:1 pcm_s24le -shortest "ONE.mkv"

2. In AVStoDVD preferences disable audio delay correction AND force FFmpegSource for video and audio.

So far I tested 6 different captured sources, and they all came out in perfect sync. During the remuxing to MKV there are dozens of FFmpeg warnings at the beginning, but the garbled non-decodable frames are removed perfectly.


Cheers
manolito

[MrC]

@manolito

great, thanks for sharing the workflow

;)

Bye

[manolito]

New versions of my A2D plugins...
https://files.videohelp.com/u/172211/Manolito_s%20A2D%20Plugins.7z

Changes:
For the FF_VBR and the HC_Mod plugins I added an option to append a Prefetch() command to the end of the AVS script generated by AVStoDVD. This is for users of AVS+ who want to automatically enable multithreading.


Cheers
manolito

[thescrapyard]

Bit of a strange error/bug here

Setting up a project everything is fine, but if I save any project then load it again, a few lines have been added onto the end of the avisynth scripts which then causes it to fail with a script error

I've tried literally running AVStoDVD, setting up a very simple project and saving it without touching any settings or fiddling with anything. Loading the project straight back into AVstoDVD gives the extra lines

No ideas where they are being added from, or why

All that has been done is use the A2DPlugins for FFMPEG, HCEnc and WAVI mods. These have always worked perfectly

The scripts still work as they should, BUT the extra lines have to be removed first from any loaded project or it fails with an error

The lines added to the end of AVISynth scripts for any project that has been saved and then loaded are :

AVSDelayAudio1: 0
AudioDelay1: 0
AVSAmplifyAudio1: 0
AudioAmplify1: 1

But I haven't changed any settings. Just tried saving a job list then loading it. Nothings changed, so seems to be an issue with saving and loading projects only


Thanks

[manolito]

This post is in the wrong thread. It should be moved to the "AVStoDVD Support Thread". Can a moderator please move the post...
[moved from Avisynth+ thread]

But you are right, you have discovered a bug in the latest AVStoDVD versions. I can confirm it under version 2.8.8 Alpha, I have no idea when this regression was introduced. I also tested if my plugins have anything to do with it, but they don't.

Some work for MrC... :devil:


Cheers
manolito


//EDIT//
This regression was introduced with version 2.8.8 Alpha. Probably issues with the new code which was needed for the audio peak level detection. Going back to version 2.8.7 stable solves the problem.

[MrC]

Yes, there's a load project routine section not updated after the introduction of the peak level detection feature. My bad. I will fix it asap, together with a better management of the peak level stuff.

Thanks for the report.

;)

Bye

[thescrapyard]

Yes, there's a load project routine section not updated after the introduction of the peak level detection feature. My bad. I will fix it asap, together with a better management of the peak level stuff.

Thanks for the report.

;)

Bye



Thanks. At least it wasn't me messing about with things again

[manolito]

@MrC

Sorry I have to bug you with another request to change the A2D behavior for progressive 23.976 clips with pulldown flags... :eek:

Turns out that some of my previous findings about source filter behavior for such sources were wrong.
https://forum.doom9.org/showthread.php?p=1850321#post1850321

These statements are not true:
The problem with A2D is that whenever DSS2Mod or DirectShowSource or FFmpegSource is used then the frame rate reported by MediaInfo is included in the call for the source filter. This will give incorrect results. If MediaInfo reports 2:3 pulldown then the frame rate for the source filter call should be 29.97 (or it could be omitted).

The reason for this incorrect behavior is that all the above source filters have no option to remove pulldown flags with a "Forced Film" option like DGIndex. They all honor the pulldown flags and serve a "pseudo-interlaced" output to AviSynth.

I recently did some more thorough tests about source filter behavior for such sources, have a look here:
https://forum.doom9.org/showthread.php?p=1850321#post1850321

Mainly AVStoDVD should use these procedures for the different source filters:

1: DGIndex / DGDecode
Basically leave it as it is. Only add the D2V parameter to the TFM call like:
TFM(d2v="my_d2v_file").TDecimate()

2: FFmpegsource
Use 23.976 as the fps value. Do not invoke IVTC

3: DSS2Mod and DirectShowSource
Use 23.976 as the fps value. Do not invoke IVTC


FFmpegSource does not honor the pulldown flags. When called without fpsnum/fpsden it will decode to 23.976.

DSS2Mod and DirectshowSource when called without an "fps=" parameter will decode to 29.97. But this is misleading because it does not honor the pulldown flags. Instead it decodes to 23.976 first and then adds duplicate frames to reach the 29.97 frame rate. Quite stupid. A2D should add the "fps=23.976" parameter to avoid this stupid behavior.


Alright, you won't like these new findings, I apologize for having misled you. The DSS2Mod/DirectShowSource way of outputting 29.97 but with dupes instead of repeated fields got me on the wrong track.


Cheers
manolito

[manolito]

Bug report for the latest version 2.88 Alpha
-------------------------------------------------

When converting a PAL progressive DVD title (in an MKV container) to NTSC with HCenc, then AVStoDVD applies pulldown twice. First by putting "*PULLDOWN" into the HC.ini, then again by using DGPulldown. I think that doing this only once would be better... :devil:

Here is the relevant part of the log:
<06.09.2018 01:35:25>
START VIDEO ENCODING OPERATIONS
Video Encoding Profile: HCenc VBR 1-pass
Target Video FileSize: 4180 MB
Encoding Parameters: -ini "D:\DVD_test.HCenc.ini"
HCenc ini file:
*INFILE D:\DVD_test_1.avs
*AVSRELOAD
*OUTFILE D:\DVD_test.m2v
*LOGFILE D:\DVD_test.HCenc.log
*MAXBITRATE 8724
*1PASS
*BITRATE 5580
*PROFILE NORMAL
*ASPECT 16:9
*PROGRESSIVE
*TFF
*PULLDOWN
*BIAS 60
*DC_PREC 9
*MATRIX MANONO1
*AQ 2
*LUMGAIN 2
*SMP
*PRIORITY IDLE
*DBPATH D:
*WAIT 2
<>

<06.09.2018 01:49:41>
END VIDEO ENCODING OPERATIONS
Video Source Filter: A2DSource - DSS2 mod (LAV Filters on)
Created File: D:\DVD_test.m2v (4182,2 MB)
Ouput Video Info: MPEG-2 Video - 5583 kbps - 720x480 - DAR 16:9 - 29,97 fps - Progressive (2:3 Pulldown) - 1:44:44 hours - 188318 frames
Avg Video Encoding Speed: 223,4 fps
<>

<06.09.2018 01:49:41>
START PULLDOWN OPERATIONS
DGPulldown Parameters: "D:\DVD_test.m2v" -srcfps 29.97 -destfps 29.97 -inplace -tff
<>

<06.09.2018 01:51:49>
END PULLDOWN OPERATIONS
DGPulldown executed on File: D:\DVD_test.m2v (4182,2 MB)
Output Video Info: MPEG-2 Video - 6979 kbps - 720x480 - DAR 16:9 - 29,97 fps - Progressive (TFF) - 1:23:47 hours - 150656 frames
<>

<06.09.2018 01:51:59>
Process halted during Title 1 VIDEO encoding operations.

Error Message: 'Warning! Title 1 output Video duration (01:23:47) is shorter than expected duration (01:44:44).'

This issue might have been there for a while, I do NTSC conversions only rarely.


Cheers
manolito

[MrC]

@manolito

back from job marathon...

Thanks for the bug report about the double pulldown procedure. It was a recent entry, after the re-definition of NTSC progressive w/ pulldown flags framerate as 29.97 (2:3 pulldown) instead of 23.976 (2:3 pulldown). Very easy to fix.

About the other post (https://forum.doom9.org/showpost.php?p=1850490&postcount=3135), I will take a careful look. My time for A2D is running so low that I have to be absolutely sure in making changes to the code in order not to insert more damages than gains. I'm sure you can understand. From the link you reported (https://forum.doom9.org/showthread.php?p=1850321#post1850321) the discussion was way long: after sept 3rd (your post here), solutions #1, #2, #3 are still valid from your more recent findings?

;)

Bye

[manolito]

Hi MrC,

good to see you back after more than a month (I had hoped that you were on a nice and long vacation...).

For the NTSC progressive with pulldown sources, yes, the 3 solutions are still valid, but only #1 is really fool proof. DSS2Mod and ffms2 have problems with such sources no matter which settings are used.

If the MPEG2 video is in an MKV container, the MKV should probably be demuxed first, then use DGIndex/DGDecode for the video and add the other streams manually. Mr. Graft indicated in the linked thread that he might expand DGIndex to support MPEG2 in an MKV container, but I have no idea if this will materialize.

For ffms2 a working solution is to add "RFFMode=1" to the command line which will honor the pulldown flags. But the field order needs to be the reverse value of the DGIndex field order. Not something the average user wants to deal with.


Another thing you might want to add to the next stable version is AVS+ support. I have been using it on my Core i5 laptop for some time now without any issues. It was requested by steptoe at VideoHelp, see here:
https://forum.videohelp.com/threads/277852-AVStoDVD-Support-Thread/page124#post2526075

It basically comes down to adding a "Prefetch" call at the end of the AVS script after detecting if AVS+ is installed. The number of threads can be determined automatically, Myrsloik proposed this formula:
max(physical cores, min(logical threads, 8))

I have already integrated it into my FF_VBR and HCenc_Mod plugins, but most folks probably do not use them... :devil:


Cheers
manolito

[SuLyMaN]

@mrc Heh man It's been a while since I posted there as I simply am not making an DVDs at the moment. I have shifted to converting my stuffs and watching them on TV via a TV Box.
So, until I need the wonderful piece of free software that is AVStoDVD, a big thank you for the work. Top level software!

[manolito]

Just found another bug when dealing with clips with more than 1 audio tracks:

With the default source configuration (A2DSource) DirectShow will be used for audio. But only for the first audio track, because DirectShowSource does not allow track selection. The second and third audio tracks will use FFmpegSource because it allows track selection.

This works nicely as long as DirectShowSource picks the first audio track of the source clip. But I found that this is not always true. The sample clip from this post
https://forum.doom9.org/showthread.php?p=1854124#post1854124
has 3 audio tracks, and the second one is marked as "default". For this clip DirectShowSource will pick the second (default) audio track as the first audio track, and A2D will throw an error because the number of channels is different for the two tracks.

The only workaround I can think of so far is to not use DirectShowSource Audio at all for such sources, force using FFmpegSource instead. This will treat the track numbers correctly, but the "Default" audio track flag will be lost. Does MPEG2 even support this flag at all?


Cheers
manolito

[thescrapyard]

Just found another bug when dealing with clips with more than 1 audio tracks:

With the default source configuration (A2DSource) DirectShow will be used for audio. But only for the first audio track, because DirectShowSource does not allow track selection. The second and third audio tracks will use FFmpegSource because it allows track selection.

This works nicely as long as DirectShowSource picks the first audio track of the source clip. But I found that this is not always true. The sample clip from this post
https://forum.doom9.org/showthread.php?p=1854124#post1854124
has 3 audio tracks, and the second one is marked as "default". For this clip DirectShowSource will pick the second (default) audio track as the first audio track, and A2D will throw an error because the number of channels is different for the two tracks.

The only workaround I can think of so far is to not use DirectShowSource Audio at all for such sources, force using FFmpegSource instead. This will treat the track numbers correctly, but the "Default" audio track flag will be lost. Does MPEG2 even support this flag at all?


Cheers
manolito

I thought it was me, but I've had this issue a few times with multiple audio tracks

I also had issues with sometimes you end up with the default audio track which may not be the audio track you actually want, even though you chose something different as the ONLY audio track. I found the easiest way aroudn this problem was to use MKVToolnix and just strip what audio you don't want and try again ...

[imsrk48]

how to make any mkv or mp4 into DVD player playable format??

[manolito]

Download AVStoDVD (the installer version), install the required helper software if it's not already installed (AviSynth, LAVFilters, optionally IMGBurn), then install AVStoDVD. Leave all settings at their defaults for now.

Have a look at the documentation to familiarize yourself with the GUI interface. Load your source file(s) and click "Start".

If AVStoDVD is too complicated for you, I suggest to try DVDFlick v2 (get it at VideoHelp). It is based on FFMpeg, very easy to use and delivers more than acceptable quality.


Cheers
manolito

[imsrk48]

Thanks buddyDownload AVStoDVD (the installer version), install the required helper software if it's not already installed (AviSynth, LAVFilters, optionally IMGBurn), then install AVStoDVD. Leave all settings at their defaults for now.

Have a look at the documentation to familiarize yourself with the GUI interface. Load your source file(s) and click "Start".

If AVStoDVD is too complicated for you, I suggest to try DVDFlick v2 (get it at VideoHelp). It is based on FFMpeg, very easy to use and delivers more than acceptable quality.


Cheers
manolito

[manolito]

Found a tiny little issue in the latest non-public Alpha:

The WEBM format was added a short while ago to the officially supported formats. Works perfectly when opening source files, but under "Tools/Demux" the WEBM extension is not included in the "all supported formats" file mask. Adding a WEBM file by specifying a "*" character in the "file open" field works fine, the file gets demuxed perfectly.


Cheers
manolito

[manolito]

And another year is almost over...

A Merry Christmas and a Happy New Year to everone,

Cheers
manolito

[Sir Didymus]

Best wishes from my side too, to you Manolito, for the impressive contributions you have given in the years to the doom9 community, to MrC for the great work of coding and support on AVStoDVD, to all forum users and your families...

Cheers,
sd

[MrC]

@manolito

thanks for the tiny bug report... final 2.8.8 should see the light before New Year's Eve ;)

@manolito, SD, all

happy holidays to everybody, I wish you all the best for the upcoming 2019

;)

Bye

[MrC]

OK, 2.8.8 final release is out (https://sourceforge.net/projects/avstodvd/files/avstodvd/AVStoDVD%202.8.8/).

No major updates from latest 2.8.8 alpha. Cumulative change log from 2.8.7:

- Some bugs fixed
- Added 'Audio Peak Level Check' feature in 'Title Edit'/'AviSynth'/'Audio'/'Delay Audio' option
- Added support to OGG chapters txt format (timestamps) in 'Title Edit'/'Chapters'/'Import Chapters' routine
- Added management of 'Default=Yes/No' audio and subs tracks tags from MediaInfo, instead of assuming that 1st track is the default one
- Improved 'Title Edit'/'Chapters'/'Export Chapters' routine
- Improved source chapters detection routine (now it works again for IFO/DVD files)
- Improved handling of NTSC progressive sources with pulldown flags
- MKVToolNix updated to release 23.0.0
- MediaInfo updated to release 18.03
- LAV Filters updated to release 0.73.1

;)

Bye

[manolito]

Thanks very much MrC, works beautifully... :thanks:

And again a happy new year to you and your family, hopefully with a little less stress.


Cheers
manolito

[manolito]

Small request for the next version:

For high bitdepth sources the current ffms2 versions need the parameter colorspace="YV12". Without this parameter it quits with the error message that it cannot find a suitable output format.

Since A2D always needs YV12 output it won't hurt to specify this parameter no matter what the soure bitdepth is.
The last ffms2 version which works without the colorspace parameter is ffms2_r1140+101-avs+vsp.7z. Download here:
https://forum.doom9.org/showthread.php?p=1783312#post1783312


Cheers
manolito

[Emulgator]

Many thanks to all for the continuous work !
System here: Win7U64 SP1, Avisynth is used in the Repository form
(no vanilla install at the usual place, rather switchable between 6 versions in separate folder by .bat file (Groucho2004 system)

I am just trying A2D 2.8.8 and it won't find any Avisynth installation, warns that it would be missing.

While my external AvsMeter 2.9.0 finds and reports all Avisynth versions I switch to.

Maybe somebody can enlighten me.

[Groucho2004]

Many thanks to all for the continuous work !
System here: Win7U64 SP1, Avisynth is used in the Repository form
(no vanilla install at the usual place, rather switchable between 6 versions in separate folder by .bat file (Groucho2004 system)

I am just trying A2D 2.8.8 and it won't find any Avisynth installation, warns that it would be missing.

While my external AvsMeter 2.9.0 finds and reports all Avisynth versions I switch to.

Maybe somebody can enlighten me.The problem is the Avisynth detection routine in AVStoDVD. It's very error prone and should be replaced. Since MrC is already using AVSMeter to detect clip properties it would be easy to also use it to detect the Avisynth version reliably -> "avsmeter avsinfo -log" and then parse the log file.

[manolito]

I am just trying A2D 2.8.8 and it won't find any Avisynth installation, warns that it would be missing.

AFAIK this warning is purely cosmetic and you can ignore it - of course only if AVS 2.60 or 2.61 Alpha or a current 32-bit AVS+ version is correctly installed. With AVS+ I also get this warning that at least AVS v. 2.60 is required (AVS+ returns 0.1.0 as the version number), but it never caused a problem for me. BTW I do not use Groucho's AVS switcher batch file, I copy the relevant files manually from the repository to the relevant folders. Both official installers for either classic AVS as well as for AVS+ work with AVStoDVD.

PLease have a look at this post and MrC's answer:
https://forum.doom9.org/showthread.php?p=1775057#post1775057

[Groucho2004]

PLease have a look at this post and MrC's answer:
https://forum.doom9.org/showthread.php?p=1775057#post1775057

Instead there is a show stop when AviSynth.dll is not found from the path taken from "HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth" registy key.
This is nonsense. The entries under that key don't include the path where avisynth.dll is located (System32/SysWoW64). These entries only hold the install- and plugin path:
[HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth]
@="D:\\Program Files\\AviSynth"
"plugindir2_5"="D:\\Program Files\\AviSynth\\plugins"
"initialplugindir"="D:\\Program Files\\AviSynth\\plugins"

[manolito]

This is nonsense. The entries under that key don't include the path where avisynth.dll is located (System32/SysWoW64).

Yes, you are right, I believe that this was an error from MrC.

AVStoDVD needs a 32-bit AviSynth.dll either in System32 (for a 32-bit Windows) or in SysWOW64 (for a 64-bit Windows), and I think it does check for this.

Whatever, if AviSynth is installed correctly then it will work in AVStoDVD, even if it throws a warning about an incorrect version in case you are using AVS+. After all AVStoDVD does not interface with AVS directly, it just creates an AVS script which becomes the input for the selected encoder. It does not even care for the AviSynth\Plugins folder, it loads all necessary plugins explicitly from its own Lib folder.

[Groucho2004]

Whatever, if AviSynth is installed correctly then it will work in AVStoDVD, even if it throws a warning about an incorrect version in case you are using AVS+.
Sure. However, my point is - It could be so simple to use a reliable way to detect Avisynth (via AVSMeter) instead of confusing users who don't know that they can ignore the warning. It's just seems bizarre to me to keep using this horribly flawed (well, at least from a developers point of view) detection method.

[manolito]

Well, you know how old AVStoDVD is... ;)

Newer AviSynth forks were non-existent then, and up to now only classic AVS 2.60 is officially supported. Users who want to try other AVS versions are on their own - or need to rely on information they can get at the usual places.

MrC has not posted here or at VideoHelp for almost 3 months now, his real life (work and family) seems to leave not much time for maintaining AVStoDVD these days. That's perfectly alright with me. The software is very mature as it is, and creating DVDs is not too sexy today so the user base is diminishing. Keeping the software up to date in the sense that it continues supporting current source formats is probably all anyone could ask for, and so far this seems to be the case.

[thescrapyard]

Well, you know how old AVStoDVD is... ;)

Newer AviSynth forks were non-existent then, and up to now only classic AVS 2.60 is officially supported. Users who want to try other AVS versions are on their own - or need to rely on information they can get at the usual places.

MrC has not posted here or at VideoHelp for almost 3 months now, his real life (work and family) seems to leave not much time for maintaining AVStoDVD these days. That's perfectly alright with me. The software is very mature as it is, and creating DVDs is not too sexy today so the user base is diminishing. Keeping the software up to date in the sense that it continues supporting current source formats is probably all anyone could ask for, and so far this seems to be the case.

He has said that real life and work leave him very little time for AVStoDVD these days so any updates have to be made that won't break or change anything that is already working fine, hence just minor updates as and when


I use the latest avisynth+, using the official installer, and it works perfectly with AVstoDVD. It just reports that encoding routines 'may' not work as the avisynth base isn't found. It still works though

https://github.com/pinterf/AviSynthPlus/releases


I also update AVSMeter when a new release comes out and also FFMPEG is updated to nightlies every now and then and both work perfectly. The nightly of FFMPEG (32bit static ONLY) seems to be faster for me. Just a case of overwriting the original or make a backup first just in case it does break something in AVStoDVD

[Emulgator]

Many thanks, that clears it up.
So I did safely ignore that warning and encoding did indeed start.

[dr_ml422]

All night now and I'm getting that " can not find Title 1 " error. Clean install, opens up in MPC classic etc..., tried w/ and w/out the .srt file and nothing. Everything was well until that file. It's a regular .,mp4 w/aac and etc... Here's the log file.

<3/27/2019 8:01:25 AM>
START PROCESS
<>

<3/27/2019 8:01:25 AM>
PROJECT SETTINGS

DVD Video Standard: NTSC
DVD Titles number: 1
DVD Size: 4450/4450 MB (100%)
DVD Output Setup: Burn DVD
DVD Label: 6.THE_WOLVERINE_2013~1
DVD Menu: Static Menu
Output Folder: C:\Users\Noloc42\Videos
Delete Temp Assets Files: Yes
Delete Temp Working Files: Yes
Edit Command Parameters: No
Post Process Task: Show Progress Status window

PREFERENCES

MultiThread: 1
AVS Video Source Filter: A2DSource
AVS Audio Source Filter: A2DSource
AVS UpSize/DownSize Filter: Lanczos4Resize/Spline16Resize
Frame Adjust Strategy: 0
FPS Hard Conversion: 0
PAL SpeedUp: 0
NTSC SlowDown: 0
Video Resolution: 0
Video Encoder: 0
Video BitRate Min: 2500
Video BitRate Max: 8500
Keep DVD Compliant Video: 1
AC3 Audio Encoder: 0
Force FFmpeg for Long Audio: 1
DVD Audio Format: 0
DVD Audio BitRate: 192
Keep DVD Compliant Audio: 1
Normalize Audio: 0
Auto Delay Audio: 1
DVD Audio Language (Primary): EN - English
DVD Audio Language (Secondary): EN - English
DVD Subs Language (Primary): EN - English
DVD Subs Language (Secondary): EN - English
DVD Subs Font: Tahoma 16pt (240,240,240)
Chapters Interval: 5
Use Source Chapters: 1
DVD Burning Drive: D:\
DVD Burning Speed: 4x
Auto Erase DVD RW: 1
Unload ActiveMovie Library: 1
Adjust DirectShow Filters at runtime: 1
Save General Settings: 0

SYSTEM INFO

Processor Name: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
Operating System: Windows 10 (10.0.17763) 64 bit
User has Admin Rights: YES
Running with Elevated Privileges: YES
Available Output Disc Space: 134 GB
AviSynth is installed: YES (release 2.6.0)
LAV Filters is installed: YES (release 0.74.1)
ffdshow is installed: NO

CODECS REPORT

H.264/AVC: Enhanced Video Renderer
Xvid: Enhanced Video Renderer
DivX 4/5/6: Enhanced Video Renderer
Other MPG4: Enhanced Video Renderer
DV: LAV Video Decoder
MPEG1: LAV Video Decoder
MPEG2: LAV Video Decoder
AAC: LAV Audio Decoder
MP3: LAV Audio Decoder
MP2: LAV Audio Decoder
AC3: LAV Audio Decoder
<>

<3/27/2019 8:01:36 AM>
AVStoDVD Project ended successfully.
<>

<3/27/2019 8:01:36 AM>
Log file created by AVStoDVD Release 2.8.8
<>

It says No FFDshow? I just finished installing the Klite Full Codec pack which I think includes ffdshow if I'm not mistaken.

another one just in case.

<3/27/2019 4:14:52 AM>
START PROCESS
<>

<3/27/2019 4:14:52 AM>
PROJECT SETTINGS

DVD Video Standard: NTSC
DVD Titles number: 1
DVD Size: 4450/4450 MB (100%)
DVD Output Setup: Burn DVD
DVD Label: 6.THEWOLVERINE EXTENDED 2013~1
DVD Menu: Static Menu
Output Folder: C:\Users\Noloc42\Videos
Delete Temp Assets Files: Yes
Delete Temp Working Files: Yes
Edit Command Parameters: No
Post Process Task: Show Progress Status window

PREFERENCES

MultiThread: 1
AVS Video Source Filter: A2DSource
AVS Audio Source Filter: A2DSource
AVS UpSize/DownSize Filter: Lanczos4Resize/Spline16Resize
Frame Adjust Strategy: 0
FPS Hard Conversion: 0
PAL SpeedUp: 0
NTSC SlowDown: 0
Video Resolution: 0
Video Encoder: 0
Video BitRate Min: 2500
Video BitRate Max: 8500
Keep DVD Compliant Video: 1
AC3 Audio Encoder: 0
Force FFmpeg for Long Audio: 1
DVD Audio Format: 0
DVD Audio BitRate: 192
Keep DVD Compliant Audio: 1
Normalize Audio: 0
Auto Delay Audio: 1
DVD Audio Language (Primary): EN - English
DVD Audio Language (Secondary): EN - English
DVD Subs Language (Primary): EN - English
DVD Subs Language (Secondary): EN - English
DVD Subs Font: Tahoma 16pt (240,240,240)
Chapters Interval: 5
Use Source Chapters: 1
DVD Burning Drive: D: HL-DT-ST DVDRAM GH24NSB0 LF00
DVD Burning Speed: 8x
Auto Erase DVD RW: 1
Unload ActiveMovie Library: 1
Adjust DirectShow Filters at runtime: 1
Save General Settings: 0

SYSTEM INFO

Processor Name: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
Operating System: Windows 10 (10.0.17763) 64 bit
User has Admin Rights: YES
Running with Elevated Privileges: NO (3)
Available Output Disc Space: 144 GB
AviSynth is installed: YES (release 2.6.0)
LAV Filters is installed: YES (release 0.73.1)
ffdshow is installed: NO

CODECS REPORT

H.264/AVC: LAV Video Decoder
Xvid: LAV Video Decoder
DivX 4/5/6: LAV Video Decoder
Other MPG4: LAV Video Decoder
DV: LAV Video Decoder
MPEG1: LAV Video Decoder
MPEG2: LAV Video Decoder
AAC: LAV Audio Decoder
MP3: LAV Audio Decoder
MP2: LAV Audio Decoder
AC3: LAV Audio Decoder
<>

<3/27/2019 4:15:03 AM>
AVStoDVD Project ended successfully.
<>

<3/27/2019 4:15:03 AM>
Log file created by AVStoDVD Release 2.8.8
<>

[manolito]

A few remarks about your log files:

Why did you cut out the most relevant parts? Please post the full log file so we can see the error messages.

Codec Packs like K-Lite are evil. AVStoDVD supports LAV Filters and ffdshow as DirectShow Filters. But just one or the other, not both. And then you overlooked the fact that starting with Win7 Microsoft decided that users are not smart enough to decide which DS filters to use, so they created a "Preferred Filters" registry entry (not editable by users without first grabbing the rights), and no matter which different filters a user installs, they won't get used.

The safest way for AVStoDVD is to go to "Codecs -> Preferred Directshow Codecs Setup" and set ALL codecs to LAV Filters. If your LAV Filters were installed by a codec pack you might have the additional problem that the codec pack might have altered the LAV configuration. It looks like for your second log file you did use LAV Filters exclusively, so maybe a codec pack excluded some formats from the LAV configuration.

To rule out all DirectShow related problems you can specify "FFmpegSource" for video and audio under "Preferences -> AviSynth". This will use ffms2 as your source filter bypassing DirectShow completely.

To fully understand your issues please post the full AVStoDVD log file, and a MediaInfo report about your source file would also be very useful.

[dr_ml422]

I downloaded Klite Full afterwards not before. It uses LAV now and not ffdshow. I made sure all the directshow filters were set to LAV both 32 bit and 64 bit. Should uninstall Klite Full along with MPC HC? This was my first log of that file. I have a more recent one as well that says .Net framework 2 not found on my computer? Something's not right. Worked just fine then all of a sudden all these issues. Here goes:

<3/27/2019 4:04:57 AM>
START PROCESS
<>

<3/27/2019 4:04:57 AM>
PROJECT SETTINGS

DVD Video Standard: NTSC
DVD Titles number: 1
DVD Size: 4450/4450 MB (100%)
DVD Output Setup: Burn DVD
DVD Label: 6THEWO~1 EXTENDED 2013
DVD Menu: Static Menu
Output Folder: C:\Users\Noloc42\Videos
Delete Temp Assets Files: Yes
Delete Temp Working Files: Yes
Edit Command Parameters: No
Post Process Task: Show Progress Status window

PREFERENCES

MultiThread: 1
AVS Video Source Filter: A2DSource
AVS Audio Source Filter: A2DSource
AVS UpSize/DownSize Filter: Lanczos4Resize/Spline16Resize
Frame Adjust Strategy: 0
FPS Hard Conversion: 0
PAL SpeedUp: 0
NTSC SlowDown: 0
Video Resolution: 0
Video Encoder: 0
Video BitRate Min: 2500
Video BitRate Max: 8500
Keep DVD Compliant Video: 1
AC3 Audio Encoder: 0
Force FFmpeg for Long Audio: 1
DVD Audio Format: 0
DVD Audio BitRate: 192
Keep DVD Compliant Audio: 1
Normalize Audio: 0
Auto Delay Audio: 1
DVD Audio Language (Primary): EN - English
DVD Audio Language (Secondary): EN - English
DVD Subs Language (Primary): EN - English
DVD Subs Language (Secondary): EN - English
DVD Subs Font: Tahoma 16pt (240,240,240)
Chapters Interval: 5
Use Source Chapters: 1
DVD Burning Drive: D: HL-DT-ST DVDRAM GH24NSB0 LF00
DVD Burning Speed: 8x
Auto Erase DVD RW: 1
Unload ActiveMovie Library: 1
Adjust DirectShow Filters at runtime: 1
Save General Settings: 0

SYSTEM INFO

Processor Name: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
Operating System: Windows 10 (10.0.17763) 64 bit
User has Admin Rights: YES
Running with Elevated Privileges: NO (3)
Available Output Disc Space: 144 GB
AviSynth is installed: YES (release 2.6.0)
LAV Filters is installed: YES (release 0.73.1)
ffdshow is installed: NO

CODECS REPORT

H.264/AVC: LAV Video Decoder
Xvid: LAV Video Decoder
DivX 4/5/6: LAV Video Decoder
Other MPG4: LAV Video Decoder
DV: LAV Video Decoder
MPEG1: LAV Video Decoder
MPEG2: LAV Video Decoder
AAC: LAV Audio Decoder
MP3: LAV Audio Decoder
MP2: LAV Audio Decoder
AC3: LAV Audio Decoder
<>

<3/27/2019 4:05:05 AM>
AVStoDVD Project ended successfully.
<>

<3/27/2019 4:05:05 AM>
Log file created by AVStoDVD Release 2.8.8
<>

<3/27/2019 4:24:38 AM>
START PROCESS
<>

<3/27/2019 4:24:38 AM>
PROJECT SETTINGS

DVD Video Standard: NTSC
DVD Titles number: 1
DVD Size: 4450/4450 MB (100%)
DVD Output Setup: DVD Folder
DVD Label: 6THEWO~1
DVD Menu: Static Menu
Output Folder: C:\Users\Noloc42\Videos
Delete Temp Assets Files: Yes
Delete Temp Working Files: Yes
Edit Command Parameters: No
Post Process Task: Show Progress Status window

PREFERENCES

MultiThread: 1
AVS Video Source Filter: A2DSource
AVS Audio Source Filter: A2DSource
AVS UpSize/DownSize Filter: Lanczos4Resize/Spline16Resize
Frame Adjust Strategy: 0
FPS Hard Conversion: 0
PAL SpeedUp: 0
NTSC SlowDown: 0
Video Resolution: 0
Video Encoder: 0
Video BitRate Min: 2500
Video BitRate Max: 8500
Keep DVD Compliant Video: 1
AC3 Audio Encoder: 0
Force FFmpeg for Long Audio: 1
DVD Audio Format: 0
DVD Audio BitRate: 192
Keep DVD Compliant Audio: 1
Normalize Audio: 0
Auto Delay Audio: 1
DVD Audio Language (Primary): EN - English
DVD Audio Language (Secondary): EN - English
DVD Subs Language (Primary): EN - English
DVD Subs Language (Secondary): EN - English
DVD Subs Font: Tahoma 16pt (240,240,240)
Chapters Interval: 5
Use Source Chapters: 1
DVD Burning Drive: D: HL-DT-ST DVDRAM GH24NSB0 LF00
DVD Burning Speed: 8x
Auto Erase DVD RW: 1
Unload ActiveMovie Library: 1
Adjust DirectShow Filters at runtime: 1
Save General Settings: 0

SYSTEM INFO

Processor Name: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
Operating System: Windows 10 (10.0.17763) 64 bit
User has Admin Rights: YES
Running with Elevated Privileges: NO (3)
Available Output Disc Space: 144 GB
AviSynth is installed: YES (release 2.6.0)
LAV Filters is installed: YES (release 0.73.1)
ffdshow is installed: NO

CODECS REPORT

H.264/AVC: LAV Video Decoder
Xvid: LAV Video Decoder
DivX 4/5/6: LAV Video Decoder
Other MPG4: LAV Video Decoder
DV: LAV Video Decoder
MPEG1: LAV Video Decoder
MPEG2: LAV Video Decoder
AAC: LAV Audio Decoder
MP3: LAV Audio Decoder
MP2: LAV Audio Decoder
AC3: LAV Audio Decoder
<>

<3/27/2019 4:24:47 AM>
AVStoDVD Project ended successfully.
<>

<3/27/2019 4:26:22 AM>
START PROCESS
<>

<3/27/2019 4:26:22 AM>
PROJECT SETTINGS

DVD Video Standard: NTSC
DVD Titles number: 1
DVD Size: 4450/4450 MB (100%)
DVD Output Setup: DVD Folder
DVD Label: 6THEWO~1
DVD Menu: Static Menu
Output Folder: C:\Users\Noloc42\Videos
Delete Temp Assets Files: Yes
Delete Temp Working Files: Yes
Edit Command Parameters: No
Post Process Task: Show Progress Status window

PREFERENCES

MultiThread: 1
AVS Video Source Filter: A2DSource
AVS Audio Source Filter: A2DSource
AVS UpSize/DownSize Filter: Lanczos4Resize/Spline16Resize
Frame Adjust Strategy: 0
FPS Hard Conversion: 0
PAL SpeedUp: 0
NTSC SlowDown: 0
Video Resolution: 0
Video Encoder: 0
Video BitRate Min: 2500
Video BitRate Max: 8500
Keep DVD Compliant Video: 1
AC3 Audio Encoder: 0
Force FFmpeg for Long Audio: 1
DVD Audio Format: 0
DVD Audio BitRate: 192
Keep DVD Compliant Audio: 1
Normalize Audio: 0
Auto Delay Audio: 1
DVD Audio Language (Primary): EN - English
DVD Audio Language (Secondary): EN - English
DVD Subs Language (Primary): EN - English
DVD Subs Language (Secondary): EN - English
DVD Subs Font: Tahoma 16pt (240,240,240)
Chapters Interval: 5
Use Source Chapters: 1
DVD Burning Drive: D: HL-DT-ST DVDRAM GH24NSB0 LF00
DVD Burning Speed: 8x
Auto Erase DVD RW: 1
Unload ActiveMovie Library: 1
Adjust DirectShow Filters at runtime: 1
Save General Settings: 0

SYSTEM INFO

Processor Name: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
Operating System: Windows 10 (10.0.17763) 64 bit
User has Admin Rights: YES
Running with Elevated Privileges: NO (3)
Available Output Disc Space: 144 GB
AviSynth is installed: YES (release 2.6.0)
LAV Filters is installed: YES (release 0.73.1)
ffdshow is installed: NO

CODECS REPORT

H.264/AVC: LAV Video Decoder
Xvid: LAV Video Decoder
DivX 4/5/6: LAV Video Decoder
Other MPG4: LAV Video Decoder
DV: LAV Video Decoder
MPEG1: LAV Video Decoder
MPEG2: LAV Video Decoder
AAC: LAV Audio Decoder
MP3: LAV Audio Decoder
MP2: LAV Audio Decoder
AC3: LAV Audio Decoder
<>

<3/27/2019 4:26:25 AM>
AVStoDVD Project ended successfully.
<>

<3/27/2019 4:33:32 AM>
START PROCESS
<>

<3/27/2019 4:33:32 AM>
PROJECT SETTINGS

DVD Video Standard: NTSC
DVD Titles number: 1
DVD Size: 4450/4450 MB (100%)
DVD Output Setup: Burn DVD
DVD Label: 6THEWO~1
DVD Menu: Static Menu
Output Folder: C:\Users\Noloc42\Videos
Delete Temp Assets Files: Yes
Delete Temp Working Files: Yes
Edit Command Parameters: No
Post Process Task: Show Progress Status window

PREFERENCES

MultiThread: 1
AVS Video Source Filter: A2DSource
AVS Audio Source Filter: A2DSource
AVS UpSize/DownSize Filter: Lanczos4Resize/Spline16Resize
Frame Adjust Strategy: 0
FPS Hard Conversion: 0
PAL SpeedUp: 0
NTSC SlowDown: 0
Video Resolution: 0
Video Encoder: 0
Video BitRate Min: 2500
Video BitRate Max: 8500
Keep DVD Compliant Video: 1
AC3 Audio Encoder: 0
Force FFmpeg for Long Audio: 1
DVD Audio Format: 0
DVD Audio BitRate: 192
Keep DVD Compliant Audio: 1
Normalize Audio: 0
Auto Delay Audio: 1
DVD Audio Language (Primary): EN - English
DVD Audio Language (Secondary): EN - English
DVD Subs Language (Primary): EN - English
DVD Subs Language (Secondary): EN - English
DVD Subs Font: Tahoma 16pt (240,240,240)
Chapters Interval: 5
Use Source Chapters: 1
DVD Burning Drive: D: HL-DT-ST DVDRAM GH24NSB0 LF00
DVD Burning Speed: 8x
Auto Erase DVD RW: 1
Unload ActiveMovie Library: 1
Adjust DirectShow Filters at runtime: 1
Save General Settings: 0

SYSTEM INFO

Processor Name: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
Operating System: Windows 10 (10.0.17763) 64 bit
User has Admin Rights: YES
Running with Elevated Privileges: NO (3)
Available Output Disc Space: 144 GB
AviSynth is installed: YES (release 2.6.0)
LAV Filters is installed: YES (release 0.73.1)
ffdshow is installed: NO

CODECS REPORT

H.264/AVC: LAV Video Decoder
Xvid: LAV Video Decoder
DivX 4/5/6: LAV Video Decoder
Other MPG4: LAV Video Decoder
DV: LAV Video Decoder
MPEG1: LAV Video Decoder
MPEG2: LAV Video Decoder
AAC: LAV Audio Decoder
MP3: LAV Audio Decoder
MP2: LAV Audio Decoder
AC3: LAV Audio Decoder
<>

<3/27/2019 4:33:36 AM>
AVStoDVD Project ended successfully.
<>

<3/27/2019 4:41:16 AM>
START PROCESS
<>

<3/27/2019 4:41:16 AM>
PROJECT SETTINGS

DVD Video Standard: NTSC
DVD Titles number: 1
DVD Size: 4450/4450 MB (100%)
DVD Output Setup: Burn DVD
DVD Label: 6THEWO~1
DVD Menu: Static Menu
Output Folder: C:\Users\Noloc42\Videos
Delete Temp Assets Files: Yes
Delete Temp Working Files: Yes
Edit Command Parameters: No
Post Process Task: Show Progress Status window

PREFERENCES

MultiThread: 1
AVS Video Source Filter: A2DSource
AVS Audio Source Filter: A2DSource
AVS UpSize/DownSize Filter: Lanczos4Resize/Spline16Resize
Frame Adjust Strategy: 0
FPS Hard Conversion: 0
PAL SpeedUp: 0
NTSC SlowDown: 0
Video Resolution: 0
Video Encoder: 0
Video BitRate Min: 2500
Video BitRate Max: 8500
Keep DVD Compliant Video: 1
AC3 Audio Encoder: 0
Force FFmpeg for Long Audio: 1
DVD Audio Format: 0
DVD Audio BitRate: 192
Keep DVD Compliant Audio: 1
Normalize Audio: 0
Auto Delay Audio: 1
DVD Audio Language (Primary): EN - English
DVD Audio Language (Secondary): EN - English
DVD Subs Language (Primary): EN - English
DVD Subs Language (Secondary): EN - English
DVD Subs Font: Tahoma 16pt (240,240,240)
Chapters Interval: 5
Use Source Chapters: 1
DVD Burning Drive: D: HL-DT-ST DVDRAM GH24NSB0 LF00
DVD Burning Speed: 8x
Auto Erase DVD RW: 1
Unload ActiveMovie Library: 1
Adjust DirectShow Filters at runtime: 1
Save General Settings: 0

SYSTEM INFO

Processor Name: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
Operating System: Windows 10 (10.0.17763) 64 bit
User has Admin Rights: YES
Running with Elevated Privileges: NO (3)
Available Output Disc Space: 144 GB
AviSynth is installed: YES (release 2.6.0)
LAV Filters is installed: YES (release 0.73.1)
ffdshow is installed: NO

CODECS REPORT

H.264/AVC: LAV Video Decoder
Xvid: LAV Video Decoder
DivX 4/5/6: LAV Video Decoder
Other MPG4: LAV Video Decoder
DV: LAV Video Decoder
MPEG1: LAV Video Decoder
MPEG2: LAV Video Decoder
AAC: LAV Audio Decoder
MP3: LAV Audio Decoder
MP2: LAV Audio Decoder
AC3: LAV Audio Decoder
<>

<3/27/2019 4:41:18 AM>
AVStoDVD Project ended successfully.
<>

<3/27/2019 7:12:34 AM>
START PROCESS
<>

<3/27/2019 7:12:34 AM>
PROJECT SETTINGS

DVD Video Standard: NTSC
DVD Titles number: 1
DVD Size: 4450/4450 MB (100%)
DVD Output Setup: Burn DVD
DVD Label: 6THEWO~1
DVD Menu: Static Menu
Output Folder: C:\Users\Noloc42\Videos
Delete Temp Assets Files: Yes
Delete Temp Working Files: Yes
Edit Command Parameters: No
Post Process Task: Show Progress Status window

PREFERENCES

MultiThread: 1
AVS Video Source Filter: A2DSource
AVS Audio Source Filter: A2DSource
AVS UpSize/DownSize Filter: Lanczos4Resize/Spline16Resize
Frame Adjust Strategy: 0
FPS Hard Conversion: 0
PAL SpeedUp: 0
NTSC SlowDown: 0
Video Resolution: 0
Video Encoder: 0
Video BitRate Min: 2500
Video BitRate Max: 8500
Keep DVD Compliant Video: 1
AC3 Audio Encoder: 0
Force FFmpeg for Long Audio: 1
DVD Audio Format: 0
DVD Audio BitRate: 192
Keep DVD Compliant Audio: 1
Normalize Audio: 0
Auto Delay Audio: 1
DVD Audio Language (Primary): EN - English
DVD Audio Language (Secondary): EN - English
DVD Subs Language (Primary): EN - English
DVD Subs Language (Secondary): EN - English
DVD Subs Font: Tahoma 16pt (240,240,240)
Chapters Interval: 5
Use Source Chapters: 1
DVD Burning Drive: D: HL-DT-ST DVDRAM GH24NSB0 LF00
DVD Burning Speed: 8x
Auto Erase DVD RW: 1
Unload ActiveMovie Library: 1
Adjust DirectShow Filters at runtime: 1
Save General Settings: 0

SYSTEM INFO

Processor Name: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
Operating System: Windows 10 (10.0.17763) 64 bit
User has Admin Rights: YES
Running with Elevated Privileges: NO (3)
Available Output Disc Space: 144 GB
AviSynth is installed: YES (release 2.6.0)
LAV Filters is installed: YES (release 0.74.1)
ffdshow is installed: NO

CODECS REPORT

H.264/AVC: LAV Video Decoder
Xvid: LAV Video Decoder
DivX 4/5/6: LAV Video Decoder
Other MPG4: LAV Video Decoder
DV: LAV Video Decoder
MPEG1: LAV Video Decoder
MPEG2: LAV Video Decoder
AAC: LAV Audio Decoder
MP3: LAV Audio Decoder
MP2: LAV Audio Decoder
AC3: LAV Audio Decoder
<>

<3/27/2019 7:12:42 AM>
AVStoDVD Project ended successfully.
<>

[manolito]

All your logs look incomplete. Right after the codecs report comes the message "Project ended successfully", and the time stamp of this message shows only less than 10 seconds after the project start.

Here is my log of a complete short conversion:

<29.03.2019 11:12:04>
START PROCESS
<>

<29.03.2019 11:12:04>
PROJECT SETTINGS

DVD Video Standard: PAL
DVD Titles number: 1
DVD Size: 266/4450 MB (6%)
DVD Output Setup: MPEG2-Datei
DVD Label: DVD
DVD Menu: No Menu
Output Folder: I:
Delete Temp Assets Files: Yes
Delete Temp Working Files: Yes
Edit Command Parameters: No
Post Process Task: Fortschrittsfenster anzeigen (Voreinstellung)

PREFERENCES

MultiThread: 1
AVS Video Source Filter: A2DSource
AVS Audio Source Filter: A2DSource
AVS UpSize/DownSize Filter: Spline36Resize/Spline36Resize
Frame Adjust Strategy: 1
FPS Hard Conversion: 2
PAL SpeedUp: 1
NTSC SlowDown: 1
Video Resolution: 0
Video Encoder: 0
Video BitRate Min: 2000
Video BitRate Max: 8500
Keep DVD Compliant Video: 0
AC3 Audio Encoder: 2
Force FFmpeg for Long Audio: 1
DVD Audio Format: 0
DVD Audio BitRate: 224
Keep DVD Compliant Audio: 0
Normalize Audio: 0
Auto Delay Audio: 1
DVD Audio Language (Primary): DE - German
DVD Audio Language (Secondary): EN - English
DVD Subs Language (Primary): DE - German
DVD Subs Language (Secondary): EN - English
DVD Subs Font: Tahoma 16pt (240,240,240)
Chapters Interval: 5
Use Source Chapters: 1
DVD Burning Drive: H: BENQ DVD DD DW1620 B7W9
DVD Burning Speed: 8x
Auto Erase DVD RW: 0
Unload ActiveMovie Library: 0
Adjust DirectShow Filters at runtime: 1
Save General Settings: 0

SYSTEM INFO

Processor Name:
Operating System: Windows XP - Service Pack 3 (5.1.2600) 32 bit
User has Admin Rights: YES
Running with Elevated Privileges: NO (-1)
Available Output Disc Space: 43 GB
AviSynth is installed: YES (release 2.6.1)
LAV Filters is installed: YES (release 0.69.0)
ffdshow is installed: NO
<>

<29.03.2019 11:12:04>
TITLE 1 SOURCE FILES
Video: I:\Test.flv
Info: AVC - 400 kbps - 544x408 - DAR 4:3 - 25 fps - Progressive - 7:01 minutes - 10527 frames
Audio 1: I:\Test.flv
Info: AAC LC - 94 kbps - CBR - 2 ch - 44100 Hz - 16 bit - 7:01 minutes (57 ms delay)
[MediaInfoLib - v18.05]
<>

<29.03.2019 11:12:04>
AVISYNTH SCRIPT
Import("E:\Programme\AVStoDVD\Lib\A2DSource.avsi")

Video = A2DVideoSource("I:\Test.flv", CacheFolder="I:", FrameRate=25)
Audio = A2DAudioSource("I:\Test.flv", CacheFolder="I:")

Video = Video.ConvertToYV12()
Video = Video.Spline36Resize(720,576)

Audio = Audio.SSRC(48000)
Audio = Audio.DelayAudio(0.057)

AudioDub(Video, Audio)
<>

<29.03.2019 11:12:04>
DIRECTSHOW AUDIO MIXER OPERATIONS:
No LAV Filters mixer ON/OFF adjustment required at runtime
<>

<29.03.2019 11:12:04>
START VIDEO ENCODING OPERATIONS
Video Encoding Profile: FFmpeg CBR 1-pass
Target Video FileSize: 250,9 MB
Encoding Parameters: -i "I:\DVD_Test_1.avs" -threads 1 -aspect 4:3 -c:v mpeg2video -b:v 5000k -minrate 5000k -maxrate 5000k -bufsize 2000k -dc 9 -y "I:\DVD_Test.m2v"
<>

<29.03.2019 11:27:12>
END VIDEO ENCODING OPERATIONS
Video Source Filter: A2DSource - DSS2 mod (LAV Filters on)
Created File: I:\DVD_Test.m2v (213,7 MB)
Ouput Video Info: MPEG-2 Video - 4247 kbps - 720x576 - DAR 4:3 - 25 fps - Progressive - 7:02 minutes - 10550 frames
Avg Video Encoding Speed: 12,4 fps
<>

<29.03.2019 11:27:12>
START AUDIO ENCODING OPERATIONS (Track 1)
FFmpeg Parameters: -i "I:\DVD_Test_1.avs" -threads 1 -y -vn -c:a ac3 -ab 224k "I:\DVD_Test_1.ac3"
<>

<29.03.2019 11:30:28>
END AUDIO ENCODING OPERATIONS (Track 1)
Audio Source Filter: A2DSource - DirectShowSource
Created File: I:\DVD_Test_1.ac3 (11,3 MB)
Output Audio Info: AC3 - 224 kbps - CBR - 2 ch - 48000 Hz - 16 bit - 7:02 minutes (0 ms delay)
<>

<29.03.2019 11:30:28>
START MUXING OPERATIONS
Mplex Parameters: -f 8 -L 48000:2:16 -o "I:\DVD_Test.mpg" "I:\DVD_Test.m2v" "I:\DVD_Test_1.ac3"
<>

<29.03.2019 11:31:08>
END MUXING OPERATIONS
Created File: I:\DVD_Test.mpg (230,2 MB)
<>

<29.03.2019 11:31:08>
AVStoDVD Project ended successfully.
<>

<29.03.2019 11:31:08>
Log file created by AVStoDVD Release 2.8.8 Hotfix build 190115
<>


According to your logs AVStoDVD does not even show title information or the created AVS script. Something about your system configuration must be terribly wrong.

I do know that A2D runs under Win10, MrC does test the software under Win10. So I can just guess what is wrong here. Could be the Codec Pack, could be an antivirus software which blocks something important, could be that you tried to update some helper software with newer but incompatible versions. Whatever, if you do not have an image backup made before these problems appeared then the best advice I have is a fresh reinstall of Windows and all your software.

Should uninstall Klite Full along with MPC HC?

One of the problems about Codec Packs is that you just cannot uninstall them completely. In most cases they leave stuff behind, and oftentimes they have reconfigured other stuff which persists even after uninstalling.


About .Net framework you should read the A2D manual under the FAQ section. NET Framework 2.0 is only necessary for SubtitleCreator. For users who do not need subtitles .NET Framework is not required for using AVStoDVD.

From the A2D manual:
SubtitleCreator requires .NET Framework 2 to run. You can download .NET 2 from Microsoft website. You can also download .NET 3.5 which includes .NET 2 and .NET 3. Unfortunately .NET 4.x packages do not include previous releases libraries, so you have to install either .NET 2 or .NET 3.5.

If you have Windows 10, you can activate .NET 3.5 by following this guide: https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install-insiderplat_pc/how-to-instal-net-framework-35-on-windows-10/450b3ba6-4d19-45ae-840e-78519f36d7a4

[dr_ml422]

Those are the logs that came up. The issue is something, as AVStoDVD is not the only encoding program installed and working. ConvertXToDVD, ConvertXtoVideo despite it not supporting h.264, DVDFAB, VidCoder, .... I read and installed the .net framework 3.5 just for AVStoDVD as no other needed it to insert subtitles. Matter of fact I'm finishing whatever was done and not done with ConvertXToDVD.

A suggestion would be to concentrate on the newer updated versions of Windows and have the software completely up to date. Let users meet you at the present level. Many don't want to acknowledge the new and prefer to hold on to the past and it causes issues.

Matter of fact even Microsoft decided to concentrate on newer, present level hardware etc... and not support older depecrated hardware, OD, etc... Even yourself got tired of that useless QUenc.

That said with that file and 9 others similar, AVStoDVD couldn't acknowledge the dual Audio. I could care less about the Hindu, it came from land of the files iykwim. Lol...

I had to get rid of 2 perfectly well burners because of Windows 10. Didn't know that they weren't supported until I did research.

Easy does it. I know this is hard work. Especially as a gift from yourself and all others. We'll figure it out. I will definitely have to build me a newer more updated PC, as Windows 10 expects. XP was a God back then, only 1 CD. I still have a disc. 2019 is here.

The internal or even external player won't play unless ffdshow is installed. I'm not going to install it as LAV is doing the necessary work.

[manolito]

AVStoDVD is written in Visual Basic 6. Very old, only partly supported in Win10, but it sure does work. Only 32-bit helper software is supported, if a user tries to outsmart the author and replace some 32-bit helper software with 64-bit versions then he/she should not complain if it does not work. The same goes for other tools like MediaInfo where the latest versions are not supported.

I do not use Win10 (for me it is evil spyware), technically it has absolutely nothing to offer over Win7. Of course there are (mostly younger) folks who feel that newer is always better, but those folks should not use software like AVStoDVD.

From your log files I can see that your system configuration has huge problems, of course AVStoDVD can work together with other video converters like ConvertXToDVD, ConvertXtoVideo, DVDFAB, VidCoder, but not if you destroyed some basic configuration settings.

I'm out of here, I think you will be better off using other video conversion software than AVStoDVD.

[dr_ml422]

manolito you don't have to go anywhere. You're you. Only thing is everyone one else and everything else is not. That's all that was needed was to establish the fact that the software really isn't up to date. Please try not to berate new members or their systems, ways, views, etc... If my system is not configured correctly nothing would work, especially Video software. If you want to do something positive then just for the sake of the software bring it up to date. I can't change your view on life, though I can only suggest that you will never, ever beat any establishment, you can only work with it and take what you can and leave the rest. I seriously doubt MS or Apple, or Ubuntu, or anything else running in this present day is going to stop for you or anyone else. Matter of fact the whole USA is behind the times. Most other places have been implementing x64 computing for a while now and as default. It's a great program. Maybe too many individual parts to ever work right all the time even if updated. The probability that something will err out is very high when there's too much not working in sync or at least close to it. It's in your hands. The April 2nd update is here and I doubt it's stopping because of the few. I myself didn't learn to smarten up until recently. I kept trying to get married when the first sin ever recorded for those that follow, was the deception of a woman. So why should I expect anything different now in 2019? Something to think about. Stop being lazy. Grab the bull by the horns and get to work. I wish I could compensate for the hard work no matter you're position. A little something always comes in handy. If one day my fortune changes I'll blow up the donate button and Amazon Gift card. One day is not today. I'm heading to either Amazon, Microcenter, or both to full proof a new build soon. Windows 10 requires updated hardware so I will update it. Simple. Never have I understood why some come to the party and at least don't try to dance.
I've learned that I will never change who I am, though I do my best to change my response to everything. All will work out for the best.

[Groucho2004]

I kept trying to get married when the first sin ever recorded for those that follow, was the deception of a woman.Maybe you'd be happier with a man? Any recorded sins with that gender?


Never have I understood why some come to the party and at least don't try to dance.They don't want to hurt anyone.

[dr_ml422]

If you don't comprehend what I'm saying then please refrain. Usually those that speak about men are the ones that get with them. This is a forum for knowledge. Not to get off on your plastic ego when no one is in front of you.

Otn. You have to have everything downloaded for this to work properly. Including Java runtime. Now it's working like never.

manolito is a big boy mr. Groucho. He doesn't need to be cuddled by anyone. Especially you. Stop behaving as an emotional 2 year old coming to someone's rescue. Remember please if there's enough space between your ears what happens to volunteers and heroes. You want to be useful? Shut up and fix w/e is still wrong with any freeware. It's free for a reason.
I will definitely hit the donate button for whomever the link to AVStoDVD goes. It's worth it. Again make sure everything is installed, and if the preview window doesn't open the file run the AviSynth tool from the codec option. Also just close it and open it up again. If it goes black your good.
I've had more women than you or anyone you know has ever had! Even if I go right now and you stay I'd have more. If you're one of these puppies that wobble their heads up and down every time your w/e significant other says something, then please refrain from a real man's world. Have a good night. Beware of open subtitles.org, they're messing with the subs and hardcoding them with a sign up message. Screwed me up after a 2 hour encode. Common sense isn't common anymore. Why on earth provide a free service then complain about it. If you want to charge then charge from the beginning.

[thescrapyard]

Don't use codecs packs, they can and usually do cause more headache than they claim to fix. I tried them a few years back and ended up doing a full system reinstall because of all the drivers they updated or replaced with their own 'optimized' versions and made a right mess

LAVFilters should be good enough for pretty much everything. I use only PotPlayer and its good enough MLC should be even easier. I personally stay away from VLC Player after trying to use a few different times but other love it

I went back to Windows 7 as I got fed up of Windows 10 telling me half my software wasn't doing things the Microsoft way and refusing to play nicely with them

There are 'some' things that CAN be replaced with 64-bit versions in AVStoDVD, BUT make sure its working first THEN replace files. If it breaks then YOU have made the mistake

DO NOT replace FFMPEG with 64bit versions it WILL NOT work, I've tried and it won't. 32bit and 64bit are actually not that much different in speed, more about how much memory then can access

If you think AVStoDVD is outdated, then try looking at DVD Rebuilder. Thats even older and hasn't been updated in years BUT its very very good at what it does and the output quality is better than anything. That also uses HCEnc so the quality is on par


AVStoDVD works great with Avisynth and also now Avisynth+, which is why I use it, some don't work correctly and has difficulties with complex scripts (MeGUI personally is a pain)


My suggestion is to total remove AVStoDVD from your system, and klite codecs pack (if you can remove it ALL). Reinstall AVStoDVD (noinstall is my persoanl choice), install LAVFilters ONLY and try again (Make sure to check the codecs as Microsoft has a habit of refusing to change to anything but theirs ... which suck). If it still fails then you KNOW AVStoDVD is at fault

Dual audio DOES work, BUT some video releases from 'sources' fails to play convert, as I personally, just simply a crap source

[Groucho2004]

Usually those that speak about men are the ones that get with them.
...
I've had more women than you or anyone you know has ever had! Even if I go right now and you stay I'd have more. If you're one of these puppies that wobble their heads up and down every time your w/e significant other says something, then please refrain from a real man's world.
You don't have to pretend to be something you're not. Denial is toxic. Embrace what you are!

[manolito]

You have to have everything downloaded for this to work properly. Including Java runtime. Now it's working like never.

AVStoDVD comes with a very good and comprehensive documentation. These days unfortunately a lot of users think that reading manuals is a waste of time... :devil:

From the doc:
Software requirements
· Microsoft Windows 2000/XP/Vista/7/8/10
· Microsoft DirectX 9.0 or higher
· AviSynth 2.6.0 or higher (AviSynth 2.6.0 is included in the installer)
· A good media splitter (LAV Filters 0.73.1 is included in the installer)
· A good 32bit DirectShow codecs/filters suite (LAV Filters is included in the installer, ffdshow is a valid alternative, but do not install both of them)
· Microsoft Windows Common Controls 6.0 ActiveX Library (mscomctl.ocx, included in the Installer, see the NOTE below)
· Microsoft .NET Framework 2 (required to encode and author text-based subtitles)
· Java Runtime Environment (required to encode and author bitmap-based subtitles)
· ImgBurn 2.5.0.0 or higher (not mandatory, but required to build DVD ISO Images and to burn DVDs)

For updating the A2D helper software also have a look at this post:
https://forum.doom9.org/showthread.php?p=1814958#post1814958

Cheers
manolito

[dr_ml422]

Everything seems to be fine now. I downloaded and installed everything including Java Script. Only thing now is a darker output? Was this taken care of previously in an update? I see mention of it in a post, but just an individual adjustment with Lumin Gain or something like that.

Hope anyone who likes it is enjoying "Game Of Thrones". It really is one of the best series all time imho.

How is DVDStyler fairing nowadays? Should I go with the 64 bit build or stay with the 32 bit? Not too many apps I've used in 64 bit have really panned out. Always something going wrong. Looks great!

I'm looking into the AVStoDVD Helper software update now. Thanks.

Be very cautious when using OpenSubtitle as they now are almost demanding support?! When using MPC's auto subtitle option it goes to opensubtitle and it downloads and puts in the subtitle. Only thing it comes with a warning message embedded in all the way through the movie. Or it'll just say it at the end. It totally messed up at least 2 of my movies from AVStoDVD and I had to redo them over from scratch.

Do you highly recommend that flawlessly working FFMS2 C plugin to update the older one? Thanks.

[manolito]

Only thing now is a darker output?

This should not happen. The most likely reason is that your source uses a different color scheme than your target. Generally you can say that HD content uses Rec709 and SD content is Rec601. But this is not always the case, and AVStoDVD makes no general assumption about the source color format. Only if MediaInfo explicitly reports Rec709 the ColorMatrix filter will be automatically used to convert the color to Rec601.

So if you find a discrepancy between the source and the target, you need to experiment with the ColorMatrix filter in your AVS script. If Colormatrix is present, try to comment it out and see what happens. If it is not there, try to add it right after the source filter.

How is DVDStyler fairing nowadays? Should I go with the 64 bit build or stay with the 32 bit? Not too many apps I've used in 64 bit have really panned out.

Compared to AVStoDVD you will get much more elaborate menu creation abilities. For transcoding it only uses FFmpeg (A2D uses FFmpeg only for very high video bitrates, otherwise it uses HCenc). Most people say that HCenc creates slightly better quality encodes than FFmpeg, but when using the right parameters FFmpeg these days certainly delivers very high quality. Since my FFmpeg-VBR plugin has been transparently integrated into DVDStyler the quality may even be higher in some cases than HCenc, at least for low bitrate encodes. You need to test this yourself.

If the 64-bit version of DVDStyler gives you a speed boost mainly depends on how much memory FFmpeg will address when doing an MPEG2 encode. Since the output will be SD and not HD the memory consumption is probably quite limited, so the speed gain will be small or even nonexistent. Personally I only use the 32-bit version of DVDStyler.

Do you highly recommend that flawlessly working FFMS2 C plugin to update the older one?

See this post:
https://forum.doom9.org/showthread.php?p=1868878#post1868878

If you never use high bitdepth sources then you won't be affected, no problem to continue using the version which comes with AVStoDVD.


Cheers
manolito

[MrC]

Guys, just to tell you that AVStoDVD is still alive (for the dinosaurs like me that stubbornly use it). A new release will be available soon. Mainly bugfixes (e.g. https://forum.doom9.org/showpost.php?p=1868878&postcount=3151 or https://forum.doom9.org/showpost.php?p=1869507&postcount=3153) and support to HDMV presentation graphics BluRay subs.

Stay tuned.

;)

Bye

P.S. Now is the right time to go out with requests, suggestions and complaints. Not too fanciful, we come from the Jurassic.

[manolito]

Guys, just to tell you that AVStoDVD is still alive (for the dinosaurs like me that stubbornly use it).

This is really good news... :D:D

Just when I started to think that this software is no longer maintained. My usual threshold is 6 months. If a software has not been touched by its author for this time then it is normally safe to assume that there will be no further development. Almost 5 months in this case...

I cannot think of too many feature requests, the software is almost perfect in its current state. The bug fixes you already mentioned (of course do not forget to integrate the latest hotfix from 15.01.2019) will be very welcome.

No idea if supporting AVS+ better by adding multithreading automatically would be a good idea. It is not without problems depending on the plugins which are used, so it mght be better to leave it to the users to add the appropriate params to the AVS script. The same goes for the LSMASH source filter. In some cases it gives better results than FFMS2, but the interface is not compatible with FFMS2, and advanced users can easily add it themselves by editing the AVS script.

Alright, these are my 2 cents...

Cheers
manolito

[MrC]

My bad... AVS+ w/ SSRC (https://forum.doom9.org/showthread.php?p=1811053#post1811053)...

In your knowledge, are there any other classic AVS functions that do not "explicitly" works with AVS+?

:scared:

Bye

[manolito]

Thanks for digging out this 2 year old stuff. It was amazing for me to see how I got carried away quite a bit in my disgust about the AVS+ devs deliberately breaking backward compatibility to classic AVS. But my points are still valid.

And so far (to the best of my knowledge) this is the only occasion where AVS+ is not compatible with classic AVS.

Luckily this has only a minor impact for AVStoDVD. If the selected source filter can output 32-bit float audio then there is no problem if the script contains SSRC. For LAV audio this means that the user should not disable 32-bit float audio in the audio filter setup. For all audio source formats I use LAV audio will output 32-bit float as long as the user has not disabled it.

FFMS2 also outputs 32-bit float audio by default, there is no problem with AVS+.


But integrating AVS+ support into AVStoDVD still can cause problems. Just adding a "Prefetch()" command at the end of the AVS script won't be enough. There are many older AVS plugins which need special treatment when multithreading is enabled.

I had numerous problems with random crashes until almosely posted this:
https://forum.doom9.org/showthread.php?p=1865279#post1865279

There are a couple of older filters which need to be run in MT_SERIALIZED mode, sometimes requiring an additional "RequestLinear" command. Colormatrix is one of the problematic filters. After a lot of experimentation I managed to get AVS+ running absolutely stable on my machine, but the speed gain from multithreading is far from spectacular. All the additional AVS+ features like support for high bit depth and fancy color spaces are irrelevant for AVStoDVD since the DVD format only supports 8-bit with 4-2-0 color space (YV12).

So I really do not know if AVS+ support is essential for AVStoDVD. My FF_VBR and HCenc_Mod plugins do support it already, but they require a little bit of effort from the users.


Cheers
manolito

[MrC]

Yeah, I got thru the posts your disappontment... it was mine as well.

In case of using LAV Filters or FFMS2 there are no problems, but if using MS filters (like MP3 Decoder DMO, which is not that bad), the output is not float, so AVS+ throws out an error w/ SSRC. Anyway, when AVS+ is detected, I will add a ConvertAudioToFloat function to SSRC.

Thanks for the other hints about AVS+. Nevertheless I'm not willing to add full compliance to AVS+, for now. Simply I do not have the time to do that.

2.8.9 Alpha is almost ready.

;)

Bye

[manolito]

Nevertheless I'm not willing to add full compliance to AVS+, for now. Simply I do not have the time to do that.

This is fine with me. Maybe I will add a small guide how to use AVS+ with my FFmpeg_VBR and HCenc_Mod plugins to my plugin distribution...


Cheers
manolito

[MrC]

AVStoDVD 2.8.9 Alpha 190519 is available (https://sourceforge.net/projects/avstodvd/files/avstodvd_alpha_beta/AVStoDVD%202.8.9%20Alpha%20190519/).

Change log:

- Added support to PGS BluRay subtitles
- Added handling and display of MediaInfo BitDepth video tag
- Added support to 8 channels audio source (Downmix.avsi script file updated)
- Improved Muxing routine: better errors handling and switch to FFmpeg (instead of Mplex) when no audio source is present
- Improved usage of FFMS2: now YV12 colorspace is always specified (A2DSource external AviSynth function updated as well)
- Improved AviSynth program info retrieving routine (now using AVSMeter)
- LAV Filters updated to release 0.74.1

Feedbacks and suggestions are welcome, mainly on 8 to 6 audio channels downmix routine, which is very basic.

;)

Bye

[manolito]

Thanks a lot for this new version, put it on my test bench already, here's what I think...

As usual I cannot comment on the new subtitle support feature. I don't do BluRay, and I don't ever use subtitles.

The same goes for the 8-channel audio downmix feature. I only do stereo (maybe mono sometimes) and 6-ch audio sources, I never came across an 8-ch audio source. I would suggest to ask Tebasuna about the new downmix.avsi.

The new muxing routine for sources without any audio tracks works fine. The only thing I found is that for such cases the AVS script is not deleted, even if the options to delete helper files are ticked. No big deal. BTW you could have continued using mplex even for video-only sources by omitting the -L option of mplex.

Always specifying the YV12 colorspace option for ffms2 works perfectly.

Adding the ConvertAudioToFloat function to SSRC does not work for PAL speedup or NTSC slowdown. For a command like this:
AssumeFPS("pal_film", sync_audio=true).SSRC(48000)
the ConvertAudioToFloat call does not get added. BTW for the sake of consistency you should use ConvertAudioToFloat() with the brackets.

And now really nitpicking... :D
The new AviSynth detection routine using AVSMeter works nicely, but it sure slows down the AVStoDVD startup. Not too bad on my Core i5 Win 7 laptop, but very much on my ancient desktop machine. (please ignore this...)


Cheers
manolito

[MrC]

Thanks manolito, you are my usual savior :)

To mitigate the slow start, I can add a message to wait for the ext sw properties to be read.

;)

Bye

[Groucho2004]

The new AviSynth detection routine using AVSMeter works nicely, but it sure slows down the AVStoDVD startup.AVSMeter checks all auto-load plugins for compatibility/dependencies/bitness. If you have lots of plugins and a slow CPU, this will slow down the detection process.

AVStoDVD should probably check the "[Plugin errors/warnings]" section of the log file (if present, see example below) and throw an error message if necessary.

[Plugin errors/warnings]
_______________________________________________________________________________________________________

Cannot load file 'E:/Apps/VideoTools/AVSPlugins/AutoLoad/LSMASHSource.dll'. Platform returned code 127:
The specified procedure could not be found.

Note: You may need a newer OS version in order to use this plugin
_______________________________________________________________________________________________________


Alternatively, I may add a switch for basic Avisynth info without the plugin parsing.

[manolito]

Maybe I will add a small guide how to use AVS+ with my FFmpeg_VBR and HCenc_Mod plugins to my plugin distribution...

Done... :)

Download link is at the bottom of this post:
https://forum.doom9.org/showthread.php?p=1814958#post1814958


Cheers
manolito

[manolito]

To mitigate the slow start, I can add a message to wait for the ext sw properties to be read.


No need for this any more...

I had a PM exchange with Groucho2004, and he agreed to compile a modded version of AVSMeter 2.6.5 especially for AVStoDVD. This modded version does not check the AVS autoload plugins at all making it way faster than the original version. On my Win7 computer with AVS+ there is almost no startup delay at all, and on my ancient WinXP machine the delay was reduced from more than 15 seconds to less than 3 seconds.

Here is the link:
https://www.dropbox.com/s/z1ekmfrhlkf4te3/AVSMeter_265_mod01.7z?dl=1

Please include this version with the next AVStoDVD versions, and many thanks to Groucho 2004... :D:D


Cheers
manolito

[MrC]

Great! Special release for A2D! Wow! Thanks manolito and Groucho2004. I will check it out ASAP.

;)

Bye

[dr_ml422]

Thank you very much manolito for all your help and your input! everything seems to be working fine with AVSTODVD now, especially after I installed Java. I think that it probably was the source a bit that was a bit dark and so when putting it through AVS to DVD it just came out just a little bit darker but it was dark to begin with. The movie was "Unforgiven" and that movie is dark to begin with anyway. Yes I stayed with the 32-bit applications myself because as I said many of the 64-bit applications just don't take well for whatever reason. I don't think they pay too much mind to it seeing that here in the states we're way behind in a lot of things especially with 64-bit computing. There's not too much of a speed gain that you will get with 64-bit and video work. The only observable gains that you will ever get with video work and encoding is having at least a quad-core and up CPU and of course the appropriate Ram to go with it.

if there's anything that needs to be looked at would be the preview window which as I noticed all you have to do if it doesn't show up the first time is just close it and open it up again and then you will get the picture going. other than that everything has been working very very well with Windows 10 64-bit home premium and the last build before the next 1809 update.

Manolito I'm going to take a look at DVD Styler as it's been getting a lot a lot of positive reviews online if you haven't noticed it yet. Seems they've been keeping up with it and keeping it present with any bugs and fixes etc etc.

Yes you're correct about the ffmpeg encoder and how to use it correctly. I'm not that skilled knowing how to be as advanced user with those kind of things, the only thing I've seen is that VSO's convert x to DVD and anything else they use is based on the ffmpeg encoder and they seem to be doing very very well with that app. They also have some kind of optimization going on as well that I don't know about which will give you almost always a two-point 6 GB more less DVD with excellent quality.

My Specs if anyone is going to upgrade their PC.

ASRock B450M mobo
AMD Ryzen 5 2600 CPU
32gb Crucial Ballistic DDR4 Ram
Crucial 500gb NVme SSD
POWERSPEC Midtower

I'm getting 18 mins. or less with DVD-RB Pro.
1200fps with DVDFab Converter and their default settings for MKV etc...
AVStoDVD also about 18mins.

There might be a hole in the Cinavia protection when ripping to mp4 etc... I'm not 100% sure but it seems like it just kicks in when copying to DVD.
If you have a Blu-ray drive some are copying ultra hd straight to the drive also. They got hip to it with one of the LG drives.
This is the time to rack up with the DVDs as they're not paying attention to them anymore like they used to. so I went back and got some old downloads from the old Goodies which we all know without naming them which I just name one DVD shrink and the other software that came before image burn and the other one that's associated with those two and I'm getting some very very quality clean Rips!

[manolito]

if there's anything that needs to be looked at would be the preview window which as I noticed all you have to do if it doesn't show up the first time is just close it and open it up again and then you will get the picture going.
Are you aware that you can specify to use a different external player for the preview? Go to "Preferences -> Paths" and check out if other players work better for you...

[MrC]

Just uploaded latest 2.8.9 Alpha (https://sourceforge.net/projects/avstodvd/files/avstodvd_alpha_beta/AVStoDVD%202.8.9%20Alpha%20190616/).

Cumulative 2.8.9 change log:

- Some bugs fixed
- Added support to PGS BluRay subtitles
- Added handling and display of MediaInfo BitDepth video tag
- Added support to 8 channels audio source (Downmix.avsi script file updated)
- Improved Muxing routine: better errors handling and switch to FFmpeg (instead of Mplex) when no audio source is present
- Improved usage of FFMS2: now YV12 colorspace is always specified (A2DSource external AviSynth function updated as well)
- Improved AviSynth program info retrieving routine (now using AVSMeter)
- LAV Filters updated to release 0.74.1
- AVSMeter updated to 2.6.5.1 (2.6.5 modded release to improve reading speed)

;)

Bye

[manolito]

Yes, I am totally happy with this new version... :thanks:

All the small issues I found with the previous Alpha are fixed, as far as I am concerned this is a release candidate.

Thanks again
manolito

[MrC]

Thanks manolito for the feedback. Just to update the Help section and the 2.8.9 final will be released.

;)

Bye

[Mike-uk]

Hi, Great program and nice to see your still working on it :)

a few Qs

ive tried to search the internet for my answers but not getting what im after

my source files are 1080p clear clean and sharp as youd expect from modern 1080p source :)

so ive set all the normal setting in avstodvd to max

but there is the avisynth settings

video and audio filter, and upsize and downsize
would changing any of thouse to a different one make the resulting dvd better ?? im after producing the best quality dvd i can

also source files are 23.9 fps im converting to pal so is pal speedup still the best method for reducing panning jerking on dvd playback ?

thanks

Mike

[MrC]

Hi Mike-uk,

first of all thanks for the kind words.

Quality wise, you can start by leaving the default options and judge with your eyes the result. If HCenc VBR 2pass is not auto selected, you can force it in Edit Title > Video > Video Encoder. Then you can play with HCenc Advanced Options.

There are no magic rules to obtain the best result: the "best" depends on the type of video input and your subjective evaluation of the output.

I agree that PAL Speedup is the optimal choice for NTSC-film to PAL conversions.

There is also the possibility to use the ff_vbr plugin by manolito, which brings FFmpeg to its max quality level. I would leave manolito to jump in and to explain how it works.

;)

Bye

[Mike-uk]

ok thanks for the reply, i will try some of those options

[manolito]

Sorry for the late reply, I am just back from my annual motorcycle trip... :cool:
Austrian and Swiss mountains this time, very nice driving, a little bit too hot for my taste.


The AviSynth source filters do not really have an influence on quality, it's more like some work better on specific source formats than others. The default "A2DSource" is not a source filter by itself, instead it tries several source filters until it finds one which does not issue an error message. It tries the filters in this order: AVISource, DSS2Mod, FFMpegSource, DirectShowSource. Mostly you will end up with DSS2Mod which works very well with most sources.

The different resizers are really a matter of personal taste. Some resizers are sharper than others, often with the downside that they introduce ringing artifacts. My all time favorite is Spline36Resize for upscaling and downscaling, it is very neutral without visible artifacts. BlackmanResize is also a very high quality resizer.

For NTSC-film to PAL conversions the PAL-Speedup method is the most widely used method. It does not introduce judder, but for audio with musical content some folks will notice the audio speedup due to the higher pitch. If you want to speed up audio, but keep the original pitch you can do that by editing the AVS script to use the AviSynth TimeStretch function. But this has a tendency to create audible artifacts, you may want to use external commercial timestretch software which delivers better quality.

A while ago I found an excellent script at VideoHelp which avoids all these disadvantages. Gavino was involved in creating this script, and this always means that it is state of the art...

Progressive 23.976 NTSC to Progressive 25 PAL.avs:
# Alternative method avoiding speedup or pulldown.
# No audio speed correction required.
# Insert after the resizer.

# -------------------------------------------------------------

Last = Video
f1=ChangeFPS(24)
f2=Trim(0,-1).AssumeFPS(24) + Trim(1,0).ChangeFPS(24)
Film=Merge(f1,f2)
p1=ChangeFPS(Film,25)
p2=Trim(Film,0,-1).AssumeFPS(25) + Trim(Film,1,0).ChangeFPS(25)
Pal=Merge(p1,p2)
Last = PAL.AssumeFPS(25)
Video = Last

#-------------------------------------------------------------

To use this method you select Pal-Speedup in AVStoDVD. Then paste the above script into the AVS script which was created by AVStoDVD just after the resizer command. Finally you need to delete the whole "AssumeFPS" call (but keep the SSRC or ResampleAudio command).


If you have more questions don't be shy to ask...


Good luck
manolito

[Mike-uk]

Thanks manolito

[Mike-uk]

hmm ok so i edited the avisynth script in avstodvd but it goes red ??, also hcenc says it dont understand the script ??

[manolito]

Whenever the AVS script in AVStoDVD is edited, it goes red to signal the user that he no longer uses the automatically generated script. This is perfectly normal.

To understand the HCenc error please post your edited script and also the exact HCenc error message...

[Mike-uk]

ah sorry my bad :P , i wasnt deleting assume fps from audio, all seems ok now

[manolito]

Glad you got it working... :D

And how do you like the quality?

Another tip I forgot to mention is when using high quality HD sources you will often be a little bit disappointed by the SD quality of the resulting DVD. I found that using FineSharp by Didée does a very good job of bringing back some of this crisp HD character to the result. If you are interested, get it here:
https://www.sendspace.com/file/s5wu0v
Just extract the files into your "AviSynth\Plugins" folder and add "Video = Video.FineSharp()" (without the quotes) to your AVS script.

Cheers
manolito

[Mike-uk]

cheers manolito, havent had a chance to try out an encode with ffmpeg yet but when i do ill also try that plugin also

thanks

[Mike-uk]

cant get Video = Video.FineSharp() to work ??

<06/07/2019 11:54:05>
AVISYNTH SCRIPT
Import("C:\Program Files (x86)\AVStoDVD\Lib\A2DSource.avsi")

Video = A2DVideoSource("F:\Movies\test.mkv", CacheFolder="C:\Users\user\AppData\Local\Temp", VFR=false, FrameRate=23.976)
# Audio is frameserved by AviSynth just for Preview and Edit purposes.
Audio = A2DAudioSource("F:\Movies\test.mkv", CacheFolder="C:\Users\user\AppData\Local\Temp")

Video = Video.FineSharp()
Video = Video.ConvertToYV12()
Video = Video.AddBorders(0,140,0,140)
Video = Video.Spline36Resize(720,576)
Last = Video
f1=ChangeFPS(24)
f2=Trim(0,-1).AssumeFPS(24) + Trim(1,0).ChangeFPS(24)
Film=Merge(f1,f2)
p1=ChangeFPS(Film,25)
p2=Trim(Film,0,-1).AssumeFPS(25) + Trim(Film,1,0).ChangeFPS(25)
Pal=Merge(p1,p2)
Last = PAL.AssumeFPS(25)
Video = Last


AudioDub(Video, Audio)
SSRC(48000)

Trim(0,5000)
<>

<06/07/2019 11:54:05>
DIRECTSHOW AUDIO MIXER OPERATIONS:
No LAV Filters mixer ON/OFF adjustment required at runtime
<>

<06/07/2019 11:54:05>
START VIDEO ENCODING OPERATIONS
Video Encoding Profile: FFmpeg CBR 1-pass
Target Video FileSize: 203.9 MB
Encoding Parameters: -i "C:\Users\mike7\AppData\Local\Temp\DVD_14_test.avs" -threads 12 -aspect 16:9 -c:v mpeg2video -b:v 8552k -minrate 8552k -maxrate 8552k -bufsize 2000k -dc 10 -bf 2 -mbd rd -cmp 2 -subcmp 2 -y "C:\Users\mike7\Videos\DVD_14_test.m2v"
<>

<06/07/2019 11:54:10>
Process aborted during Title 1 VIDEO encoding operations.

Error Message: Warning! Title 1 output Video duration (00:00:00) is shorter than expected duration (00:03:20).

For Video issues troubleshooting see Help/FAQ/Video section.
<>

<06/07/2019 11:54:10>
Warning! AVStoDVD Project ended with errors.

[manolito]

FineSharp only works in YV12, so the filter needs to be AFTER the "ConvertToYV12()" statement.

Also did you extract all three files to the AviSynth autoload folder (usually "C:\program files x86\Avisynth\Plugins"). If there is another MaskTools2 DLL in this folder please try to rename the extension temporarily to DL_. Plus make sure that you have all current VC++ runtimes installed. The easiest way to do this is using the AIO runtime installer by abbodi1406 hrom here:
https://github.com/abbodi1406/vcredist/releases

[Mike-uk]

still no joy in getting finesharp to work

this is the error ffmpeg gives

[avisynth @ 02c77200] Script error: there is no function named "repair"
(FineSharp.avsi, line 48)
(C:\Users\user\AppData\Local\Temp\test.avs, line 8)


line 48

\ : mt_lutxy(shrp,shrp.removegrain(20,-1),"x x y - 9.9 * +",U=2,V=2).repair(shrp,12,0).mergeluma(shrp,1.0-xstr)

[Groucho2004]

there is no function named "repair"You need RGTools (https://github.com/pinterf/RgTools/releases)

[manolito]

Sorry, completely forgot Repair.DLL from Kassandro`s RemoveGrain package... :o

Get it here:
https://www.sendspace.com/file/gj6w3e

or use RGTools as Groucho suggested. But then you need to delete RemoveGrain.DLL from your autoload folder to avoid having two different DLLs with identical functions.

[Mike-uk]

Thanks Groucho and manolito all working now

[manolito]

Any comments on the visual quality of the resulting DVD?

[jim26]

Hi, and thanks for all the help. I have a question. Why when i am using the script about converting from NTSC to PAL the resulting DVD is oversized? Instead of being about 4,32 gb it results to about 4,50 gb.
<13/07/2019 09:29:58>
AVISYNTH SCRIPT
Import("C:\Program Files (x86)\AVStoDVD\Lib\A2DSource.avsi")

Video = A2DVideoSource("C:\Users\Dimitris\Desktop\MyMovie.mkv", CacheFolder="C:\Users\Dimitris\AppData\Local\Temp", VFR=false, FrameRate=23.976)
Audio = A2DAudioSource("C:\Users\Dimitris\Desktop\MyMovie.mkv", CacheFolder="C:\Users\Dimitris\AppData\Local\Temp")

Video = Video.ConvertToYV12()
Video = Video.AddBorders(0,86,0,88)
Video = Video.Spline16Resize(720,576)
Last = Video
f1=ChangeFPS(24)
f2=Trim(0,-1).AssumeFPS(24) + Trim(1,0).ChangeFPS(24)
Film=Merge(f1,f2)
p1=ChangeFPS(Film,25)
p2=Trim(Film,0,-1).AssumeFPS(25) + Trim(Film,1,0).ChangeFPS(25)
Pal=Merge(p1,p2)
Last = PAL.AssumeFPS(25)
Video = Last


AudioDub(Video, Audio)
SSRC(48000)
<>

[Mike-uk]

Any comments on the visual quality of the resulting DVD?

i did 2 encodes 1 with hcenc all high settings 2pass and ffmpeg 2pass ultra hq with finesharp, ive played them side by side, the ffmpeg version i would say has slightly better sharpness on letters buts its hard to see any major difference, but i guess thats partly due to the low res of dvd, what can we expect from such res, but i guess we are getting the absolute best we can from dvd standard now

[manolito]

Why when i am using the script about converting from NTSC to PAL the resulting DVD is oversized? Instead of being about 4,32 gb it results to about 4,50 gb.

Sorry, no idea... :eek:

Is this consistent for all sources, or did it just happen with one specific source? Also if you used 1-pass VBR for the conversion, please try to use 2-pass instead.

[jim26]

I am using HCenc vbr 2-pass. I will try a different source and i will comment later, thanks!

[jim26]

Unfortunately same thing and with other sources. I am gonna use the PAL speed up from AVSTODVD that works fine.

[manolito]

Alright, I found it... :devil:

When calculating the required bitrate to reach the specified size AVStoDVD takes into account if speedup or slowdown is specified. When PAL speedup is selected, but the script is later modified so there will be no speedup, then the bitrate will be off by about 4%. :stupid:

To get the correct bitrate you need to do the following:
1. In Explorer go to the AVStoDVD\DGPullown folder and temporarily rename DGPulldown.exe to something else.
2. Fire up AVDStoDVD, under Preferences->AviSynth uncheck PAL Speedup.
3. Load your source, under View/Edit Title Settings->AviSynth edit the AVS script by inserting my script after the resize command.

Don't forget to rename DGPulldown.exe back to its original name when you are finished with your encode.


Cheers
manolito


P.S.
If you rather stick with the speedup routine, but you would like to add audio pitch correction (so audio will play faster, but at its original pitch), you can do this by using the AviSynth TimeStretch command. Let me know if you are interested...

[Mike-uk]

Alright, I found it... :devil:

When calculating the required bitrate to reach the specified size AVStoDVD takes into account if speedup or slowdown is specified. When PAL speedup is selected, but the script is later modified so there will be no speedup, then the bitrate will be off by about 4%. :stupid:

To get the correct bitrate you need to do the following:
1. In Explorer go to the AVStoDVD\DGPullown folder and temporarily rename DGPulldown.exe to something else.
2. Fire up AVDStoDVD, under Preferences->AviSynth uncheck PAL Speedup.
3. Load your source, under View/Edit Title Settings->AviSynth edit the AVS script by inserting my script after the resize command.

Don't forget to rename DGPulldown.exe back to its original name when you are finished with your encode.


Cheers
manolito


P.S.
If you rather stick with the speedup routine, but you would like to add audio pitch correction (so audio will play faster, but at its original pitch), you can do this by using the AviSynth TimeStretch command. Let me know if you are interested...

Thanks :)

[manolito]

If you rather stick with the speedup routine, but you would like to add audio pitch correction (so audio will play faster, but at its original pitch), you can do this by using the AviSynth TimeStretch command.

You did not ask for this, but I figured that it would be good to have all the possible NTSC to PAL conversion options explained in one place. So here comes how to use PAL speedup with pitch correction...

AviSynth has an internal TimeStretch function which lets you alter the pitch or the tempo of an audio stream. We will use the "tempo" parameter here.

In AVStoDVD you need to select "PAL speedup" under "Preferences", under "View/Edit Title Settings->AviSynth" the script must be edited like this: The line
AssumeFPS("pal_film", sync_audio=true).ResampleAudio(48000)

must be edited so it will become
AssumeFPS("pal_film").ResampleAudio(48000)
TimeStretch(tempo = 25.0/(24000.0/1001.0)*100.0)
(Instead of "ResampleAudio(48000)" there could be "SSRC(48000)" present in this line. Just leave it as it is...)

Some important notes about the different TimeStretch versions:
Classic AviSynth 2.60 comes with a rather outdated version of the TimeStretch plugin which does not support audio streams with more than two channels. There are several ways to deal with this:

1. Keep AVS 2.60, but download and install the external TimeStretch plugin by Wilbert. You can find it here:
https://forum.doom9.org/showthread.php?p=1722472#post1722472
Extract TimeStretch.dll into your AviSynth\Plugins folder. To make the external plugin coexist with the internal function, it must be called with "timestretchplugin()" instead of "timestretch()". Make sure your VC++ redistributables are installed. Get the latest versions here:
https://github.com/abbodi1406/vcredist/releases

2. Upgrade to AviSynth 2.61 Alpha. Don't worry about the "Alpha" label, it is stable. Download the stripped-down version here:
https://www.sendspace.com/file/gvkxp1
No installation required, just extract the files into the corresponding folders overwriting the existing files.

3. If you are adventurous you can upgrade to the latest AVS+. The current AVStoDVD version supports it. Only use the latest release from here:
https://github.com/AviSynth/AviSynthPlus/releases
Note: The installer defaults to installing both the 32-bit and the 64-bit versions. AVStoDVD can only use the 32-bit version, so you could probably uncheck the option to install the 64-bit version (unless you have other software which can use the 64-bit version).


Cheers
manolito

[Mike-uk]

Thanks again Manolito

[Mike-uk]

hmm why is mediainfo reporting a file is only 6 seconds long when its actualy 2 hours ??, so avstodvd wont work

[manolito]

Obviously this should not happen, but sometimes it still does...

It could be MediaInfo itself, or your source file is problematic. You can try updating MediaInfo to the latest working version 18.5. The DLL is here:
https://www.sendspace.com/file/m4myu1
Just extract the DLL into your "AVStoDVD\Lib" folder.

Otherwise try to remux your source, maybe using a different container. If your source is a transport stream (extension TS, MTS, M2TS) then it is always a good idea to remux it into an MKV container (use MKVToolNix). The reason is that transport streams do not contain time stamps, but MKV streams do.

Good luck...

[Mike-uk]

ah hmm, something seems to be broken with my system :(, so i swaped out media info for the 18.5 and now it displays no media info, ive uninstalled and reinstalled avstodvd and still the same :(

see attached photo

16914

[manolito]

First of all do not attach pictures directly in this forum, it can take forever until a moderator approves them. Use a hosting service like postimg.cc instead.

Did you really replace "Mediainfo.dll" in the "Program Files (x86)\AVStoDVD\Lib" folder with the extracted version from my upload? Or did you just copy the uploaded ZIP file?

[Mike-uk]

no i extracted the mediainfo.dll to the lib folder, although just noticed a strange thing within avstodvd in the operations window its saying mediainfo v19.07 initialized ??

but in avstodvd prefrences and under software it clearly says it has found version 18.5.0.0

[manolito]

All MediaInfo versions after 18.5 are NOT compatible with AVStoDVD. Looks like you have version 19.07 installed somewhere else on your computer, and this folder where the newer version is located is in your environment "Path" variable.

[Mike-uk]

yes i unfortunately installed 19.07, but have uninstalled mediainfo and avstodvd reinstalled avstodvd and still the same, avstodvd is set to the correct path to mediainfo.dll and reports 18.5 but when avstodvd reads a file it seems its still seeing 19.07 ?? not sure whats happened :(, looks like i need to reinstall windows

[manolito]

No you don't need to reinstall Windows...
Use Search to find all instances of MediaInfo.dll on your System partition. If you find any instance of the file in a folder like "syswow64" check the version (just hover the mouse over the file), and if it says "version 19.07" delete the file.

[red5goahead]

Hi guys.

I was wondering if you could manage the automatic avi script with the automatism that allows you to perform an interlaced encoding with better motion quality. If the source is progressive at 50 fps and you have chosen to interlace currently the script is as follows

Video = Video.ConvertToYV12()
Video = Video.Spline16Resize(720,576)
Video = Video.SelectEven()

but as we have already verified with Manolito, in this case with a real 50 fps at source, the most correct script would be this

Video = Video.ConvertToYV12()
Video = Video.Spline16Resize(720,576)
Video = Video.AssumeTFF()
Video = Video.SeparateFields()
Video = Video.SelectEvery(4,0,3)
Video = Video.Weave()

another question: is it not possible with AVStoDVD edit the source? Even just at the beginning and at the end?

I prefer HCenc because have 2-pass mode that it is not allowed with ffmpeg

Thank you!

[Mike-uk]

No you don't need to reinstall Windows...
Use Search to find all instances of MediaInfo.dll on your System partition. If you find any instance of the file in a folder like "syswow64" check the version (just hover the mouse over the file), and if it says "version 19.07" delete the file.

Thanks you saved the day again

[manolito]

Thanks you saved the day again

Now that you got MediaInfo 18.5 working, does this version report the correct duration of your problematic source file?

[manolito]

@ red5goahead

Nice to see you back so soon... :)

Yes, in AVStoDVD you can edit the source, but you can only cut away one section at the start and another section at the end. No splicing together multiple parts. This is how you do it:

Load your source and click "View/Edit Title Settings -> AviSynth". Untick automatic script creation and press the Preview button at the lower left. Now you have two additional buttons "[" and "]" which let you set the start and end frames. Close the preview window, now you will notice a new Trim command at the end of the script.

Usually using HCenc is preferred over FFmpeg. By default FFmpeg only allows basic CBR encodes without B-Frames. This will only give you good quality at very high bitrates, and this is how AVStoDVD uses it by default. But you can also use FFmpeg in 1-pass and 2-pass VBR modes by installing my VBR plugin:
https://files.videohelp.com/u/172211/Manolito_s%20A2D%20Plugins.7z
It is almost identical to the DVDStyler plugin. Only there is no integration into the software, users have to edit a batch file with NotePad to change settings.


For using the script to interlace 50fps sources, don't forget to also set "Interlaced TFF" flags for the encoder. After editing the scipt go to the Video tab, uncheck Automatic and tick "Interlaced -> TFF". If you forget this, the encoder will encode the (now interlaced) source using progressive settings, very bad for the quality.

I do have my doubts if MrC will agree to make this automatic, though. It is not too common creating an interlaced DVD from a progressive source. Then having a 50fps progressive source means mostly that the broadcaster just inserted duplicate frames. At least for film sources which were originally shot at 24fps the broadcaster just speeds it up to 25fps and then inserts a repeated frame for every source frame. In such cases interlacing it makes no sense. Users would have to analyze the source first before making a decision about interlacing it or not.


Cheers
manolito


//EDIT//
but you can only cut away one section at the start and another section at the end. No splicing together multiple parts.
Actually there is an easy workaround for this restriction. It uses VirtualDub together with a simple tool called VCF2AVS. Basically you just load your source into VDub, do all your edits, then save your work into a VCF configuration file with "Save Processing Settings". VCF2AVS converts this into an AVS file which has all the necessary Trim commands in it. Paste these Trim commands to the end of your AVS script in AVsToDVD...

[red5goahead]

The editing function is more than enough but the problem is that you do not see the video and therefore it is not usable (I'm under Windows 10 64 bit 19H1)

https://i.postimg.cc/44tQLRHL/immagine.png

As for the fact that sources are hardly at 50/60 fps real is certainly true but with Hdmi acquisition cards this is possible (or in my case a sender Hdmi that using multicast, I wrote a utility (https://github.com/Red5goahead/Lenkeng-Hdmi-Extender-Encoder)to grab it with ffmpeg). Avstodvd developers could add a check as for the DV source confirming manually that the source is at 50/60 fps real and set the proper avisynth script

[manolito]

Damn, another report that the A2D preview is not working under Win10... :mad:

You are not the first user with this problem. A2D uses the ancient Quartz.dll for the preview, but I never found something that MS has stopped supporting this method under Win10. I am on Win7-64, and I have no problem with the A2D preview. If there is no way to make the preview work, you know that you can specify a different software player for the preview under preferences? Just no editing...

Here is something you could try:
The batch file in the linked archive restores a couple of AviSynth Registry entries which get altered by installing LAV filters. It may or may not help, but it sure does not do any damage.
https://www.sendspace.com/file/l9zgsz

The other file in the archive is VCF2AVS which you need if you want to use the VDub method to edit your source files.

Avstodvd developers could add a check
There's only one single A2D developer, and this is MrC. Unfortunately he does only have very limited time lately to work on AVStoDVD, I try to help out with user support as much as I can, but of course my contributions are limited - I am just an informed user, not a developer.


Cheers
manolito

[Mike-uk]

Now that you got MediaInfo 18.5 working, does this version report the correct duration of your problematic source file?

the m2ts file is still not seen correctly, but i plexed into an mkv and then tried to mux back into an m2ts with tsmuxer and it complained about a track not being reconised i ignored it and let it mux and it works fine, also the mkv works fine too

[manolito]

Another thing you can try for transport streams is TSDoctor. It is payware, but they have a 30 day trial period.

[manolito]

Here are some updated audio downmix functions for AVStoDVD for possible inclusion for the next version... ;)

The discussions are here:
https://forum.videohelp.com/threads/277852-AVStoDVD-Support-Thread/page128#post2557993
https://forum.doom9.org/showthread.php?t=176788

From the Readme:
Updated audio downmix functions for AVStoDVD
---------------------------------------------

Proposed by JuMe from the VideoHelp support forum
and using some help by tebasuna51


These are the changes:

1. Fixed a bug in the function "Dmix6Dpl2Lfe".
(The second "Return" statement did not belong there)

2. Added downmix functions for 7ch -> 6ch and a Dolby ProLogic IIx
compatible function for 8ch -> 6ch. (Thanks to JuMe for proposing it)

3. For the 7to6 and 8to6 downmix functions I added tebasuna's suggestion
to avoid clipping in the surround channels by converting the input
to float and use an audio limiter for the surround channels at the end.



Usage:

Extract the files from the "Lib" folder into your "AVStoDVD\Lib" folder.

To apply these new functions you need to edit the AVStoDVD AVS script
manually because A2D does not use them by default.

Download here:
https://files.videohelp.com/u/172211/A2D_Downmix.zip


Enjoy
manolito

//EDIT//
Some refactoring, please redownload...

[Mike-uk]

Hi, me again :P

29.97 fps to pal 25 fps results in very choppy panning shots :( , any way to solve this ??

im pritty sure i had ntsc slowdown ticked, but i see no changes in the avisynth script ??

Thanks
Mike

[manolito]

Yes, there are several ways to create smoother results...

First question is if your source is progressive or interlaced. If the source is interlaced then you do not have a choice. AVStoDVD will automatically use the preferred method for the conversion which will result in an interlaced PAL DVD. And this resulting DVD should play just as smoothly as the source.

But if your source is progressive then you do have choices. Pans will be juddery if you use ChangeFPS for the fps conversion. Under "Preferences -> AviSynth" you can specify the method for hard fps conversion. The "Insert/Drop Frames" option does use ChangeFPS. Using "Blend Frames" uses ConvertFPS instead. Looks smoother, but you will get ghosting. "Motion Compensation" uses the MCJMFPS.avsi script which interpolates frames. Should be very smooth, but depending on the source characteristics you may get some artifacts (most often warped vertical lines).

The last option is not included in the A2D options, you need to edit your AVS script manually. This option will not drop whole frames like ChangeFPS, it will drop fields instead which looks much smoother. The downside is that your result will be interlaced. Here is the script:
# Insert after the resizer


Last = Video
Interleave(Last, Last)
ChangeFPS(50) # Drops Frames
# ConvertFPS(50) # Blends Frames
AssumeTFF()
SeparateFields()
SelectEvery(4,0,3)
Weave()
Video = Last


# The encoder must be set to "Interlaced".


Cheers
manolito


//EDIT//
Just saw your edited post...
NTSC slowdown won't help you here. This option applies if your source is PAL progressive (25 fps). When this option is ticked, A2D will slowdown 25fps to 23.976 fps and then add soft pulldown flags to make the output fps 29.97 fps.

[Mike-uk]

Hi manolito thanks for the fast reply,

the source file is progressive,

[Mike-uk]

went with motion compensation as a test proved to be fine

but im seeing a first pass encode at 30 fps, where as when using smart selection i was getting 200-300 ??

also i see there is a new FrameRateConverter v1.3 script, but the version Mrc uses is an edited version so i guess the new script wont work

[manolito]

Yes, using MVTools based motion compensation is very slow. The default settings are still tolerable for me, but wait until you add the "DCT=1" parameter. This can improve the quality considerably, but at a ridiculously low speed.

FrameRateConverter and the simplified John Meyer version are closely related. Basically FrameRateConverter is based on the JM script and adds some artifact masking. For me the difference in quality is very small, in most cases it is not worth the effort. But of course you can use FrameRateConverter with AVStoDVD. Put the AVSI script in your AviSynth autoload folder, and make sure that only the latest versions of all the dependencies are installed (only use the latest Pinterf versions). To call the script you need to edit your AVS script in AVStoDVD, there you replace the call to MCJMFPS with FrameRateConverter. The calling parameter convention is a little different, though. For the frame rate you do not use a float value, instead you use two integers for fpsnum and fpsden. For a target frame rate of 29.97 you need to specify "fpsnum=30000" and "fpsden=1001" instead of "fps=29.97".

[Mike-uk]

ok thanks, think ill just stick with the internal motion then, what i dont understand is cpu is at 18% yet only achieves 30fps ??

almost 6hrs for 3 hours of content :eek:

maybe just encode in NTSC format and take a slight resolution hit

[Mike-uk]

ok so i installed avisynth + MT and used prefetch (4) at the end of the script and that seems to bump fps back to 100 fps, any insight to negative effects ?

[manolito]

Multitasking does help a lot with MVTools. If you use it for HD conversions using X264 or X265 you might get crashes sooner or later. AVStoDVD seems to be less affected in my experience.

My plugin package for AVStoDVD now also has a section on using AVS+ MT under AVStoDVD. Download here:
https://files.videohelp.com/u/172211/Manolito_s%20A2D%20Plugins.7z

Cheers
manolito

[Mike-uk]

hmm ok might of found a bug, i cant create a dvd menu if ive got use PAL speedup selected on certain media files, did a load fine that were 29.97 fps, but if i use a file that has 23.976 i get the error cant create dvd thumbnail for title

[Mike-uk]

also is there anyway of editing avisynth.dll location, as i use bd rebuilder but it only works with avisynth 2.60, but i want to use the + with avs2dvd,

[manolito]

but if i use a file that has 23.976 i get the error cant create dvd thumbnail for title

Can you cut out a short section of such a source file and upload it to a file hoster? And the AVStoDVD log file would also be nice...

[manolito]

also is there anyway of editing avisynth.dll location, as i use bd rebuilder but it only works with avisynth 2.60, but i want to use the + with avs2dvd,

Yes, you can use Groucho's universal AviSynth installer for quickly switching AviSynth versions:
https://forum.doom9.org/showthread.php?p=1720988#post1720988

But before doing this you should try if BD Rebuilder really refuses to run under AVS+. I am not familiar with BD Rebuilder, but for DVD Rebuilder jdobbs says the same thing, and it is not true. DVD Rebuilder runs nicely under the latest AVS+ version by pinterf.

[Mike-uk]

Yes, you can use Groucho's universal AviSynth installer for quickly switching AviSynth versions:
https://forum.doom9.org/showthread.php?p=1720988#post1720988

But before doing this you should try if BD Rebuilder really refuses to run under AVS+. I am not familiar with BD Rebuilder, but for DVD Rebuilder jdobbs says the same thing, and it is not true. DVD Rebuilder runs nicely under the latest AVS+ version by pinterf.

ok will look into the switcher, i did stumble upon it, but then forgot :P

bd rebuilder forces it's self closed if Avisynth is not present or wrong version

[Mike-uk]

Can you cut out a short section of such a source file and upload it to a file hoster? And the AVStoDVD log file would also be nice...

here

https://drive.google.com/open?id=1DP74IEWfOOiPDX_y4f2dzokozcxIH2h6

[manolito]

Thanks for uploading your sample...

But I cannot reproduce your issue. I tried to replicate your settings as good as I could, but I got a very nice result. BatchMux had no complaints. I used the first 3 subtitle tracks, and something is wrong here. Only the first subs track shows English subs, the other 2 just show question marks. Weird...

I know almost nothing about subs, might well be that BatchMux stumbled upon one of your subtitle tracks. But it sure has nothing to do with the PAL Speedup option. At least not on my machine.

Get my test results here:
https://www.sendspace.com/file/k6ul79

[Mike-uk]

Thanks for uploading your sample...

But I cannot reproduce your issue. I tried to replicate your settings as good as I could, but I got a very nice result. BatchMux had no complaints. I used the first 3 subtitle tracks, and something is wrong here. Only the first subs track shows English subs, the other 2 just show question marks. Weird...

I know almost nothing about subs, might well be that BatchMux stumbled upon one of your subtitle tracks. But it sure has nothing to do with the PAL Speedup option. At least not on my machine.

Get my test results here:
https://www.sendspace.com/file/k6ul79

very odd, if i have speedup selected i get the error about not being able to create thumbnail, but if i unselect speed up dvd menu creation works as normal

[manolito]

The key line in your DVD log is this one:
Created File (Menu Page 1): C:\Users\mike7\Videos\DVD_1_MenuPage1.m2v (0 Byte)

AVStoDVD always uses FFMpeg to create the motion menu video even if HCenc is selected as the video encoder. And this encoding step fails on your computer.

First thing I thought was that the reason could be that you had selected a duration of 25 sec for the motion menu while the source only has a duration of 12 sec. But this was wrong, my computer had no problem using 25 sec as the menu duration.

You could try anyways to shorten the menu duration to no more than 12 sec, but if this does not help then I believe that AVS+ is the reason.

//EDIT//
Or did you update your FFmpeg version in AVStoDVD without observing this?
FFmpeg:
The included version 2.2.3 is from 2014 and is slowly getting a little old. For the purpose of AVStoDVD it probably has everything it needs, though...
If you want to upgrade to a later version, there are a few things to keep in mind:

Starting with version 3.1.2 the FFmpeg AVS interface has changed. To work with A2D it is necessary to include the folder "...\AVStoDVD\Lib" in your "PATH" environment variable. It is also recommended to include the folder "...\AviSynth\Plugins" in the "PATH" variable.

Current FFmpeg versions do NOT work under Win XP. There are a couple of fairly recent builds by CoRoNe, rogerdpack and Sherpya which do work under Win XP, though.

The latest and highly recommended version which works under Win XP and does not require to modify the "PATH" variable is this one from July 2016 by rogerdpack:
https://sourceforge.net/projects/ffmpegwindowsbi/files/2016-07-18/ffmpeg.static.2016-07-18-g450cf40.32-bit.ffmpeg-static-xp-compatible.zip/download

[Mike-uk]

ahh quite possibly :p ill check that out when i got 5 mins

[Mike-uk]

reverting back to ffmpeg that comes with avs2dvd doesnt fix it

[manolito]

Sorry, out of ideas...

[Mike-uk]

no worries, my work around is enable menu, let it moan about not being able to create thumbnail, encode, it will fail when it gets to encoding and creating the menu, keep assest files , start new project, add the .m2v files, edit menu, re prosses but it wont do any encoding, but it will finish making the menue and then creat the dvd struture

[dr_ml422]

I opened AVStoDVD to start a conversion and something told me to go to the codecs setting. Well everything was under ffdshow, and of course LAV is installed. So, is it Windows or something else that kicks it back to other than LAV filters? Or is it the program itself that picks best settings fir a project? Should I always check and make sure LAV is default? How other than going down one by one and hitting LAV can I do this? Thanks. Also should I just delete FFDShow out of my system? What's using it? Is it old and true MPC-HC 64 bit the one that's using it? Or DVDFab, VidCoder,...? That way I'll always have LAV as default for AvstoDVD. Thanks.

[manolito]

So, is it Windows or something else that kicks it back to other than LAV filters?

Is it old and true MPC-HC 64 bit the one that's using it? Or DVDFab, VidCoder,...? That way I'll always have LAV as default for AvstoDVD. Thanks.

This should not happen. If you are under Win10 it may be that after a feature update the preferred DS filters will be reset, but it will certainly reset the filters to the MS default filters and not to ffdshow.

So I believe that either yourself or some software you are using has changed the preferred filter settings to ffdshow. MPC-HC 64 has been using LAV Filters for quite some time, if your version still uses ffdshow it must be pretty old. Time to upgrade...

If you do not need the newer LAV features (supporting newer video codecs or current hardware assisted decoding features) then ffdshow is really not so bad. AVStoDVD fully supports it, and if you are not getting any problems like audio/video sync problems then you could probably stay with ffdshow. I have no idea which of your other installed software might insist on ffdshow, this is something you need to find out yourself by uninstalling ffdshow and check all your video playback or conversion software.


Cheers
manolito

[dr_ml422]

I keep getting this error. Never got it before. After I close the command window it tells me if I want to proceed with something about FFMPeg etc... and then it turns out ok. Here's the screenshot I attached. Thanks.

[manolito]

Getting attachments approved in the Doom9 forum can take ages... :mad:

Upload your image to a file hoster like https://postimages.org/ instead...

[dr_ml422]

https://i.postimg.cc/grTRHxWD/AVSto-DVD-error.png (https://postimg.cc/grTRHxWD)

Please let me know. Thanks manolito.

[manolito]

This is a thumbnail which is far too small. For me it is completely unreadable...

[videoh]

???

I clicked the link, it is perfectly readable.

[manolito]

This is weird...

I use my good old Opera 12 browser, and this is how it looks here:

https://i.postimg.cc/Cdpw4vPR/Opera12.png (https://postimages.org/)

In Chrome it is readable.

[manolito]

@ dr_ml422

It looks like your AviSynth script for the project cannot be opened. The file is located in your local Windows temp folder.

Do you have enough free space on your Windows system drive?

Have you tried to run AVStoDVD as an administrator?

You could try to move your A2D temp folder to a different drive and / or partition. This is done under "Preferences -> Paths".

And the last thing I can think of is to use a different method for extracting the audio, You are using the default "Wavi + Aften" method. Try to change it to "FFmpeg(AviSynth)".


For debugging it would be helpful if you could open your temp folder right after the crash message appears. Then copy the AVS file to a different folder, open it with NotePad and post the content here,


Good luck
manolito


//EDIT//
Don't forget to try to disable your antivirus software temporarily...
And I almost forgot:
Please post your AVStoDVD log file here.

[dr_ml422]

This never happened before and when I close the command window with the error and proceed with FFMPeg etc... as suggested everything comes out fine. Couldn't find any logs. Probably deleted. I should uncheck that preference to delete them in the main window. I don't know anything about Aften etc... so I just left defaults asis. Is the FFMPeg option better? It says it'll automatically switch to FFMPeg if Temp Wav bigger than 4GB. There's more than enough space as it's my C drive and only my apps and regular associated stuff is there. Maybe it's the type of file being processed, or that I had 2 other encoding jobs happening at the same time? Let me run a solo job and keep the logs. They're in the AVSDVD output folder correct? Thanks.

[dr_ml422]

Here goes. I couldn't edit yet so I had to reply in another message. Is DVDStyler 64 bit just as good as 32bit? I'm needing a backup app for my DVDs. Thanks.


<11/8/2019 10:16:38 PM>
START PROCESS
<>

<11/8/2019 10:16:38 PM>
PROJECT SETTINGS

DVD Video Standard: NTSC
DVD Titles number: 1
DVD Size: 8100/8100 MB (100%)
DVD Output Setup: DVD Folder
DVD Label: Suicide Squad (2016)
DVD Menu: Static Menu
Output Folder: C:\Users\Noloc42\Videos\AVStoDVD DVD Output
Delete Temp Assets Files: No
Delete Temp Working Files: No
Edit Command Parameters: No
Post Process Task: Show Progress Status window

PREFERENCES

MultiThread: 1
AVS Video Source Filter: A2DSource
AVS Audio Source Filter: A2DSource
AVS UpSize/DownSize Filter: Lanczos4Resize/Spline16Resize
Frame Adjust Strategy: 0
FPS Hard Conversion: 0
PAL SpeedUp: 0
NTSC SlowDown: 0
Video Resolution: 0
Video Encoder: 0
Video BitRate Min: 2500
Video BitRate Max: 8500
Keep DVD Compliant Video: 1
AC3 Audio Encoder: 0
Force FFmpeg for Long Audio: 1
DVD Audio Format: 0
DVD Audio BitRate: 192
Keep DVD Compliant Audio: 1
Normalize Audio: 0
Auto Delay Audio: 1
DVD Audio Language (Primary): EN - English
DVD Audio Language (Secondary): EN - English
DVD Subs Language (Primary): EN - English
DVD Subs Language (Secondary): EN - English
DVD Subs Font: Tahoma 16pt (240,240,240)
Chapters Interval: 5
Use Source Chapters: 1
DVD Burning Drive: G: Slimtype eBAU108 5 L 4L01
DVD Burning Speed: 8x
Auto Erase DVD RW: 1
Unload ActiveMovie Library: 0
Adjust DirectShow Filters at runtime: 1
Save General Settings: 0

SYSTEM INFO

Processor Name: AMD Ryzen 5 2600 Six-Core Processor
Operating System: Windows 10 (10.0.18362) 64 bit
User has Admin Rights: YES
Running with Elevated Privileges: NO (3)
Available Output Disc Space: 228 GB
AviSynth is installed: YES (release 2.6.0)
LAV Filters is installed: YES (release 0.74.1)
ffdshow is installed: NO

CODECS REPORT

H.264/AVC: LAV Video Decoder
Xvid: LAV Video Decoder
DivX 4/5/6: LAV Video Decoder
Other MPG4: LAV Video Decoder
DV: LAV Video Decoder
MPEG1: LAV Video Decoder
MPEG2: LAV Video Decoder
AAC: LAV Audio Decoder
MP3: LAV Audio Decoder
MP2: LAV Audio Decoder
AC3: LAV Audio Decoder
<>

<11/8/2019 10:16:38 PM>
TITLE 1 SOURCE FILES
Video: J:\Ready To ConvertXToDVD 7\DCEU Justice League\Suicide Squad (2016) [YTS.AG]\Suicide.Squad.2016.720p.BluRay.x264-[YTS.AG].mp4
Info: AVC - 900 kbps - 1280x534 - DAR 2.399 - 23.976 fps - Progressive - 2:14:33 hours - 193555 frames
Audio 1: J:\Ready To ConvertXToDVD 7\DCEU Justice League\Suicide Squad (2016) [YTS.AG]\Suicide.Squad.2016.720p.BluRay.x264-[YTS.AG].mp4
Info: AAC LC - 132 kbps - CBR - 2 ch - 48000 Hz - 2:14:33 hours (0 ms delay) - Default
Subs 1: J:\Ready To ConvertXToDVD 7\DCEU Justice League\Suicide Squad (2016) [YTS.AG]\Suicide.Squad.2016.EXTENDED.720p.BluRay.x264-SPARKS-RARBG-ShAaNiG-[YTS.AG].srt
Info: SubRip (SRT) - Suicide.Squad.2016.EXTENDED.720p.BluRay.x264-SPARKS-RARBG-ShAaNiG-[YTS.AG].srt
[MediaInfoLib - v18.03.1]
<>

<11/8/2019 10:16:38 PM>
AVISYNTH SCRIPT
Import("C:\Program Files (x86)\AVStoDVD\Lib\A2DSource.avsi")

Video = A2DVideoSource("J:\Ready To ConvertXToDVD 7\DCEU Justice League\Suicide Squad (2016) [YTS.AG]\Suicide.Squad.2016.720p.BluRay.x264-[YTS.AG].mp4", CacheFolder="C:\Users\Noloc42\AppData\Local\Temp", FrameRate=23.976)
Audio = A2DAudioSource("J:\Ready To ConvertXToDVD 7\DCEU Justice League\Suicide Squad (2016) [YTS.AG]\Suicide.Squad.2016.720p.BluRay.x264-[YTS.AG].mp4", CacheFolder="C:\Users\Noloc42\AppData\Local\Temp")

Video = Video.ConvertToYV12()
Video = Video.AddBorders(0,92,0,94)
Video = Video.Spline16Resize(720,480)
#PullDown: using DGPulldown/HCenc to upsize FPS

AudioDub(Video, Audio)
<>

<11/8/2019 10:16:38 PM>
DIRECTSHOW AUDIO MIXER OPERATIONS:
No LAV Filters mixer ON/OFF adjustment required at runtime
<>

<11/8/2019 10:16:38 PM>
START VIDEO ENCODING OPERATIONS
Video Encoding Profile: FFmpeg CBR 1-pass
Target Video FileSize: 7696.1 MB
Encoding Parameters: -i "C:\Users\Noloc42\AppData\Local\Temp\Suicide Squad (2016)_Suicide Squad (2016)_1.avs" -threads 12 -aspect 16:9 -c:v mpeg2video -b:v 7997k -minrate 7997k -maxrate 7997k -bufsize 2000k -dc 10 -y "C:\Users\Noloc42\Videos\AVStoDVD DVD Assets\Suicide Squad (2016)_Suicide Squad (2016).m2v"
<>

<11/8/2019 10:23:09 PM>
END VIDEO ENCODING OPERATIONS
Video Source Filter: A2DSource - DSS2 mod (LAV Filters on)
Created File: C:\Users\Noloc42\Videos\AVStoDVD DVD Assets\Suicide Squad (2016)_Suicide Squad (2016).m2v (7696 MB)
Ouput Video Info: MPEG-2 Video - 7997 kbps - 720x480 - DAR 16:9 - 23.976 fps - Progressive - 2:14:33 hours - 193557 frames
Avg Video Encoding Speed: 495 fps
<>

<11/8/2019 10:23:09 PM>
START PULLDOWN OPERATIONS
DGPulldown Parameters: "C:\Users\Noloc42\Videos\AVStoDVD DVD Assets\Suicide Squad (2016)_Suicide Squad (2016).m2v" -srcfps 23.976 -destfps 29.97 -inplace -tff
<>

<11/8/2019 10:24:35 PM>
END PULLDOWN OPERATIONS
DGPulldown executed on File: C:\Users\Noloc42\Videos\AVStoDVD DVD Assets\Suicide Squad (2016)_Suicide Squad (2016).m2v (7696 MB)
Output Video Info: MPEG-2 Video - 7997 kbps - 720x480 - DAR 16:9 - 23.976 fps - Progressive (2:3 Pulldown) - 2:14:33 hours - 193557 frames
<>

<11/8/2019 10:24:35 PM>
START AUDIO ENCODING OPERATIONS (Track 1)
Wavi+Aften Parameters: "C:\Users\Noloc42\AppData\Local\Temp\Suicide Squad (2016)_Suicide Squad (2016)_1.avs" - | "C:\Program Files (x86)\AVStoDVD\Aften\aften.exe" -b 192 -pad 0 -dynrng 5 -bwfilter 0 - "C:\Users\Noloc42\Videos\AVStoDVD DVD Assets\Suicide Squad (2016)_Suicide Squad (2016)_1.ac3"
<>

<11/8/2019 10:27:22 PM>
WARNING! Errors found during Title 1 Audio Track 1 encoding.
Audio filesize is too small (0 MB)
Backup Audio encoding routine (FFmpeg Safe Mode) is starting ...
<>

<11/8/2019 10:27:22 PM>
START FFMPEG (SAFE MODE) AUDIO ENCODING OPERATIONS (Track 1) - Trial 1/2
FFmpeg Parameters: -threads 12 -i "J:\Ready To ConvertXToDVD 7\DCEU Justice League\Suicide Squad (2016) [YTS.AG]\Suicide.Squad.2016.720p.BluRay.x264-[YTS.AG].mp4" -vn -c:a ac3 -ar 48000 -ab 192k -y "C:\Users\Noloc42\Videos\AVStoDVD DVD Assets\Suicide Squad (2016)_Suicide Squad (2016)_1.ac3"
<>

<11/8/2019 10:28:15 PM>
END AUDIO ENCODING OPERATIONS (Track 1)
Created File: C:\Users\Noloc42\Videos\AVStoDVD DVD Assets\Suicide Squad (2016)_Suicide Squad (2016)_1.ac3 (184.8 MB)
Output Audio Info: AC3 - 192 kbps - CBR - 2 ch - 48000 Hz - 16 bit - 2:14:33 hours (0 ms delay)
<>

<11/8/2019 10:28:49 PM>
Process aborted during Title 1 SUBS (Track 1) encoding operations.
For Subtitles issues troubleshooting see Help/FAQ/Subtitles section.
<>

<11/8/2019 10:28:49 PM>
Warning! AVStoDVD Project ended with errors.
<>

<11/8/2019 10:28:49 PM>
Log file created by AVStoDVD Release 2.8.8
<>

:)

[manolito]

Thanks for posting your log...

I cannot see any problems in your AVS2DVD setup, so I can only make an educated guess. The path+filename string in your Wavi commandline is technically correct, but it is awfully long. In theory the command processor can handle a much longer parameter string, but I do not know if Wavi and/or Aften can handle such a long parameter string.

I suppose that Wavi and Aften parse the commandline and put it into a string variable. And this string variable might be limited in length. My recommendation is to put your source file into a folder with a short name plus rename the file itself to a short name. If this works then my suspicion is correct.

And the other option would be to use "FFmpeg (AviSynth)" instead of "Wavi + Aften" as your audio conversion method. According to your log file FFmpeg has no problems with long parameter strings, and at least for current FFmpeg versions the AC3 encoding quality in FFmpeg is even better than in Aften.


Cheers
manolito

[dr_ml422]

Thanks. I kinda thought the title name had something to do with it as sometimes it would even tell me it couldn't recognize the file. Then I would load it directly in with the Add+ button and it would take. It's been making some really nice outputs and so I need it in my arsenal. Not too many out there except DVDStyler, ConvertXToDVD, and w/e DVDFab has.

[dr_ml422]

It worked! I also started it with Admin Rights. I used FFmpeg-AviSynth for the audio. Thanks.

[manolito]

Great!
Glad I could help...

[dr_ml422]

Now I found a new bug if at all. I can't edit the titles when more than one title is present in a project. It will come up with all the title's names plus the edited name in the Menu after hitting the Menu Wizard. Is there anything I'm missing here?

Ok so now everything went back to normal after restting the menu. One thing is that if you hit save preferences and have the name of your previous DVD in the Label instead of DVD, it will bring that back again unless you change it again. So it's better to just leave it as DVD because one could easily miss that and then have to do it over.

[dr_ml422]

I have a question. What can I do in preferences etc... so that on startup or just after, I don't get that "I couldn't find so and so drive" popup? I had a burner I took out and it was still searching for it apperently. Do I have to go into settings somewhere and change something? Thanks.

[manolito]

Three possible solutions I can think of...

Under AVStoDVD preferences -> Authoring/Burning you can try to remove the offending burner from the dropdown list and save the preferences as default.

Or open RegEdit and go to HKCU/Software/AVStoDVD. There is a value "DVDBurningDrive" in the right pane, you can doubleclick it and delete the burner string.

If all this does not work then there is a nifty little tool by Uwe Sieber called DriveCleanup.
https://www.uwe-sieber.de/files/drivecleanup.zip
This tool will remove all non present drives from the device tree of device manager.

Good luck
manolito

[dr_ml422]

Thanks Manolito, everything is working fine now, especially after switching to FFmpeg for the Audio encoding. The DVDs are really nice, and I noticed that AVStoDVD preserves menu functionality when using the PC to watch it. I couldn't get that with ConvertXToDVD. I'm experimenting with the subtitle output as the regular Tahoma kinda gives a shadow effect. I switched to Bold and will see soon if it looks clearer.

[Mike-uk]

Damn, another report that the A2D preview is not working under Win10... :mad:

You are not the first user with this problem. A2D uses the ancient Quartz.dll for the preview, but I never found something that MS has stopped supporting this method under Win10. I am on Win7-64, and I have no problem with the A2D preview. If there is no way to make the preview work, you know that you can specify a different software player for the preview under preferences? Just no editing...

Here is something you could try:
The batch file in the linked archive restores a couple of AviSynth Registry entries which get altered by installing LAV filters. It may or may not help, but it sure does not do any damage.
https://www.sendspace.com/file/l9zgsz

The other file in the archive is VCF2AVS which you need if you want to use the VDub method to edit your source files.


There's only one single A2D developer, and this is MrC. Unfortunately he does only have very limited time lately to work on AVStoDVD, I try to help out with user support as much as I can, but of course my contributions are limited - I am just an informed user, not a developer.


Cheers
manolito
Hi
any update on getting this working ??
the file you linked is no longer available
Thanks
Mike

also ive noticed the resulting dvd, pretty much all edges are a bit jaggedy ??

[manolito]

Hi
any update on getting this working ??
the file you linked is no longer available

also ive noticed the resulting dvd, straight edges are a bit jaggedy ??

Unfortunately no update to this issue...

I reuploaded my archive, will be available for 30 days:
https://www.sendspace.com/file/vqeuv2

For the jagged edges this could have several reasons. Aliasing caused by downscaling maybe. Could you upload a short sample? There are some blurring filters which can improve aliasing, but I am not really too familiar with this.


Cheers
manolito

[Mike-uk]

https://ibb.co/84MSMjh

youll prob need to zoom in to see, but edges have slanted lines

[manolito]

Yes, I really had to zoom in to 500% to notice...

Try some of the Anti-Aliasing filters from here:
http://avisynth.nl/index.php/External_filters#Anti-aliasing

[Mike-uk]

Yes, I really had to zoom in to 500% to notice...

Try some of the Anti-Aliasing filters from here:
http://avisynth.nl/index.php/External_filters#Anti-aliasing

ok will take a look, its deffo more noticeable on the tv.

im comparing a bluray to dvd, and just the dvd, and the hd-sd converstion you notice the edges

thanks
Mike

[manolito]

ok will take a look, its deffo more noticeable on the tv.

Not on my TV I guess... :D
I still watch my movies on my oldfashioned CRT TV which doesn't know how to spell "High Definition", but which has very natural colors no LCD TV I have seen so far could match.

[Mike-uk]

have you tried OLED tv ??

[manolito]

No I haven't. But I am a big believer in sustainability, and I do not believe in replacing stuff which still works perfectly by the latest and greatest new toys.

[dr_ml422]

I'm getting way better results lately after taking manolito's suggestion and using FFmpeg to encode my audio. There's definitely something better going on when you use FFmpeg instead of the Aften encoder. My DVDs aren't darker anymore where they were using the Aften encoder. I know it's kind of weird being it's an audio setting, though the results definitely tell another story. I also set my output to DVD-9 to get the best possible picture without further compression. Also AVStoDVD always has DVD Menu functionality on the PC which ConvertXToDVD as of now doesn't. I'm staying with AVStoDVD right now. So if you haven't already tried using the FFmpeg for Audio together with the recommended Video settings go ahead and give it a try.

[manolito]

I'm getting way better results lately after taking manolito's suggestion and using FFmpeg to encode my audio. There's definitely something better going on when you use FFmpeg instead of the Aften encoder. My DVDs aren't darker anymore where they were using the Aften encoder. I know it's kind of weird being it's an audio setting, though the results definitely tell another story.

This really puzzles me... :scared:
Using FFmpeg instead of Aften for audio encoding should not affect the video conversion at all. There must be something else going on.

The only way to find out would be to make 2 different conversions of a short clip, using your previous settings with Aften first and then using your new settings with using FFmpeg for the audio conversion. Save both log files and post them here.

[Mike-uk]

edit title and add trim to avisynth script and do like 3000 frames to make short clips

[dr_ml422]

This really puzzles me... :scared:
Using FFmpeg instead of Aften for audio encoding should not affect the video conversion at all. There must be something else going on.

The only way to find out would be to make 2 different conversions of a short clip, using your previous settings with Aften first and then using your new settings with using FFmpeg for the audio conversion. Save both log files and post them here.

After going to DVDVOB2Mpg's site and reading his explanation of how the DVD structure, mainly VTS Folders and their Vob files contain all sorts of data, and how this can easily get corrupt, I believe it. Especially after clearly seeing the results I'm getting with FFmpeg and DVD-9. The exact file when converted to .iso which should preserve everything, won't have Menu functionality and even not play sometimes. Sometimes fast forwarding it will bring up the main video, sometimes not. Now that same .iso when I convert back to a DVD VTS Folder using either DVD-RB Pro or Shrink, will not only play, it will have menu functionality and the timing also would come back, as with the .iso it was off as well. Kept posting a 37... minute for Full Video.

Better yet you run a video or short clip using Aften as Audio and then FFmpeg with the same Video settings which would be DVD-9 output, DVD Title same as Disc Label, and run the menu preview, then the Avisynth Frame Serving Check.

You'll see how crisp that resulting DVD will be with the FFmpeg Audio settings. I'm now having to go through my whole .iso collection and running them through DVD-RB Pro or Shrink to have a workable VTS folder. Also reason for the VTS folder is when burning and wanting to add it's high-def counterpart, it will burn as data only with the .iso. With the VTS folder I will get both my DVD and it's mp4 or mkv counterpart on the same disc size permitting, and when I play that DVD I will get playback from the VTS folder. Not with the exact .iso on that same disc as it'll not be burned as DVD video but data. Now on the PC that .iso will play from the disc, but only AVStoDVD will make the .iso alone functionable with menu. Using a disc with the PC is ok but kinda defeats the purpose of converting etc...

[Mike-uk]

hmm odd I tried to do some comparisons myself, but I cant get avs2dvd to work with wavi+aften or ffmpeg+aften as it either says unsupported number of channels, or if I choose an ac3 stream it just freezes HCEnc ? so I can only use ffmpeg

[manolito]

Really odd...

Can you post your log file?


//EDIT//
Just guessing, but could it be that you updated MediaInfo.DLL in the A2D\Lib folder with a newer version? If so then please go back to an older version. The last working version is v. 18.05.

The reason for my guess is that you are getting an "Unsupported number of channels" message. A2D gets all the source info from MediaInfo, and versions after 18.05 use a different output format so software like AVStoDVD will get wrong source properties.

[Mike-uk]

Really odd...

Can you post your log file?


//EDIT//
Just guessing, but could it be that you updated MediaInfo.DLL in the A2D\Lib folder with a newer version? If so then please go back to an older version. The last working version is v. 18.05.

The reason for my guess is that you are getting an "Unsupported number of channels" message. A2D gets all the source info from MediaInfo, and versions after 18.05 use a different output format so software like AVStoDVD will get wrong source properties.

nope going back to 18.05 hasn't sorted it

Found PCM audio: 8 channels, 48000 Hz, 32 bits, 80.040000 seconds.
Audio track contains floating-point samples.
Writing WAV file...
input format: Microsoft WAVE Floating-point 32-bit little-endian 48000 Hz multi-channel
Unsupported # of channels passed to aften_wav_chmask_to_acmod
mismatch in channels, acmod, and lfe params
Error: Could not write to the standard output.

not a problem for me as I use ffmpeg anyway

it seems any file with 8 channels/6 channels is not liked, just tried a file with 2 channels and its fine

[Mike-uk]

https://ibb.co/wLPH6Ck

just done a comparision with all 3 audio encoders and I don't see a difference ??

surely audio cant effect image as video encoding is done first ??

[manolito]

just done a comparision with all 3 audio encoders and I don't see a difference ??

surely audio cant effect image as video encoding is done first ??

Yes, the selected audio conversion method cannot have any effect on the video quality, the A2D workflow does not allow this. Unless something else is going on, but as long as dr_ml422 does not post his log files there is no way to analyze the problem.

[manolito]

Found PCM audio: 8 channels, 48000 Hz, 32 bits, 80.040000 seconds.

it seems any file with 8 channels/6 channels is not liked, just tried a file with 2 channels and its fine

Since the DVD specs do not allow for more than 6 audio channels, A2D always automatically downmixes 8-ch source audio to 6-ch. Which obviously does not work for your source audio.

I spent some time testing clips with different 8-ch audio formats this afternoon, and the result was that A2D is not well suited for 8-ch audio sources.

I used clips from here for my tests:
https://www.demo-world.eu/2d-demo-trailers-hd/

One problem is that there are many different 7.1 audio formats, and depending on the format MediaInfo spits out very different results. Which oftentimes leads to A2D making wrong downmix decisions.

One example is 8-ch EAC3 audio. This format is always detected as 6-ch, I have no idea how the other 2 channels are embedded in the format, but since LAV audio sees it as 6-ch there is no other way than treating it as 6-ch for the conversion.

For other formats MediaInfo reports 8-ch/6-ch audio, and A2D will probably pick the wrong format. Other 8-ch formats like DTS or Dolby Atmos may even cause A2D to detect 0 audio channels. So currently if you have 8-ch source audio you will need to apply some manual workarounds to convert such audio correctly.

The only way to reliably detect the number of audio channels is to check how many channels your audio source filter recognizes. For LAV audio there is a "Status" tab in the configuration window. Play the file in a DirectShow based player and open the LAV audio configuration to get the real number of channels.

Then in A2D right-click on the source title and click "Edit Source Title Info". Under "Audio Channels" enter the correct number of channels.

If you have 8 audio channels then make sure that your AVS script has the command "Audio = Audio.Dmix86()" in it. This will execute a function from "Downmix.avsi" which is located in your "AVStoDVD\Lib" folder.


So my conclusion is that right now there is no automatic way to treat 8-ch audio sources correctly. It would be a major undertaking to detect all possible 8-ch formats reliably, and I have my doubts if MrC has the time to do this in the near future. He has not posted here for almost 6 months, I sure hope that he is doing well...


BTW you may be interested in using an improved version of the "Downmix.avsi" script. Have a look here:
https://forum.doom9.org/showthread.php?p=1882617#post1882617


Cheers
manolito

[Mike-uk]

cheers manolito for the info, yes most of my sources get detected as 0 channel and encode in 2 channel, but manualy setting the channels now allows me to encode in 5.1 :)

[manolito]

Another year is almost over...

Time to wish everyone on this forum, and especially those who still do DVD conversions, a Merry Christmas and a Happy New Year... :D

Very special greetings to MrC, the author of this wonderful software. He has not posted here for some time, so I hope that he is doing well. All my best wishes for him and his family...


Cheers
manolito

[Mike-uk]

Another year is almost over...

Time to wish everyone on this forum, and especially those who still do DVD conversions, a Merry Christmas and a Happy New Year... :D

Very special greetings to MrC, the author of this wonderful software. He has not posted here for some time, so I hope that he is doing well. All my best wishes for him and his family...


Cheers
manolito

Yes Merry Christmas all

yes thanks to MrC for this wonderfull program

Hopefully MrC has been locked away in his room 24/7 making avs2whatever-you-want for us :D

but I know this prob isn't true im sure he has life to deal with first

and thanks to manolito for your outstanding tech support :)

[dr_ml422]

Happy New Year to all! Ok I'll run two tests with each and compare the two. Do I have to uncheck delete AVSToDVD Log Files in the main window, or are these different files? I always see some files after conversion. Remember I was having issues with FFMpeg and Aften so lets see if it takes with these tests. You have to do a whole movie. A short clip will not be enough to see any solid differences. It could just be the update since I was comparing to some older conversions before Mr, C came back with an update.

[manolito]

Do I have to uncheck delete AVSToDVD Log Files in the main window, or are these different files? I always see some files after conversion.

No, there is no need to uncheck this option. The AVStoDVD log file will always stay in the output folder after every conversion, and this is the file we need to analyze.

[dr_ml422]

Just like I said. Here goes two logs. Angel Has Fallen is with Aften/FFMpeg, and Olympus Has Fallen is with FFMpeg/AviSynth.

https://filebin.net/5mqvdamyolbg0fc0/Angel_Has_Fallen_2019.log?t=ue5gq302

https://filebin.net/5mqvdamyolbg0fc0/Olympus_Has_Fallen_2013.log?t=ue5gq302

If I were to somehow share the video you'll see that Angel Has Fallen has darker more greenish color. It could possibly be a leak from the Menu as I used the Greenish Menu with the DVD Disc in the Background.

[Mike-uk]

? that's 2 different movies, you ned to compare with the same movie and same time frame

[Mike-uk]

if you used the trim command and made small clips then upload them to google drive then share the link

[manolito]

? that's 2 different movies, you ned to compare with the same movie and same time frame

Yes, of course, but I do not think that this is even necessary... :p

Comparing the logs I noticed that "Olymus has fallen" uses the ColorMatrix command to convert the colorimetry from HD (Rec.709) to SD (Rec.601). And this results in correct colors.

"Angel has fallen" does not use the Colormatrix command, and this results in darker and more greenish colors. This is an indication that the source file uses Rec.709, but is incorrectly flagged so AVStoDVD cannot recognize the source colorimetry.

This can be easily fixed by adding the ColorMatrix command manually.

https://i.postimg.cc/0Q1wyyPZ/Colormatrix.png (https://postimages.org/)

Add the Colormatrix command and use a source value of 0 and a target value of 2. This should fix it.

In any case your issue has nothing to do with the audio conversion. The FFmpeg AC3 encoder should have a slight edge over Aften these days, but I doubt that you will be able to hear the difference.


Cheers
manolito

[dr_ml422]

Well, one thing for sure is that the menu is bleeding into the picture. I just opened Olympus Has Fallen which was made with the Red background Menu and it bleeds through the picture and characters. Now, sometimes it doesn't happen because I would of noticed it, so maybe it's menu specific as there's a natural color menu also provided. I'll do the same movie with the different audio codecs just for checking that issue out. Man, you guys can't snatch an .mp4 from one of the hundreds of sites available and test it out for yourself? I'll do kit but you doing your own conversions will be even better. I'm not tinkering with any settings other than the Audio and a different menu, so you could do the same. I'll post back the logs.


Sometimes the menu bleeds into the picture and sometimes it doesn't. Now I've compared the original file to the two conversions and even at DVD-9 they weren't as clear as the original. Sometimes it's as clear as anything.

https://filebin.net/5mqvdamyolbg0fc0/Olympus_Has_Fallen_2013_1.log?t=ep26lzmb https://filebin.net/5mqvdamyolbg0fc0/Olympus_Has_Fallen_2013_2.log?t=ep26lzmb First is with Aften and Second with AviSynth. See if you can spot anything. Thanks.

The original did have a color discrepancy with a little red in the beginning and creeping through here and there. So if anything if we can try to see where we can make FFMpeg put out a better conversion.

[manolito]

Well, one thing for sure is that the menu is bleeding into the picture. I just opened Olympus Has Fallen which was made with the Red background Menu and it bleeds through the picture and characters.

I went through your log files, and I could no see any problems.

"Menu bleeding into the picture" is not possible technically (unless some Voodoo is going on inside your computer). The encoder (FFmpeg in your case) has no knowledge whatsoever about the menu you have created. Could it be that your subtitles have a funny color which shines through even in sections without subtitles? Try to make an encode with subs disabled.

For your encoder settings you are using CBR mode at the highest possible bitrate of 8500 kbps. This should give you a good quality encode, but for even better quality you can try to use HCenc 2-pass VBR mode instead.

This "Menu bleeding through" thing is something nobody else has ever experienced, so I will believe it when I see it. Upload a short section of an encode which shows the issue together with the same section cut out from the source file...

[dr_ml422]

I checked my sources and there's some with bad coloring so that was that. I think I should keep it at DVD-5 since the sources are just @ 1-2GBs... Maybe stretching it out made it downgrade the quality. I have it set to default value with encoding, which picks what's best according to the source. I'll try this HCenc 2-pass VBR mode and see what happens. Sometimes I get really great quality encodes, and sometimes not. So I don't know if the better ones are when it decides to use HCenc...

[manolito]

I checked my sources and there's some with bad coloring so that was that.
This is what I suspected right from the beginning...

I think I should keep it at DVD-5 since the sources are just @ 1-2GBs...
It does not have much to do with the size of your source files. The source files are already compressed, and the size of the sources depends on the efficiency of the compression codec. MPEG2 is not very efficient, MPEG4-ASP (Xvid, DivX) is almost twice as efficient, then comes AVC (aka H.264), and HEVC (aka H.265) is the most efficient video compressor today. (I left out other formats like VP8, VP9 or AV1).

If your source is compressed with HEVC and it has a size of 700 MB, then converting it to MPEG2 (which is used for DVD) you will likely get a size of more than 5 GB for a comparable quality.

What matters instead is the lenght of your video and the characteristics (compressability) of the video. A clip with little motion, low details and darker textures will need less bitrate than a high action clip with lots of motion, fast cuts, high details and complex textures like fog for the same quality.

My rule of thumb is that for an average movie up to a duration of a little over 2 hours a DVD-5 will be big enough for very good quality.

Maybe stretching it out made it downgrade the quality.
No way...

I have it set to default value with encoding, which picks what's best according to the source. I'll try this HCenc 2-pass VBR mode and see what happens. Sometimes I get really great quality encodes, and sometimes not. So I don't know if the better ones are when it decides to use HCenc...

Generally if you use a high bitrate (above 7000 kbps) the encoder quality is less important than for a medium or low bitrate encode. For high bitrates AVStoDVD uses FFmpeg CBR, for bitrates below 6000 kbps it uses HCenc 2-pass VBR (slightly different algo for a single core CPU).

The FFmpeg parameters are simple and not optimized for quality. But at high bitrates this does not necessarily mean that the resulting encode
will look bad. But if your computer is fast and you want the best possible quality each and every time, then you should always use HCenc 2-pass VBR mode.

[dr_ml422]

Thanks manolito. Excuse the tardiness though I don't get any notifications via my email no matter what I do. Sometimes I miss the color saturation on the source. Maybe so wound up to watch it I don't notice the colors that saturate. I've had some very impressive conversions, and then some not so great. Which player are you mostly using if I may ask? I'm used to MPC-HC, though for some reasons it will not play some of my .mkv files that all the others play, even MS's Movie & TV app. Sometimes it gives me issues with a DVD as well. The sound is great though compared to VLC etc... How could I install the Lav filters w/out using a codec pack like K-Lite etc...? Thanks.

If you haven't seen the "Joker" by Joaquin Phoenix, please do if it's something your interested in. That acting in that movie is nothing I've seen in a very long time! Really identified with the whole plot, theme etc...

[manolito]

My 2 favorite players are MPC-HC and Tiny Player. I also have VLC installed, but I only use it when both DirectShow based players fail.

In MPC-HC I have disabled the internal LAV filters and use the latest installed LAV Filters version.

You can download LAV Filters here:
https://files.1f0.de/lavf/LAVFilters-0.74.1.exe
This is the installer version containing both 32-bit and 64-bit filters. Before installing you should remove older versions and also remove the settings from this Registry key:
HKEY_CURRENT_USER\Software\LAV
Then install the latest version, use all the default installer settings. The only thing I have changed in the settings is activating the tray icons for all 3 components.

Tiny Player is a very lightweight DirectShow based player, very solid and fast, but no longer maintained. Download here:
https://sourceforge.net/projects/tinyplayer/
The readme says that the author prefers ffdshow, but I use LAV Filters without any problems.

Cheers
manolito

[StainlessS]

This is the installer version containing both 32-bit and 64-bit filters. Before installing you should remove older versions and also remove the settings from this Registry key:
HKEY_CURRENT_USER\Software\LAV
Then install the latest version, use all the default installer settings.


Run Regedit, Go To "HKEY_CURRENT_USER\Software\LAV"
Export that key with name "RestoreLav_x86_SettingsToRegistry.reg"
'reg will be auto appended.

If you have x64 Lav installed, Regedit, Go To "HKEY_CURRENT_USER\Software\LAV64"
Export that key with name "RestoreLav_x64_SettingsToRegistry.reg"
'reg will be auto appended.

Create this file to delete settings [will make no difference to attempt delete of LAV64 if on x86].

RemoveLavSettingsFromRegistry.reg

Windows Registry Editor Version 5.00

[-HKEY_CURRENT_USER\Software\LAV]
[-HKEY_CURRENT_USER\Software\LAV64]

Add the files to your lav filters installer folder.

Thanks Mani.

EDIT: Damn, Lav filters v0.74.1 not for XP.
v0.70.2, seems to be last for XP.

[manolito]

From my AVStoDVD "update tools" post:

LAV Filters:
The current LAV versions require Windows Vista or higher. For a non-SSE2 CPU the nightly build 0.69.0.85 is the latest working version, under Win XP the latest working nightly is LAVFilters-0.70.2-16. So you may have to downgrade...

[dr_ml422]

Thanks manolito, StainlessS, I was able to delete the registry files and now am installing from the link manolito provided. I like that Mediainfo Lite that came with the K-Litepack. I'll just find where it's at and install it. Probably here afaik.

[manolito]

I like that Mediainfo Lite that came with the K-Litepack. I'll just find where it's at and install it. Probably here afaik.

Careful... :devil:
AVStoDVD is not compatible with current MediaInfo versions. The last working version is 18.05 , and the light version is not supported.

So please do not update the file "mediainfo.dll" in the "AVStoDVD\Lib" folder to anything newer than v. 18.05. However it should not hurt to have a different MediaInfo GUI version installed. It just could happen that the two versions report slightly different clip properties.

[dr_ml422]

Yes, of course, but I do not think that this is even necessary... :p

Comparing the logs I noticed that "Olymus has fallen" uses the ColorMatrix command to convert the colorimetry from HD (Rec.709) to SD (Rec.601). And this results in correct colors.

"Angel has fallen" does not use the Colormatrix command, and this results in darker and more greenish colors. This is an indication that the source file uses Rec.709, but is incorrectly flagged so AVStoDVD cannot recognize the source colorimetry.

This can be easily fixed by adding the ColorMatrix command manually.

https://i.postimg.cc/0Q1wyyPZ/Colormatrix.png (https://postimages.org/)

Add the Colormatrix command and use a source value of 0 and a target value of 2. This should fix it.

In any case your issue has nothing to do with the audio conversion. The FFmpeg AC3 encoder should have a slight edge over Aften these days, but I doubt that you will be able to hear the difference.


Cheers
manolito


So, there was something going on after all, even if it wasn't the Audio Encoder as I thought. This is too advanced for me right now. I can only try to do some troubleshooting whenever something pops up. This ColorMatrix command then has been the culprit in several encodings which I previously noticed darker colors.

I won't update anything regarding AVStoDVD unless it's a formal update, so Mediainfo will stay the same in that folder. I do need it installed because it helps me see what actually is in my files if I want or need something different, or to troubleshoot.

Right now MPC-HC doesn't want to play a .mkv file which plays just fine everywhere else, and so Mediainfo might be able to shed some light. Thanks.

[Mike-uk]

hmm ok so when using this
AVISYNTH SCRIPT
Import("C:\Program Files (x86)\AVStoDVD\Lib\A2DSource.avsi")

Video = A2DVideoSource("F:\Movies\test.mkv", CacheFolder="C:\Users\user\AppData\Local\Temp", VFR=false, FrameRate=23.976)
# Audio is frameserved by AviSynth just for Preview and Edit purposes.
Audio = A2DAudioSource("F:\Movies\test.mkv", CacheFolder="C:\Users\user\AppData\Local\Temp")


Video = Video.ConvertToYV12()
Video = Video.FineSharp()
Video = Video.Spline36Resize(720,576)
Last = Video
f1=ChangeFPS(24)
f2=Trim(0,-1).AssumeFPS(24) + Trim(1,0).ChangeFPS(24)
Film=Merge(f1,f2)
p1=ChangeFPS(Film,25)
p2=Trim(Film,0,-1).AssumeFPS(25) + Trim(Film,1,0).ChangeFPS(25)
Pal=Merge(p1,p2)
Last = PAL.AssumeFPS(25)
Video = Last


AudioDub(Video, Audio)
SSRC(48000)

Trim(0,5000)

the resulting dvd has a judder every 1 second, smooth judder, smooth judder, repeat,
any idea ?
Thanks
Mike

[manolito]

Yes, this method does cause a slight judder, this is how ChangeFPS works. But the Merge() command makes this judder much less obvious (at the cost of introducing a little blending) than just using a simple ChangeFPS(25) on the 23.976 source clip.

Make a short test conversion and compare the results once using your above script and then only using ChangeFPS(25).

If you cannot live with this judder then you need to use classical PAL speedup which involves speeding up the audio, too.


More thoughts:
Is your source really pure 23.976 progressive, or does it have soft pulldown?

And yet another method you could try is to use frame rate interpolation instead of ChangeFPS. A2D comes with the (renamed) jm_fps function. To use it you need to import the MCJMFPS.avsi from the AVStoDVD\Lib folder at the top of your script and then use MCJMFPS(25) to change the frame rate. The result will not have judder and audio can be left alone. But depending on the source characteristics you could end up with some artifacts (mainly warped vertical lines). And it does not work well on anime.

[Mike-uk]

Hi manolito, thanks for the reply, using the script posted the judder is very noticeable esp on panning shots,

ill just stick with speed up, that's nice and smooth

Thanks

Mike

[manolito]

Since I cannot reproduce this very noticeable judder with the above script, I made a few tests... :cool:

Could it be that for your conversion AVStoDVD executed DGPulldown on the converted M2V? Because this is what A2D always does when the target is PAL and the source is either 23.076 or 24 NTSC progressive (and PAL speedup is not specified). To avoid this you need to rename the DGPulldown folder to something else temporarily.

Anyways, I downloaded a demo trailer with a lot of horizontal motion and converted it using 5 different methods. The results are here:
https://we.tl/t-97Xpu5NCjh

Please tell me what you think...

[Mike-uk]

Hi manolito, thanks for the test samples, ive played then all, I guess they all play smoothly on your system ??, alt merg, change fps, and dgpulldown all have the judder every 1 second, but frame rate inter and pal speed up play smooth

for my script run I renamed the dgpulldown.exe to xxxxxdgpulldownsxxx.exe and unchecked pal speed up as per you instructions, although confusing cos in a previous post you say tick speed up but that calculated the wrong size file

the pc file has a slight judder almost un noticeable but there, but once a dvd is made and played on a dvd player and tv the judder becomes very noticable

[manolito]

I guess they all play smoothly on your system ??

So far I had only watched the files on my computer, but now I burned a DVD and watched it on my ancient CRT TV. You are right, the judder is far more obvious on the TV than on the computer.

But for me only the ChangeFPS clip looks annoying, I could live with all the others. Funny thing that for me the judder is only visible on fast horizontal motion. On scenes with slow steady motion I can't see any judder.

And what really surprised me was how good the Frame Rate Interpolation clip looked. I could not see any artifacts even on the TV, and the source with all the CGI stuff is very demanding for the interpolator.

although confusing cos in a previous post you say tick speed up but that calculated the wrong size file
This only happens if you have ticked PAL Speedup, but later edit the AVS script so there will no longer be any speedup. The workaround is to untick PAL Speedup, but to avoid that DGPulldown kicks in you have to rename DGPulldown.exe. If you really want PAL Speedup then the A2D file size calculation is correct.

[Mike-uk]

thanks for testing, I think ill just stick with pal speed up for now, cant ffmpeg change the cents as its encoding to ac3, to bring it back down to original tone ?

[manolito]

Sure it can... :D
Have a look here:
https://forum.doom9.org/showthread.php?p=1879712#post1879712

[Mike-uk]

Sure it can... :D
Have a look here:
https://forum.doom9.org/showthread.php?p=1879712#post1879712

ah ok thanks I kinda glossed over that at the time :D, ill have a play and see what the results are

Thanks

Mike

[dr_ml422]

@manolito Wow! That 2 Pass with HCencVBR you suggested is right on the money! I knew that something had to give because when I use DVD-RB Pro, it uses the HCenc and the results are immaculate. Thanks again. I'll maybe take a look at that Tiny player just for kicks. For the preview to work natively from the app, ffdshow has to be installed, otherwise you have to set it to use an external player.

[mayasl]

AVStoDVD ver: 2.8.8
AviSynth: 2.6

Please assist me to create a DVD with DTS audio from the following file.

Source details:
General
Unique ID : xxxxxxxx
Complete name : xxxxx.mkv
Format : Matroska
Format version : Version 4
File size : 3.27 GiB
Duration : 1 h 24 min
Overall bit rate : 5 562 kb/s
Encoded date : UTC 2020-03-05 18:45:42
Writing application : mkvmerge v42.0.0 ('Overtime') 32-bit
Writing library : libebml v1.3.10 + libmatroska v1.5.2

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings : CABAC / 8 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 8 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 h 24 min
Bit rate : 4 050 kb/s
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.183
Stream size : 2.39 GiB (73%)
Writing library : x264 core 159 r2991 1771b55
Encoding settings : cabac=1 / ref=8 / deblock=1:-3:-3 / analyse=0x3:0x133 / me=umh / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=16 / lookahead_threads=2 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=23 / scenecut=40 / intra_refresh=0 / rc_lookahead=50 / rc=2pass / mbtree=1 / bitrate=4050 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=1:1.00
Language : English
Default : Yes
Forced : No
Color range : Limited
Matrix coefficients : BT.709

Audio
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Codec ID : A_DTS
Duration : 1 h 24 min
Bit rate mode : Constant
Bit rate : 1 509 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 910 MiB (27%)
Title : English
Language : English
Default : Yes
Forced : No

Menu
00:00:00.000 : en:Chapter 01
00:08:15.453 : en:Chapter 02
00:16:59.852 : en:Chapter 03
00:27:19.179 : en:Chapter 04
00:38:09.954 : en:Chapter 05
00:48:38.374 : en:Chapter 06
00:56:55.621 : en:Chapter 07
01:02:34.459 : en:Chapter 08
01:12:30.596 : en:Chapter 09
01:21:39.978 : en:Chapter 10

[Mike-uk]

AVStoDVD ver: 2.8.8
AviSynth: 2.6

Please assist me to create a DVD with DTS audio from the following file.

Source details:

from reading, avs2dvd does not encode to DTS format only ac-3 wav and mp2 I guess this is due to licencing issues with DTS labs

it also seems DTS source audio tracks need to be 20bit or lower to be direct copied by avs2dvd, this apparently is a muxman problem ? , id guess Blu-ray source files are 24bit DTS audio, as is your MKV so will need re encoding

as quoted by Mrc, Many (I would say all) 24bit DTS tracks are refused by muxman. Sometimes it refuses 20bit tracks as well... hence the DTS compliance is not 100% solved. (wheter this is still relevant im not sure)

so I guess your options are, AC-3, or find a way of re encoding your DTS audio tracks to 20bit and hopfully avs2dvd will direct copy, and hopefully muxman will accept it

and do you really need DTS on a DVD ???, AC-3 is almost on par

on a Blu ray, yes I understand, superior picture and audio DTS-HD and master, im guessing DTS will take up more space leaving a lot less space for the video on a dvd ?, considering your compressing video from a already compressed video at only 3 gig to start with for 1hr+ of footage the sorce is prob not the best to start with

[manolito]

and do you really need DTS on a DVD ???, AC-3 is almost on par

Totally agreed...

Also keep in mind that DTS audio is not a mandatory format for DVDs, it is only optional. There are tons of standalone DVD players out there without a built-in DTS decoder. A DVD with only a DTS audio track without also having one of the mandatory audio formats is NOT DVD compliant.

[dr_ml422]

Hi manolito I have a question. I've been getting the warning "A file with AAC (Advanced Audio Coding) audio stream has been added, and default audio codec is Microsoft DTV-DVD Audio decoder". I haven't changed anything with regards to my LAV filters so unless Windows did this on its own I have no idea where this is coming from. Anyway the DVD came out just fine. I did go and use the tool to have LAV filters as default. Should I change the Avisynth tab settings in preferences and set video and audio source filters to FFMpegSource? Thanks.

[manolito]

Are you using Win10?
The only reason I can think of that your DS Filter Settings change by itself is that Win10 updates change these filter settings back to the original Windows filters.

If using the Microsoft DTV-DVD Audio decoder gives you good results (check for Audio/Video sync problems) then of course you can use these filters. Or rerun the Filter Tweaker tool after each Windows update.

Ditching DirectShow altogether and using FFmpegSource as your source filters is an alternative. The only drawback is that the source files need to be indexed which can take some time for longer sources.

[dr_ml422]

Yes you were correct. It was an update after which the settings were changed. Everything's fine now. Thanks. Running the Filter Tweaker Tool doesn't automatically change everything to LAV Filters. You have to make the changes yourself for each item.

[MrC]

Guys, back in business... after some time I finally decided that 2.8.9 must have a final build. So... here you are a new alpha ;)

AVStoDVD 289 Alpha 200925 @ SourceForge (https://sourceforge.net/projects/avstodvd/files/avstodvd_alpha_beta/AVStoDVD%202.8.9%20Alpha%20200925/)

Cumulative changes log from release 2.8.8. Changes from latest alpha are marked with +.

- Added support to PGS BluRay subtitles
- Added handling and display of MediaInfo BitDepth video tag
+ Added support to 7 and 8 channels audio source (Downmix.avsi script file updated, thanks to Manolito)
+ Added Chapters section to Demux File tool
- Improved Muxing routine: better errors handling and switch to FFmpeg (instead of Mplex) when no audio source is present
- Improved usage of FFMS2: now YV12 colorspace is always specified (A2DSource external AviSynth function updated as well)
- Improved AviSynth program info retrieving routine (now using AVSMeter)
+ Improved Seek Chapters routine (new "aggressive" mode added, original mode is now called "mild" mode)
- LAV Filters updated to release 0.74.1
- AVSMeter updated to 2.6.5.1 (2.6.5 modded release to improve reading speed)
+ MediaInfo updated to release 18.05

;)

Bye

[manolito]

Guys, back in business...

:):):)

Will start testing tomorrow...

[MrC]

:):):)

Will start testing tomorrow...

:thanks: manolito, for that, for the patches, for the mods and for all the support here and @ VideoHelp in the last months

Bye

[manolito]

My pleasure... :D

Finished my tests with this new build, not much to report:

A very very small correction to the German language file:
104087 SSA/ASS Untertitel in SRT konvertieren
Just cosmetic, brings it more in line with other translated lines.


The addition of the new audio downmix functions works well.

I noticed that you overhauled the menu highlight colors. Also no problems, the only thing is for folks who overinstall the new build over an older build will have to reselect the hightlight colors to get the colors they want.

As usual I did not test the new subtitle features, this should be tested by users who actually use subs.

My tests were under WinXP and Win7 - 64bit, Win10 users should make their own tests.


There were reports by Win10 users that the preview did not work for them. I cannot reproduce this.
Another Win10 related issue seems to be that Win10 updates can sometimes reset the preferred DS filters to the original MS DMO filters.


If you intend to release a last and final stable version of AVStoDVD there are a couple of considerations how you could harden it for the future. The DVD specs are static, only new source file formats may cause problems. The source filters should handle new formats, the problem I see is with MediaInfo. The current MediaInfo versions do not work with A2D since Zenitram changed the output format. But even if you made A2D compatible with current MediaInfo versions (which would mean a lot of work) there could still be problems in the future. Right now there are already issues with multichannel audio. There are many different 8-ch audio formats, and MediaInfo reports very different output for the number of channels. Sometimes A2D interprets such MediaInfo output as 0 channels. The workaround is to play the source file with a DS based player and check the LAV audio status tab which reports the number of channels which LAV sees. Then the user can manually change the number of audio input channels in A2D.

Of course Win10 updates are another threat for the future stability of A2D, but there is nothing you can do about it.


Whatever, as far as I am concerned this new build is ready to go stable... ;)


Cheers
manolito

[manolito]

I almost forgot to mention a long standing issue when users specify to use an external player AND the default source filter is A2DSource...

(I stumbled upon this issue after recommending to use an external player to users who could not get the internal preview working.)

When A2DSource is selected then the AviSynthP.avs script loads A2DSource.avsi from the "AVStoDVD\Lib" folder. But AviSynthP.avs is called while the active folder is "C:\Windows". This means that A2DSource.avsi is not executed correctly, so the external player will either not work at all, or there will be no audio. Including the Lib folder in the Path does not fix it.

The current workaround is to use DirectShowSource or FFMS2 instead of A2DSource. To fix the issue completely AVStoDVD would need to make the Lib folder the active folder before calling the preview.


Cheers
manolito

[MrC]

Hi manolito, thanks again for the valuable inputs.

A very very small correction to the German language file:

Just cosmetic, brings it more in line with other translated lines.

Good, a final build should address cosmetic issue as well ;)

I noticed that you overhauled the menu highlight colors. Also no problems, the only thing is for folks who overinstall the new build over an older build will have to reselect the hightlight colors to get the colors they want.

You are right, but it was a necessary change, there was a bug in HL colors management. I can add to the History.txt change log section a note to do a complete uninstall before installing 2.8.9.

There were reports by Win10 users that the preview did not work for them. I cannot reproduce this.

I'm aware of this limitation with Win10. Unfortunately I have not found yet a more recent alternative to quartz.dll library. Still searching.

Another Win10 related issue seems to be that Win10 updates can sometimes reset the preferred DS filters to the original MS DMO filters.

True, something definitively out of my control. BTW there is already a warning message if a AVC/AAC file is added and if MS filters are the default filters. Hope it is enough to remind users to switch to LAVs.

Right now there are already issues with multichannel audio. There are many different 8-ch audio formats, and MediaInfo reports very different output for the number of channels. Sometimes A2D interprets such MediaInfo output as 0 channels. The workaround is to play the source file with a DS based player and check the LAV audio status tab which reports the number of channels which LAV sees. Then the user can manually change the number of audio input channels in A2D.

Likely the routine I use to detect AviSynth script properties could come in handy as "backup plan" when Mediainfo 18.05 is messing with audio channels. I will give it a try. Could slow down the file properties reading section.

When A2DSource is selected then the AviSynthP.avs script loads A2DSource.avsi from the "AVStoDVD\Lib" folder. But AviSynthP.avs is called while the active folder is "C:\Windows". This means that A2DSource.avsi is not executed correctly, so the external player will either not work at all, or there will be no audio. Including the Lib folder in the Path does not fix it.

Truly, I cannot reproduce the issue: I have tried with WMPlayer and Tiny Player as external player and the script is rendered properly, both video and audio. The script (AviSynthP.avs, stored in the Temp folder) is exactly the script used during A2D conversion processes, with a simple resizing command at the end to output the correct AR. If the preview is failing, the conversion should fail as well...
Or, maybe, I did not get the issue. :o

;)

Bye

[manolito]

Hi MrC,

I found the post where I published my 8-ch audio findings:
https://forum.doom9.org/showthread.php?p=1893390#post1893390

Unfortunately I did not keep my test clips, and demo-world.eu closed shop recently.

But you could use AVSMeter instead of MediaInfo to retrieve the number of audio channels which the currently used source filter actually sees. No idea if this is feasible...


For the external player issue I made more tests, this time including WinXP and Win7-64. Results:

WMP and Tiny Player worked under both OS

MPC-HC 32 gave this error:
https://i.postimg.cc/HxC6bPHS/MPC-HC-32.png (https://postimages.org/)

VirtualDub 1.6.19 did not find an audio decompressor:
https://i.postimg.cc/nrS5KY3C/VDub-Error.png (https://postimages.org/)
https://i.postimg.cc/0N5B4Bhb/VDub-Info.png (https://postimages.org/)

For me especially VDub is an excellent replacement for the internal preview, because it allows me to do multiple cuts (editing out commercials), and with the help of a small utility called VCF2AVS the edit points can be translated into AviSynth Trim commands.
And as I already mentioned the problems disappear when I use FFMS2 or DirectShowSource, so it must be related to the fact that A2DSource.avsi lies in a different folder so the plugins it tries to load do not load correctly. This happens only for the preview, the encoding is not affected.


Cheers
manolito


//EDIT//
Good news, I managed to solve the problems with the external players...

For MPC-HC it was necessary to copy all the plugin DLLs from the "AVStoDVD\Lib" folder into the "AviSynth\plugins" folder. Easy enough, and I do not expect any adverse effects as long as the plugins in both folders are identical.

For VDub I believe that my old version 1.6.19 was to blame. Upgrading to the latest VDub2 version solved it, and so far this VDub version seems to work nicely even on my ancient desktop computer.

[MrC]

Hi manolito, thanks for the double check with VirtualDub2 and MPC-HC.

Another oddity with MPC-HC is that anytime I feed it with a simple AVISource() script, it chokes (no render). Since AVISource is the first choice in A2DSource, that could be another reason of preview failure with MPC-HC.

The AVSMeter workaround to grab audio channels works well. E.g. some dolby atmos tracks are read by MediaInfo as "15 objects / 6 channels". Very, very misleading. AVSMeter way or improved MediaInfo string parsing? Will do some testing. If you have any other exotic audio tracks, please advise.

;)

Bye

[manolito]

For some 8-ch demo clips I found www.demolandia.net quite useful (too bad that demo-world.eu has closed down).

AVSMeter way or improved MediaInfo string parsing?
I think that AVSMeter is safer, but also slower. For clips with more than 1 audio track you would have to check the number of audio channels separately for each track, and you would have to use FFMS2 for each track higher than #1. Tough decision...

Cheers
manolito

[manolito]

Another oddity with MPC-HC is that anytime I feed it with a simple AVISource() script, it chokes (no render)

Are you sure you used the 32-bit version of MPC-HC? Because I get this error only when using MPC-HC 64.

And I also managed to find the reason why my old VDub version could not decompress the audio when using it for the preview.
This old version cannot handle 32-bit float audio... :scared:
At some point in the A2D develoment you added the line
global OPT_AllowFloatAudio = True
at the beginning of A2DSource.avsi. This command is not present in the AVS script when a source filter like FFMpegSource or DirectShowSource is explicitly specified under preferences, so the old VDub will work. Only if A2DSource is used VDub will choke.


Cheers
manolito

[manolito]

FWIW I found another method at StackOverflow for determining the number of audio channels. It uses FFProbe, this is the call:

ffprobe -i yourFile.mp4 -show_entries stream=channels -select_streams a:0 -of compact=p=0:nk=1 -v 0

It looks much clearer than the MediaInfo output for several 8-ch formats. No idea if it is as reliable as the AVSMeter method.

The StackOverflow page is here:
https://stackoverflow.com/questions/47905083/how-to-check-number-of-channels-in-my-audio-wav-file-using-ffmpeg-command

[MrC]

Are you sure you used the 32-bit version of MPC-HC? Because I get this error only when using MPC-HC 64.
Yes, both with 32bit and 64bit :)

And I also managed to find the reason why my old VDub version could not decompress the audio when using it for the preview.
This old version cannot handle 32-bit float audio... :scared:
At some point in the A2D develoment you added the line
global OPT_AllowFloatAudio = True
at the beginning of A2DSource.avsi. This command is not present in the AVS script when a source filter like FFMpegSource or DirectShowSource is explicitly specified under preferences, so the old VDub will work. Only if A2DSource is used VDub will choke.

My memory is fading, but I found this 2015 thread (https://forum.doom9.org/archive/index.php/t-172310.html) about the topic.

FWIW I found another method at StackOverflow for determining the number of audio channels. It uses FFProbe, this is the call:

It looks much clearer than the MediaInfo output for several 8-ch formats. No idea if it is as reliable as the AVSMeter method.

The StackOverflow page is here:
https://stackoverflow.com/questions/47905083/how-to-check-number-of-channels-in-my-audio-wav-file-using-ffmpeg-command

Thanks, that could be a good alternative basically for all clip properties. Now I'm trying to improve parsing of MediaInfo "verbose" output. I would come out with a quick fix in the next days.

;)

Bye

[MrC]

About the preview issue with Win10, another alternative could be to use Graph Studio Next (https://www.majorgeeks.com/files/details/graphstudionext.html) to open and run the AviSynth script within a clear directshow environment (unfortunately GraphStudio 0.3.2.0 does not support the run command thru CLI).

;)

Bye

[manolito]

The more I dig into these 8-ch audio formats, the more confusing it gets. I am sure glad that I only have a stereo sound system... :devil:

I have tested these formats:
DD+ (aka E-AC3) 7.1
DTS-HD MA 7.1
Dolby ATMOS/TrueHD/EAC3

For the DD+ 7.1 format MediaInfo as well as LAV Audio only see 6 channels. This audio format is handled correctly by A2D.

The DTS-HD MA 7.1 format also contains a 6-ch audio stream, and MediaInfo reports it as 8 / 6 channels which causes A2D to issue invalid downmix commands like "Dmix8 / 66()". LAV Audio sees it as 8-ch, so the MediaInfo parsing must be corrected to 8.

For Dolby ATMOS MediaInfo sees 3 audio streams. The first one is ATMOS which right now cannot be decoded by any free audio decoder. So A2D sees it as having 0 channels which of course results in a crash in DownMix.avsi. LAV Audio sees it as 8-ch.


If 8-ch audio is only available in these 3 formats then it should be easy to correct the MediaInfo parsing.

But I found some more confusing facts:
8-ch audio tracks can consist of several audio streams within one track. This concept is rather new to me. MediaInfo 18.05 enumerates the audio as tracks while all FFMpeg based software enumerates the audio as streams. This means trouble for AVStoDVD.

LAV Audio has no way for a user to specify a certain stream from an audio track, it always uses the first stream within a track which it can decode. A specific stream can be selected at playback via LAV splitter (right-click on the splitter tray icon), but I have found no way to select a specific stream within a track for AVStoDVD. So with the exception of DD+ 7.1 LAV Audio will always see 8-ch audio.

If more than one audio track should be included in the A2D project, and the first audio track has 8 channels, the result will be broken. A2D needs to use FFMS2 as the source filter for the second audio track (because DS based source filters do not allow to select the audio track). But if the first audio track contains more than 1 stream, the FFMS2 enumeration will see 2 or more streams in the first audio track pushing up the index numbers. In the case of 2 audio streams within the first audio track the index number for the second audio track will be 3 (instead of 2). This is probably tough to fix.


Cheers
manolito

[MrC]

That's weird. But intriguing ;)

First step is to read properly ATMOS clips. Time to put aside MediaInfo and to embrace FFprobe? It could be a good idea... maybe giving the user the option to choose the media reader in the Preferences... to consider for 2.9.0 release.

;)

Bye

[manolito]

I don't know if handling 8-ch audio correctly for DVD output is worth all the trouble... :(

My workaround is to preprocess source clips with 8-ch audio using dmMediaConverter. This is an FFMpeg GUI specializing in video conversion, and it is very smart. Source clips with 8-ch audio are shown stream based, you can easily select or discard specific audio streams. If you want to downmix audio streams you can either do it into WAV or into the desired DVD target audio format. For video you just use "Copy", and the target container should be MKV. This MKV can be used as the A2D source file, and I never had any issues with the conversion.


Cheers
manolito

[MrC]

Probably you are right, btw sometimes troubles mean fun. Just to save some time...

On the path of releasing 2.8.9 final: hotfix (https://sites.google.com/site/avstodvdmain/AVStoDVD_289_Alpha201004_exe_only.7z) with improvements to define previewer (default external for Win10) and better parsing of Mediainfo audio channels.

;)

Bye

[manolito]

...and better parsing of Mediainfo audio channels.

Thanks, this is a major progress, and the number of audio channels are now correctly detected even for the most demanding source files... :D

The test clip I mostly use is the helicopter demo from here:
https://drive.google.com/open?id=0BwxFVkl63-lENElIcC1xTnF2Yk0
It has 2 audio tracks, but 3 audio streams. A nasty thing is that the second audio track contains an E-AC3 stream where MediaInfo reports 15 objects first, so A2D used to think that it had 15 audio channels.

This is now completely fixed, I tested at least 10 clips with 8-ch audio, and this new build always detected the correct number of channels.

There is a small glitch in the A2D GUI, though. For a source with 2 audio tracks users can switch the active audio track in the "View/Edit Titles" window. The change is correctly reflected in the AviSynth tab, and the preview also uses the selected audio track. But after selecting audio track #2 and pressing OK it is not possible to edit the title properties for audio track #2. Only track #1 shows up for editing, I found no way to select track #2.

As long as A2D detects the correct number of channels (which it does now) this is not a big problem, but it would be nice if it would get fixed.


The other bigger issue is for sources with more than 1 audio track. The "Helicopter" clip is a good example. The first audio track has two streams, so the index numbers for the audio get shifted if an FFMpeg based (i.e. stream based) software is used. If I specify to include both audio tracks in my project then FFMS2 will be called with "track=2" for the second audio track. This is wrong, to use the audio in the second audio track FFMS2 would have to be called with "track=3".

I cannot think of an automatic and foolproof way to fix this. It is the "culture clash" between enumerating audio track based or stream based. A foolproof workaround is to repack such source files into an MKV container before feeding them to AVStoDVD (MKVToolnix does this painlessly). When you feed this MKV into A2D every audio stream becomes a separate audio track again, and FFMS2 will use the correct track number for the second (or higher) audio track.


Whatever, thanks again for this latest build, it solves many problems...

Cheers
manolito

[manolito]

I cannot think of an automatic and foolproof way to fix this. It is the "culture clash" between enumerating audio track based or stream based.
Maybe there is a way to determine if a track contains more than one audio stream by parsing the MediaInfo output. For a typical audio track with ATMOS/TrueHD plus an AC3 substream Mediainfo reports this:
Format profile : TrueHD+Atmos / TrueHD / AC-3
Channel(s) : Object Based / 8 channels / 6 channels

Both keys could be used IMO. An entry with "Atmos" or "Object Based" needs to be ignored, and if there are more than one entries left you will know that there is one or more additional substreams in this track. In the above example there is one substream, this means that 1 has to be added to the track number of the second and higher audio tracks for FFMS2 to work correctly.

For all the 8-ch clips I tested only the first audio track ever contained more than one stream, so it would not be hard to implement this. Of course I have no idea if higher audio tracks can also have more than one stream. If yes this would complicate the math to pass the correct track number to FFMS2.

Just an idea... ;)

Cheers
manolito

[MrC]

Thanks manolito for all the research. Frankly speaking I would not spend too much time to fix that mismatch between Mediainfo and FFmpeg. I don't know which program is handling properly the recent 8 channels audio tracks. Right now I prefer to stand by the window and see if the 2 apps come to a convergence. If not, I will second FFmpeg and for 2.9.0 release (2025 maybe? :rolleyes:) I can develop a new media info parser from FFprobe output (xml or json based).

Meanwhile I will add a new entry in the FAQ audio section, to suggest to use MKVtoolnix in case of "problematic" 8 channels tracks.

;)

Bye

[manolito]

I have my doubts that MediaInfo and FFMpeg will ever come to a convergence in this respect. And in 2025 nobody except a few geezers like you and me will even know that the DVD format ever existed... :devil:

But I do agree with your conclusion. It is hardly worth the trouble to make A2D foolproof for handling source videos with 8-ch audio, especially for ATMOS. Experienced users have a choice of several workarounds.

But still I have a hard time conceiling the fact that I am a perfectionist. It bugs me that software like DVDStyler which is completely FFMpeg based can handle such sources without problems, and AVStoDVD cannot... :eek:

This issue would not exist if DirectShowSource had a way to specify a specific audio track for decoding (like FFMS2 and LSMASH have). Probably this won't happen anytime soon.


Cheers
manolito

[MrC]

2.8.9 Final is out (https://sourceforge.net/projects/avstodvd/files/avstodvd/AVStoDVD%202.8.9/). No changes from latest Alpha+hotfix.

Two main items for next release: advanced preview under Win10 and switch from MediaInfo to FFprobe.

;)

Bye

[manolito]

:thanks: for this new stable build...

Two main items for next release: advanced preview under Win10 and switch from MediaInfo to FFprobe.

Sounds like you have no intention to abandon your baby...
Great news :D

The switch from MediaInfo to FFprobe could be a lot of work. Especially for 8-ch audio sources with a Dolby ATMOS track I can already see the pitfalls... :devil:


Cheers
manolito

[manolito]

This is a heads-up for everyone using my upmix routines from the Wavi_Mod plugin:

It turns out that I have been using wrong channel mappings for the final 6-ch output all the time. See this post and Tebasuna's reply:
https://forum.doom9.org/showthread.php?p=1929900#post1929900

To fix it you can either download and install the latest version of my A2D plugins from here:
https://files.videohelp.com/u/172211/Manolito_s%20A2D%20Plugins.7z

Or you can edit the file "wavi_mod.bat" in your "AVStoDVD\Wavi" folder. You can open the file in NotePad and use Search and Replace. Search for
"%TempPath%Upmix_Temp\rear_left.wav" "%TempPath%Upmix_Temp\rear_right.wav" "%TempPath%Upmix_Temp\center.wav" "%TempPath%Upmix_Temp\lfe.wav"
and replace all 3 instances with
"%TempPath%Upmix_Temp\center.wav" "%TempPath%Upmix_Temp\lfe.wav" "%TempPath%Upmix_Temp\rear_left.wav" "%TempPath%Upmix_Temp\rear_right.wav"
Sorry for the inconvenience...

Cheers
manolito

[Mike-uk]

Hope you have a good Holidays MrC and thanks again for your hard work on AVStoDVD , and to all the others on here that have helped

[marioxb]

Hello there MrC! I've used your program many times in the past and I am very happy with it. However, now I am having an issue with all MKV and MP4 files. I get the dreaded "runtime of 00:00:00 is shorter.." bla bla. I've even tested it with MKV files I know I've correctly converted before. I updated to the latest version of your program today to see if that fixes my issue to no avail. I assume I've (un)installed too many codecs or something but this is driving me crazy. I've attached two log files. The first one is if I say "No" at the duration error and the second if I say "Yes". Thank you in advance for your help.

Log 1:
<12/25/2020 8:46:59 PM>
START PROCESS
<>

<12/25/2020 8:46:59 PM>
PROJECT SETTINGS

DVD Video Standard: NTSC
DVD Titles number: 1
DVD Size: 1442/4450 MB (32%)
DVD Output Setup: DVD Folder
DVD Label: DVD
DVD Menu: No Menu
Output Folder: C:\Users\Tom\Videos
Delete Temp Assets Files: Yes
Delete Temp Working Files: Yes
Edit Command Parameters: No
Post Process Task: Show Progress Status window

PREFERENCES

MultiThread: 1
AVS Video Source Filter: A2DSource
AVS Audio Source Filter: A2DSource
AVS UpSize/DownSize Filter: Lanczos4Resize/Spline16Resize
Frame Adjust Strategy: 0
FPS Hard Conversion: 1
PAL SpeedUp: 0
NTSC SlowDown: 0
Video Resolution: 0
Video Encoder: 0
Video BitRate Min: 2500
Video BitRate Max: 8500
Keep DVD Compliant Video: 1
AC3 Audio Encoder: 0
Force FFmpeg for Long Audio: 1
DVD Audio Format: 0
DVD Audio BitRate: 192
Keep DVD Compliant Audio: 1
Normalize Audio: 0
Auto Delay Audio: 1
DVD Audio Language (Primary): JA - Japanese
DVD Audio Language (Secondary): EN - English
DVD Subs Language (Primary): EN - English
DVD Subs Language (Secondary): EN - English
DVD Subs Font: Tahoma 16pt (240,240,240)
Chapters Interval: 5
Use Source Chapters: 1
DVD Burning Drive: D: hp CDDVDW SH-216ALN HA5A
DVD Burning Speed: 4x
Auto Erase DVD RW: 1
Unload ActiveMovie Library: 1
Adjust DirectShow Filters at runtime: 1
Save General Settings: 0

SYSTEM INFO

Processor Name: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz
Operating System: Windows 10 (10.0.19041) 64 bit
User has Admin Rights: YES
Running with Elevated Privileges: NO (3)
Available Output Disc Space: 62 GB
AviSynth Version: AviSynth 2.60, build:Mar 31 2015 [16:38:54] (release 2.60)
LAV Filters is installed: YES (release 0.74.1)
ffdshow is installed: NO

CODECS REPORT

H.264/AVC: Broken
Xvid: Broken
DivX 4/5/6: Broken
Other MPG4: Broken
DV: Broken
MPEG1: Broken
MPEG2: Broken
AAC: Broken
MP3: Broken
MP2: Broken
AC3: Broken
<>

<12/25/2020 8:46:59 PM>
TITLE 1 SOURCE FILES
Video: F:\test.mkv
Info: AVC - 941 kbps - 640x480 - DAR 4:3 - 29.97 fps (CFR) - 8 bit - Progressive - 22:49 minutes - 41039 frames
Audio 1: F:\test.mkv
Info: MPEG-1 Audio layer 3 - 128 kbps - CBR - 2 ch - 48000 Hz - 22:49 minutes (0 ms delay) - JA - Default
[MediaInfoLib - v18.05]
<>

<12/25/2020 8:46:59 PM>
AVISYNTH SCRIPT
Import("C:\Program Files (x86)\AVStoDVD\Lib\A2DSource.avsi")

Video = A2DVideoSource("F:\test.mkv", CacheFolder="C:\Users\Tom\AppData\Local\Temp", VFR=false, FrameRate=29.97)
Audio = A2DAudioSource("F:\test.mkv", CacheFolder="C:\Users\Tom\AppData\Local\Temp")

Video = Video.ConvertToYV12()
Video = Video.Lanczos4Resize(720,480)

AudioDub(Video, Audio)
<>

<12/25/2020 8:46:59 PM>
DIRECTSHOW AUDIO MIXER OPERATIONS:
No LAV Filters mixer ON/OFF adjustment required at runtime
<>

<12/25/2020 8:46:59 PM>
START VIDEO ENCODING OPERATIONS
Video Encoding Profile: FFmpeg CBR 1-pass
Target Video FileSize: 1387.2 MB
Encoding Parameters: -i "C:\Users\Tom\AppData\Local\Temp\DVD_test_1.avs" -threads 2 -aspect 4:3 -c:v mpeg2video -b:v 8500k -minrate 8500k -maxrate 8500k -bufsize 2000k -dc 10 -y "C:\Users\Tom\Videos\DVD_test.m2v"
<>

<12/25/2020 8:47:06 PM>
Process aborted during Title 1 VIDEO encoding operations.

Error Message: Warning! Title 1 output Video duration (00:00:00) is shorter than expected duration (00:22:49).

For Video issues troubleshooting see Help/FAQ/Video section.
<>

<12/25/2020 8:47:06 PM>
Warning! AVStoDVD Project ended with errors.
<>

<12/25/2020 8:47:06 PM>
Log file created by AVStoDVD Release 2.8.9
<>


Log 2:
<12/25/2020 8:47:15 PM>
START PROCESS
<>

<12/25/2020 8:47:15 PM>
PROJECT SETTINGS

DVD Video Standard: NTSC
DVD Titles number: 1
DVD Size: 1442/4450 MB (32%)
DVD Output Setup: DVD Folder
DVD Label: DVD
DVD Menu: No Menu
Output Folder: C:\Users\Tom\Videos
Delete Temp Assets Files: Yes
Delete Temp Working Files: Yes
Edit Command Parameters: No
Post Process Task: Show Progress Status window

PREFERENCES

MultiThread: 1
AVS Video Source Filter: A2DSource
AVS Audio Source Filter: A2DSource
AVS UpSize/DownSize Filter: Lanczos4Resize/Spline16Resize
Frame Adjust Strategy: 0
FPS Hard Conversion: 1
PAL SpeedUp: 0
NTSC SlowDown: 0
Video Resolution: 0
Video Encoder: 0
Video BitRate Min: 2500
Video BitRate Max: 8500
Keep DVD Compliant Video: 1
AC3 Audio Encoder: 0
Force FFmpeg for Long Audio: 1
DVD Audio Format: 0
DVD Audio BitRate: 192
Keep DVD Compliant Audio: 1
Normalize Audio: 0
Auto Delay Audio: 1
DVD Audio Language (Primary): JA - Japanese
DVD Audio Language (Secondary): EN - English
DVD Subs Language (Primary): EN - English
DVD Subs Language (Secondary): EN - English
DVD Subs Font: Tahoma 16pt (240,240,240)
Chapters Interval: 5
Use Source Chapters: 1
DVD Burning Drive: D: hp CDDVDW SH-216ALN HA5A
DVD Burning Speed: 4x
Auto Erase DVD RW: 1
Unload ActiveMovie Library: 1
Adjust DirectShow Filters at runtime: 1
Save General Settings: 0

SYSTEM INFO

Processor Name: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz
Operating System: Windows 10 (10.0.19041) 64 bit
User has Admin Rights: YES
Running with Elevated Privileges: NO (3)
Available Output Disc Space: 62 GB
AviSynth Version: AviSynth 2.60, build:Mar 31 2015 [16:38:54] (release 2.60)
LAV Filters is installed: YES (release 0.74.1)
ffdshow is installed: NO

CODECS REPORT

H.264/AVC: Broken
Xvid: Broken
DivX 4/5/6: Broken
Other MPG4: Broken
DV: Broken
MPEG1: Broken
MPEG2: Broken
AAC: Broken
MP3: Broken
MP2: Broken
AC3: Broken
<>

<12/25/2020 8:47:15 PM>
TITLE 1 SOURCE FILES
Video: F:\test.mkv
Info: AVC - 941 kbps - 640x480 - DAR 4:3 - 29.97 fps (CFR) - 8 bit - Progressive - 22:49 minutes - 41039 frames
Audio 1: F:\test.mkv
Info: MPEG-1 Audio layer 3 - 128 kbps - CBR - 2 ch - 48000 Hz - 22:49 minutes (0 ms delay) - JA - Default
[MediaInfoLib - v18.05]
<>

<12/25/2020 8:47:15 PM>
AVISYNTH SCRIPT
Import("C:\Program Files (x86)\AVStoDVD\Lib\A2DSource.avsi")

Video = A2DVideoSource("F:\test.mkv", CacheFolder="C:\Users\Tom\AppData\Local\Temp", VFR=false, FrameRate=29.97)
Audio = A2DAudioSource("F:\test.mkv", CacheFolder="C:\Users\Tom\AppData\Local\Temp")

Video = Video.ConvertToYV12()
Video = Video.Lanczos4Resize(720,480)

AudioDub(Video, Audio)
<>

<12/25/2020 8:47:15 PM>
DIRECTSHOW AUDIO MIXER OPERATIONS:
No LAV Filters mixer ON/OFF adjustment required at runtime
<>

<12/25/2020 8:47:15 PM>
START VIDEO ENCODING OPERATIONS
Video Encoding Profile: FFmpeg CBR 1-pass
Target Video FileSize: 1387.2 MB
Encoding Parameters: -i "C:\Users\Tom\AppData\Local\Temp\DVD_1_test_1.avs" -threads 2 -aspect 4:3 -c:v mpeg2video -b:v 8500k -minrate 8500k -maxrate 8500k -bufsize 2000k -dc 10 -y "C:\Users\Tom\Videos\DVD_1_test.m2v"
<>

<12/25/2020 8:47:18 PM>
Process halted during Title 1 VIDEO encoding operations.

Error Message: 'Warning! Title 1 output Video duration (00:00:00) is shorter than expected duration (00:22:49).'

Video errors warning message skipped.
<>

<12/25/2020 8:47:18 PM>
START AUDIO ENCODING OPERATIONS (Track 1)
Wavi+Aften Parameters: "C:\Users\Tom\AppData\Local\Temp\DVD_1_test_1.avs" - | "C:\Program Files (x86)\AVStoDVD\Aften\aften.exe" -b 192 -pad 0 -dynrng 5 -bwfilter 0 - "C:\Users\Tom\Videos\DVD_1_test_1.ac3"
<>

<12/25/2020 8:47:38 PM>
WARNING! Errors found during Title 1 Audio Track 1 encoding.
Audio filesize is too small (0 MB)
Backup Audio encoding routine (FFmpeg Safe Mode) is starting ...
<>

<12/25/2020 8:47:38 PM>
START FFMPEG (SAFE MODE) AUDIO ENCODING OPERATIONS (Track 1) - Trial 1/2
FFmpeg Parameters: -threads 2 -i "F:\test.mkv" -vn -c:a ac3 -ar 48000 -ab 192k -y "C:\Users\Tom\Videos\DVD_1_test_1.ac3"
<>

<12/25/2020 8:47:55 PM>
END AUDIO ENCODING OPERATIONS (Track 1)
Created File: C:\Users\Tom\Videos\DVD_1_test_1.ac3 (31.3 MB)
Output Audio Info: AC3 - 192 kbps - CBR - 2 ch - 48000 Hz - 16 bit - 22:49 minutes (0 ms delay)
<>

<12/25/2020 8:47:55 PM>
DVD CHAPTERS CREATION OPERATIONS
Title 1 Input Chapters List: 8991 17982 26973 35964
Title 1 Output Chapters List:
No Chapters List created for Title 1
<>

<12/25/2020 8:47:55 PM>
START DVD AUTHORING OPERATIONS
BatchMux Parameters: -arglist "C:\Users\Tom\AppData\Local\Temp\DVD_1_BatchMux.ini"
BatchMux ini file:
-bmlog "C:\Users\Tom\AppData\Local\Temp\DVD_1_BatchMux.log"
-d "C:\Users\Tom\Videos\DVD_1\VIDEO_TS"
-mxp "C:\Users\Tom\AppData\Local\Temp\DVD_1_MuxMan.mxp"
-l "C:\Users\Tom\AppData\Local\Temp\DVD_1_MuxMan.log"
-muxman "C:\Program Files (x86)\AVStoDVD\MuxMan"
-prio LOW
-palette "C:\Users\Tom\AppData\Local\Temp\DVD_1_Palette.txt"
-v "C:\Users\Tom\Videos\DVD_1_test.m2v"
-vidmode 4:3
-a1 "C:\Users\Tom\Videos\DVD_1_test_1.ac3"
-a1lang ja
<>

<12/25/2020 8:48:14 PM>
Process aborted during DVD AUTHORING operations!

Check following files for more details:

AVStoDVD log file <C:\Users\Tom\Videos\DVD_1.log>
BatchMux log file <C:\Users\Tom\Videos\DVD_1_BatchMux.log>

For more troubleshooting on Authoring issues, see Help/FAQ/Authoring.
<>

<12/25/2020 8:48:17 PM>
Warning! AVStoDVD Project ended with errors.
<>

<12/25/2020 8:48:17 PM>
Log file created by AVStoDVD Release 2.8.9
<>

[manolito]

From both of your logs:
CODECS REPORT

H.264/AVC: Broken
Xvid: Broken
DivX 4/5/6: Broken
Other MPG4: Broken
DV: Broken
MPEG1: Broken
MPEG2: Broken
AAC: Broken
MP3: Broken
MP2: Broken
AC3: Broken

This means that your DirectShow based source filters are broken. They cannot decode your source files, so the encoder cannot encode anything.

Two things you can do:

1. Do not use DirectShow based source filters, use FFMpegSource instead. Under "Preferences->AviSynth" change the source filters for video and audio from the default A2DSource to FFMpegSource. If you want to make these changes permanent, tick the checkbos at the lower left corner.

2. Fix the DirectShow based source filters. You can do this either directly under AVStoDVD or by downloading a small tool called DS Filter Tweaker. You can find this option under "Codecs->Preferred DirectShow Codecs Setup".
https://i.postimg.cc/htDks2Q3/Codecs2.png
Set ALL filters to LAV Filters and close the window. If this does not work, use the link at the bottom to download the Tweaker tool.

Please note that Win10 is very stubborn and insists on using its own built-in source filters (this is BAD because most of the MS source filters are crap). After every automatic update of the OS the MS filters will be active again, so users will have to repeat the above procedure.


Good luck
manolito

[marioxb]

From both of your logs:


This means that your DirectShow based source filters are broken. They cannot decode your source files, so the encoder cannot encode anything.

Two things you can do:

1. Do not use DirectShow based source filters, use FFMpegSource instead. Under "Preferences->AviSynth" change the source filters for video and audio from the default A2DSource to FFMpegSource. If you want to make these changes permanent, tick the checkbos at the lower left corner.

2. Fix the DirectShow based source filters. You can do this either directly under AVStoDVD or by downloading a small tool called DS Filter Tweaker. You can find this option under "Codecs->Preferred DirectShow Codecs Setup".
https://i.postimg.cc/htDks2Q3/Codecs2.png
Set ALL filters to LAV Filters and close the window. If this does not work, use the link at the bottom to download the Tweaker tool.

Please note that Win10 is very stubborn and insists on using its own built-in source filters (this is BAD because most of the MS source filters are crap). After every automatic update of the OS the MS filters will be active again, so users will have to repeat the above procedure.


Good luck
manolito

Oh wow, thanks so much! Yup, probably didn't have Windows 10 last time I ran AVStoDVD. Stupid Microsoft! Anyway, seems to be working great now, I appreciate the help!

[oopsie]

This question has probably been asked and answered but I can't find it...

I've had lots of experience with this tool on a Win7 machine but it died so I'm starting over on a Win10 machine. I've installed the latest version and I've started a project.

PROBLEM:

When I add menus and want to change the start and end frames of the motion thumbnails, I click 'Edit Thumbnail Frame selection' / 'Video' and it launches wmp12 by default. The video plays fine but I can't get wmp12 to display frame numbers so its kind of useless in terms of determining start/end frames.

The real issue is that I've tried using AVS2DVD's internal player (which I'm used to) but when I play the video, the numbers advance but no video is displayed.

I'm looking for some help on either getting the video to play with AVS2DVD's internal player (preferred) or a recommendation on an external third party player that will display frame numbers as the video plays.

[oopsie]

Issues with video preview when creating menus

Not sure my previous post went through...

Trying AVS2DVD with Windows 10.

If I preview a video during menu creation using the builtin player, I get no video. The numbers increment but the screen is blank.

If this can't be fixed, please suggest an external video player that can show frame numbers during play.

Regards

[manolito]

This is a known Win10 problem. MrC is aware of it, but I am not sure when (or if at all) he will find the time to work on a new build.

In the meantime I recommend to use VirtualDub (the 32-bit version) as your external player...

[oopsie]

That worked great.

Thanks manolito!

[manolito]

Glad I could help...

Using VDub instead of the internal player has another big advantage if you want to edit out commervials from your source video. The internal player only lets you cut off a chunk at the start and another chunk at the end of the clip. With VDub you can edit out an unlimited number of segments and then save the edit points in a VCF file.

Once you have this VCF file you can use a tool called VCF2AVS which converts the edit commands in the VCF to Trim commands for AviSynth. Paste these Trim commands to the end of your AVStoDVD AVS script, and all edited out commercials will be gone without any audio sync problems. Get the latest VCF2AVS from this post:
https://forum.doom9.org/showthread.php?p=1328024#post1328024

[thescrapyard]

Issues with video preview when creating menus

Not sure my previous post went through...

Trying AVS2DVD with Windows 10.

If I preview a video during menu creation using the builtin player, I get no video. The numbers increment but the screen is blank.

If this can't be fixed, please suggest an external video player that can show frame numbers during play.

Regards


Try MPC. I used MPC portable as I have this annoying minor issue with Windows 10 as well or stop the preview and start it again then it works

It runs from where you put the folder, just tell AVStoDVD to use the external player

https://portableapps.com/apps/music_video/mpc-be-portable

Let it auto-extract the folder to where the file was downloaded, then simply copy/move that folder to where youw ish. I have it in the AVStoDVD folder as I use the portable release of AVStoDVD

[davexnet]

Hi manolito - still working A2D?

There is a strange problem I'm looking at on videohelp, on certain cases of the input file containing (apparent)
compliant streams. There is an issue during the demux, the only clue, a line missing from the log that should be there
https://forum.videohelp.com/threads/277852-AVStoDVD-Support-Thread/page135#post2638162
Once this occurs the chapter points are not picked up.

If you save the m2v and ac3 from these "bad" files and give them to A2D as the source everything works.

I was wondering if you'd seen it before or if you had any thoughts --
regards,
Dave

EDIT manolito, I just read your recent posting, wishing you all the best for the future

[manolito]

Hi davexnet,

good to hear from you after a long time. Unfortunately I can no longer give any advice concerning computer software at all, those times seem to be over. I do not even understand the stuff I wrote myself just six months ago. See here:
https://forum.doom9.org/showthread.php?p=1958117#post1958117

I noticed that over at VideoHelp you are doing a great job providing support for A2D, please keep it up. This is a great software, it does not deserve to die just yet...


Take care
Manolito

[Sir Didymus]

Hey Manolito! It is shocking to read about the troubles in your life. You have spent dedication and energy to help and assist an incredible number of people all around. We all consider you more than a friend. So, coraggio! And don't be worried about the cryptic of the code written by yourself some time ago... Give time to yourself to recover, we are sure your attitude, which is lovely, has not changed after the accident happened to you... Take care about you!

[davexnet]

Hi manolito,
thanks for the kind words, not so many issues come up with A2D these days, but I try to answer them
and help out when I can. On a personsal note I wanted to say I really enjoyed the energetic back and forth
of working with you in that thread. Good times! Your life has changed and you have some new
challenges now. I wish you all the best and success moving forward.
Dave

[Arizoa]

Hello, to make my dvds i use avstodvd since several years and i am very satisfied with it. But i have a small problem when creating the menu. At this moment i am creating dvds with 20 titles-titles labels- on each dvd.
I use the static menu.
If i edit the menu, each title label has a default value of 20 in the height case
i wish to change this 20 value and the basic way is to do the change by editing each of the 20 title label one after the other.
so my question is: in what folder of avstodvd program is the title "label heiht" value? If i could change this default value i will no more have to do the change in the 20 "title label height" one after the other.
I looked in the menu template -labels.ini- but there is no height value.
thank you for your attention

[rohan023]

Hi Arizoa, I think AVStoDVD's label-height setting is part of its .a2d project templates, not in the labels.ini file. You can modify these .a2d files directly, but it's more efficient to save a customized template.

[Arizoa]

hello rohan023,
thank you for your interest to my problem and your fast reply.
1. what do you mean with ".a2d project templates"?
The a2d file is the file created when we do "save the project as" if i am right. Yes in this file there are the "ThumbLabelHeight" value for each title but it is the default value -20- I could change this value in the a2d but i have to do that for each title -i have about 20 titles- so it is almost as long as to change directly in the menu.
2. In a template i have only the arrows right-left, play all button, labels.ini where there is not the "ThumbLabelHeight" and the bmp background picture.
Remember i use static menu.
Thank you for your attention.

[Arizoa]

hello rohan23,
I thought a few more about your reply, looked in the avstodvd menu wizard and i have found an option " settings from a2d project". As i kept a previous project i loaded it with " settings from a2d project" and new project titltes.
And it seems to work. The "ThumbLabelHeight" value is no more the default value.
I did only a quick test but i think that will be a good solution.
Many thanks again to you for your very useful help.

[MikeC]

Hi, someone suggested your program to convert my 1080P AVCHD 29.97fps video to DVD compliant NTSC widescreen MPEG-2.

See attached screenshot. Why does it show Progressive in the parameters? Isn't the DVD spec for 29.97fps video supposed to be interlaced?

Also, can you tell me what resizing algorithm it uses such as bicubic, spline36, etc?