[请教]第一次做BDrip，有些问题需要请教大家

引用

最初由 upyzl 发布
此外，这些m2ts貌似都是24fps cfr，但为什么网上的BDrip都是23.976fps cfr？这是做了什么处理？

引用

最初由 ssnake 发布
首先你说的两个Index都不是AviSynth的Function，我不知道你是怎么操作的，无法分析。另外提问前把版本、脚本等等信息写全是基本。

ffms的用法：http://www.nmm-hd.org/doc/index.php?title=FFmpegSource2&variant=zh-hans
（感谢liti姐姐翻译= =）

ffms方便主要体现在你不用"事先"跑一遍index上。另外就是Frame Accurate。

BD可以是24.000fps的。ef那个FD说不定也是24.000fps（游戏的OPED好像就是），没做过不清楚。

Resize一般Lanczos3/4或者Spline36/64。

另外，你的要求直接x264就够了，x264自带ffms和resize。

引用

LoadPlugin("D:\Program Files\MeGUI\tools\dgavcindex\DGAVCDecode.dll")
AVCSource("E:\00009.dga")

引用

LoadPlugin("D:\Program Files\MeGUI\tools\ffms\ffms2.dll")
FFVideoSource("E:\00009.m2ts",colorspace="YV12")

引用

最初由 ssnake 发布
BD可以是24.000fps的。ef那个FD说不定也是24.000fps（游戏的OPED好像就是），没做过不清楚。

引用

最初由 halsboss 发布

[QUOTE]
Originally Posted by Blue_MiSfit
DSS2 works very well - it's an improved DirectShowSource. I use it for my BluRay encodes all the time

引用

Originally Posted by Blue_MiSfit
... then using DSS2(...) to load the MKV. DSS2 is part of avss.dll, which can be found in your installation directory for haali media splitter.

引用

DSS2 is Haali's implementation of Directshowsource. It has the advantage of being frame-accurate, but only supports VFR by converting it to CFR; at least that was the case when I tried it last time, it might have changed.
and
Well if this is going to be turned into a general DSS2 thread... the syntax is:

复制代码

1. dss2(string infile, float fps)

i.e.

复制代码

1. loadplugin("avss.dll")
2. dss2("X:/test.mkv",fps=23.976)

Unlike the original DSS, it does not support loading audio. It also always converts VFR to CFR; i.e. it acts like the original DSS with convertfps=true does.
also
Avisource uses VfW codecs and the VfW framework only. Think of it like VirtualDub but in Avisynth. As long as the AVI in question doesn't have any particularly funky hacks, it will always have frame-accurate seeking.
Directshowsource uses Directshow codecs and is hence the Avisynth equivalent of Windows Media Player. It's usually NOT frame-accurate, but it does support VFR, kind of; either through converting to CFR (convertfps=true) or by just reading all frames and ignoring timecodes.
DSS2 is Haali's implementation of Directshowsource. It has the advantage of being frame-accurate, but only supports VFR by converting it to CFR; at least that was the case when I tried it last time, it might have changed.

引用

Originally Posted by Zwitterion
There are some problems with it, however (M2TS files from Blu-ray, using Haali's splitter and ffdshow in the graph):
- artifacts when seeking in AVC video. They disappear after a few frames.
- When seeking in VC-1 video, sometimes it shows two or three duplicate frames before continuing in the stream.
- It can't load graph files (This isn't a bug, but it'd be a nice feature).
So you can't rely on perfect picture quality in the first few frames after seeking. But at least you know that it is the right frame unlike with DSS, where sometimes the whole stream gets shifted by a few frames.

引用

Originally Posted by neuron2
It just means you have seeked to an open GOP. That's the price you pay for frame accuracy. If you suppress the orphaned frames, then you haven't really seeked to the frame number requested. This is why the DG tools back off by one GOP and decode all the frames necessary to correctly decode the seeked-to frame.

引用

Originally Posted by neuron2
(DSS2)... relies on the stream having completely accurate and continuous timestamps throughout the file, and of course raw streams don't have timestamps. Just clarifying the different niches for DSS2() versus DG. I think the SPS/PPS injection heuristics are a bit better in the DG tools also, which can be relevant for some streams.