Recherche avancée

Sur d’autres sites (7822)

• FFPLAY read mp4 file from HTTP sever : report error : stream 1, offset 0x1c33 : partial file

  25 mai 2018, par whmiao

  I use command line like :

  ffplay http://192.168.4.56:5656/files/video/failed_111.mp4

  output :
  ffplay version N-87130-g2b9fd15 Copyright (c) 2003-2017 the FFmpeg developers
  built with gcc 7.1.0 (GCC)
  configuration : —enable-gpl —enable-version3 —enable-cuda —enable-cuvid —enable-d3d11va —enable-dxva2 —enable-libmfx —enable-nvenc —enable-avisynth —enable-bzlib —enable-fontconfig —enable-frei0r —enable-gnutls —enable-iconv —enable-libass —enable-libbluray —enable-libbs2b —enable-libcaca —enable-libfreetype —enable-libgme —enable-libgsm —enable-libilbc —enable-libmodplug —enable-libmp3lame —enable-libopencore-amrnb —enable-libopencore-amrwb —enable-libopenh264 —enable-libopenjpeg —enable-libopus —enable-librtmp —enable-libsnappy —enable-libsoxr —enable-libspeex —enable-libtheora —enable-libtwolame —enable-libvidstab —enable-libvo-amrwbenc —enable-libvorbis —enable-libvpx —enable-libwavpack —enable-libwebp —enable-libx264 —enable-libx265 —enable-libxavs —enable-libxvid —enable-libzimg —enable-lzma —enable-zlib
  libavutil 55. 74.100 / 55. 74.100
  libavcodec 57.104.100 / 57.104.100
  libavformat 57. 79.100 / 57. 79.100
  libavdevice 57. 8.100 / 57. 8.100
  libavfilter 6.101.100 / 6.101.100
  libswscale 4. 7.103 / 4. 7.103
  libswresample 2. 8.100 / 2. 8.100
  libpostproc 54. 6.100 / 54. 6.100
  [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000025048e0] stream 1, offset 0x1c33 : partial file
  [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000025048e0] Could not find codec parameters for stream 0 (Video : h264 (avc1 / 0x31637661), none(tv, bt709), 544x960, 1140 kb/s) : unspecified pixel format
  Consider increasing the value for the ’analyzeduration’ and ’probesize’ options

  I download the file,Open local storage,It works well,like :

  ffplay e:\failed_111.mp4

  file can download from :
  https://pan.baidu.com/s/19H9cl3YAjG-AK60nIn0KzQ

• ffmpeg, /dev/video0, -f decklink

  20 mars 2019, par Camille Goudeseune

  I’m trying to capture video from a PCI card, the Blackmagic DeckLink Mini Recorder, via ffmpeg, on a headless host running Ubuntu 18.04.2 LTS, hopefully with a command like

  ffmpeg -f decklink -i /dev/video0 ...

  How can I make that work ? I have two obstacles.

  No /dev/video0

  ffmpeg -i /dev/video0 ... fails : /dev/video0: No such device or address.
  v4l2-ctl --list-devices fails with the same error message.

  I built /dev/video0, and it looks okay :

  mknod /dev/video0 c 81 0
  
  chown root.video /dev/video0
  
  chmod g+rw /dev/video0

  To compare this file with a working one, I ran strace cat /dev/video0 on this host, and on another host (Ubuntu 14) with a working /dev/video0. The outputs began to differ here (good, then bad) :

  fstat(1, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
  
  open("/dev/video0", O_RDONLY)           = 3  
  
  fstat(3, {st_mode=S_IFCHR|0660, st_rdev=makedev(81, 0), ...}) = 0
  
  fadvise64(3, 0, 0, POSIX_FADV_SEQUENTIAL) = 0
  
  ----
  
  
  
  fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
  
  openat(AT_FDCWD, "/dev/video0", O_RDONLY) = -1 ENXIO (No such device or address)

  So /dev/video0 is broken at a level lower than ffmpeg or v4l2 or even cat.

  On Ubuntu 14, man 8 MAKEDEV suggests that the error message means that "the kernel does not have the driver configured or loaded."

  This Ubuntu 18 host lacks that manpage, but it does have a few /snap/core/*/sbin/MAKEDEV, all the same, so I tried

  /snap/core/6350/sbin/MAKEDEV -n -v video

  It would have created over a hundred devices videoXX, radioXX, vtxXX, vbiXX. Those devices didn’t exist yet, so it seemed harmless to try it.

  rm /dev/video0; /snap/core/6350/sbin/MAKEDEV video

  That rebuilt /dev/video0, but "No such device" remains, from cat or ffmpeg.

  No decklink

  ffmpeg -f decklink ... fails with Unknown input format: 'decklink'.

  Neither black nor deck nor link is mentioned by ffmpeg -devices (fbdev, lavfi, oss, v4l2) and ffmpeg -formats (about 350), either for Ubuntu’s own version 3.4.4-0ubuntu0.18.04.1, or for version N-93330-g7ff89574c7 compiled from source on 2019 Mar 13 :

  git clone https://git.ffmpeg.org/ffmpeg.git ffmpeg
  
  cd ffmpeg
  
  ./configure --enable-nonfree --disable-doc --disable-w32threads --enable-pthreads

  (Although ./configure --help mentions --enable-decklink, using that yielded "ERROR : DeckLinkAPI.h not found." updatedb && locate DeckLinkAPI.h finds no file with that name, either.)

  The DeckLink PCI card is recognized by hwinfo and lspci.

  lsmod reports the loaded modules blackmagic and blackmagic_io.

  Maybe the PCI card is installed ok, but ffmpeg just can’t reach it because I can’t configure it for that.

  Edit : Rebooting didn’t fix anything.

• Anomalie #4495 (Nouveau) : migration 3.2.7 vers 3.3.0

  24 mai 2020, par josiane aletto

  test 1-
  j’ai installée en local un site qui était en SPIP 3.2.7 [24473] pour le migrer en SPIP 3.3.0-dev [24578].
  fichier mesoptions.php avec
  

  <span class="CodeRay"><span class="predefined">define</span>(<span class="string"><span class="delimiter">'</span><span class="content">_IMG_MAX_HEIGHT</span><span class="delimiter">'</span></span>,<span class="integer">1200</span>); <span class="comment">// largeur en pixels</span>
  <span class="predefined">define</span>(<span class="string"><span class="delimiter">'</span><span class="content">_IMG_MAX_WIDTH</span><span class="delimiter">'</span></span>, <span class="integer">1024</span>);  <span class="comment">// hauteur en pixels</span>
  <span class="predefined">define</span>(<span class="string"><span class="delimiter">'</span><span class="content">_IMG_MAX_SIZE</span><span class="delimiter">'</span></span>,  <span class="integer">650</span>);   <span class="comment">// taille en kilo-octets</span>
  </span>
  Télécharger

  
  Des logos de taille superieure a _IMG_MAX_SIZE’, 650 ne sont plus dans IMG Pas non plus dans logo_erreur non plus.
  par exemple rubon3 : 1630 × 648 pixels
  Plugins :
  Adaptive Images 1.9.2 -
  Agenda 3.26.0 -
  API de vérification 1.8.1 - stable
  Centre image 0.10.4 - dev
  Couleur de rubrique 2.3.8
  Facteur 3.6.2 - stable
  Formidable 3.34.3 - stable
  Insérer Modèles 1.3.3 - stable
  Massicot 0.8.1 -
  Mini Calendrier 2.4.1 - stable
  oEmbed 2.0.10 - stable
  Owl Carousel 1.0.18
  Carousel responsive avec support du multi-touch.
  Palette 4.0.7
  pdf.js 0.6.3
  Picto mod avec FontAwesome 2.1.0
  Saisies pour formulaires 3.11.1
  SPIP Bonux 3.4.6
  YAML 2.0.10
  test2
  Pour mieux voir J’ai recommencé installation /migration en désinstallant le plugin massicot et en le supprimant du repertoire plugin et en mettant dans mes_options.php
  define(’_IMG_MAX_HEIGHT’,800) ; // largeur en pixels
  define(’_IMG_MAX_WIDTH’, 500) ; // hauteur en pixels
  define(’_IMG_MAX_SIZE’, 400) ; // taille en kilo-octets

  je constate ; que les logos de taille >400Ko sont présent mais retaillé, rubon3 qui avait 1630 × 648 pixels a maintenant à 500 × 199 pixels 221 ko dans logo/IMG alors qu’il n’ y a pas massicot.
  si je supprime ce rubon3 par logo de la rubrique et télécharge l’image originale j’obtiens une image retaillé avec du noir en plus. mais si je clique dessus l’image est retaillée mais ok et elle est bien en 500*199 dans IMG sans le noir.

  • les images migrées ont bien gardées leurs dimensions*.

  test3
  je telecharge le logo rubon3 de 1630 × 648 pixels comme un document d’un article —> il est enregistré directement en 500 × 199 pixels 221 ko . Ce mécanisme a changé, en mieux, car dans la version 3.2 j’avais un message "Les images doivent obligatoirement faire moins de 650 ko (ce fichier fait 847.5 ko)".