Recherche avancée

Sur d’autres sites (6565)

• FFmpeg matlab error : At least one output file must be specified ? [closed]

  3 mars, par as moh

  I'm trying to get I frames from a video using Matlab using this command system(sprintf('ffmpeg -i testVid.mp4 -vf "select=eq(pict_type\,I)" -vsync vfr output_%03d.png')); ,but i get this message

  


   ffmpeg version 7.1-full_build-www.gyan.dev Copyright (c) 2000-2024 the FFmpeg developers 
  built with gcc 14.2.0 (Rev1, Built by MSYS2 project) 
  configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma --enable-libsnappy --enable-zlib --enable-librist --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libaribb24 --enable-libaribcaption --enable-libdav1d --enable-libdavs2 --enable-libopenjpeg --enable-libquirc --enable-libuavs3d --enable-libxevd --enable-libzvbi --enable-libqrencode --enable-librav1e --enable-libsvtav1 --enable-libvvenc --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxeve --enable-libxvid --enable-libaom --enable-libjxl --enable-libvpx --enable-mediafoundation --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libharfbuzz --enable-liblensfun --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-dxva2 --enable-d3d11va --enable-d3d12va --enable-ffnvcodec --enable-libvpl --enable-nvdec --enable-nvenc --enable-vaapi --enable-libshaderc --enable-vulkan --enable-libplacebo --enable-opencl --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libcodec2 --enable-libilbc --enable-libgsm --enable-liblc3 --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint 
  libavutil      59. 39.100 / 59. 39.100 
  libavcodec     61. 19.100 / 61. 19.100 
  libavformat    61.  7.100 / 61.  7.100 
  libavdevice    61.  3.100 / 61.  3.100 
  libavfilter    10.  4.100 / 10.  4.100 
  libswscale      8.  3.100 /  8.  3.100 
  libswresample   5.  3.100 /  5.  3.100 
  libpostproc    58.  3.100 / 58.  3.100 
Trailing option(s) found in the command: may be ignored. 
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'testVid.mp4': 
  Metadata: 
    major_brand     : isom 
    minor_version   : 512 
    compatible_brands: isomiso2avc1mp41 
    encoder         : Lavf57.83.100 
  Duration: 00:00:02.02, start: 0.000000, bitrate: 12798 kb/s 
  Stream #0:0[0x1](eng): Video: h264 (Baseline) (avc1 / 0x31637661), yuvj420p(pc, progressive), 1280x720 [SAR 1:1 DAR 16:9], 12662 kb/s, 29.74 fps, 30 tbr, 90k tbn (default) 
      Metadata: 
        handler_name    : VideoHandler 
        vendor_id       : [0][0][0][0] 
  Stream #0:1[0x2](eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 121 kb/s (default) 
      Metadata: 
        handler_name    : SoundHandler 
        vendor_id       : [0][0][0][0] 
At least one output file must be specified 


  


  i searched and tried many cases but i don't know where is the problem, any help please ?

  


• How to measure the performance of a newsletter (or any email) with Matomo

  19 décembre 2017, par InnoCraft

  To be able to grow your business, it is crucial to track all your marketing efforts. This includes all newsletters and emails that you share with people outside of your business. Otherwise, you won’t be able to know which of your daily efforts are yielding results.

  Are you wondering if it is possible to track the performance of an emailing campaign in Matomo (Piwik) efficiently ? Would you like to know if it is technically easy ? No worries, here is a “How to” tutorial showing you how easily you can track an emailing in Matomo properly.

  Different tracking levels for different needs

  There are many things that you may be interested to track, for example :

  

  1. How many users opened your email
  2. How many users interacted with the links in your email
  3. How many users interacted on your website through your email

  Let’s have a look at each of these levels.

  Step 1 – Tracking email and newsletter openings in Matomo

  Tracking email openings requires to add an HTML code to your newsletter. It works through what we call a tracking pixel, a tiny image of 1×1 that is transparent so the user will not be able to see it.
  In order to install it, here is an example of what this code looks like :

  <img src="https://piwik.example.com/piwik.php?idsite=YOUR_PIWIK_WEBSITE_ID&rec=1&bots=1&url=https%3A%2F%2Fexample.com%2Femail-opened%2Fnewsletter_XYZ&action_name=Email%20opened&_rcn=internal%20email%20name&_rck=newsletter_XYZ" style="border:0;” alt="" />

  The Matomo tracking pixel explained

  The above URL is composed of the following URL parameters which are part of our Tracking API :

  • idsite : Corresponds to the ID of the website you would like to track.
  • rec : You need to have rec=1 in order for the request to be actually recorded.
  • bots : Set it to 1 to include all the connections made to this request, bots included.
  • url : corresponds to the URL you would like to display in Matomo (Piwik) every time the email is opened.
  • action_name : This is the page name you would like to be tracked when the email is opened.
  • _rcn : The name you would like to give to your campaign.
  • _rck : The keyword you may like to use in order to summarize the content of your newsletter.

  You may have noticed some special characters here such as “%20”, “%2F”. That’s because the URL is encoded. We strongly recommend you to do so in order for your tracking not to break. Many tools are available on the web in order to encode your URLs such as https://www.urlencoder.org/.

  If you would like to access the previous tracking code easily, keep in mind that you can always find the tracking code generator within the “Matomo admin panel → Tracking code” :

  

  You can find more information about it on our guide at : How do I track how many users open and read my newsletter emails (using a pixel / beacon) ?

  As a result, the information will be pushed as following for any user who opens your email :

  

  To not bias your regular page views on your website with newsletter openings, we recommend tracking newsletter openings into a new website.

  Tracking even more data : the user ID example

  You can go deeper in your URL tracking by inserting other parameters such as the user id if you have this information within your emailing database. One of the main benefit of tracking the User ID is to connect data across multiple devices and browsers for a given user.

  You only need to add the following parameter &uid=XXX where XXX equals the dynamic value of the user ID :

  

  Make sure that UID from your emailing provider is the same as the one used on your website in order for your data to be consistent.

  Important note : some email providers are loading email messages by default which results in an opening even if the user did not actually open the email.

  Step 2 – Measure the clicks within your emailing

  Tracking clicks within an email lets you know with which content readers interacted the most. We recommend tracking all links in all your emails as a campaign, whether it is a newsletter, a custom support email, an email invoice, etc. You might be surprised to see which of your emails lead to conversions and if they don’t, try to tweak those emails, so they might in the future.

  Tracking clicks This works thanks to URL campaign tracking. In order to perform this action, you will need to add Matomo (Piwik) URL parameters to all your existing link URLs :

  • Website URL : for example “www.your-website.com”.
  • Campaign name : for example “pk_campaign=emailing”. Represents the name you would like to give to your campaign.
  • Campaign keyword : for example “pk_keyword=name-of-your-article”. Represents the name you would like to give to your content.
  • Campaign source : for example “pk_source=newsletter”. Represents the name of the referrer.
  • Campaign medium : for example “pk_medium=email”. Represents the type of referrer you are using.
  • Campaign content : for example “pk_content=title”. Represents the type of content.

  You can find more information about campaign url tracking in our “Tracking marketing campaigns with Matomo” guide.

  Here is a sample showing you how you can differentiate some links in a newsletter, all pointing to the same URL :

  

  Once you have added these URL parameters to each of your link, Matomo (Piwik) will clearly indicate the referrer of this specific campaign when a user clicks on a link in the newsletter and visits your website.

  Important note : if you do not track your campaigns, it will result in a bad interpretation of your data within Matomo (Piwik) as you will get webmail services or direct entries as referrer instead of your newsletter campaign.

  Step 3 – Measure emailing performances on your website

  Thanks to Matomo (Piwik) URL campaign parameters, you can now clearly identify the traffic brought through your emailing. You can now specifically isolate users who come from emails by creating a segment :

  

  Once done, you can either have a look at each user specifically through the visitor log report or analyze it as a whole within the rest of the reports.

  You can even measure your return on investment directly if goals have been defined. In order to know more about how to track goals within Matomo (Piwik).

  Did you like this article ?

  If you enjoyed reading this article, do not hesitate to share it around you. Moreover, if there are any topics you would like to write us about in particular, just drop us an email and we will be more than happy to write about it.

  The post How to measure the performance of a newsletter (or any email) with Matomo appeared first on Analytics Platform - Matomo.

