203
LosslessCut, the Swiss army knife for lossless video and audio editing (ubunlog.com)
submitted 3 months ago by aprnu@feddit.ch to c/opensource@lemmy.ml
27 comments fedilink hide all child comments
all 29 comments
sorted by: hot top controversial new old
[-] aBundleOfFerrets@sh.itjust.works 69 points 3 months ago

The swiss army knife for lossless video and audio editing is ffmpeg

[-] aleph@lemm.ee 83 points 3 months ago

And LosslessCut is a ffmpeg frontend, so that checks out.

[-] brbposting@sh.itjust.works 29 points 3 months ago

Neat, love me a GUI

[-] Shyfer@ttrpg.network 6 points 3 months ago

Oh hell ya. I won't have to Google to find the specific ffmpeg command I need anymore with this?

[-] xapr@lemmy.sdf.org 8 points 3 months ago

I've been using LosslessCut for a few years now. It's really easy and smooth. It does exactly what I want and what the name says, and I couldn't ask for more.

[-] JustUseMint@lemmy.world 6 points 3 months ago

I'll never need this but I want to hoard all FOSS software regardless

[-] theamigan@lemmy.dynatron.me 4 points 3 months ago* (last edited 3 months ago)

lol@typescript and appImage. Yuck. Just use mpv to find cutpoints and man ffmpeg

[-] ryannathans@aussie.zone 9 points 3 months ago

What did ffplay do to you

[-] theamigan@lemmy.dynatron.me 3 points 3 months ago

Nothing, I just never think to use it since mpv has more features for general use.

[-] mranderson17@infosec.pub 2 points 3 months ago
[-] PipedLinkBot@feddit.rocks 3 points 3 months ago

Here is an alternative Piped link(s):

https://piped.video/watch?v=9kaIXkImCAM

Piped is a privacy-respecting open-source alternative frontend to YouTube.

I'm open-source; check me out at GitHub.

[-] nutbutter@discuss.tchncs.de 4 points 3 months ago

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.

[-] eceforge@iusearchlinux.fyi 13 points 3 months ago

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.

[-] ryannathans@aussie.zone 2 points 3 months ago* (last edited 3 months ago)

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

[-] mudeth@lemmy.ca 3 points 3 months ago

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.

[-] ReversalHatchery@beehaw.org 1 points 3 months ago* (last edited 3 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.

[-] ryannathans@aussie.zone 0 points 3 months ago

Lossless codecs can be decoded and reencoded without effect

[-] mudeth@lemmy.ca 2 points 3 months ago

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

[-] Hadriscus@lemm.ee 1 points 3 months ago

This has always bothered me, I suspect it's the same underlying reason most video players can't do reverse frame-by-frame. But Quicktime allowed it twenty years ago, so it's possible. I suppose you'd have to actually decode the entire keyframe interval and use the resulting frames as new "baked-in" keyframes so to say. I suppose that's more or less what djv and other frame checkers do under the hood. But I don't know what I'm talking about so...

[-] gila@lemm.ee 2 points 3 months ago* (last edited 3 months ago)

That's what I've always assumed it does since back when quicktime player barely even ran on my PC yet for timeline operations it was significantly more responsive than WMP/MPC.

For Losslesscut I just get around this by encoding my input from source using keyint=n:scenecut=0 in ffmpeg where n is a manually set keyframe interval.

So e.g. if my expected cut occurs on a frame that occurs at t+10 seconds of footage, n can be the same as the fps and then there'll always be a keyframe exactly at timestamp 00:00:01, 00:00:02 and so on. I can then open it in losslesscut and easily snap to the frame I want and make the cut losslessly.

Yeah the first encode generally means a lossy transcode by the time I get to my final video but being realistic that'd be a part of my workflow either way and this way it's less

[-] MangoPenguin@lemmy.blahaj.zone 1 points 3 months ago

That's due to the source codec using keyframes, you can only cut without re-encode on those specific points.

[-] nutbutter@discuss.tchncs.de 1 points 3 months ago

They allow re-encoding, but that is in experimental state. It never works for me.

[-] fmstrat@lemmy.nowsci.com 4 points 3 months ago

Or Shotcut, which can trim and so much more?

I mean, they all use ffmpeg.

[-] gila@lemm.ee 1 points 3 months ago* (last edited 3 months ago)

It's a slightly different use case, I default to Losslesscut and switch to Shotcut when I need a vfilter or if I'm just generally willing to concede to making a lossy cut.

Shotcut is way more flexible but I can make a quick clip in Losslesscut with probably 1/3 the number of user effort/inputs. Let alone trying to remember every ffmpeg parameter under the sun just to get consistent usable output

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

Open Source

28971 readers
424 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 4 years ago
MODERATORS
Cloak@lemmy.ml
kevincox@lemmy.ml
CrypticCoffee@lemmy.ml
Lettuceeatlettuce@lemmy.ml