lunaticmoon
10th November 2004, 02:45
Hi, everyone.:)
I have groped for the method of processing Anime of hybrid material in a RMVB creation environment, several months. I write the present conclusion (it is individual).
Conclusion:
If compromise is not allowed, compared with other codecs, it is difficult.
Reason:
It can be considered that several approaches from which it is related with processing of Anime of hybrid material, and shoes differ.(Anime of HM -> RMVB of VFR)
The method is divided into a large frame and following three are it.
A) You use only the function of Producer.
B) You cooperate with Fake VFR technology and use Producer.
C) You make perfect VFR and are crowded manually.
The problem in the present condition of these methods is as follows.
About A): DropDupe goes wrong in order not to bring about a result with the desirable action. In the present condition, interlace-related pre-filter has the too low performance of combing detection and removal, and goes wrong. Good VFR is not obtained as a result.
About b): The present condition and the Fake VFR tool which detects 24/30/60fps and corresponds individually automatically do not exist. If compromise is allowed, although processing of 24/30fps is possible at DecombVFR, there is also much incorrect detection strictly. At a detection system, it is the maximum major candidate. Although there is Auto Filed Shift Plug-in (AFS for AVIUTL/Avisynth), output plug-in does not correspond to AVI2.0, and cannot breathe all out for a middle output by HuffYUV in video of 25-min.
About C): It is the method of carrying out file division of Anime of hybrid material for every fps, processing by Producer by fps specification individually, and finally adhering by rmeditor. Although it is a steadiest and troublesome method, there is no compromise in this method.
However, there are two problems.
One is that the discerning eye which recognizes correctly which portion is which fps is indispensable. Another is a thing which rmeditor has gone up [ the claim that there is lack of a frame at the time of combination ] and to require.
Appendix:
I have submitted now in HelixCommunity. If there is progress by bug-report, there may be some which are solved. :confused:
Since MARUMO's exavi output plug-in is a correspondence schedule at AVI2.0, if it corresponds, there may be progress. :cool:
Thanks, everyone. :)
I have groped for the method of processing Anime of hybrid material in a RMVB creation environment, several months. I write the present conclusion (it is individual).
Conclusion:
If compromise is not allowed, compared with other codecs, it is difficult.
Reason:
It can be considered that several approaches from which it is related with processing of Anime of hybrid material, and shoes differ.(Anime of HM -> RMVB of VFR)
The method is divided into a large frame and following three are it.
A) You use only the function of Producer.
B) You cooperate with Fake VFR technology and use Producer.
C) You make perfect VFR and are crowded manually.
The problem in the present condition of these methods is as follows.
About A): DropDupe goes wrong in order not to bring about a result with the desirable action. In the present condition, interlace-related pre-filter has the too low performance of combing detection and removal, and goes wrong. Good VFR is not obtained as a result.
About b): The present condition and the Fake VFR tool which detects 24/30/60fps and corresponds individually automatically do not exist. If compromise is allowed, although processing of 24/30fps is possible at DecombVFR, there is also much incorrect detection strictly. At a detection system, it is the maximum major candidate. Although there is Auto Filed Shift Plug-in (AFS for AVIUTL/Avisynth), output plug-in does not correspond to AVI2.0, and cannot breathe all out for a middle output by HuffYUV in video of 25-min.
About C): It is the method of carrying out file division of Anime of hybrid material for every fps, processing by Producer by fps specification individually, and finally adhering by rmeditor. Although it is a steadiest and troublesome method, there is no compromise in this method.
However, there are two problems.
One is that the discerning eye which recognizes correctly which portion is which fps is indispensable. Another is a thing which rmeditor has gone up [ the claim that there is lack of a frame at the time of combination ] and to require.
Appendix:
I have submitted now in HelixCommunity. If there is progress by bug-report, there may be some which are solved. :confused:
Since MARUMO's exavi output plug-in is a correspondence schedule at AVI2.0, if it corresponds, there may be progress. :cool:
Thanks, everyone. :)