Recherche avancée

Sur d’autres sites (6491)

• FFmpeg stuck on frame 0 during time-lapse conversion with `-ss` start time

  2 janvier 2021, par rgov

  I have a long video that I'd like to speed up into a time-lapse. Following the FFmpeg wiki, I came up with this incantation :

  



  ffmpeg -i IMG_0238.MOV -r 60 -ss 00:04:41 -filter:v "setpts=PTS/60.0" -an output.mp4


  



  It should clip off the first few minutes, then create a new 60fps video file at 60x the speed.

  



  Although it spins all my CPU cores up to 100%, the status bar simply shows frame=    0 fps=0.0 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x and never progresses.

  



  The problem seems related to the -ss 00:04:41 flag, which specifies the start time ; I want to drop the first 4 minutes 41 seconds of source video. When I omit this option, the video conversion succeeds.

  



  Full log follows.

  



  ---

  



  ffmpeg version 3.4.1 Copyright (c) 2000-2017 the FFmpeg developers
  built with Apple LLVM version 9.1.0 (clang-902.0.30)
  configuration: --prefix=/usr/local/Cellar/ffmpeg/3.4.1 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-gpl --enable-libmp3lame --enable-libx264 --enable-libx265 --enable-libxvid --enable-opencl --enable-videotoolbox --disable-lzma
  libavutil      55. 78.100 / 55. 78.100
  libavcodec     57.107.100 / 57.107.100
  libavformat    57. 83.100 / 57. 83.100
  libavdevice    57. 10.100 / 57. 10.100
  libavfilter     6.107.100 /  6.107.100
  libavresample   3.  7.  0 /  3.  7.  0
  libswscale      4.  8.100 /  4.  8.100
  libswresample   2.  9.100 /  2.  9.100
  libpostproc    54.  7.100 / 54.  7.100
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fb59b800000] stream 2, missing mandatory atoms, broken header
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fb59b800000] stream 3, missing mandatory atoms, broken header
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'IMG_0238.MOV':
  Metadata:
    major_brand     : qt  
    minor_version   : 0
    compatible_brands: qt  
    creation_time   : 2017-04-20T16:25:14.000000Z
    com.apple.quicktime.location.ISO6709: +36.4610+025.3727+123.613/
    com.apple.quicktime.make: Apple
    com.apple.quicktime.model: iPhone 7
    com.apple.quicktime.software: 10.3.1
    com.apple.quicktime.creationdate: 2017-04-20T19:25:13+0300
  Duration: 01:22:45.53, start: -0.000023, bitrate: 44171 kb/s
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 3840x2160, 44077 kb/s, 30 fps, 30 tbr, 600 tbn, 1200 tbc (default)
    Metadata:
      rotate          : 180
      creation_time   : 2017-04-20T16:25:14.000000Z
      handler_name    : Core Media Data Handler
      encoder         : H.264
    Side data:
      displaymatrix: rotation of -180.00 degrees
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 84 kb/s (default)
    Metadata:
      creation_time   : 2017-04-20T16:25:14.000000Z
      handler_name    : Core Media Data Handler
    Stream #0:2(und): Data: none (mebx / 0x7862656D) (default)
    Metadata:
      creation_time   : 2017-04-20T16:25:14.000000Z
      handler_name    : Core Media Data Handler
    Stream #0:3(und): Data: none (mebx / 0x7862656D) (default)
    Metadata:
      creation_time   : 2017-04-20T16:25:14.000000Z
      handler_name    : Core Media Data Handler
File 'output.mp4' already exists. Overwrite ? [y/N] y
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
Press [q] to stop, [?] for help
[libx264 @ 0x7fb59b82b800] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
[libx264 @ 0x7fb59b82b800] profile High, level 5.2
[libx264 @ 0x7fb59b82b800] 264 - core 148 r2795 aaa9aa8 - 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=6 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 'output.mp4':
  Metadata:
    major_brand     : qt  
    minor_version   : 0
    compatible_brands: qt  
    com.apple.quicktime.creationdate: 2017-04-20T19:25:13+0300
    com.apple.quicktime.location.ISO6709: +36.4610+025.3727+123.613/
    com.apple.quicktime.make: Apple
    com.apple.quicktime.model: iPhone 7
    com.apple.quicktime.software: 10.3.1
    encoder         : Lavf57.83.100
    Stream #0:0(und): Video: h264 (libx264) (avc1 / 0x31637661), yuv420p, 3840x2160, q=-1--1, 60 fps, 15360 tbn, 60 tbc (default)
    Metadata:
      encoder         : Lavc57.107.100 libx264
      creation_time   : 2017-04-20T16:25:14.000000Z
      handler_name    : Core Media Data Handler
    Side data:
      cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
      displaymatrix: rotation of -0.00 degrees
frame=    0 fps=0.0 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x


  


• FFMPEG sound not playing in video converted from audio in browsers (chrome/firefox) except safari

  7 février 2019, par Bhavik Rathod

  Sound not playing in Video (mp4) converted from Audio (mp3), Below is my code

  I am using FFMPEG version 4.1

  ffmpeg -y -loop 1 -i background.jpg -i dia.mp3 -c:v libx264 -tune stillimage -pix_fmt yuv420p -c:a ac3_fixed -b:a 128k -shortest -vf "[in]drawtext=text=Hi:x=(w-text_w)/2:y=(h-text_h):fontfile=arial.ttf:fontsize=100:fontcolor=ffffff:alpha='if(lt(t,9.2763066666667),0,if(lt(t,9.2763066666667+1),(t-9.2763066666667)/1,if(lt(t,12.83428),1,if(lt(t,12.83428+1),(1-(t-12.83428))/1,0))))'" output.mp4 2>&1

  I have tried putting -movflags +faststart as an output option

  I am using ac3_fixed because i found that fix for handle memory management, My server is getting hang on using aac no video created nothing i have to restart instance to get back to work. by using ac3_fixed everything is perfect but issue is only sound playing in chrome and firefox.

  Below is full log while using aac

  `ffmpeg version 4.1-static https://johnvansickle.com/ffmpeg/  Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 6.3.0 (Debian 6.3.0-18+deb9u1) 20170516
  
    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-libaom --enable-libfribidi --enable-libass --enable-libvmaf --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband --enable-libsoxr --enable-libspeex --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg
  
    libavutil      56. 22.100 / 56. 22.100
  
    libavcodec     58. 35.100 / 58. 35.100
  
    libavformat    58. 20.100 / 58. 20.100
  
    libavdevice    58.  5.100 / 58.  5.100
  
    libavfilter     7. 40.101 /  7. 40.101
  
    libswscale      5.  3.100 /  5.  3.100
  
    libswresample   3.  3.100 /  3.  3.100
  
    libpostproc    55.  3.100 / 55.  3.100
  
  Input #0, image2, from '/var/www/html/xxxxx/assets/media/guest/e0ce3bfdab4b305d00459328afb94ca6.jpg':
  
    Duration: 00:00:00.04, start: 0.000000, bitrate: 196382 kb/s
  
      Stream #0:0: Video: mjpeg, yuvj444p(pc, bt470bg/unknown/unknown), 1920x1080 [SAR 1:1 DAR 16:9], 25 fps, 25 tbr, 25 tbn, 25 tbc
  
  [mp3 @ 0x5970440] Estimating duration from bitrate, this may be inaccurate
  
  Input #1, mp3, from '/var/www/html/xxxxx/assets/media/guest/e0ce3bfdab4b305d00459328afb94ca6.mp3':
  
    Metadata:
  
      title           : In the Cafe
  
      album           : British Council
  
      genre           : Blues
  
    Duration: 00:01:02.77, start: 0.000000, bitrate: 128 kb/s
  
      Stream #1:0: Audio: mp3, 44100 Hz, stereo, fltp, 128 kb/s
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (mjpeg (native) -> h264 (libx264))
  
    Stream #1:0 -> #0:1 (mp3 (mp3float) -> aac (native))
  
  Press [q] to stop, [?] for help
  
  [swscaler @ 0x5b91ec0] deprecated pixel format used, make sure you did set range correctly
  
  [libx264 @ 0x598e640] using SAR=1/1
  
  [libx264 @ 0x598e640] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
  
  [libx264 @ 0x598e640] profile High, level 4.0, 4:2:0, 8-bit
  
  [libx264 @ 0x598e640] 264 - core 157 r2935 545de2f - H.264/MPEG-4 AVC codec - Copyleft 2003-2018 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:-3:-3 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=2.00:0.70 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-4 threads=1 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.20
  
  Output #0, mp4, to '/var/www/html/xxxxx/assets/media/guest/created_video/e0ce3bfdab4b305d00459328afb94ca6.mp4':
  
    Metadata:
  
      encoder         : Lavf58.20.100
  
      Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=-1--1, 25 fps, 12800 tbn, 25 tbc
  
      Metadata:
  
        encoder         : Lavc58.35.100 libx264
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
      Stream #0:1: Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 128 kb/s
  
      Metadata:
  
        encoder         : Lavc58.35.100 aac
  
  frame=   14 fps=0.0 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   frame=   28 fps= 27 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   frame=   42 fps= 27 q=28.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=  frame=   44 fps= 21 q=28.0 size=     256kB time=00:00:00.02 bitrate=72266.5kbitsframe=   49 fps= 19 q=28.0 size=     256kB time=00:00:00.20 bitrate=10323.8kbitsframe=   55 fps= 18 q=28.0 size=     256kB time=00:00:00.48 bitrate=4353.4kbits/frame=   62 fps= 17 q=28.0 size=     256kB time=00:00:00.72 bitrate=2890.7kbits/frame=   68 fps= 16 q=28.0 size=     256kB time=00:00:01.00 bitrate=2088.6kbits/    
  
  `

• What is Web Log Analytics and Why You Should Use It

  26 juin 2024, par Erin

  Can’t use JavaScript tracking on your website ? Need a more secure and privacy-friendly way to understand your website visitors ? Web log analytics is your answer. This method pulls data directly from your server logs, offering a secure and privacy-respecting alternative.  

  In this blog, we cover what web log analytics is, how it compares to JavaScript tracking, who it is best suited for, and why it might be the right choice for you. 

  What are server logs ? 

  Before diving in, let’s start with the basics : What are server logs ? Think of your web server as a diary that notes every visit to your website. Each time someone visits, the server records details like : 

  • User agent : Information about the visitor’s browser and operating system. 

  • Timestamp : The exact time the request was made. 

  • Requested URL : The specific page or resource the visitor requested. 

  These “diary entries” are called server logs, and they provide a detailed record of all interactions with your website. 

  Server log example 

  Here’s what a server log looks like : 

  192.XXX.X.X – – [24/Jun/2024:14:32:01 +0000] “GET /index.html HTTP/1.1” 200 1024 “https://www.example.com/referrer.html” “Mozilla/5.0 (Windows NT 10.0 ; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36” 

  192.XXX.X.X – – [24/Jun/2024:14:32:02 +0000] “GET /style.css HTTP/1.1” 200 3456 “https://www.example.com/index.html” “Mozilla/5.0 (Windows NT 10.0 ; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36” 

  192.XXX.X.X – – [24/Jun/2024:14:32:03 +0000] “GET /script.js HTTP/1.1” 200 7890 “https://www.example.com/index.html” “Mozilla/5.0 (Windows NT 10.0 ; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36” 

  192.XXX.X.X – – [24/Jun/2024:14:32:04 +0000] “GET /images/logo.png HTTP/1.1” 200 1234 “https://www.example.com/index.html” “Mozilla/5.0 (Windows NT 10.0 ; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36” 

  Breakdown of the log entry 

  Each line in the server log represents a single request made by a visitor to your website. Here’s a detailed breakdown of what each part means : 

  • IP Address : 192.XXX.X.X 
    • This is the IP address of the visitor’s device. 
  • User Identifier : – – 
    • These fields are typically used for user identification and authentication, which are not applicable here, hence the hyphens. 
  • Timestamp : [24/Jun/2024:14:32:01 +0000] 
  • • • The date and time of the request, including the timezone. 
  • Request Line : “GET /index.html HTTP/1.1” 
    • The request method (GET), the requested resource (/index.html), and the HTTP version (HTTP/1.1). 
  • Response Code : 200 
    • The HTTP status code indicates the result of the request (200 means OK). 
  • Response Size : 1024 
    • The size of the response in bytes. 
  • Referrer : “https://www.example.com/referrer.html“ 
    • The URL of the referring page that led the visitor to the current page. 
  • User Agent : “Mozilla/5.0 (Windows NT 10.0 ; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36” 
    • Information about the visitor’s browser and operating system. 

  In the example above, there are multiple log entries for different resources (HTML page, CSS file, JavaScript file, and an image). This shows that when a visitor loads a webpage, multiple requests are made to load all the necessary resources. 

  What is web log analytics ? 

  Web log analytics is one of many methods for tracking visitors to your site.  

  

  Web log analytics is the process of analysing server log files to track and understand website visitors. Unlike traditional methods that use JavaScript tracking codes embedded in web pages, web log analytics pulls data directly from these server logs. 

  How it works : 

  1. Visitor request : A visitor’s browser requests your website. 
  2. Server logging : The server logs the request details. 
  3. Analysis : These logs are analysed to extract useful information about your visitors and their activities. 

  Web log analytics vs. JavaScript tracking 

  JavaScript tracking 

  JavaScript tracking is the most common method used to track website visitors. It involves embedding a JavaScript code snippet into your web pages. This code collects data on visitor interactions and sends it to a web analytics platform. 

  

  Differences and benefits :
  

  Privacy : 

  • Web log analytics : Since it doesn’t require embedding tracking codes, it is considered less intrusive and helps maintain higher privacy standards. 

  • JavaScript tracking : Embeds tracking codes directly on your website, which can be more invasive and raise privacy concerns. 

  Ease of setup : 

  • Web log analytics : No need to modify your website’s code. All you need is access to your server logs. 

  • JavaScript tracking : Requires adding tracking code on your web pages. This is generally an easier setup process.  

  Data collection : 

  • Web log analytics : Contain requests of users with adblockers (ghostery, adblock, adblock plus, privacy badger, etc.) sometimes making it more accurate. However, it may miss certain interactive elements like screen resolution or user events. It may also over-report data.  

  • JavaScript tracking : Can collect a wide range of data, including Custom dimensions, Ecommerce tracking, Heatmaps, Session recordings, Media and Form analytics, etc. 

  Why choose web log analytics ? 

  Enhanced privacy 

  Avoiding embedded tracking codes means there’s no JavaScript running on your visitors’ browsers. This significantly reduces the risk of data leakage and enhances overall privacy. 

  Comprehensive data collection 

  It isn’t affected by ad blockers or browser tracking protections, ensuring you capture more complete and accurate data about your visitors. 

  Historical data analysis 

  You can import and analyse historical log files, giving you insights into long-term visitor behaviour and trends. 

  Simple setup 

  Since it relies on server logs, there’s no need to alter your website’s code. This makes setup straightforward and minimises potential technical issues. 

  Who should use web log analytics ? 

  Web log analytics is particularly suited for businesses that prioritise data privacy and security.

  Organisations that handle sensitive data, such as banks, healthcare providers, and government agencies, can benefit from the enhanced privacy.  

  By avoiding JavaScript tracking, these entities minimise data exposure and comply with strict privacy regulations like Sarbanes Oxley and PCI. 

  Why use Matomo for web log analytics ? 

  Matomo stands out as a top choice for web log analytics because it prioritises privacy and data ownership

  

  Here’s why : 

  • Complete data control : You own all your data, so you don’t have to worry about third-party access. 
  • IP anonymisation : Matomo anonymises IP addresses to further protect user privacy. 
  • Bot filtering : Automatically excludes bots from your reports, ensuring you get accurate data. 
  • Simple migration : You can easily switch from other tools like AWStats by importing your historical logs into Matomo. 
  • Server log recognition : Recognises most server log formats (Apache, Nginx, IIS, etc.). 

  Start using web log analytics 

  Web log analytics offers a secure, privacy-focused alternative to traditional JavaScript tracking methods. By analysing server logs, you get valuable insights into your website traffic while maintaining high privacy standards.  

  If you’re serious about privacy and want reliable data, give Matomo’s web log analytics a try.  

  Start your 21-day free trial now. No credit card required. 

  Try Matomo for Free

  21 day free trial. No credit card required.

  
  

  Your email address
  

  Your website address
  

  Your Analytics subdomain will be .matomo.cloud (change)

  Choose your analytics subdomain
  

  .matomo.cloud