• FFmpeg image to video conversion error : [image2] Opening file for reading

  14 février 2018, par user1690179

  I am running ffmpeg on an AWS Lambda instance. The Lambda function takes an input image and transcodes it into a video segment using ffmpeg :

  ffmpeg -loop 1 -i /tmp/photo-SNRUR7ZS13.jpg -c:v libx264 -t 7.00 -pix_fmt yuv420p -vf scale=1280x720 /tmp/output.mp4

  I am seeing inconsistent behavior where sometimes the output video is shorter than the specified duration. This happens inconsistently to random images. The same exact image sometimes renders correctly, and sometimes is cut short.

  This behavior only happens on Lambda. I am not able to replicate this on my local computer, or on a dedicated EC2 instance with the same environment that runs on lambda.

  I noticed that when the output video is short, the ffmpeg log is different. The main difference are repeated [image2 @ 0x4b11140] Opening '/tmp/photo-2HD2Z3UN3W.jpg' for reading lines. See ffmpeg logs below.

  Normal execution with the correct output video length :

      ffmpeg -loop 1 -i /tmp/photo-SNRUR7ZS13.jpg -c:v libx264 -t 7.00 -pix_fmt yuv420p -vf scale=1280x720 /tmp/video-TMB6RNO0EE.mp4
  
  ffmpeg version N-89773-g7fcbebbeaf-static https://johnvansickle.com/ffmpeg/  Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 6.4.0 (Debian 6.4.0-11) 20171206
  
    configuration: --enable-gpl --enable-version3 --enable-static --disable-debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio --cc=gcc-6 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gray --enable-libfribidi --enable-libass --enable-libvmaf --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband --enable-librtmp --enable-libsoxr --enable-libspeex --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libzimg
  
    libavutil      56.  7.100 / 56.  7.100
  
    libavcodec     58.  9.100 / 58.  9.100
  
    libavformat    58.  3.100 / 58.  3.100
  
    libavdevice    58.  0.100 / 58.  0.100
  
    libavfilter     7. 11.101 /  7. 11.101
  
    libswscale      5.  0.101 /  5.  0.101
  
    libswresample   3.  0.101 /  3.  0.101
  
    libpostproc    55.  0.100 / 55.  0.100
  
  Input #0, image2, from '/tmp/photo-SNRUR7ZS13.jpg':
  
    Duration: 00:00:00.04, start: 0.000000, bitrate: 18703 kb/s
  
      Stream #0:0: Video: mjpeg, yuvj444p(pc, bt470bg/unknown/unknown), 687x860 [SAR 200:200 DAR 687:860], 25 fps, 25 tbr, 25 tbn, 25 tbc
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (mjpeg (native) -> h264 (libx264))
  
  Press [q] to stop, [?] for help
  
  [swscaler @ 0x5837900] deprecated pixel format used, make sure you did set range correctly
  
  [libx264 @ 0x51c2340] using SAR=1477/3287
  
  [libx264 @ 0x51c2340] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
  
  [libx264 @ 0x51c2340] profile High, level 3.1
  
  [libx264 @ 0x51c2340] 264 - core 155 r61 b00bcaf - H.264/MPEG-4 AVC codec - Copyleft 2003-2017 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  Output #0, mp4, to '/tmp/video-TMB6RNO0EE.mp4':
  
    Metadata:
  
      encoder         : Lavf58.3.100
  
      Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 6183:13760 DAR 687:860], q=-1--1, 25 fps, 12800 tbn, 25 tbc
  
      Metadata:
  
        encoder         : Lavc58.9.100 libx264
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
  frame=   49 fps=0.0 q=28.0 size=       0kB time=-00:00:00.03 bitrate=N/A speed=N/A    
  
  frame=   69 fps= 66 q=28.0 size=       0kB time=00:00:00.76 bitrate=   0.5kbits/s speed=0.728x    
  
  frame=   89 fps= 57 q=28.0 size=       0kB time=00:00:01.56 bitrate=   0.2kbits/s speed=0.998x    
  
  frame=  109 fps= 53 q=28.0 size=       0kB time=00:00:02.36 bitrate=   0.2kbits/s speed=1.14x    
  
  frame=  129 fps= 50 q=28.0 size=       0kB time=00:00:03.16 bitrate=   0.1kbits/s speed=1.22x    
  
  frame=  148 fps= 48 q=28.0 size=       0kB time=00:00:03.92 bitrate=   0.1kbits/s speed=1.27x    
  
  frame=  168 fps= 47 q=28.0 size=       0kB time=00:00:04.72 bitrate=   0.1kbits/s speed=1.31x    
  
  No more output streams to write to, finishing.
  
  frame=  175 fps= 39 q=-1.0 Lsize=      94kB time=00:00:06.88 bitrate= 112.2kbits/s speed=1.54x    
  
  video:91kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 3.161261%
  
  Input file #0 (/tmp/photo-SNRUR7ZS13.jpg):
  
    Input stream #0:0 (video): 176 packets read (16459168 bytes); 176 frames decoded; 
  
    Total: 176 packets (16459168 bytes) demuxed
  
  Output file #0 (/tmp/video-TMB6RNO0EE.mp4):
  
    Output stream #0:0 (video): 175 frames encoded; 175 packets muxed (93507 bytes); 
  
    Total: 175 packets (93507 bytes) muxed
  
  [libx264 @ 0x51c2340] frame I:1     Avg QP:14.33  size: 73084
  
  [libx264 @ 0x51c2340] frame P:44    Avg QP:14.09  size:   302
  
  [libx264 @ 0x51c2340] frame B:130   Avg QP:23.31  size:    50
  
  [libx264 @ 0x51c2340] consecutive B-frames:  0.6%  1.1%  0.0% 98.3%
  
  [libx264 @ 0x51c2340] mb I  I16..4:  3.3% 84.5% 12.1%
  
  [libx264 @ 0x51c2340] mb P  I16..4:  0.0%  0.0%  0.0%  P16..4:  3.2%  0.1%  0.0%  0.0%  0.0%    skip:96.7%
  
  [libx264 @ 0x51c2340] mb B  I16..4:  0.0%  0.0%  0.0%  B16..8:  0.4%  0.0%  0.0%  direct: 0.0%  skip:99.6%  L0:31.2% L1:68.8% BI: 0.0%
  
  [libx264 @ 0x51c2340] 8x8 transform intra:84.5% inter:98.8%
  
  [libx264 @ 0x51c2340] coded y,uvDC,uvAC intra: 95.1% 63.9% 51.6% inter: 0.1% 0.6% 0.0%
  
  [libx264 @ 0x51c2340] i16 v,h,dc,p: 26% 21%  4% 49%
  
  [libx264 @ 0x51c2340] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 20% 27% 21%  3%  5%  6%  6%  4%  9%
  
  [libx264 @ 0x51c2340] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 23% 36% 10%  4%  7%  5%  6%  2%  6%
  
  [libx264 @ 0x51c2340] i8c dc,h,v,p: 51% 29% 16%  4%
  
  [libx264 @ 0x51c2340] Weighted P-Frames: Y:0.0% UV:0.0%
  
  [libx264 @ 0x51c2340] ref P L0: 96.5%  0.0%  3.3%  0.2%
  
  [libx264 @ 0x51c2340] ref B L0: 42.4% 57.6%
  
  [libx264 @ 0x51c2340] ref B L1: 97.0%  3.0%
  
  [libx264 @ 0x51c2340] kb/s:106.08

  Log from a short video :

  ffmpeg -framerate 25 -y -loop 1 -i /tmp/photo-2HD2Z3UN3W.jpg -t 15.00 -filter_complex "[0:v]crop=h=ih:w='if(gt(a,16/9),ih*16/9,iw)':y=0:x='if(gt(a,16/9),(ow-iw)/2,0)'[tmp];[tmp]scale=-1:4000,crop=w=iw:h='min(iw*9/16,ih)':x=0:y='0.17*ih-((t/15.00)*min(0.17*ih,(ih-oh)/6))',trim=duration=15.00[tmp1];[tmp1]zoompan=z='if(lte(pzoom,1.0),1.15,max(1.0,pzoom-0.0005))':x='iw/2-(iw/zoom/2)':y='ih/2-(ih/zoom/2)':d=1,setsar=sar=1:1[animated];[animated]fade=out:st=12.00:d=3.00:c=#000000[animated]" -map "[animated]" -pix_fmt yuv420p -s 1280x720 -y /tmp/video-QB1JCDT021.mp4
  
  ffmpeg version N-89773-g7fcbebbeaf-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2018 the FFmpeg developers
  
  built with gcc 6.4.0 (Debian 6.4.0-11) 20171206
  
  configuration: --enable-gpl --enable-version3 --enable-static --disable-debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio --cc=gcc-6 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gray --enable-libfribidi --enable-libass --enable-libvmaf --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband --enable-librtmp --enable-libsoxr --enable-libspeex --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libzimg
  
  libavutil 56. 7.100 / 56. 7.100
  
  libavcodec 58. 9.100 / 58. 9.100
  
  libavformat 58. 3.100 / 58. 3.100
  
  libavdevice 58. 0.100 / 58. 0.100
  
  libavfilter 7. 11.101 / 7. 11.101
  
  libswscale 5. 0.101 / 5. 0.101
  
  libswresample 3. 0.101 / 3. 0.101
  
  libpostproc 55. 0.100 / 55. 0.100
  
  Input #0, image2, from '/tmp/photo-2HD2Z3UN3W.jpg':
  
  Duration: 00:00:00.04, start: 0.000000, bitrate: 373617 kb/s
  
  Stream #0:0: Video: mjpeg, yuvj444p(pc, bt470bg/unknown/unknown), 1936x2592 [SAR 72:72 DAR 121:162], 25 fps, 25 tbr, 25 tbn, 25 tbc
  
  Stream mapping:
  
  Stream #0:0 (mjpeg) -> crop
  
  fade -> Stream #0:0 (libx264)
  
  Press [q] to stop, [?] for help
  
  [swscaler @ 0x4d63b40] deprecated pixel format used, make sure you did set range correctly
  
  [swscaler @ 0x4df7340] deprecated pixel format used, make sure you did set range correctly
  
  [swscaler @ 0x50e97c0] deprecated pixel format used, make sure you did set range correctly
  
  [swscaler @ 0x50e97c0] Warning: data is not aligned! This can lead to a speed loss
  
  [libx264 @ 0x4b17480] using SAR=1/1
  
  [libx264 @ 0x4b17480] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
  
  [libx264 @ 0x4b17480] profile High, level 3.1
  
  [libx264 @ 0x4b17480] 264 - core 155 r61 b00bcaf - H.264/MPEG-4 AVC codec - Copyleft 2003-2017 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  Output #0, mp4, to '/tmp/video-QB1JCDT021.mp4':
  
  Metadata:
  
  encoder : Lavf58.3.100
  
  Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 25 fps, 12800 tbn, 25 tbc
  
  Metadata:
  
  encoder : Lavc58.9.100 libx264
  
  Side data:
  
  cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
  [swscaler @ 0x5bd0380] deprecated pixel format used, make sure you did set range correctly
  
  debug=1
  
  cur_dts is invalid (this is harmless if it occurs once at the start per stream)
  
  [image2 @ 0x4b11140] Opening '/tmp/photo-2HD2Z3UN3W.jpg' for reading
  
  [AVIOContext @ 0x4b6ecc0] Statistics: 1868086 bytes read, 0 seeks
  
  [mjpeg @ 0x4b14940] marker=d8 avail_size_in_buf=1868084
  
  [mjpeg @ 0x4b14940] marker parser used 0 bytes (0 bits)
  
  [mjpeg @ 0x4b14940] marker=e0 avail_size_in_buf=1868082
  
  [mjpeg @ 0x4b14940] marker parser used 16 bytes (128 bits)
  
  [mjpeg @ 0x4b14940] marker=db avail_size_in_buf=1868064
  
  [mjpeg @ 0x4b14940] index=0
  
  [mjpeg @ 0x4b14940] qscale[0]: 0
  
  [mjpeg @ 0x4b14940] marker parser used 67 bytes (536 bits)
  
  [mjpeg @ 0x4b14940] marker=db avail_size_in_buf=1867995
  
  [mjpeg @ 0x4b14940] index=1
  
  [mjpeg @ 0x4b14940] qscale[1]: 1
  
  [mjpeg @ 0x4b14940] marker parser used 67 bytes (536 bits)
  
  [mjpeg @ 0x4b14940] marker=c0 avail_size_in_buf=1867926
  
  [mjpeg @ 0x4b14940] sof0: picture: 1936x2592
  
  [mjpeg @ 0x4b14940] component 0 1:1 id: 0 quant:0
  
  [mjpeg @ 0x4b14940] component 1 1:1 id: 1 quant:1
  
  [mjpeg @ 0x4b14940] component 2 1:1 id: 2 quant:1
  
  [mjpeg @ 0x4b14940] pix fmt id 11111100
  
  [mjpeg @ 0x4b14940] marker parser used 17 bytes (136 bits)
  
  [mjpeg @ 0x4b14940] marker=c4 avail_size_in_buf=1867907
  
  [mjpeg @ 0x4b14940] class=0 index=0 nb_codes=11
  
  [mjpeg @ 0x4b14940] marker parser used 30 bytes (240 bits)
  
  [mjpeg @ 0x4b14940] marker=c4 avail_size_in_buf=1867875
  
  [mjpeg @ 0x4b14940] class=1 index=0 nb_codes=242
  
  [mjpeg @ 0x4b14940] marker parser used 82 bytes (656 bits)
  
  [mjpeg @ 0x4b14940] marker=c4 avail_size_in_buf=1867791
  
  [mjpeg @ 0x4b14940] class=0 index=1 nb_codes=8
  
  [mjpeg @ 0x4b14940] marker parser used 27 bytes (216 bits)
  
  [mjpeg @ 0x4b14940] marker=c4 avail_size_in_buf=1867762
  
  [mjpeg @ 0x4b14940] class=1 index=1 nb_codes=241
  
  [mjpeg @ 0x4b14940] marker parser used 51 bytes (408 bits)
  
  [mjpeg @ 0x4b14940] escaping removed 7149 bytes
  
  [mjpeg @ 0x4b14940] marker=da avail_size_in_buf=1867709
  
  [mjpeg @ 0x4b14940] component: 0
  
  [mjpeg @ 0x4b14940] component: 1
  
  [mjpeg @ 0x4b14940] component: 2
  
  [mjpeg @ 0x4b14940] marker parser used 1860559 bytes (14884468 bits)
  
  [mjpeg @ 0x4b14940] marker=d9 avail_size_in_buf=0
  
  [mjpeg @ 0x4b14940] decode frame unused 0 bytes
  
  [swscaler @ 0x5bd42c0] deprecated pixel format used, make sure you did set range correctly
  
  cur_dts is invalid (this is harmless if it occurs once at the start per stream)
  
  [image2 @ 0x4b11140] Opening '/tmp/photo-2HD2Z3UN3W.jpg' for reading
  
  [AVIOContext @ 0x4b6ecc0] Statistics: 1868086 bytes read, 0 seeks
  
  [mjpeg @ 0x4b14940] marker=d8 avail_size_in_buf=1868084
  
  [mjpeg @ 0x4b14940] marker parser used 0 bytes (0 bits)
  
  [mjpeg @ 0x4b14940] marker=e0 avail_size_in_buf=1868082
  
  [mjpeg @ 0x4b14940] marker parser used 16 bytes (128 bits)
  
  [mjpeg @ 0x4b14940] marker=db avail_size_in_buf=1868064
  
  [mjpeg @ 0x4b14940] index=0
  
  [mjpeg @ 0x4b14940] qscale[0]: 0
  
  [mjpeg @ 0x4b14940] marker parser used 67 bytes (536 bits)
  
  [mjpeg @ 0x4b14940] marker=db avail_size_in_buf=1867995
  
  [mjpeg @ 0x4b14940] index=1
  
  [mjpeg @ 0x4b14940] qscale[1]: 1
  
  [mjpeg @ 0x4b14940] marker parser used 67 bytes (536 bits)
  
  [mjpeg @ 0x4b14940] marker=c0 avail_size_in_buf=1867926
  
  [mjpeg @ 0x4b14940] sof0: picture: 1936x2592
  
  [mjpeg @ 0x4b14940] component 0 1:1 id: 0 quant:0
  
  [mjpeg @ 0x4b14940] component 1 1:1 id: 1 quant:1
  
  [mjpeg @ 0x4b14940] component 2 1:1 id: 2 quant:1
  
  [mjpeg @ 0x4b14940] pix fmt id 11111100
  
  [mjpeg @ 0x4b14940] marker parser used 17 bytes (136 bits)
  
  [mjpeg @ 0x4b14940] marker=c4 avail_size_in_buf=1867907
  
  [mjpeg @ 0x4b14940] class=0 index=0 nb_codes=11
  
  [mjpeg @ 0x4b14940] marker parser used 30 bytes (240 bits)
  
  [mjpeg @ 0x4b14940] marker=c4 avail_size_in_buf=1867875
  
  [mjpeg @ 0x4b14940] class=1 index=0 nb_codes=242
  
  [mjpeg @ 0x4b14940] marker parser used 82 bytes (656 bits)
  
  [mjpeg @ 0x4b14940] marker=c4 avail_size_in_buf=1867791
  
  [mjpeg @ 0x4b14940] class=0 index=1 nb_codes=8
  
  [mjpeg @ 0x4b14940] marker parser used 27 bytes (216 bits)
  
  [mjpeg @ 0x4b14940] marker=c4 avail_size_in_buf=1867762
  
  [mjpeg @ 0x4b14940] class=1 index=1 nb_codes=241
  
  [mjpeg @ 0x4b14940] marker parser used 51 bytes (408 bits)
  
  [mjpeg @ 0x4b14940] escaping removed 7149 bytes
  
  [mjpeg @ 0x4b14940] marker=da avail_size_in_buf=1867709
  
  [mjpeg @ 0x4b14940] component: 0
  
  [mjpeg @ 0x4b14940] component: 1
  
  [mjpeg @ 0x4b14940] component: 2
  
  [mjpeg @ 0x4b14940] marker parser used 1860559 bytes (14884468 bits)
  
  [mjpeg @ 0x4b14940] marker=d9 avail_size_in_buf=0
  
  [mjpeg @ 0x4b14940] decode frame unused 0 bytes
  
  [swscaler @ 0x5bd8200] deprecated pixel format used, make sure you did set range correctly
  
  cur_dts is invalid (this is harmless if it occurs once at the start per stream)
  
  ...
  
  ...
  
  ...

  As requested, here is a link to the full log. In this log - ffmpeg renders only 323 out of 375 frames.

  The Opening '/tmp/photo-2HD2Z3UN3W.jpg' segment repeats many many times until it finally renders out a short video. Does anyone have insight into why it keeps opening the image file ? This must have something to do with the underlying issue.