Tweet
After implementing the mentioned line in MSP's ini file (thank you very much, Doc !), I noticed the Motion Search indicator in the Advance Video tab. However, this setting doesn't seem to "stick", as it returns to it's default value each time to leave the Mpeg dialogue. Other settings, like the "Encoder Quality" (which influences the Motion Search vector) are kept at the same value that were set the previous time you entered them through the "Advance" tab.
Question : +does it work+ ? And if so, how exactly ? If I understand what little info I found on this vector, a lower value should result in better results in the movements in the encoded file, no ? Either I'm blind, or it makes no difference in my case. I'm not that impressed with the encoding so far in terms of quality : near static images and such are fine, highly defined and good in colour, but in videos with all-screen movement like a zoom-in or out, I see FAR too much encoding noise to my taste. And before you ask, I've encoded the same footage using other encoders, and the results looked _a lot better_ then. (Hardware DV500 encoder, not nearly the best around but it still does this in a better way at lower data speeds, tmpeg same story : looks better, less image noise caused by the movement).
I've used a great number of different settings during my tests so far, but in the end I ended my testing at an Encoding Quality setting of 45, a Motion Search of 4 and a VBR datarate of 8000, speculating that this _should be sufficient to get a better result than I'm seeing now_. Note that I'm in the dark about the impact of the "Noise Sensitivity" setting. Can I expect hardware-like results from this software, or is that not in the realms of possiblity using the build-in Mpeg encoder, and can I only expect better results using a frameserver and a multipass capable encoder ?
Anyone wanting to comment, or who's got access to better documentation than I have been able to find, please share the info you have.
Thank you in Advance,
Kris
Question : +does it work+ ? And if so, how exactly ? If I understand what little info I found on this vector, a lower value should result in better results in the movements in the encoded file, no ? Either I'm blind, or it makes no difference in my case. I'm not that impressed with the encoding so far in terms of quality : near static images and such are fine, highly defined and good in colour, but in videos with all-screen movement like a zoom-in or out, I see FAR too much encoding noise to my taste. And before you ask, I've encoded the same footage using other encoders, and the results looked _a lot better_ then. (Hardware DV500 encoder, not nearly the best around but it still does this in a better way at lower data speeds, tmpeg same story : looks better, less image noise caused by the movement).
I've used a great number of different settings during my tests so far, but in the end I ended my testing at an Encoding Quality setting of 45, a Motion Search of 4 and a VBR datarate of 8000, speculating that this _should be sufficient to get a better result than I'm seeing now_. Note that I'm in the dark about the impact of the "Noise Sensitivity" setting. Can I expect hardware-like results from this software, or is that not in the realms of possiblity using the build-in Mpeg encoder, and can I only expect better results using a frameserver and a multipass capable encoder ?
Anyone wanting to comment, or who's got access to better documentation than I have been able to find, please share the info you have.
Thank you in Advance,
Kris
Comment