3 ms·
At 30fps, which is not high, that would mean chunks of less than 7 seconds. Doable but highly impractical to say the least.
by prmoustache 3y ago
At 30fps, which is not high, that would mean chunks of less than 7 seconds. Doable but highly impractical to say the least.
- rowanG077 3y agoYou will probably have to have some overhang of time to get the state space to match enough to minimize flicker in between fragments.
- bredren 3y agoPerhaps a second pass that focuses on smoothing out the frames where the clips are joined.
- bmicraft 3y agoYou could probably mitigate this by using overlapping clips and fading between them. Pretty crude but could be close to unnoticeable, depending on how unstable the technique actually is.
- IanCal 3y ago7s is pretty alright, I've seen HLS chunks of 6 seconds, that's pretty common I think.
- _puk 3y ago6s was adopted as the "standard" by Apple [0]. For live streaming it's pretty common to see 2 or 3 seconds (reduces broadcast delay, but with some caveats). 0: https://dev.to/100mslive/introduction-to-low-latency-streaming-with-hls-27f1#:~:text=Reducing%20the%20default%20segment%20size https://dev.to/100mslive/introduction-to-low-latency-streami...
- sp332 3y agoMaybe they could do a lower framerate and then use a different AI tool to interpolate something smoother.
- littlestymaar 3y agoIt's not so much that it would be impratical (video streaming, like HLS or MPEG-Dash, requires to chunk videos in pieces of roughly this size) but you'd lose the inter-frame consistency at segments boundaries, and I suspect the resulting video would be flickering at the transition. It could work for TV or movies if done properly at the scene transition time though.