06.08.2022, 10:58
Hi Selur,
Thanks for the extensive reply.
I'm going to reply quickly because its late/early here in the USA.
I think there might be some confusion here (maybe on my part). The video output that is being generated by Hybrid is still interleaved, not separated yet it is being tagged as separated. Then, if I used the output file (not the input file) for deinterlacing, it is processed wrong because it is tagged wrong. The progressive output file at that point is unusable. I have no need and see no benefit to have any level of UI/processing control over how the interlace is stored since it's visually identical in the end.
Since, obviously, the interlace storage method is maintained through Hybrid processing and all you're setting is bff/tff, couldn't the tag "group" just be chosen from the source file field storage order and appended to the final tags? This would be your last bullet point to implement, I think. I believe this is how Hybrid treated interlace in general in the past and it worked beautifully. Once again, FFMpeg seems to just "go with the flow" when it comes to the source file storage format. Only the tag needs to be correct...
Does this thread help at all? https://forum.videohelp.com/threads/4029...ost2629750
Alternatively, do you have the your old dev build from April that you had supplied me. That worked well for me for deinterlacing and I didn't back it up...
Please don't! This is one of the only easy-to-use tools that works well with interlace and we (as in the whole world) have 40+ years of analog video sources to archive!
Thanks for the extensive reply.
I'm going to reply quickly because its late/early here in the USA.
Quote:Main issue is the first point: I don't know how saving interlaced content with separated fields could be done with anything other than mkvmerge.
I do not plan to only add this as an advanced mkvmerge option.
I think there might be some confusion here (maybe on my part). The video output that is being generated by Hybrid is still interleaved, not separated yet it is being tagged as separated. Then, if I used the output file (not the input file) for deinterlacing, it is processed wrong because it is tagged wrong. The progressive output file at that point is unusable. I have no need and see no benefit to have any level of UI/processing control over how the interlace is stored since it's visually identical in the end.
Since, obviously, the interlace storage method is maintained through Hybrid processing and all you're setting is bff/tff, couldn't the tag "group" just be chosen from the source file field storage order and appended to the final tags? This would be your last bullet point to implement, I think. I believe this is how Hybrid treated interlace in general in the past and it worked beautifully. Once again, FFMpeg seems to just "go with the flow" when it comes to the source file storage format. Only the tag needs to be correct...
Does this thread help at all? https://forum.videohelp.com/threads/4029...ost2629750
Quote:Nor have I ever encountered that anyone used it for formats that are newer than MPEG-2, which is why Hybrid doesn't use it.Unfortunately, this is the way Blackmagic chose to handle interlaced captures... It's quite common in the archival scene, not in any consumer formats.
Alternatively, do you have the your old dev build from April that you had supplied me. That worked well for me for deinterlacing and I didn't back it up...
Quote:Ps.: the more I have to deal with interlaced output the more I think about dropping the whole thing since it seems to pointless. *gig*
Please don't! This is one of the only easy-to-use tools that works well with interlace and we (as in the whole world) have 40+ years of analog video sources to archive!