Recherche avancée

Sur d’autres sites (7126)

• Evolution #2995 : Améliorer la présentation de input file sur les Logos

  8 février 2014, par Franck Dalot

  Bonjour
  Test fait en SPIP 3.1.0-dev [21175]
  A la recherche des bugs de spip 3.1 :-D
  J’actualise les copies d’écrans dans le cas ou cela serait utile
  Sauf concernant Opéra la 12.16 est identique à la 12.15, donc pas de nouvelle copie

  J’ai également fait un test avec le navigateur de ma TV (samsung serie F6500), il s’agit du bloc de la médiathèque, mais c’est pareil pour les logos
  Le texte à côté du bouton est couper suivant le navigateur et sur la TV, c’est comme s’il ne comprenait pas la langue car il affiche en anglais le bouton et aucun texte à côté

• avformat_open_input crash using ffmpeg on android

  2 octobre 2019, par Timmy K

  I am writing an Android app to capture audio streams from a USB device using ffmpeg, and mux them into an m4a file. I then open the recording file to read back the audio data. The app works fine on Samsung S8 (Android 8.0) and S9 (Android 9.0). On a Moto G5+ (Android 8.1), however the app crashes inside avformat_open_input() when I try to open the recording file ; but if I restart the app and it reads the same file with the same code, it works without crashing.

  I thought maybe that I hadn’t closed the recording file properly ; or there was maybe a race condition : trying to read the file before it was written. However I have established that av_write_trailer() is called successfully and avio_closep() is called successfully before the call to avformat_open_input. I also established that the length of the file is the same just before the call to avformat_open_input() in the crash case as it is in the non-crash case.

  The code that finishes the recording :

  // AVFormatContext *mAvFormatContext
  
  // ...
  
  int ret = av_write_trailer(mAvFormatContext);
  
  if ( ret != 0 )
  
  {
  
      __android_log_print(ANDROID_LOG_DEBUG, "MyTag", "failed to write trailer %s", av_err2str( ret ) );
  
      goto fail;
  
  }
  
  
  
  ret = avio_close( mAvFormatContext->pb );
  
  if ( ret < 0 )
  
  {
  
      __android_log_print(ANDROID_LOG_DEBUG, "MyTag", "failed to avio_close %s", av_err2str( ret ) );
  
      goto fail;
  
  }
  
  
  
  avformat_free_context(mAvFormatContext);

  The call that causes a crash immediately after the above code, on a Moto 5G+ (but not Samsung S8/S9) :

  mAvFormatContext = nullptr;
  
  if ( (ret = avformat_open_input( &mAvFormatContext, filePath, 0, 0)) < 0 )
  
  {
  
      __android_log_print(ANDROID_LOG_DEBUG, "MyTag++", "Could not open input file '%s' error %s ", filePath, av_err2str(ret) );
  
      cleanup();
  
      return false;
  
  }

  Also, when the call to avformat_open_input() does not crash, there is no output in logcat from within that call. However, I’ve noticed that in the crash case there is output of what seems to be corrupted data :

  2019-09-02 09:39:14.105 19999-19999/fm.x.y D/AudioEngine: Opening '@�7���-d��@�7�' for 
  
  2019-09-02 09:39:14.106 19999-19999/fm.x.y D/AudioEngine: Setting default whitelist '<��'
  
  2019-09-02 09:39:14.106 19999-19999/fm.x.y D/AudioEngine: Probing ���d score:-1828887548 size:-1093138844
  
  2019-09-02 09:39:14.106 19999-19999/fm.x.y D/AudioEngine: Format ��� probed with size=-1093138756 and score=-1093138748
  
  (crash occurs)

  Any advice on what to look into further to investigate this problem ? Is there something I am missing when cleaning up the muxing state before I try to open the recording file for demuxing ? For simplicity I have not included the freeing of codec contexts, AVFrames and AVPackets.

• ffserver_config : fix line lengths

  3 novembre 2014, par Reynaldo H. Verdejo Pinochet

  ffserver_config : fix line lengths
  Signed-off-by : Reynaldo H. Verdejo Pinochet <reynaldo@osg.samsung.com>
  

  • [DH] ffserver_config.c