search

mifi / lossless-cut

The swiss army knife of lossless video/audio editing
https://losslesscut.app/
GNU General Public License v2.0
28.23k stars 1.37k forks source link

📱 Mobile version of LosslessCut (Android/iOS) #818

Open mifi opened 3 years ago

mifi commented 3 years ago

This has been suggested a few times. #419 #479

Porting LosslessCut to mobile

tl;dr: It's not possible to simply port LosslessCut to Android or iOS. And the UI is very desktop-specific (keyboard shortcuts etc) which wouldn’t work well on a small touch device.

Also re-implementing all existing functionality on mobile would be a huge task, so it would probably be a subset of functionality.

Arguments against:

Arguments for:

LosslessCut Mini

It's possible to make a new app for Android or iOS with a subset of features, like:

If you would like to see such a LosslessCut mini mobile app, what is your most needed use case and which functionality do you need? Please reply below 👇

If I were to make one, I would probably use react-native and ffmpeg.

LosslessCut mobile companion

A alternative suggested by someone is to make a lite version of LosslessCut to run on phones, that lets you select cutpoints and then save the project files to the PC version of LosslessCut for the final export.

mattack1 commented 3 years ago

AFAIK, the trim on iOS is just like in Quicktime Player -- only ONE section. LosslessCut obviously lets you save multiple chunks of a recording.

mifi commented 3 years ago

Yea you can do multiple sections, by choosing "Save as a new video" every time, then going back to the original video and trim again. It works but it's slightly clunky.

jonas99g commented 2 years ago

There is Lossless Video Cutter for android. But lossless-cut has more features.

Is it possible to run losslesscut in aarch64 linux? Can it be built or does it require x86_64 emulation?

mifi commented 2 years ago

It may be possible to build it for aarch64, but it also requires ffmpeg for that architecture. Not something I'm going to prioritize, because the losslesscut UI is not really suited for mobile also. But you're welcome to try :)

zenmanic commented 2 years ago

My solution right now has been to use another ios video editor, export to Final cut xml, then import into Lossless Cut. Sort of clunky but very doable especially if you're very use to the other ios app. Currently using LumaFusion with paid extra. The extra cost is the final cut export.

cunlem commented 2 years ago

It may be possible to build it for aarch64, but it also requires ffmpeg for that architecture.

FWIW fully functional ffmpeg build can be installed inside Termux environment from the repo maintained by the authors. It's possible to integrate third-party apps with Termux with the use of intents

mifi commented 2 years ago

in recent versions of llc, you can select your own external ffmpeg. losslesscut still needs to be build for aarch64. I think electron supports that now, but losslesscut needs to upgrade its electron which is a big rewrite #714

FernandoFuvio commented 1 year ago

My solution right now has been to use another ios video editor, export to Final cut xml, then import into Lossless Cut. Sort of clunky but very doable especially if you're very use to the other ios app. Currently using LumaFusion with paid extra. The extra cost is the final cut export.

How did you make it work the fcpxml from LumaFusion on LLC? I exported it on my iPhone and it’s giving me an error in LLC: “invalid attributes”.

FernandoFuvio commented 1 year ago

My solution right now has been to use another ios video editor, export to Final cut xml, then import into Lossless Cut. Sort of clunky but very doable especially if you're very use to the other ios app. Currently using LumaFusion with paid extra. The extra cost is the final cut export.

How did you make it work the fcpxml from LumaFusion on LLC? I exported it on my iPhone and it’s giving me an error in LLC: “invalid attributes”.

After a few hours analyzing the differences between an successful fcpxml export and a failed one, I found out what the problem was.

I noticed that the ones that worked didn't start at the actual start of the file on LumaFusion, and the ones who failed were starting at "0s".

In these cases, the first "spine" entry, had the start time as "0s", and I noticed that the others had "xxxxx/600s".

I just changed the first entry to "0/600s" and it worked perfectly.

darinhouston commented 12 months ago

the iOS trim is more than adequate, but merge is completely absent - merging without transcoding is all I'm after on the phone. Multiple in/out points to trim multiple segments would be great, but merge alone would be a lifesaver. It really needs no UI - using iOS share sheets or a shortcut interface would work fine for simple merge.