(05-04-2013, 05:06 PM)billyash Wrote: I didn't mean to ask or anything. I just give idea and ask question, if dev accept it and they working on it . I call it bonus, but if they won't ,I won't persistance cos im none here. Beside I need answer wich could enrich my knowledge
PS: people getting fool if they stop asking question
I know, what other reason I'm answering? But in the end is that lack (for now) of understanding on the complexities involved what makes things looking simpler they are.
You see, developing a deinterlace method means a proper project by its own merits. And if one is found which would be better performing and having greater quality than the already existent, this could be ever monetary gain, with cause for patent and attracting the attention of that media producers. One could get rich!!! ... the problem is exactly it's far from simple finding such method if one exist at all.
I mean, people developing those methods had specific goals in mind. They don't mean one is "better" than the other, they are specific to attend needs.
One method is meant to be easy on performance, allowing real time conversion at cost of quality, another method focus on quality without worrying about performance, this last is not meant to real time presentation most of the times with current hardware, the process at slow time at almost perfect quality but very slowly and them having that quality at normal speed at "run time".
One method could scan the frames and intelligently correcting every detail but doing it in a image reconstruction method which could take seconds or even more to render a single frame.
So, one method is better for real time conversion, another is meant for high quality and cares not for the slowness. Just that the two things are mutually exclusive, then very few people are getting rich nowadays with new deinterlace methods, because those in existence are already optimized for what they are meant.
Besides, what you told is what Blend already does. Edit: Ahh, I see what you mean, no way billy, the information is already coded at 30 FPS (60 fields), increasing the pace they come or are processed would not change this. Where a meaningful attempt to increase the actual FPS would be like that which VirginKLM proposed to do with Kingdom hearts II (iirc), which involves patching "that specific game" to increase the original FPS pace... and without surprise has sync issues and in a way is meant more to making videos than to actually play in current hardware at correct "speed" (not FPS... SPEED).
Same speed + greater FPS = smooth
Same FPS + smaller speed = Slugg!!! (that's what happens with too much VU cycle stealing).