Quote:
Originally Posted by lrhorer
Evidently so, since it seems you are too impatient to follow the thread.
I never asked or suggested I needed any help with MakeMKV. Frankly, it is insulting that anyone suggest I would. I wouldn't mention it, however, except that it underlines the issue at hand. There are tons of useless, trivial volumes of information on perfectly obvious matters, but almost nothing I have been able to find on important or obscure ones.
|
Really? This seemed like a request for help with MakeMKV, which I why I linked that particular tutorial.
Quote:
Originally Posted by lrhorer
Yes, but that can be problematical:
As you can see, there are three good candidates, all 22.1GB each. Which one is the "right" one? That 750M title with 39 titles is an interesting suspect, too. An SD version, perhaps? Do the three (or four) largest files need to be spliced together? Without some form of preview, that's all hard to determine.
--snip-- |
Quote:
Originally Posted by lrhorer
I never asked to be spoon fed anything. All I am requesting is a clear, concise documentation set. Although they hate doing documentation, and although they are often terrible at it, it is the responsibility of any developer to see to it such documentation exists.
Oh, and just BTW, spoon-feeding is what any GUI, and MeGUI in particular, is about, which is one of the many reasons why I hate GUIs.
|
The tone of your post where you post multiple images interlaced with many questions is what makes it seem like you are asking to be spoon fed.
Quote:
Originally Posted by lrhorer
Point me to the documentation and I will gladly do so. I am all for trial and error, but in this case trial and error are not a practical means for a learning path. With each test iteration taking at least a day and often several days, it could easily take years to discover the things one needs to know, given the large number of pathways handled by the program.
Ultimately I may, since Handbrake is producing generally superior results at this point, except when played on the THD. Wouldn't it be a shame, however, to abandon what is ultimately a better solution merely because the author failed to provide decent documentation? (Actually, my preference would be ffmpeg, and if I can figure out what pyTivo doesn't like about the output from my ffmpeg string, I will edit it and use that.)
I'm not jumping down anyone's throat. The shortfalls of the MeGUI documentation or of the program itself are certainly not jcthorne's fault. Certainly my hat is off to him for his assistance.
|
I went out on Sunday and purchased my first blu-ray disc so that I could play around with one. I found
this guide that made it pretty clear what the process should be to get from blu-ray to a single mkv with main movie only. Like jcthorne, I use AnyDVD HD.
Now, depending on the disc and what you want your final form to be, you might be very close to finished. If the disc was already encoded with AVC, you might have been able to use Yamb or mp4box (command line) to mux the video/audio into a mp4 container. If you want to transcode the audio to AAC or reduce the resolution to 720p or hardcode subtitles, etc, then you need to do more. I did want to transcode to 720p, transcode to AAC and hardcode the subtitles. I already know how to use avisynth, so that part was pretty straight forward.
I use a batch file like this:
Code:
:LOOP
FOR %%A IN (*.mkv) DO (
IF NOT EXIST "%%~nA.avs" ((
ECHO DGSource("%%~nA.dgi"^)
ECHO Spline16resize(1280,720^)
ECHO TextSub("%%~nA.srt"^)
) > "%%~nA.avs"
) )
SHIFT
@if %1X==X goto END
@goto LOOP
:END
setlocal
set mp4box="C:\Program Files (x86)\GPAC\mp4box.exe"
set x264="c:\encode\x264.exe"
set ffmpeg="c:\encode\ffmpeg.exe"
set mkvextract="C:\Program Files (x86)\MKVToolNix\mkvextract.exe"
set dgindex="C:\encode\dgdecnv2042\dgindexnv.exe"
FOR %%A IN (*.mkv) DO (
%dgindex% -i %%A -o %%~nA.dgi -h -e
%ffmpeg% -i %%A -acodec libfaac -ab 128k -ac 2 %%~nA.aac
%x264% --crf 21 --tune film --keyint 48 --sar 1:1 -o I:\temp\%%~nA.264 %%~nA.avs 2>%%~nA.log
%mp4box% -add "I:\temp\%%~nA.264":fps=23.976 -add "%%~nA.aac" "I:\temp\%%~nA.mp4"
)
DGIndexNV is an indexer for a decoder that uses Nvidia GPU for decoding the video to frameserve to avisynth.
The particular ffmpeg version I use still has libfaac enabled for AAC encoding. You can also use eac3to with the Nero encoding tools.
I think x264 is known to you and there are a lot of locations for information on its settings. I can point you to some if you don't know the best place to find them.
mp4box is the command line backbone to the Yamb GUI. Documentation for mp4box can be found
here.
For the subtitles, I simply downloaded a copy off of the nets, but I am sure there are ways to take the .sup subtitles and convert them to srt or simply render them in the video with a
mod'd version of vsfilter.
I don't have time at the moment to get into avisynth scripting, but the script that I used only requires dgdecnv and vsfilter aside from the base avisynth installation.
And this:
