Recherche avancée

Médias (1)

Mot : - Tags -/bug

Autres articles (42)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 is the first MediaSPIP stable release.
    Its official release date is June 21, 2013 and is announced here.
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

Sur d’autres sites (6244)

  • Unresolved externals with statically built ffmpeg on Windows

    7 juillet 2013, par user1764961

    I built ffmpeg 1.2.1 as a static lib - x64, debug. And I tried to open one of my older projects that links against it. After modifying some changed APIs and similar in my source, it compiled fine, but I have major problems with linking.

    EDITED : the complete latest build output :

    1>libavformat.a(mov.o) : error LNK2019: unresolved external symbol __imp__gmtime64 referenced in function mov_read_mvhd
    
1>libavutil.a(parseutils.o) : error LNK2001: unresolved external symbol __imp__gmtime64
    
1>libavformat.a(os_support.o) : error LNK2019: unresolved external symbol __imp__wsopen referenced in function ff_win32_open
    
1>libavcodec.a(pthread.o) : error LNK2019: unresolved external symbol __imp__beginthreadex referenced in function ff_thread_init
    
1>libavcodec.a(frame_thread_encoder.o) : error LNK2001: unresolved external symbol __imp__beginthreadex
    
1>libavutil.a(parseutils.o) : error LNK2019: unresolved external symbol __imp__localtime64 referenced in function av_parse_time
    
1>libavutil.a(parseutils.o) : error LNK2019: unresolved external symbol __imp__time64 referenced in function av_parse_time
    
1>libavutil.a(parseutils.o) : error LNK2019: unresolved external symbol __imp__mktime64 referenced in function av_parse_time
    
1>libmingwex.a(lib64_libmingwex_a-mingw_output_format.o) : error LNK2019: unresolved external symbol __mingw_get_msvcrt_handle referenced in function __mingw_set_output_format
    
1>libmingwex.a(lib64_libmingwex_a-mingw_get_codepage.o) : error LNK2001: unresolved external symbol __mingw_get_msvcrt_handle

    What am I doing wrong ?
    What am I missing here ?
    Does ffmpeg even work today on Windows platform as a static lib, or it becomes less functional on Windows with each new version ?

  • How can I manually pass a SoundCloud track duration to HTML5 audio ?

    30 janvier 2016, par thebaer

    I’m currently using a stripped-down version of Canvas.fm to convert SoundCloud mp3 streams into ogg streams using Node and ffmpeg, to support the audio element in ogg-playing browsers like Firefox. My problem is : while the duration is correctly set for SoundCloud’s mp3 streams, the ogg stream gives an indefinite duration in the player ; I want the actual duration to show up.

    I noticed when requesting a SoundCloud mp3 stream, I get a canceled request, a pending one, and then a 206 Partial Content response. My Node app does similar redirects, without as many headers, since I’m sending them myself.

    Should I be trying to calculate/forge the Content-Length or Content-Range headers ? Or does HTML5 audio get the duration from mp3 metadata/ID3 information ? If I can get the duration from SoundCloud’s API (which I can), how can I pass this to the client in my ogg stream ?

  • jpeg2000 : Validate block lengthinc

    1er juillet 2013, par Luca Barbato
    jpeg2000 : Validate block lengthinc

    Currently we are using an array with a static data size.
    

    Similar to a patch with the same purpose by Michael Niedermayer.
    

    Found-by : Mateusz "j00ru" Jurczyk and Gynvael Coldwind
    

    Signed-off-by : Luca Barbato <lu_zero@gentoo.org>
    • [DBH] libavcodec/jpeg2000dec.c

Navigation