Thanks my friend. I installed the new AVS2DVD version. I tried your script out and yes it is a lot better than before but in the panning shots its as if it jumps slightly. you can see this in your converted clipped at 00.08 time when played back on vlc player. I'm not sure if this is maybe a error in my installation that's causing this or the script but since its in the converted file you did I am thinking its maybe the script.
I think we know for sure the framerate of these source files are 23.976 so if we can get to 25fps smoothly I would say we has accomplished this. do I need to check or uncheck the "use pal speed up for progessive NTSC Film to Pal" in the options?
Our website is made possible by displaying online advertisements to our visitors.
Please consider supporting us by disabling your ad blocker or buy PlayOn (record Netflix) :)
Please consider supporting us by disabling your ad blocker or buy PlayOn (record Netflix) :)
+ Reply to Thread
Results 3,271 to 3,289 of 3289
The result depends entirely on how well the duplicates are removed. FDecimate is probably not the best solution, you may get better results using TDecimate.
I have attached 2 files using either TDecimate(mode=0,cycleR=3,cycle=5) or TDecimate(mode=7,rate=23.976). I think that both look better than the FDecimate version.
The "use PAL speedup" option does not really matter here, because when your source is a 59.94 fps clip then PAL speedup will not be used by AVStoDVD anyways. To get the PAL speedup you need to edit your AVS script and add the line "AssumeFPS("pal_film", sync_audio=true).SSRC(48000)" at the end.
Thanks again, yes I agree both the TDecimate methods look a lot better than the FDecimate .
I have tried both and they work really well but I am aimng to use the the TDecimate(mode=7,rate=23.976) method as it seems more easier for me to understand how it works and what its doing. i have also unchecked the pal speed up in the AVS2DVD preferences as you mentioned it doesn't matter so theres no point on checking it anyway if Im using "AssumeFPS("pal_film", sync_audio=true).SSRC(48000)" at the end. I will continue along using this method and see how they turn out but so far so good and Thanks to you for that I do appreciate your time and effort.
so just to confirm my script will look like this for sources reporting bck as 23.976fps:
Audio = FFAudioSource("C:\Users\IntelVPro\Desktop\sample1. mp4", track=-1)
Video = FFVideoSource("C:\Users\IntelVPro\Desktop\sample1. mp4", track=-1, seekmode=0)
Video = Video.ConvertToYV12()
Video = Video.Spline36Resize(720,576)
Video = Video.TDecimate(mode=7,rate=23.976)
#PALSpeedUp: using AssumeFPS() to upsize FPS
Now as for a separate matter I have did a complete uninstall of 2.83.4 and a reinstall of the new AVS2DVD Release 2.8.5 final version and reinstalled your FFmpeg Vbr plugin I think its the updated on from post #3217 (Link is http://www28.zippyshare.com/v/YKGhbfmL/file.html), it does not have a mplex option in the bat file but as you said I don't need this has its now built into AVS2DVD v2.8.5. Is this the correct version of your plugin for the new final release?
In post #3268 you also metion "AVStoDVD comes with an older version of FFmpeg (2.2.3 from 2014) which is not really up to date, but it does the job" so should I update this version and if so how?
also you metiuoned about "For FFmpegSource AVStoDVD now uses the C-Plugin by qyot27, but it ships with an outdated version. You should update it using the version from this post:
I spotted your comment in that link #2307 and downloaded the "FFMS2 C-plugin 1140+101" So to intsall this do I just copy the three files FFMS2.avsi, ffms2.dll, ffmsindex.exe from the 32 bit folder to the folder AVS2DVD\lib and replace the three thats in this folder with the new ones?
I think then That is it if all is correct, I have moved correctly to v2.8.5 and we have setup everything and gathered the scripts to work with all the various sources files from the recorder.
Yes, your script looks fine. (There are more TDecimate modes you can play with, e.g. mode 2, but in most cases mode 7 should work well).
You have the latest FF_VBR plugin version, and Mplex is no longer in it because AVStoDVD now uses Mplex by itself.
Upgrading the FFmpeg version is something you have to decide for yourself. I have no idea if the MPEG2 encoder got any improvements during the last couple of years. If you decide to update, here are a few tips:
1. You will always need a 32-bit static version of FFmpeg. The Zeranoe builds are fine.
2. The current FFmpeg builds do not work under WinXP. If you need WinXP compatability, use the version I have linked to below..
3. The current FFmpeg builds will crash under AVStoDVD unless you add the "AVStoDVD\Lib" folder to your Path variable. See this post: https://forum.doom9.org/showthread.php?p=1786007#post1786007
Since I still use XP I use the following FFmpeg build by rogerdpack:
Your ffms2 update is correct (actually you only need the file ffms2.dll, the others are not used).
So yes, you did move to the lastest AVStoDVD successfully. Actually I am waiting for a hotfix version since the stable release does have a few bugs, but MrC is a very busy man these days...
Just switched from XP to Windows 10. AVStoDVD used to hardcode forced subtitles in mkv files automatically. I liked this feature because I only embed subs for no- english parts and the subs would be added to the video it self, not the borders automatically. Now it won't even recognize them when trying to preview or convert to dvd. I've had the same problem with them before with xp but resolved it by uninstalling codec pacs. No codec pacs installed now. I can extract the subs and add them but can not adjust the location. Any help would be appreciated
Changing Video Time to a smaller number does NOT change the duration under general info but changing it to a larger number does. Is this a bug? I had to edit the save file to change the duration to the right number.
Last edited by digicube; 13th Jan 2017 at 12:18.
Thanks again my friend for all your help. My workflow is flowing very well.
AVS2DVD is really coming along and a great programme. I am starting now to appreciate its abilities over other programmes I used in the passed. Good Work Mr C and Very good inputs Manolito.
in the AVS2DVD preferences Audio section My bitrate is set to 192kbps. I this like an ac3 standard for dvds or should I increase it a little? Just out of curiosity what do you use on your settings.
Last edited by jjcinema1; 17th Jan 2017 at 04:36.
For AC3 audio 192 kbps for stereo and 448 kbps for 6-ch is pretty much considered "Standard". Myself I normally use 224 kbps for stereo, mainly to have some headroom. My sources are mostly TV captures which have MP2 audio at 192 kbps. AC3 is considered to be a more effective codec than MP2, so using the same bitrate of 192 kbps already should give me enough slack. But I usually normalize my audio to a higher loudness than the original, so I want to play it safe and use a slightly higher audio bitrate. If you can really hear the difference between 192 and 224 is another question (I believe you cannot, at least not for usual film content).
A new Alpha release is available to download.
- 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)
Only for testing purpose. Feedbacks are very appreciated.
is the program still fully compatible with Windows XP. I noticed it needs the new common controls that is included; the version from the 2.84
release did not work.. Also the included BAT file did not work, the old one was still registered, I could see it using regedit
After I did it manually I have the new version running now.
Will version 2.84 work OK with this newer common controls?
I see that the size calculation looks better now. On version 2.84 a 4GB compliant m2v file + ac3 (@ 160kbps) + srt subtitles was flagged as too
big on the main screen but in this release it correctly determined it was OK.
I've been experimenting with blackmanresize, I've found it to maintain the "look" of the original more than other resizers. For example,
Video = Video.blackmanResize(720,480,taps=5) - I would like to be able to add it to the preferences, but I'm unable to do so because of the
looks like MrC is quite busy these days, so let me try...
I found no problems with the latest A2D versions under XP. But I always use the NoInstall version, and I also generally uninstall the old version completely (including the reg key under HKCU/Software) before installing a new version.
And yes, the size calculation used to be buggy, and it has been fixed recently.
For the BlackmanResize, I also do like this resizer, but in a couple of tests I was unable to spot a difference between the default taps=4 and taps=5. But maybe I am getting too old, my vision is certainly no longer 20/20.
Whatever, if you insist to use taps=5 with BlackmanResize all of the time, you can either wait until MrC finds the time to add this to the software, or you can hack the call to the encoder and modify the source AVS script before the encoder gets called. This must be done separately for HCenc and FFmpeg, though. This should be pretty easy to add to my A2D plugins, I already made a proof of concept test for HCenc.
Before I start working on it, please make sure that the taps=5 parameter really makes a difference for you. And would you need it only for HCenc or for FFmpeg also?
Hi manolito, for me, only Hcenc is an issue. It's not that big a thing, but I just thought that since MrC was in the code, perhaps he could find an
elegant way to add this option, and while we're at it the extra bit for bicubicresize also. eg:
I switch amongst them depending on source issues and to be honest, I don't mind editing the script on the avisynth tab as I do
almost always now for one reason or another
I did a test myself, and I'm enclosing the two files in case you or anybody else is interested in seeing the result. Too my eyes,
the taps=5 looks ever so slightly smoother. if you look at the HCenc log I see average quant for the default blackmanresize is 2.692
while for the taps=5 encode it is 2.689 They're so close, but perhaps the lower quant for taps=5 corroborates my theory that it looks
slight smoother !
The source is the 1080p m2ts.
Alright, I will probably hack something together until tomorrow...
For BicubicResize A2D already uses b and c values of 0 and 0.5. This is hardcoded into the executable, but it should also be easy to replace with different values. Initially I will probably just support BlackmanResize, but the plugin will be expandable for other resizers.
Thanks for the attached examples, but I still cannot see any visible difference between the two. And the slightly lower quantizer for taps=5 also results in a slightly bigger file, so the comparison is a bit unfair.
New version of my HCenc_Mod plugin for AVStoDVD
This new version now lets the user specify additional resizer commands (like "taps=n"). It covers all 5 AviSynth resizers where this makes any sense.
I tested it quite a bit this afternoon, please give it a thorough test run and post your comments...
Corrected an issue for BicubicResize. Sometimes A2D adds offset parameters in addition to the b and c parameters. Please redownload...
The download page is two posts further downwards...
The hacked "HCenc.exe" is a compiled batch file. You may have to exclude it from your antivirus software because compiled batch files are often blindly treated as malware (which is totally stupid). The file does absolutely NOT contain any malware.
Last edited by manolito; 20th Mar 2017 at 10:05.
And here is another new version...
The explanation and the download link is here:
I will not continue to support the single HCenc_Mod plugin here, you have to download the complete package (it is about 50 MB).
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
Last edited by manolito; 21st Mar 2017 at 05:52.
Thanks manolito, have not used your plugins before, only the "dss2 mod". I'll take a look