![]() ![]() It took 60 seconds to save the video while the optimization part (skipped on Windows) took slightly less than two minutes (~115 seconds). This is interesting, I checked the speed when saving a ~4 GiB mp4 file (H.264 FullHD video + AC3 audio) in copy mode with the MP4 muxer using a build from the current git master on Linux running on my pretty obsolete hardware (an AMD dual core which was mid-range 8 years ago, source video and target video on different HDDs): the average fps was 1476. In copy mode, codecs are not involved in any way. Encode priority on both versions set at High.įirst I thought it was a problem with my old hardware, but the same behaviour can be observed on my brand new laptop with a Core i5 8250U quad core CPU, 8 gigs RAM and 256 gig SSD.Īm I doing something wrong in the settings? Please help, I like the new version but the slowdown of file saves is very noticeable and if I cannot find a solution I will have to revert to 2.6.11 again. The old 2.6.11 does so at the speed of around 1400 fps, the newest 2.7.1 at around 560 fps for the same files, a 60% drop in speed, which is very noticeable - the same file in old version saves in around 30-40 seconds, the new version saves it in 2 minutes. I usually need only to trim some mp4 clips and concatinate/save them as one file. ![]() I don't know what happened after that release, if the codecs got slower or what, but each subsequent release was slower than 2.6.11 in saving files, that is why I always reverted to it after trying out new versions periodically. ![]() ![]() I have been using version 2.6.11 since it came out. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |