Recherche avancée

Médias (0)

Mot : - Tags -/flash

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (92)

  • L’utiliser, en parler, le critiquer

    10 avril 2011

    La première attitude à adopter est d’en parler, soit directement avec les personnes impliquées dans son développement, soit autour de vous pour convaincre de nouvelles personnes à l’utiliser.
    Plus la communauté sera nombreuse et plus les évolutions seront rapides ...
    Une liste de discussion est disponible pour tout échange entre utilisateurs.

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

Sur d’autres sites (10870)

  • 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 ?

  • Revision 7798aef50b : enable build on windows with msvc Change-Id : I34057b87d9713dc819b8c69990dd1408b

    9 novembre 2012, par Yaowu Xu

    Changed Paths : Modify /build/x86-msvs/obj_int_extract.bat enable build on windows with msvc Change-Id : I34057b87d9713dc819b8c69990dd1408b8c79342

  • wtvenc : output third video pts in timestamp chunk (this is what Microsoft Windows...

    7 novembre 2012, par Peter Ross

    wtvenc : output third video pts in timestamp chunk (this is what Microsoft Windows...