I asked about it in one of the beta threads, and they said they’re treating the issue discussed in this thread as a separate item and are looking into it as well.
Appreciate the clarity! Hopefully the bwdif update is a sign that deinterlacing is something that’s finally being actively worked on 
Thanks for the heads up! I can’t believe what I just read… after so many years!!! It’s happening indeed!
Looks like I may finally update from the 7.x version I am still running.
Hope this works out for everyone who has been patiently waiting for so long.
Very nice to see it’s FINALLY well and truly planned! Hopefully it’s not too far away, very anxious to test this out with both fully interlaced and mixed video content. Will be very exciting to finally have Infuse be a definitive player for NAS setups.
I’m not actually that hopeful that there will be an ideal solution for mixed video content.
As it stands, Linear deinterlacing is the best solution for mixed content (especially content that is primarily progressive), as it doesn’t add nasty shimmering artifacts to progressive frames in the way that Yadif does.
If we simply get a Yadif x2/Bob deinterlacer, it still might not be great for mixed content. Hopefully some kind of Linear x2/Bob deinterlacer is also in the pipeline.
Moreover, the current Auto setting seems to apply only Yadif if the video is flagged as interlaced, so it doesn’t seem to be able to detect progressive frames or telecined content. In an ideal world, the Auto setting would be a complete solution, capable of detecting 50i/60i interlaced, progressive and telecined content on-the-fly. Whether that’s even possible is another matter.
After all this time I expect nothing less than this. I have been waiting a long time for Infuse to perfect de-interlacing. The auto setting should choose the most appropriate method based on the source material.
Well it’s certainly possible to do that but it does rely on the content being correctly identified in every single GOP as to whether it is progressive, interlaced, or telecined.
I’ve certainly dealt with a lot of video content for which that is not the case - it’s actually pretty common, caused by people who have absolutely NFI what they are doing when they randomly transcode stuff and I have to visually identify every segment by eye before applying the correct treatment to each 
Well it’s certainly possible to do that but it does rely on the content being correctly identified in every single GOP as to whether it is progressive, interlaced, or telecined.
I’ve certainly dealt with a lot of video content for which that is not the case - it’s actually pretty common, caused by people who have absolutely NFI what they are doing when they randomly transcode stuff and I have to visually identify every segment by eye before applying the correct treatment to each
I know what you mean - there are some badly transcoded discs out there.
I’ve got one Blu-ray concert disc where it has clearly been filmed in 24p, yet the video is a weird mix of 3:2 telecine and fully progressive with 1 out of every 5 frames repeated. Choose one and stick with it FFS! Or better yet, produce a proper 24p disc.
If I use the remux of this disc in Infuse, it will just see that the video is flagged as interlaced and deinterlace the whole lot, which isn’t really correct for the content.
Does the current BWDIF deinterlacer currently use send_frame? And the ‘in-progress’ part is to enable send_field?
That is correct.
So I know this is already tagged as planned, but throwing my support behind it as well.
Some of my sports content comes from interlaced broadcast sources. And having them deinterlace to 50p would be so much better than them playing back at 25fps (25fps is a huge downgrade for sports content).
My current workaround it to deinterlace in Handbrake to 50p before adding to my library. But this is quite cumbersome.