{"id":8790,"date":"2023-09-08T13:12:20","date_gmt":"2023-09-08T12:12:20","guid":{"rendered":"https:\/\/andyland.info\/wordpress\/?p=8790"},"modified":"2023-09-08T13:12:22","modified_gmt":"2023-09-08T12:12:22","slug":"use-ffmpeg-to-find-a-possible-loop-in-a-video","status":"publish","type":"post","link":"https:\/\/andyland.info\/wordpress\/use-ffmpeg-to-find-a-possible-loop-in-a-video\/","title":{"rendered":"Use FFmpeg to find a possible loop in a video"},"content":{"rendered":"\n\n\n

As stated an multiple occasions, I am doing live visuals every now and then for various events. Most of my footage is based on shaders<\/a>. In (very) short: These are programs that are executed on your graphics-card and create visuals in real-time instead of playing pre-made videos. Extremely interesting and extremely nerdy. You might want to check out\u00a0https:\/\/glslsandbox.com\/<\/a> to get an idea. However, trying to run shaders on, for example, a Raspberry Pi 4 instead of a top-tier Macbook pro has a huge amount of its very own quirks. Playing videos on an RPI4, however, doesn’t cause too many problems.\u00a0<\/p>\n\n\n\n\n\n\n\n

So I only need to create a video loop of my shaders and … done.<\/p>\n

Well …\u00a0 no. The video below is a typical example of a shader that’s repeating- somewhere. The original video I created out of the shader is 15 seconds in duration. To make things really obvious\u00a0 I created a simple loop with FFmpeg.<\/p>\n\n\n\n

ffmpeg -stream_loop 1 -i video.mov -c copy video-loop.mov<\/code><\/pre>\n\n\n\n
You’ll recognize a noticeable cut at ~15 seconds. Obviously, this cannot be it.<\/p>\n\n\n\n
\n