Recherche avancée

Sur d’autres sites (8212)

• avformat/mpegtsenc : Changed Video PES packet length to 0.

  12 avril 2014, par Graham Booker

  avformat/mpegtsenc : Changed Video PES packet length to 0.
  The rational for this is another issue that plex has exposed.  When it is
  
  conducting a transcode of video to HLS for streaming, my father noticed
  
  artifacts when played on his GoogleTV (NSZ-GT1).  He sent me a test file
  
  and I reproduced it on my device of the same model.  It is important to
  
  note that the artifacts were not present when streaming to VLC or QuickTime
  
  Player.  I copied the command-line that plex used, and conducted all of the
  
  following tests using FFmpeg git.
  Transcode to HLS : artifacts on playback
  
  Transcode to TS : playback is fine
  
  Cat HLS segments into a single TS : playback is fine
  
  Segment single TS file to segments : artifacts on playback
  
  Segment single TS file to segments using Apple’s HLS segmenter : playback is
  
  fine
  At this point I carefully examined the differences between Apple’s HLS
  
  segmenter output and FFmpeg’s.  Among the considerable differences, I
  
  noticed that the video PES packets always had a 0 length.  So I continued :
  Transcode to HLS using FFmpeg with 0 length PES packets : playback is fine.
  
  Segment single TS to segments with 0 length PES packets : playback is fine.
  All failures mentioned are only on the GTV since it is the only player on
  
  which I could reproduce artifacts.  I only tested the GTV, VLC, and
  
  QuickTime Player though, so my test case is limited.  I do not know if
  
  other players exhibit this issue.
  Since it was useful last time, I have uploaded the test file as
  
  hls_pes_packet_length.m4v along with its associated txt file which contains
  
  the transcode command-line that was used.
  Reviewed-by : Kieran Kunhya <kierank@obe.tv>
  
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavformat/mpegtsenc.c
  • [DH] tests/ref/lavf/ts

• Circular Overlay of Video on Another Video using FFMPEG in Android

  4 novembre 2018, par kdblue

  I am trying to overlay Second videos(on Circle) on First video. I tried but i am getting glitches in Video !

  My Command is

  command = "-i " + this.video1Path.getPath() + " -i " + this.video2Path.getPath() + " -filter_complex [1]trim=end_frame=1,geq=lum_expr='st(3,pow(X-(W/2),2)+pow(Y-(H/2),2));if(lte(ld(3),"
+ (this.mZoomLayout.getZoomedWidth()/2) + "*" + (this.mZoomLayout.getZoomedWidth()/2) + "),255,0)':128:128,format=gray,loop=-1:1,setpts=N/FRAME_RATE/TB[mask];[1][mask]alphamerge,format=rgba,lutrgb=a=if(gte(val\\,16)\\,val)[cutout];[0][cutout]overlay="
+ this.mZoomLayout.getCircleX() + ":" + this.mZoomLayout.getCircleY() + ":enable='between(t,0," + this.videoTwoDuration + ") -c:v libx264 -crf 24 -preset ultrafast " + videoPath.getPath();

  Example : i want like this

  

  But i am getting glitches in Video

  

  I am using ffmpeg android library :- https://github.com/bravobit/FFmpeg-Android

  Note : I tried this links but never worked

  https://stackoverflow.com/questions/42518592/circular-movie-overlay-in-ffmpeg (getting glitches)

  FFMPEG Log

  11-04 19:56:37.505 28420-28420/app.kdblue.com.ffmpegdemo E/ffmpeg Success: ffmpeg version n4.0-39-gda39990 Copyright (c) 2000-2018 the FFmpeg developers
  
        built with gcc 4.9.x (GCC) 20150123 (prerelease)
  
        configuration: --target-os=linux --cross-prefix=/root/bravobit/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi- --arch=arm --cpu=cortex-a8 --enable-runtime-cpudetect --sysroot=/root/bravobit/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-ffprobe --enable-libopus --enable-libvorbis --enable-libfdk-aac --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-fontconfig --enable-libvpx --enable-libass --enable-yasm --enable-pthreads --disable-debug --enable-version3 --enable-hardcoded-tables --disable-ffplay --disable-linux-perf --disable-doc --disable-shared --enable-static --enable-runtime-cpudetect --enable-nonfree --enable-network --enable-avresample --enable-avformat --enable-avcodec --enable-indev=lavfi --enable-hwaccels --enable-ffmpeg --enable-zlib --enable-gpl --enable-small --enable-nonfree --pkg-config=pkg-config --pkg-config-flags=--static --prefix=/root/bravobit/ffmpeg-android/build/armeabi-v7a --extra-cflags='-I/root/bravobit/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all' --extra-ldflags='-L/root/bravobit/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-cxxflags=
  
        libavutil      56. 14.100 / 56. 14.100
  
        libavcodec     58. 18.100 / 58. 18.100
  
        libavformat    58. 12.100 / 58. 12.100
  
        libavdevice    58.  3.100 / 58.  3.100
  
        libavfilter     7. 16.100 /  7. 16.100
  
        libavresample   4.  0.  0 /  4.  0.  0
  
        libswscale      5.  1.100 /  5.  1.100
  
        libswresample   3.  1.100 /  3.  1.100
  
        libpostproc    55.  1.100 / 55.  1.100
  
      Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/emulated/0/MixVideos/video1_1541341464579.mp4':
  
        Metadata:
  
          major_brand     : mp42
  
          minor_version   : 0
  
          compatible_brands: isommp42
  
          creation_time   : 2018-11-04T14:24:29.000000Z
  
          com.android.version: 8.1.0
  
          com.android.manufacturer: OnePlus
  
          com.android.model: ONE A2003
  
        Duration: 00:00:04.15, start: 0.000000, bitrate: 9983 kb/s
  
          Stream #0:0(eng): Video: h264 (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x1080, 9978 kb/s, SAR 1:1 DAR 16:9, 29.39 fps, 30 tbr, 90k tbn, 180k tbc (default)
  
          Metadata:
  
            rotate          : 90
  
            creation_time   : 2018-11-04T14:24:29.000000Z
  
            handler_name    : VideoHandle
  
          Side data:
  
            displaymatrix: rotation of -90.00 degrees
  
      Input #1, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/emulated/0/MixVideos/video2_1541341478507.mp4':
  
        Metadata:
  
          major_brand     : mp42
  
          minor_version   : 0
  
          compatible_brands: isommp42
  
          creation_time   : 2018-11-04T14:24:42.000000Z
  
          com.android.version: 8.1.0
  
          com.android.manufacturer: OnePlus
  
          com.android.model: ONE A2003
  
        Duration: 00:00:02.62, start: 0.000000, bitrate: 9833 kb/s
  
          Stream #1:0(eng): Video: h264 (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x1080, 9824 kb/s, SAR 1:1 DAR 16:9, 29.73 fps, 30 tbr, 90k tbn, 180k tbc (default)
  
          Metadata:
  
            rotate          : 90
  
            creation_time   : 2018-11-04T14:24:42.000000Z
  
            handler_name    : VideoHandle
  
          Side data:
  
            displaymatrix: rotation of -90.00 degrees
  
      Stream mapping:
  
        Stream #0:0 (h264) -> overlay:main
  
        Stream #1:0 (h264) -> trim
  
        Stream #1:0 (h264) -> alphamerge:main
  
        overlay -> Stream #0:0 (libx264)
  
      Press [q] to stop, [?] for help
  
      [swscaler @ 0xed8a7000] No accelerated colorspace conversion found from yuv420p to rgba.
  
      [libx264 @ 0xf2016c00] using SAR=1/1
  
      [libx264 @ 0xf2016c00] using cpu capabilities: ARMv6 NEON
  
      [libx264 @ 0xf2016c00] profile Constrained Baseline, level 4.0
  
      [libx264 @ 0xf2016c00] 264 - core 152 r2851M ba24899 - H.264/MPEG-4 AVC codec - Copyleft 2003-2017 - http://www.videolan.org/x264.html - options: cabac=0 ref=1 deblock=0:0:0 analyse=0:0 me=dia subme=0 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=12 lo

• How do I deploy Whisper.cpp stream.wasm on an EC2 instance ? [closed]

  3 août, par tosUser

  How do I deploy the whisper.cpp stream.wasm demo on a EC2 instance ?

  


  The demo is available from the following git :
https://github.com/ggml-org/whisper.cpp/tree/master/examples/stream.wasm

  


  I am fairly far along, but the program hangs on Preparing ...
I do not know what is causing the issue.

  


  Here are the steps I have taken. (I am trying to make it brief, and provide more detail as necessary.)
I cloned the repository and built it locally.
It runs properly.

  


  I created an EC2 instance running Amazon Linux 2023, and uploaded the Whisper.cpp files to it.
I ssh into the server and installed nginx, it displays the default page to the server's public ip address.
I then configured nginx as a reverse proxy server :

  


      server {
        listen 80;
        server_name redactedPublicIpAddress;
        location / {
            proxy_pass http://127.0.0.1:8000;
        }
    }



  


  I enabled and restarted nginx.

  


  I then try to run whisper.cpp stream.wasm by running python3 examples/server.py
It indicates that it is serving home/ec2-user/whisper.cpp/build-em/bin to localhost:8000
This is analogous to the message when it is served locally.
Stream.wasm has a 301 response.
Helpers.js and coi-serviceworker.js have 200 responses.

  


  The index file displays normally at the public ip address/stream.wasm/

  


  However, all is not well. The js seems to hang on Preparing...
Other js functions on the page still function, I can download a model and the page indicates it was downloaded, etc. However, I cannot start recording. The start button is not active. It never properly initializes.

  


  This type of behavior is identical to trying to open the index file on my local computer without it being served.

  


  I think I am missing something simple, but do not know what it is.

  


  Here are some steps that I took afterwards that did not fix the issue :
I installed nodejs and npm so that I could install ffmpeg.wasm : npm install @ffmpeg/ffmpeg @ffmpeg/util

  


  The github page indicates that I need to put the files in the html path. So in trying to troubleshoot I put them in /user/shared/nginx/html which is where the nginx default index file is placed.

  


  I think it may be related to serving the python. The server.py file is not in a state to deploy it with uvicorn.

  


  Maybe there is some sort of cors issue.

  


  I simply do not know.