Recherche avancée

Sur d’autres sites (10724)

• avformat/async : Fix bug where async could not recover after seek to eof

  11 novembre 2015, par Bryan Huh

  avformat/async : Fix bug where async could not recover after seek to eof
  When async issues its inner seek via ffurl_seek, it treats failures as
  
  EOF being reached. This is not consistent with the behavior of other
  
  protocols (e.g. http, cache) which continue to tolerate reads after
  
  failed seeks, and therefore does not interact correctly with them.
  A common pattern where this manifests itself is where avio_seek is
  
  called with pos to be the end-of-file - the http range-request would
  
  fail here, and async would set io_eof_reached to 1. The background
  
  thread would then refuse to read more bytes, and subsequent reads would
  
  only empty the fifo and end in an error.
  Presumably the code may have expected subsequent seeks to unset the
  
  io_eof_reached but this is not guaranteed to be true - a subsequent seek
  
  that lands in the AVIOContext’s buffer (the fact that the
  
  previously-failed avio_seek leaves the AVIOContext’s buffer intact also
  
  suggests that follow-up reads are expected to be tolerated) would not be
  
  issued to the async_seek function, and when that buffer is drained only
  
  async_read calls would follow, leading to the same error just described.
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavformat/async.c

• difference between using SDL and using media player class that is videoview

  3 juin 2019, par Whoami

  I have been surfing the net for some time to get basic understanding of media framework in android. As part of this, to display video we have media player class or video view component which can easily display the video. When we have such solution provided by the framework itself, then why there are few components avaiable like SDL [ Simple Direct Media Layer], which claims the same functionality as video view ?

  How both are different ?

• StdioURLProtocolHandlerTest failed while Xuggler build under Windows

  26 mars 2012, par Dims

  Trying to build Xuggler under Windows. My Windows is x64 Win 7 prof, but all used libraries are 32bit. I am running build procedure under MinGW/MSys, from under Msys shell with the followinf script :

  #!/bin/sh
  
  export JAVA_HOME=/C/Program\ Files\ \(x86\)/Java/jdk1.6.0_25
  
  export XUGGLE_HOME=/C/Xuggler
  
  
  
  PATH=$XUGGLE_HOME/bin:/C/Program\ Files\ \(x86\)/Java/jdk1.6.0_25/bin:/d/APPS/msysgit/msysgit/bin/git:/D/APPS/MinGW/bin:/bin:/D/APPS/apa    che-ant-1.8.2/bin:/D/Users/Dims/Design/MinGW/Util:$PATH
  
  ant -Dbuild.m64=no run-tests

  The error follows

   [exec] Running 6 tests..
  
   [exec] In StdioURLProtocolHandlerTest::testRead:
  
   [exec] ../../../../../../../../../test/csrc/com/xuggle/xuggler/io/StdioURLProtocolHandlerTest.cpp:108: Error: Expected (4546420 == totalBytes), found (4546420 != 1042)
  
   [exec] In StdioURLProtocolHandlerTest::testReadWrite:
  
   [exec] ../../../../../../../../../test/csrc/com/xuggle/xuggler/io/StdioURLProtocolHandlerTest.cpp:185: Error: Expected (4546420 == totalBytes), found (4546420 != 1042)
  
   [exec] In StdioURLProtocolHandlerTest::testSeek:
  
   [exec] ../../../../../../../../../test/csrc/com/xuggle/xuggler/io/StdioURLProtocolHandlerTest.cpp:139: Error: Expected (4546420 == totalBytes), found (4546420 != 1042)
  
   [exec] .
  
   [exec] Failed 3 of 6 tests
  
   [exec] Success rate: 50%
  
   [exec] FAIL: xugglerioTestStdioURLProtocolHandler.exe

  My questions is : did anybody did this on Windows and did he/she have this test passed ? :)

  UPDATE 1

  The test code is follows :

  int32_t totalBytes = 0;
  
  do {
  
      unsigned char buf[2048];
  
      retval = handler->url_read(buf, (int)sizeof(buf));
  
      if (retval > 0)
  
           totalBytes+= retval;
  
  } while (retval > 0);
  
  VS_TUT_ENSURE_EQUALS("", 4546420, totalBytes);

  While the url_read code is follows :

  int
  
  StdioURLProtocolHandler :: url_read(unsigned char* buf, int size)
  
  {
  
      if (!mFile)
  
          return -1;
  
      return (int) fread(buf, 1, size, mFile);
  
  }

  I don't understand, under what circumstances it can return 1042 ??? May be 64 bits play here somehow ?

  UPDATE 2

  I printed out filename used and it was

  d:/......./../../../test/fixtures/testfile.flv

  the path is correct, but started with d:/ not with /d/

  Can this play a role under Msys ?