![]() Each will contain the script I used as well as the output video. As there’s 36 videos I’ll be splitting it over nine blog posts over nine days, with the last being posted on 28th March 2020. With that all said let’s jump into sharing the results. This could be down to the source material, and I’d be interested to see experiments involving datamoshed videos. It’s more predictable and controllable, but the noise and melty movement it creates, especially some of the ones using bilat me_mode, remind me of the bloom effect in datamoshing. This is good news if you don’t want to have to carry around a powerhouse laptop all the time.Īll of this reminds me a bit of datamoshing. Just compare 026_mc_mode=obmc_me_mode=bilat_me=epzs.mp4 to 008_mc_mode=obmc_me_mode=bidir_me=epzs.mp4 and you’ll see what I mean.įor a video of this length nearly all of the scripts (except for those using esa) took between 30 seconds and 1 minute to complete, and that’s on machines with and without a GPU. 3 - Rotate by 90 degrees clockwise and flip vertically. 2 - Rotate by 90 degrees counter-clockwise. 0 - Rotate by 90 degrees counter-clockwise and flip vertically (default value). Using bilat me_mode produces the most chaotic results by far. ffmpeg -i input.mp4 -vf 'transpose1' output.mp4 The available parameters for transpose are 0, 1, 2, and 3. I did consider killing the script but for completeness I let it run. My first observation is that the esa me_mode takes frikkin ages to complete! Each video using this me_mode took about four hours to process. If there’s any problems with getting FFmpeg on your machine it’s best that you contact the developers for assistance. #Ffmpeg options motion estimation mac#I don’t have a Windows or Mac machine, and haven’t used other Linux distributions so can’t test these scripts in those conditions. ![]() These videos were created using FFmpeg 7:4.1.4-1build2, installed from the Ubuntu repositories, on a Dell XPS 15 (2017 edition) with 16GB memory, a i7 processor and an Nvidia GeForce GTK 1050 graphics card, all running on Ubuntu 19.10 using proprietary drivers. I could have of course documented what happens when all of the processing options are changed but that would result in me having to make hundreds of videos! The options that were changed were the mc_mode (motion compensation mode), me_mode (motion estimation mode), and me (motion estimation algorithm). ![]() #Ffmpeg options motion estimation update#In part two of March’s Development Update I explained why I set scd to none and search_param to 400. The base script used for each video is: ffmpeg -i cat_rainbow_original.mp4 -filter:v "setpts=62.5*PTS,minterpolate='fps=25:mb_size=16:search_param=400:vsbmc=0:scd=none: ![]() I’ve slowed it down so that you can see exactly what’s in the video, but the original can be downloaded here. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |