search

mifi / lossless-cut

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

Split timeline by byte size #1219

Open mifi opened 2 years ago

mifi commented 2 years ago

Source-File for example 4,5 GB, I will export this in 5 files with 1GB for each file --> 4 x 1GB + 1 x 0,5GB.

There is already a feature of cutting into even time slices. The problem with cutting based on size is that we need to translate size into time values in order to divide it. We could estimate by dividing input file total size by the duration in seconds, but because of VBR (unstable bitrate) throughout the video, it will not be accurate. Meaning some files could become 1.1GB, others 0.9GB, etc

iG8R commented 3 months ago

Really looking forward to this feature from 2022.

mifi commented 2 months ago

unfortunately there are no thumbs up on this feature request. I usually prioritise issues that are more popular

iG8R commented 2 months ago

Is it possible to emphasis in your posts that thumbs up give priority to published issues, since not all users understand that it is this parameter that affects the speed of implementation of this or that feature?

iG8R commented 2 months ago

As you can see, out of at least 4 people who mentioned this feature in their requests above, only 1 gave it a thumbs up.

mifi commented 2 months ago

i already mention it in the pinned issue here: #691

For features you want implemented, leave a thumbs up on the first post 👍

not sure where else to mention in for people to see it

iG8R commented 2 months ago

Thank you very much for your patience in responding to such requests. People are just not used to the fact that the implementation of features depends on their voice, usually - they come, write about the problem and forget about it until the new release.

edmundlaugasson commented 2 months ago

I already started feature request but found current discussion. I can say, that even in case of Avidemux, where is possible to define target file size, this will be larger. E.g. I needed 5 GiB but got 5,3 GiB. Original file was 18 GiB. Then I set 4,7 GiB and got 5 GiB. I had to use Avidemux but wanted to use LosslessCut. If you can achieve 1,1 GiB or 0,9 GiB instead of 1 GiB - this sounds pretty good. We can handle that kind of accuracy and still predict pretty precisely the target size. Also we can undo split and make then correct one. Would also propose to estimate split size already on timeline (where split happen) also in gigabytes or what units are appropriate in exact case. Then we can already see and estimate whether splitted segments are in correct sizes we expect or not. Split is shown as segment - another option is to show segment estimated size. Currently already in segment is shown duration and frames. Estimated export size would be additional then. Some cases Avidemux does not work but LosslessCut does. But due to storage system limitations I have to find a way to use Avidemux in order to achieve target file size. As storage systems have size limitations, we need such kind of feature. If exported file will be larger, we need repeat until we get file size under limited size. When we know accuracy, we will have experience and predict already target file size accuracy and still achieve goal. But at least there would be such feature at all.