Thank you very much, fritsch! Many thanks also wolfgar & smallint for development!
Deinterlacing itself seems to be very fast now, but I still have problems playing various kind of streams whether interlaced or not.
This may or may not be directly related to deinterlacing - but perhaps due to the high frame-rate. And this in return could possibly still be related to field-doubling, or whatever these patches do.
Anyways, every high frame rate whether progressive or double frame-rate interlaced or not, seems to kills a/v syncing or proper video-decoding in some way.
Some experiences on a CuboxTV (=quad-core+1GB RAM):
Ex1:
DVB-streams:
http://www.sendspace.com/filegroup/EC1nu...UTm%2BsMRU
data0001.ts: 1280x720p50 (TV is switching to 50Hz). Many frame skips. Sometimes HDMI disconnects.
data0002.ts: 1920x1080i50 MBAFF (TV is switching to 25Hz). Ok. Double-fr-deinterlacing doesn't look good.
data0003.ts: 1920x1080i50 MBAFF (TV is switching to 25Hz). Plays flawlessly
Another DVB-stream as MKV:
1280x720p50:
https://www.sendspace.com/file/yqbkjr
Video decoding seems to be too slow. Again many frame-skips. TV is at 50Hz. Temporary audio-skipping, some HDMI disconnects.
Ex2:
https://www.sendspace.com/file/uorxs5
1920x1080i60, 29.97fps MBAFF
Audio gets async very fast.
Ex3:
https://www.sendspace.com/file/h3znta
1920x1080i60, 29.97fps interlaced
Audio gets async even faster.
Ex2 & Ex3 are from BR, so at least video should be conforming to standards. Audio was trancoded to flac, though.
While playing the videos, CPU usage is quite low and it doesn't matter much if I activate/deacticate deinterlacing.
If I understand correctly deinterlacing is done after hardware decoding. And before these patches it was quite slow, and sometimes CPUs weren't fast enough.
But should't the chipset at least be capable of decoding 1920x1080i60?