![]() ![]() View FFmpeg last command log so you can modify and re-run recent commands on the command line Saves per project cut segments to project file Timeline zoom and frame/keyframe jumping for cutting around keyframes Optionally include original timestamps in image file namesĪpply a per-file timecode offset (and auto load timecode from file)Įdit file metadata, per-track metadata and per-track dispositionĬhange rotation/orientation metadata in videos Take full-resolution snapshots from videos in JPEG/PNG format (low or high quality)Įxport ranges of video frames to images (every nth frame, second, by scene change, best thumbnails)Įxport only from a selected time range (segment) Losslessly remux video/audio into a different container (file) format add music or subtitle track to a video file)Įxtract all tracks from a file (extract video, audio, subtitle, attachments and other tracks from one file into separate files)īatch view for fast multi-file workflow (note: no mass export yet) from the same camera)Ĭombine arbitrary tracks from multiple files (ex. Lossless merge/concatenation of arbitrary files (with identical codecs parameters, e.g. Losslessly rearrange the order of video/audio segments Losslessly cut out parts of video/audio (for cutting away commercials etc.) Cutting audio like that is crude, feels random, and annoys me to no end.īut, again, it seems to be made with video in mind, and it seems to be just a happy coincidence that it can edit audio-only files too.Lossless cutting of most video and audio formats But it's just an arbitrary jump from an also arbitrary current position that you have no control over, either. It'd be something if the 60fps granularity was an absolute alignment from the start of the file. What's the point in having milisecond granularity if you have no control over it? It's just there, teasing you xD The closest to any sanity is that the cursor keys allow for full 1s steps, but, of course, it's still just an offset from the current position, so you have to go back to the start of the file and advance from there second by second until your reach the desired full-second aligned cutpoint. it annoys me quite a bit, especially considering how satisfying mp3DirectCut is in that regard. The program obviously has to round the actual cut point to a frame boundary, but you have zero control over that and instead are forced to juggle about with random 16.66666~ms steps counting from the last random point you managed to land on by clicking on the position bar. The part where you can't directly specify cutpoints despite the program giving you the position down to miliseconds and you have to accept random granularity that has no basis on the underlying file just bothers me. The main problem is the lack of any visual cue about the content of the file. Quote from: j7n on 00:23:26 Isn't 60 fps enough granularity given that audio formats offer 38-46 fps? Resuming, I'm looking for a good lossless cutter for these formats, hopefuly one that will approach the quality of mp3DirectCut. You have to use the positionbar and the framestep buttons for everything. Specially aggravating is the fact that you are given a milisecond based timestamp but you can't manually edit those. I assume that, with a video file, it will maintain frame boundary alignment, but I'm not editing video. ![]() Interestingly, if you click in the positionbar, you may reach a postion that's not aligned to these imaginary frame boundaries, and if you use the framestep buttons from that non-aligned position, it advances the equivalent of 1 frame from that position. When fed with audio-only, it seems to assume a 60Hz framerate judging by to the rounded up 0.016666~ second steps that it allows. The GUI is really meant for video, and, while, being based on FFmpeg, it also supports audio-only files, the position granularity seems to be meant for framesteps, which is not too good for audio. ![]() The problem is that the interface is terrible for cutting audio. So far I've been using LosslessCut, which does the job, at least in the technical aspect: That is, it cuts the file correctly as far as I can tell. MP3 is well covered by the excelent mp3DirectCut, which marks the standard I'm after, with it's nice visual editor. I'm looking for a good lossless cutter with suppor for the popular lossy audio codecs, mainly Opus, Vorbis, and AAC. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |