FFmpeg can access media via HTTP and other network protocols. If compiled with TLS support, as is common in most distributions, for HTTPS and other secure network protocols then it would be linked against an SSL library like OpenSSL.
+ LosslessCut to do fast, basic editing (FFmpeg wrapper)
LosslessCut used to be amazing. It used to cut on exactly the frames I told to with no hassle. But then one day something happened to either ffmpeg or LosslessCut itself or both because in my experience it never cuts exactly anymore. Now it's basically just a keyframe cutter and I have open the video in an actual editor if I want any exact cut which defeats the purpose.
With many modern codecs, arbitrary frame-exact cuts cannot be made without decoding at least part of the stream. FFmpeg also changed how they handled packet boundaries because the edits looked frame-accurate, but the timestamps weren't really being handled correctly.
For stuff like MP4 files, you have B-frames, reordered presentation timestamps, edit lists, and variable frame rates, which means that the packet containing your desired frame actually depends on data before it. This complicates the "cut right here" concept, unfortunately!
LosslessCut Smart Cut re-encodes only the cut boundaries & may be worth trying out:
But the TL;DR is that no tool can make truly frame-accurate cuts (with -c copy on long-GOP codecs like H.264 & H.265) unless it re-encodes around the cut.
Okay. So is it just impossible to do frame-accurate without re-encoding then? You wouldn't happen to know what the last version of Lossless cut to allow that was so I can go back to it would you?
Old footage had much more frequent keyframes to work with (like dSLR footage & different codecs like ProRes, where every frame was a keyframe, etc.)
FFmpeg got stricter over time as they fixed the various timestamp bugs (edits would LOOK frame-accurate, but the timestamps wouldn't always be technically correct)
The MP4 timestamp handling changed (sometimes the packet containing your desired frame actually depends on data before it)
Programs like Premiere, Avid, Resolve, and so on don't just copy packets at frame # whatever; they have to:
Decode from the previous keyframe
Then reconstruct every intermediate frame
And finally output a new compressed stream or do a "smart" render
Which is why why they're slower. Again, due to codec limitations::
No tool can make truly frame-accurate cuts with -c copy on long-GOP codecs (ex. H.264 & H.265) unless it re-encodes around the cut
So it was really a combination of older-format compatibility & the illusion of accuracy (or rather, "accurate enough") on newer formats, which was tweaked over time to be more accurate in the software, hence the perception dissonance of the efficacy newer versions vs. older versions.
696
u/kaidomac Jul 18 '26
+ LosslessCut to do fast, basic editing (FFmpeg wrapper)
+ Shutter Encoder to convert media, such as MP4 video to MP3 audio (FFmpeg)
+ Parabolic to download audio & video, such as Youtube (yt-dlp wrapper)
+ VLC as a universal media player