Recherche avancée

Sur d’autres sites (4161)

• avformat/mpegtsenc : fix first_pcr initial update

  3 novembre 2021, par Maksym Veremeyenko

  avformat/mpegtsenc : fix first_pcr initial update
  Commit 6f36eb0da71d22aadf8f056f0966bd86656ea57e claim it fixes endless loop on
  
  package generation if muxrate specified and copyts used. But actually it does
  
  not work properly if -mpegts_copyts 1 is specified :
  ffmpeg -y -copyts -i loewe.ts -c:v libx264 -x264opts nal-hrd=cbr:force-cfr=1 -b:v 3500k -minrate 3500k -maxrate 3500k -bufsize 1000k  -c:a mp2 -f mpegts -mpegts_copyts 1 -muxrate 4500k -vframes 1000 test.ts
  ffmpeg generate huge file until it reach zero-based pcr value equal to first dts.
  Attached patch fixes it.
  Reviewed-by : Limin Wang <lance.lmwang@gmail.com>
  
  Signed-off-by : Marton Balint <cus@passwd.hu>
  

  • [DH] libavformat/mpegtsenc.c

• Invalid CFBundleSupportedPlatforms value iPhoneSimulator in (DJIWidget) FFmpeg.framework

  10 mai 2022, par Brien Crean

  I cannot upload my app which contains the DJI-SDK, DJIWidget(which contains FFMpeg) to Testflight after updating to Xcode 13. When I try I get :

  


  


  Invalid CFBundleSupportedPlatforms value. The
CFBundleSupportedPlatforms key in the Info.plist file in
“Payload/app.app/Frameworks/FFmpeg.framework” bundle contains an
invalid value, [iPhoneSimulator]. Consider removing the
CFBundleSupportedPlatforms key from the Info.plist file. If this
bundle is part of a third-party framework, consider contacting the
developer of the framework for an update to address this issue. With
error code STATE_ERROR.VALIDATION_ERROR.90542 for id
f2327257-ad48-4b60-8fc8-a518da5fbac8

  


  


  # relevant pods
pod 'DJI-SDK-iOS', '~> 4.16'
pod 'DJIWidget', '~> 1.6.6'


  


  However FFMpeg seems to be a binary file Framework attached to DJIWidget so I can't edit the Info.plist directly. Is there any way to workaround this or do I have to reach out to the DJI to actually make a change ?

  


• FFMPEG command line not using GPU when compressing MP4 file

  13 avril 2022, par StealthRT

  Hey all I have been working on a good command line string to use for my movies that I would like to trim the size down to at least half the current size.

  


  My handbrake information regaurding my GPU and computer system is this :

  


  HandBrake 1.5.1 (2022011000)
OS: Microsoft Windows NT 10.0.19043.0
CPU: Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz (12 Cores, 24 Threads)
Ram: 40940 MB, 
GPU Information:
  Microsoft Remote Display Adapter - 10.0.19041.662
  NVIDIA Tesla K10 - 30.0.14.7141
  NVIDIA Tesla K10 - 30.0.14.7141
  Microsoft Basic Display Adapter - 10.0.19041.868


  


  When I originally made a command line, I was just using it to copy the file over to where it needed to go with the following :

  


  


  ffmpeg -y -hide_banner -threads 8 -hwaccel cuda -hwaccel_device 1
-hwaccel_output_format cuda -v verbose -i "c :\testingvids\AEON FLUX 2005.mp4" -c:v h264_cuvid -gpu:v 1 -preset slow -c copy "c :\testingvids\AEON FLUX 2005 nvidia.mp4"

  


  


  This produced a 828x processing speed :

  


  

  


  But for taking that same file and compressing it I seem to only get a 8x speed ?

  


  

  


  So that is quite a difference there. Am I using the correct syntax for it to only use my GPU to convert/compress the mp4 with the h264 nvenc ?