You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for the #43 improvement.
This improvement is really helpful especially for the purpose of IVTC 30fps to 25fps.
Let me mention an idea that I hope will be more useful this time.
Thank you for your consideration.
1. I want to specify an ovr file that exceeds the number of frames in the video.
If the time of each episode of a series in a common cycle is different, we need to prepare an ovr file for each episode.
Since this is a waste of resources, it would be nice if we could prepare only one ovr file for the longest episode time.
2. I want it to be acceptable if the end frame ends in the middle of the cycle range.
When splitting with Trim, if the number of end frames is less than the number of Cycles, TDecimate will generate an error, so the Trim specification must be changed to extend the range to include frames that are not needed.
It would be nice to have more flexibility if this could be avoided.
Example)
Number of video frames: 5,300
Trim(0,5372)
# Originally, Trim(0,5329) should be specified, but it is necessary to specify 73 frames more because the number of cycles is not enough for the range of cycles and an error occurs.
# I would like to be able to specify it as Trim(0,5329).
v1=Trim(0,1790).TDecimate(mode=0,cycleR=33,cycle=199,ovr="1.txt") #,display=true,displayDecimation=199,displayOpt=6)
v2=Trim(1791,0).TDecimate(mode=0,cycleR=594,cycle=3582,ovr="2.txt") #,display=true,displayDecimation=199,displayOpt=6)
v1++v2
3. I want to be able to specify normal cycles and large cycles without separating them with Trim.
If you want to change the size of the cycles in the middle of a file, you need to split the trim and also need to split the ovr file.
Since this division is a time-consuming process, it would be nice to be able to specify the cycle in the ovr file as well.
# 0,2984 cR 33 c 199 #Can be omitted as it is the same as the initial value.
0,596 +-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++
597,1790 -++++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++
1791,5372 cR 594 c 3582
1791,2984 -+++++-++++++-+++++-+++++++++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++
2985,4178 -+++++-+++++-++++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++
4179,5372 -++-++-+++++-+++++-++++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++
# 5373,0 cR 33 c 199 #Can be omitted as it is the same as the initial value.
5373,6566 -+++++-+++++-+++++-+++++-++++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++
6567,0 -+++++-+++++-+++++-+++++-+++++-++++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++-+++++
The text was updated successfully, but these errors were encountered:
Thank you for the #43 improvement.
This improvement is really helpful especially for the purpose of IVTC 30fps to 25fps.
Let me mention an idea that I hope will be more useful this time.
Thank you for your consideration.
1. I want to specify an ovr file that exceeds the number of frames in the video.
If the time of each episode of a series in a common cycle is different, we need to prepare an ovr file for each episode.
Since this is a waste of resources, it would be nice if we could prepare only one ovr file for the longest episode time.
Example)
Episode 1: Frame counts 4,000
Episode 2: Frame counts 2,500
Episode 3: Frame counts 5,000
Now
ovr file for Episode 1
ovr file for Episode 2
ovr file for Episode 3
If a value exceeding the number of frames in the video is allowed
ovr file for All Episodes
2. I want it to be acceptable if the end frame ends in the middle of the cycle range.
When splitting with Trim, if the number of end frames is less than the number of Cycles, TDecimate will generate an error, so the Trim specification must be changed to extend the range to include frames that are not needed.
It would be nice to have more flexibility if this could be avoided.
Example)
Number of video frames: 5,300
ovr 1.txt
ovr 2.txt
3. I want to be able to specify normal cycles and large cycles without separating them with Trim.
If you want to change the size of the cycles in the middle of a file, you need to split the trim and also need to split the ovr file.
Since this division is a time-consuming process, it would be nice to be able to specify the cycle in the ovr file as well.
Now
ovr 1.txt
ovr 2.txt
ovr 3.txt
If you can specify cycle in the ovr file
TDecimate(mode=0,cycleR=33,cycle=199,ovr="a.txt") #,display=true,displayDecimation=199,displayOpt=6)ovr a.txt
The text was updated successfully, but these errors were encountered: