You could reencode and make sure to not deinterlace and output progressive content (set 'Filtering->(De-)Interlace/Telecine->Overwrite scan type to' to 'progressive').
---
Bobbing does not create duplicate frames unless the source is telecined or was created using another pulldown variant.
So bobbing 29.97 fps interlaced content will leave you with 59.95 different frames using sRestore on that would simply throw out frames until the desired frame rate is met.
Cu Selur
Ps.: you could also just leave the stream as it is, H.264 hardware decoders which support mbaff should not do anything strange to the content on decoding and decode the content as progressive.
---
Bobbing does not create duplicate frames unless the source is telecined or was created using another pulldown variant.
So bobbing 29.97 fps interlaced content will leave you with 59.95 different frames using sRestore on that would simply throw out frames until the desired frame rate is met.
Cu Selur
Ps.: you could also just leave the stream as it is, H.264 hardware decoders which support mbaff should not do anything strange to the content on decoding and decode the content as progressive.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.