softworkz

## Fixing up Durations I have now applied the suggested duration fixup as follows: ```c ff_mutex_lock(&s->mutex); ass_process_chunk(s->track, ass_line, strlen(ass_line), start_time, duration); if (s->render_latest_only && s->track->n_events > 1) { const int64_t...

It's not that much of a problem when there are drawbacks, as it's not the default behavior. By default, the overlay_textsubs filter is using libass in full effect, just like...

Also: I think for all cases where this is needed we can safely assume that the events are arriving - in chronological order and - with monotonically increasing readorder values

> > It's not that much of a problem when there are drawbacks [with modifying `event->Duration`], as it's not the default behavior. > > Since you were stressing the need...

> The most “universal” would be the ability to freely modify anything, including event text and styles at all times. But I'd say handling that (with an easy API and...

> Thus, to be able to decide which API-additions would be feasible and work (reasonably) well with/for existing real-world scenarios, we first need to know what those existing real-world conditions...

I ran into the same issue. It turned out that the reason was that` options.identifiersPrefix` needs a different value for each file you are obfuscating. Also see here: https://github.com/javascript-obfuscator/javascript-obfuscator/issues/568 In...

> Does the stream actually play? Yes, it plays fine and MPV player updates the duration nicely. > As far as I remember, we were bumping the duration property every...

> A live stream by definition does not have a duration Well - philosophically rather not, but there is a duration, which is the total range of available segments in...

For illustration - it's about the blue range on the timeline.