Quote:
Originally Posted by Danette
I agree that it would be much better to have ‘clean’ progressive streams, but all decimation processes that I’ve tried on these sped-up episodes are leaving too much stutter.
|
Try with mode=2. And you have to find out the correct factor/pseudo framerate. We had two sources, one progressive with German sound, but very bad picture. So we were able to find the correct factor for decimating by aligning. When found, then decimating worked pretty well with rather no stuttering left. Without second source it may be rather hard to find the factor, I fear.
Quote:
|
The vast majority of TV series I encounter respond nicely to IVTC, but there are some hybrid videos (I prefer to call them mangled) that respond better to QTGMC.
|
If you use QTGMC for hybrid video you get the best result for the interlaced native 29.97fps parts. The pulldowned portions will still stutter. The only way to manage hybrid sources - if you want a progressive final result - is to handle 29.97 and pulldowned 23.976 scenes separately. We adapted the 29.97 sections by deinterlacing with QTGMC and afterwards converting with motion flow (we used Alchemist, but the converter some made here is also very good, sometimes better than Alchemist, even better than some A.I. approaches I tested).
Quote:
|
Note that I actually slowed the speed down, so speed issues with QTGMC are moot. Additionally, the AudioSpeed function does seem to provide the correct pitch. At least, to my ear.
|
You kept pitch. What I tried to say was, that the algorithms they used for the SOURCE surely did NOT keep pitch. So the scenes that are more accellerated will be higher than the scenes less accellerated. Without handling each seperately by using different factors the sound will never be 100% ok. Maybe the differences are not high, then you are lucky. If not ther may be quarter tones higher or lower at transitions, especially when there is music...
