this post was submitted on 14 Mar 2024
205 points (97.2% liked)

Open Source

31122 readers
290 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 8 months ago (10 children)

It is a good tool, but for me it only trims from the keyframes. To trim precisely, it has to re-encode, which, unfortunately, does not work on my machine for some reason. So, I just stick to ffmpeg cli.

[–] [email protected] 13 points 8 months ago (7 children)

I suppose that makes sense given that information is encoded as a series of key frames interspersed by 'I-frames" that simply encode the delta to the previous key-frame when using most compressed video algorithms. So cutting in-between key-frames doesn't really make sense since the I-frame would no longer have anything to reference it's delta to.

[–] [email protected] 2 points 8 months ago* (last edited 8 months ago) (4 children)

Except if it's lossless so there's no harm in reencoding to accurately clip files

[–] [email protected] 3 points 8 months ago (2 children)

You're confusing cause and effect. It's lossless because it cuts at keyframes and does not re-encode.

If it did what you're suggesting it wouldn't be lossless anymore.

[–] [email protected] 1 points 7 months ago* (last edited 7 months ago)

I think they were talking about a special kind of media file, that is not compressed but instead stored losslessly. I think H264 can do that too.

[–] [email protected] 0 points 8 months ago (1 children)

Lossless codecs can be decoded and reencoded without effect

[–] [email protected] 2 points 7 months ago

LosslessCut doesn't only use lossless codecs. It losslessly cuts video files encoded in lossy codecs.

load more comments (1 replies)
load more comments (3 replies)
load more comments (5 replies)