View Profile
View Forum Posts
Private Message
Many thanks to you. I did try MakeMkv and it's fast, very fast.
So, for me , to close this thread I have some final questions if I may.
1: Does MakeMkv rip commercial DVD removing encryption, as DvdFab does.
2: My best choice would be A: MakeMkv to do a MKV (Rip Fast and lossless)
B: AvsToDvd straight to burning DVD5 using the above MKV as input
C: Handbrake for my backup (around 1.5gb per video) using the above MKV as input.
3: After some reading for Handbrake, it seems that the best setting for me would be:
Optimise Video: X264 Preset = FAST
Tune = NONE
Profile = AUTO
Level = AUTO
Quality: 20 RF
What do you think of this setting. Any better things (Faster or quality) will be appreciate.
And may be useful to others too.
Keep this "JOB" as it's very helpful to us.
Thanks again.
Dan
+ Reply to Thread
Results 2,551 to 2,580 of 4116
-
-
Glad I could help...
1. Yes, MakeMKV removes all ecryptions from DVDs and (most) BluRays. No need to use DVDFab or AnyDVD.
2. Otherwise OK, Handbrake is a good choice for making backups, but there are alternatives (RipBot264, MeGUI, dmMediaConverter, StaxRip...) For the Windows version of Handbrake the audio quality is not top notch, others use QAAC or Nero instead of FAAC, but I have no idea if this is audible at a reasonable bitrate.
Some things you need to know about X264:
The speed presets do not affect quality, it's speed vs. file size. I mostly use Superfast, but my computer is sloooow.
If you are converting films, the Tune=Film setting would make sense.
Profile and Level have an influence on Player compatibility, I believe the AUTO setting is alright unless your player software (or hardware) has problerms.
The CRF value (only Handbrake calls it RF) determines the encoding quality. Default is a CRF (Constant Rate Factor) of 23, very high quality would be about CRF 19. A value of 15 is already considered as overkill. To determine the best value for your needs you should do some test conversions using a critical high quality source.
Alright, that's about all I can think of right now...
Cheers
manolitoLast edited by manolito; 15th Jun 2015 at 10:55.
-
Hi! again.
Thanks for the reply. I will change the the tune setting.
But I have another issue , sorry .
Since I still have the iso and the (Video_TS unzip with winrar) I use MakeMkv with the Video_TS and the output
as an MKV is OK for Minority and Lucky luke. Then I use AvsToDvd with this MKV as input and it give me that the
output will be to big like : 6540 for Minority and 4887 for Lucky Luke. So I can't processed.
If I use the .ifo instead, then both have an output of 4450 which is OK. (But still have the synchro problem)
That bugs me a lot !!!
And If I may, I did try the audio trick, "Edit Title / Avisynth : uncheck AUTO AVISYNTH SCRIPT and click on AUDIO"
but the "Amplify Audio" and "Delay Audio" knob stay grayout. But I can add or delete in the script window if I want.
Sorry to buzz you again.
Dan -
This is because under "Preferences" you have checked "Keep DVD compliant Video" and probably the same for audio. This means that AVStoDVD makes no attempt to reencode your DVD compliant source. Uncheck these options both for audio and video and try again...Originally Posted by djdan
With the .ifo method DGDecode is used as the source filter, and in this case the input will always be reencoded (the setting under "Preferences" is ignored.Originally Posted by djdan
Same as for video. If you have checked to keep compliant audio then of course you cannot add a delay.Originally Posted by djdan
As you might have noticed by now, AVStoDVD is a lot more powerful than it looks initially. Please do yourself a favor and take an hour or two to familiarize yourself with all the settings under "Preferences". Then load a source and have a look at the settings under "View/Edit Title". If anything is not clear, use the help file, it is excellent.
Cheers
manolito -
Your HCEnc patch works perfectly, thanks for the extra effort to please anally retentive people like me
-
Sorry, we talked about this a while ago over @ Doom9...Originally Posted by Groucho2004
Just curious - How does AVSMeter detect audio delays? I don't remember writing any code for that...Originally Posted by manolito
- bad short term memory.
Of course for a d2v source the audio delay gets extracted from the audio file name.
Cheers
manolito -
Finally it work properly on both video .
But the Lucky Luke has an error "Could not write to the standard output ".
I had to click the "X" to get out of it then another one windows for CMD.exe
then another one from AvsToDvd for FFmpeg in safe mode. I click yes then
everything is OK. If this is normal then many thanks to you.
One thing though I surely misunderstand the "DVD compliant" as I tough that
an MKV was a container as video_TS . I did some research on the web for it
but I'm not sure if all this technical stuff apply to AvsToDvd setting "Check/Uncheck".
Does it means that If I use MKV file then UNCHECK both video and audio.
And If use video_ts then check both.
Finally if you have a web site or a small DOC that can describe "DVD compliant"
you are referring to, that will be very appreciate.
Thanks again for all your help wishing that it may help others too.
Dan -
Thanks for the feedback, my pleasure...Originally Posted by steptoe
-
Hi Dan,Originally Posted by djdan
no, this is not normal, but it seems to be unrelated to your previous sync issues. Could you post the log for this conversion?
I do not have my own web site, but I can write a small tutorial right here...Originally Posted by djdan
As you know DVDs use the MPEG2 format for video. But MPEG2 comes in many flavors, if you want to use it for a DVD then some restrictions do apply. Only some fixed frame sizes are allowed (720 x 576/480 plus two smaller sizes). The maximum allowed bitrate is restricted to something like 9000 kbps, the MPEG2 encoding profile has to be main@main, and some other restrictions. The same goes for DVD compliant audio, only certain formats and certain bitrates are allowed.
AVStoDVD checks if the source streams already fulfil the requirements to be used for DVD without altering them. It does not matter at all if the source streams come as VOB files, as MPG files or remuxed in an MKV or MP4 container. In your case you have remuxed the source VOBs into an MKV container, but the streams within this MKV are still DVD compliant (they have not been reencoded by MakeMKV).
If "Keep DVD compliant Video or Audio" is checked in the AVStoDVD preferences, then A2D will not reencode the source streams. But in your case it will warn you that the result will not fit on a single layer blank. If you want the result to fit on a blank then at least the video stream has to be reencoded.
In AVStoDVD there are 2 places where you can change the setting to keep compliant source streams. Under "Preferences" you set the global options which will be used for all input files. You must make these settings BEFORE loading an input file, otherwise the settings will not be used. And you must decide if you only want to change settings just for the next project, or if the changes should be permanent (activate "Save settings as default").
The second place where you can change settings is under "View/Edit Title Settings". Here you can make changes for each source title separately. Let's say that you have checked "Keep already compliant..." for both audio and video under "Preferences". Now you will get the warning that the result will be too big to fit on a single layer blank. To force reencoding for this title click on "View/Edit Title Settings", go to the "Video" tab, uncheck "Automatic Settings" and also uncheck "Keep compliant Video". If you also want to reencode audio, repeat the thing under the "Audio" tab.
If you use the .ifo from a VIDEO_TS folder as the input, things are a little different. In this case the VOBs will be indexed by DGIndex first, and DGDecode will be used as the source filter. Here the source will ALWAYS be reencoded, the "Keep compliant Video" setting will be ignored. So for this case it does not matter if you have checked or unchecked this setting. But I said it before, using the .ifo as the source is something I do not recommend...
Alright, I hope things are a little clearer now...
Cheers
manolito -
Hi!. That is so simple the way you wrote it , you should include this DOC to the "Help" in AvsToDvd.
I did redo the Lucky luck to be sure and I include the LOG plus photos of what I saw. I burned it and everything i OK.
I have too "Harry Potter - Globlet of fire" that I have to lower "Lower Avg Bitrate" to 2100 in Preferences to be able to fit it to 4449Gb.
It's a 2h36m long with 2 audio tracks. I thing that it has the same going as for Lucky Luke as for audio, but I was out so when
I came back, it was done completely. I include the LOG too. But everything seems OK , I didn't check every minutes of it yet.
Is it normal that the DVD have only 3 VOB of 1.048Gb + 1 of .495gb. Shouldn't it be more near the end like 4.4G.
Thanks very much for the Doc, very readable.
You're the best.
Dan -
Hey Dan,
thanks for the detailed reports, this is very helpful...
I believe you discovered at least 1 serious bug for video conversion (it is the second file, it should have been encoded at 23.976 fps with pulldown, but the framerate was hard converted to 29.97 instead. And this confused the size calculation completely. Maybe because the source was detected as having variable frame rate which is impossible for DVD compliant MPEG2), and probably another one for audio. It's a little late for me now, I am too tired to write anything useful right now, but I'll get back to you tomorrow. And I think that MrC will have a good look at your log files, too.
And thanks for your kind words, much appreciated...
Cheers
manolito -
Sorry for the order of the photos, I did send them in order.
Here's another view of the same file. I wrote directly on it this time.
What about for Lucky Luke and the 3 windows ?
Thanks -
-
OK, I did take the time to analyze the logs for your two conversions, and I believe I have a pretty good understanding of what happened...
The MediaInfo information about your source files does not point to any problems. Sure you cannot rule out that DVDFab created some broken VOB files, but to me it does not look like DVDFab is the problem.
I believe you discovered two bugs in AVStoDVD. The first bug lies in the audio conversion routine. In your settings you have selected to use ffmpeg instead of Wavi + Aften if the resulting WAV file is > 4 GB. For both of your source files this is the case (see the Wavi console window). So the Wavi + Aften routine should not have been used in the first place. AVStoDVD falls back to use ffmpeg if Wavi + Aften results in an error, so no real damage is done except wasting some time.
For the first conversion (Lucky Luke) I can explain why AVStoDVD did not detect that the WAV file would be too big. The duration is under 2 hours, and a 16 bit 6-ch WAV file of this duration would be smaller than 4 GB. But for some reason the LAV audio source filter decided to output a 24 bit WAV file which is bigger. In the LAV audio filter setup all bit depths are enabled by default, and the "best" format will be used automatically.
For the second file (HP Goblet) I have no explanation why A2D did not use ffmpeg immediately for audio conversion. At a duration of 2 and a half hours even a 16 bit 6-ch WAV file will be > 4GB.
The second bug is much more serious, it only affects the second conversion (HP Goblet). The source file has these properties:
Detecting a variable frame rate is not correct for an MPEG2 video source.Info: MPEG-2 Video - 5365 kbps - 720x480 - DAR 4:3 - 23.976 fps (VFR) - Progressive (2:3 Pulldown) - 2:37:04 hours - 282424 frames
Quote from Mr. Donald Graft:
I do not know if the VFR detection is just cosmetic or if it is the cause of the following error. For this source format AVStoDVD should have reencoded the video at the source framerate of 23.976 fps and then should have created pulldown flags.MPEG2 video does not support VFR (other than small changes using repeat flags)
Instead it hard-converted the framerate to 29.97 fps, but then still applied pulldown. The pulldown routine had no effect at all because source fps and target fps were identical. But the target duration was recalculated to be 3 hours 16 minutes which of course is completely wrong.
So as a result you got a DVD structure where the bitrate was much lower than necessary, and the framerate conversion to 29.97 also wasted quality because more frames were encoded than necessary.Code:Title 1 output Video duration (02:37:03) is shorter than expected duration (03:16:19)
Looks like some work for MrC. I do not know if this bug is a recent regression or if it has been there for some time. Whatever, I am again glad that I live in PAL country...
Cheers
manolito -
@djdan
wow! the mkv containing Harry Potter has a DVD ripped mpeg2 stream apparently encoded in VFR (Variable Frame Rate)! You have found a new video gender!
And the DAR (Display Aspect Ratio) is 4:3! Definitively there were something wrong during the DVDFab -> MakeMKV process.
As suggested by manolito, you can skip the DVDFab step and rip the DVD directly with MakeMKV. At least you will remove one variable.
About the audio warning, I suggest you to keep the audio as it is, without re-encoding it. Just leave the 'Preferences'/'Audio'/'Keep DVD compliant audio' option ON. Re-encoding the original DVD audio track can be useful only if you want to alter the volume, apply a delay or downgrade the original AC3 (e.g. lowering the bitrate or decreasing the channels).
@manolito
thanks for taking the lead in these last days. I had a brief vacation w/o a decent access to Internet. Your advises have been excellent as usual.
Bye -
Well, "bug" is probably a big word in these cases... I would say "how to improve the 3rd party software flaws handling"... BTW... semantics...Originally Posted by manolito
Good finding. Now we have to understand what has triggered LAV Filters to output the WAV file with a 24 bit resolution. I would avoid to use ffmpeg any time there is a multichannel source track lasting more than 1 hour...Originally Posted by manolito
Actually from that log file, the ffmpeg routine was immediately used. The warning message is related to the estimated output time not matching with the real output time.Originally Posted by manolito
Yes, the VFR false reading is the culprit. Just a couple of code lines to correct the extimated output time routine and avoid the message about the wrong video and audio output duration. I agree that VFR pulled down mpeg2 source should not exist, but if they would ever exist, the framerate conversion would be "hard".Originally Posted by manolito
Open to discussion, as always.
Bye -
I have another one (Meet the Fockers) that have the sound "10 sec" after the video, really 10 sec.
So I will go pick up again the 10 DVDs and use MakeMkv instead of DvdFab as source.
And I will see if there's a difference. I did try to adjust the sound with the trick of Manolito but when
I approach 0.0 sec, in the Preview title output the synch jump back elsewhere. At around "-.120" I'm close
but as soon as I go lower, it goes very bad. It's a non sense since it should be around -10 Sec, not in MS.
I even do a Video_ts with -11 (-11000) in avisynch and the sound is around +10 ahead anyway.
Anyway I will redo everything with the MakeMkv instead of DvdFab, and see if it's help.
I include some photos of it (Meet the Fockers) in case you'd like to look at it.
P.S. If you like me to do some settings before I try again then let me know.
Thanks -
@djdan
A 10 sec audio delay is just insane, I've never come across something llike this. You should really get rid of DVDFab, I had a lot of different issues with it some years ago. I then switched to AnyDVD and never looked back. And so far MakeMKV has also been very reliable for me.
So I agree, discard all the rips you made using DVDFab and redo the ripping with MakeMKV. I am confident that your sync problems will disappear...
Cheers
manolito -
@ MrC
Looks like LAV always uses the highest bit depth which the hardware allows. AviSynth itself will automatically downconvert the bit depth if an AviSynth audio filter requires a lower bit depth. (Applying the SSRC filter to resample audio to 48 kHz is enough to trigger a conversion to 16 bit.)Originally Posted by _MrC_
It should not have anything to do with the source properties, because compressed audio does not have a bit depth (I learned this from tebasuna).
Possible remedies:
Since you already adjust the LAV settings at runtime, you could disable 32 bit and 24 bit output dynamically (at a slight cost of quality).
Or you could add the "-readtoeof 1" parameter to the Aften command line each and every time (makes the progress indicator inaccurate).
(Or tell people to use my Wavi_Mod plugin... )
BTW I recently had some problems with the plugin when LAV output was 24 bit and I was using DynamicAudioNormalizer. For some obscure reason DynamicAudioNormalizer does accept 24 bit input from a file, but not from STDIN. For STDIN the stream must be either 16 bit or 32 bit. So I had to modify the DynNorm routine to always convert the input to 16 bit.
Originally Posted by _MrC_
Yes, the VFR false reading is the culprit. Just a couple of code lines to correct the extimated output time routine and avoid the message about the wrong video and audio output duration. I agree that VFR pulled down mpeg2 source should not exist, but if they would ever exist, the framerate conversion would be "hard".
Open to discussion, as always.
Bye
This is something I do not understand. If the source is detected as VFR then DirectShowSource opens the source with the "convertfps=true" parameter. According to the AviSynth documentation this parameter converts a VFR source to CFR by dropping or repeating frames. This means that AviSynth will serve a pure CFR clip to the encoder. Why must the framerate conversion be "hard" in this case? Is there any reason why pulldown would not work?
In any case since VFR Mpeg2 video does not exist, I believe that AVStoDVD should always ignore the VFR flag for MPEG2. If an MPEG2 stream is detected as VFR, it can only be due to a faulty third party software.
Cheers
manolitoLast edited by manolito; 18th Jun 2015 at 10:00.
-
Just found an older post by Gavino which explains this behavior:Originally Posted by manolito
So AVStoDVD uses AviSynth through the VfW interface?SSRC() returns float audio.
If Avisynth is being used through the VfW interface, this is converted to 16 bit as VfW does not support float.
Add ConvertAudioTo24Bit() to the end of your script to force retention of 24 bits.
Tested it with a short Youtube clip with 44.1 kHz AAC audio. The LAV audio status window reports 32 bit float for input and output, Wavi detects 16 bit integer. This confirms Gavino's post.
Cheers
manolito -
I've been using AVStoDVD for years and am very happy with it.
One issue I have is the way it keeps popping to the front every step of the process. If I start something encoding, and then pop on netflix to watch something while it runs, it won't stay in the background. Every time a new stage of the encoding starts, the program jumps up on top of everything and requires me to re-minimize it, interrupting my movie (or whatever else I happen to be doing.)
Anything I can do to force it to stay minimized? -
Hi EmileB,
have you tried this setting (under "Preferences") ?
Cheers
manolito -
Well, my friend, you are doing the most "R" part of AVStoDVD "R&D" in these days...Originally Posted by manolito
Looks like LAV always uses the highest bit depth which the hardware allows. AviSynth itself will automatically downconvert the bit depth if an AviSynth audio filter requires a lower bit depth. (Applying the SSRC filter to resample audio to 48 kHz is enough to trigger a conversion to 16 bit.)
It should not have anything to do with the source properties, because compressed audio does not have a bit depth (I learned this from tebasuna).
Possible remedies:
Since you already adjust the LAV settings at runtime, you could disable 32 bit and 24 bit output dynamically (at a slight cost of quality).
Or you could add the "-readtoeof 1" parameter to the Aften command line each and every time (makes the progress indicator inaccurate).
(Or tell people to use my Wavi_Mod plugin... )
Since A2D is already using SSRC/ResampleAudio to make audio rate conversion, I would use the following rationale:
- if SSRC is selected -> not a problem
- if ResampleAudio is selected -> add in advance ConvertAudioTo16bit to make sure that ResampleAudio output a 16bit stream
- if none (i.e. source track is already 48 kHz) -> force SSRC(48000)
That scenario should work also when other audio source filters are selected instead of DSS.
Only if AVISource/WAVSource are selected.Originally Posted by manolito
Because we have to consider that other video source filter may be used instead of DSS.Originally Posted by manolito
I agree. A2D can easily fix this discrepancy.Originally Posted by manolito
Bye -
Hi MrC,
thanks for appreciating my modest efforts (retired folks like me do have a lot of time...)
I agree that this rationale would work, but I do have some reservations:Originally Posted by _MrC_
1. Will forcing SSRC(48000) on a clip which already has a sample rate of 48k do nothing at all, or will it actually resample the clip from 48K to 48K? Might be a bad waste of time.
2. Wouldn't it be useful to generally agree on 24 bit integer as intermediate format? I remember a while ago when I published a small AAC to AC3 conversion tool that tebasuna literally pushed me to use a 24 bit intermediate WAV file for quality reasons.
The only source filter which could get in the way is ffvideosource (DGDecode always delivers CFR). And this could easily be overcome by using fpsnum / fpsden in the parameter list.Originally Posted by _MrC_
From the ffms2 manual:
Since the final resulting video will always be CFR the conversion could just as well be done at the source filter stage instead of a hard fps conversion stage.int fpsnum = -1, int fpsden = 1
Forces a given (constant) framerate, expressed as a rational number where fpsnum is the numerator and fpsden is the denominator. Used for VFR to CFR conversion, as it will make FFVideoSource drop or duplicate frames to convert VFR to CFR if fpsnum is greater than 0. Setting fpsnum to a number less than or equal to zero means no frames will be dropped or duplicated.
Cheers
manolito -
I have a strange issue. I have some vcd videos. Im trying to make to dvd using the program. The Program sees it as 4:3. But after the disc is made it plays as a wide screen video. The videos are all 4:30 ratio. I tried telling avstodvd to use ratio 1.33 but it didn't help. I'm using windows 7 64 bit. Heres the text of one of the videos. if needed.
General
Complete name : N:\american.juniors.s01e07.songs.of.1969-vcd-bacco-xmv.mpg
Format : MPEG-PS
File size : 412 MiB
Duration : 41mn 18s
Overall bit rate : 1 395 Kbps
Video
ID : 224 (0xE0)
Format : MPEG Video
Format version : Version 1
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : Variable
Duration : 41mn 18s
Bit rate : 1 150 Kbps
Width : 352 pixels
Height : 240 pixels
Display aspect ratio : 4:3
Frame rate : 29.970 fps
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.454
Time code of first frame : 00:00:00:00
Time code source : Group of pictures header
GOP, Open/Closed : Open
Stream size : 338 MiB (82%)
Audio
ID : 192 (0xC0)
Format : MPEG Audio
Format version : Version 1
Format profile : Layer 2
Duration : 41mn 18s
Bit rate mode : Constant
Bit rate : 224 Kbps
Channel(s) : 2 channels
Sampling rate : 44.1 KHz
Compression mode : Lossy
Stream size : 66.2 MiB (16%) -
Hi Wizard23,
just a wild guess:
Forcing a DAR of 1.33 is just one thing, did you also specify a video aspect ratio of 4:3 under "View/Edit Title settings -> Video"?
Otherwise please post your A2D log file, and maybe upload a short sample of your source file...
Cheers
manolito -
I don't see that option that you put view/edit title setting. I only imported one video to test until I can get the program to let it keep at 4:3 ratio. Heres the log file if this helps.
-
This looks like a player configuration issue to me...
The encoded video file has a 4:3 aspect ratio:
And the muxing parameters also specify 4:3OUTPUT VIDEO INFO: MPEG-2 Video - 6175 kbps - 352x240 - DAR 4:3 - 29.97 fps - Progressive (TFF) - 41:19 minutes - 74294 frames
The resulting DVD should play as 4:3 unless some player settings override the aspect ratio of the input. Did you just play it using a software player, or did you actually burn a DVD and play it in a hardware DVD player?-vidmode 4:3
BTW your log shows that you have ffdshow and LAV Filters installed at the same time. This means asking for trouble. I recommend to uninstall ffdshow and Haaali splitter, then install the current version 0.65 of LAVFilters. Additionally you should go to "Codecs -> Preferred DirectShow Codecs Setup" and make sure that LAV is selected for all video and audio formats.
Cheers
manolito -
I test the dvd result on my computer using vlc media player before I burn to disk. I need both ffdshow installed I need ffdshow for me to capture ac3 5.1 audio from my directv genie hd dvr. And updating lav filters ain't a option. I use bd rebuilder and it told me not to update LAV Filters otherwise ill get sync issues.
Quote
Visit Homepage
Similar Threads
-
AVANTI - FFmpeg/Avisynth GUI (support thread).
By Chris K in forum Video ConversionReplies: 1189Last Post: 12th Jun 2017, 12:39 -
TEncoder 4.0.0 - Multithreaded GUI for FFMpeg and Mencoder (Support thread)
By ozok in forum Video ConversionReplies: 104Last Post: 4th Jun 2014, 10:10 -
Hybrid [x264/XViD - MKV/MP4] Converter Support Thread
By Bonie81 in forum Video ConversionReplies: 6Last Post: 8th Jan 2013, 03:53 -
AVStoDVD 2.4.0
By Hoser Rob in forum Authoring (DVD)Replies: 0Last Post: 30th May 2011, 20:37 -
Start product support thread?
By midders in forum FeedbackReplies: 2Last Post: 4th Aug 2009, 14:15