On 14/06/2024 12:44, Martin Storsjö wrote:
On Fri, 14 Jun 2024, Gyan Doshi wrote:
On 2024-06-14 02:18 am, Martin Storsjö wrote:
On Thu, 13 Jun 2024, Gyan Doshi wrote:
On 2024-06-13 06:20 pm, Martin Storsjö wrote:
I'd otherwise want to push this, but I'm not entirely satisfied
with the option name quite yet. I'm pondering if we should call it
"hybrid_fragmented" - any opinions, Dennis or Timo?
How about `resilient_mode` or `recoverable`?
I agree that the how is secondary.
Those are good suggestions as well - but I think I prefer
"hybrid_fragmented" still.
In theory, I guess one could implement resilient writing in a number
of different ways, whereas the hybrid fragmented/non-fragmented only
is one.
So with a couple other voices agreeing with the name
"hybrid_fragmented", I'll post a new patch with the option in that
form - hopefully you don't object to it.
The term hybrid is not applicable here. The fragmented state is
transient during writing and contingent in the finished artifact
depending on how the writing process concluded.
Hybrid implies both modes available e.g.. a hybrid vehicle can use
both types of energy sources. The artifact here will be one _or_ the
other.
Sure, the file itself is either or, but the process of writing will have
utilized both. TBH, I don't see it as such a black-or-white thing.
What do the others who have chimed in on the thread think, compared to
calling it "recoverable" or "resilient_mode"?
I don't have a super strong opinion on it, but out of the options
provided, I'd prefer the hybrid_ one, since there's a good chance it'll
become an established term now that OBS presents it quite publicly visible.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
