View Full Version : Fast or slow motion for the speed
ToiletDuck
1st March 2003, 09:24
I'm ripping movies that have both fast action scenes and slow scenes. Why does divx ask which one and Xvid not? Is there anyway to get around this. I heard that you can make a movie with divx at all high speed setting then do the exact file at all low speed setting then take the best out of both. Is that possible? Does that work any?
Duck
Acaila
1st March 2003, 09:48
You're getting a few things confused here (and confusing me along with it :)).
I'm ripping movies that have both fast action scenes and slow scenes. Why does divx ask which one and Xvid not?I'm not sure if you're talking about DivX 3.11 or DivX 5 here, because the other part of your post talks about DivX 3.11 for sure.
If you're talking about DivX 5 here, then what you mean is the "performance/quality" setting. What that does is determine the motion estimation accuracy. XviD has the exact same thing but it's called "Motion Search Precision". Faster means less accurate, slower means more accurate.
I heard that you can make a movie with divx at all high speed setting then do the exact file at all low speed setting then take the best out of both. Is that possible? Does that work any?
That only works with DivX 3.11 because it has both a fast motion codec and a low motion codec. But in reality there's no reason to use the fast motion codec, because the low motion codec can do everything the other can do only better.
ToiletDuck
1st March 2003, 10:29
using divx 5.0.3pro, doing two pass, on the second pass on the first tab there is an option for bitrate modulation. It gives me three options. High-motion|Constant quality|Low-Motion. So i was assuming that by moving this slider to High it would be like doing fast motion on divx 3.11 and moving it to low would be like using Low motion on divx 3.11. Am I just reading this option wrong? So far i ahve only used constant quality.
Duck
Acaila
1st March 2003, 10:59
That's for curve compression. Setting it to high-motion gives a bias to high motion frames. I.e. It will make high motion scenes look better at the expense of low motion scenes. Setting it to low does the opposite. Setting it to constant quality scales each frame type equally and so will give you more constant quality throughout the movie.
RMCF
1st March 2003, 16:10
I am doing a movie now:
First Pass
N Pass = Modulation -0.15 (towards high motion)
N Pass = Modulation +0.05 (toward low motion)
N Pass = Modulation 0
N Pass = Modulation + 0.15
The reason I did this, is because I was unhappy with the low motion scenes after putting -0.15 at the beginning.
Is it okay to change so much?
ToiletDuck
1st March 2003, 21:12
Acaila isn't that basically the same thing then as high and low pass?
What do you recommend doing?
ToiletDuck
2nd March 2003, 00:58
bump
Acaila
2nd March 2003, 01:15
No that's not the same thing, because the DivX 3.11 fast motion codec has a quantizer limit. It can't encode in low quantizers, I believe it can encode something like 5-31 not sure what the exact range is. This means that the maximum quality you can attain with the fast motion codec is always worse than the max quality you can encode with the low motion codec.
But all that is beside the point, because this is the DivX 5 forum.
What DivX 5 does is increase the relative importance of either fast or low motion scenes based on what you set it at, and increase the bitrate for that type. It doesn't limit the quantizers of any scene type.
Personally I would keep it at constant quality, but I recommend testing all three settings on something like a chapter (with mixed content) and decide for yourself what looks best.
Ps. Please don't bump a thread four hours after the last post. It won't give you an answer any faster. Only bump if it has been pushed off the page.
Acaila
2nd March 2003, 01:20
@RMCF
I've actually never tried nor ever heard of anyone who changed the curve compression with n-pass setting between the various passes, so I have no idea if it's good or bad.
My gut says changing it so often won't help you in any way, it will only make it that much longer before an optimal bitstream is found. But that's just a guess.
Xethos
4th March 2003, 05:15
i'd encode both and use a thingy (from divk-digest) to combine them.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.