Recherche avancée

Médias (91)

Autres articles (52)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

Sur d’autres sites (10908)

  • FFplay : WASAPI can't initialize audio client (FFmpeg 3.4 binaries)

    9 juillet 2022, par fve

    I am trying to playback a stream that is multicasted over RTP using ffplay on Windows 7 64 bits.
The computer that serves the audio over RTP runs :

    



    ffmpeg -re -f dshow -audio_buffer_size 15 -ac 1 -i audio="Mic in at front Mic-in (Realtek" -ar 8k -acodec pcm_alaw -vn -f rtp rtp://127.0.0.1:5000


    



    The client runs :

    



    ffplay rtp://127.0.0.1:5000


    



    While this was working correctly in release 3.3, release 3.4 fails with this error :

    



    SDL_OpenAudio (1 channels, 8000 Hz): WASAPI can't initialize audio client: CoInitialize has not been called.

No more combinations to try, audio open failed
Failed to open file 'rtp://127.0.0.1:5000' or configure filtergraph


    



    Anyone has an idea of whats going on ?

    



    Thanks

    



    UPDATE #1 :

    



    A workaround is to specify an alternate output driver.
Set SDL_AUDIODRIVER environment variable value to the driver you want to use.
Under windows 7, directsound and winmm both solved my issue.

    


  • ffprobe : Rename Audio Service Type 'type' field to 'service_type'

    2 août 2021, par Derek Buitenhuis
    ffprobe : Rename Audio Service Type 'type' field to 'service_type'

    677a030b26045acb50353d7954ae984ceefcd807 introduced more printable
    
side data types in ffprobe, however the Audio Service Type side data
    
'type' field that was introduced aliases an existing field of the same
    
name within the side data array, which can lead to JSON output like :
    

        "side_data_list" : [
    
        
    
            "side_data_type" : "Audio Service Type",
    
            "type" : 0
    
            ,
    
        
    
            "side_data_type" : "Stereo 3D",
    
            "type" : "side by side",
    
            "inverted" : 1
    
        
    
    ]
    

    This, while technically valid JSON, is considered bad practice, since it
    
forces all downstream users to manually parse it and check all types ;
    
it makes simple deserialization impossible. Worse, in som loosely
    
type languages, it can lead to silent bugs if exising code assumed
    
it was a different type.
    

    As such, rename this second "type" field to "service_type".
    

    Signed-off-by : Derek Buitenhuis <derek.buitenhuis@gmail.com>
    • [DH] fftools/ffprobe.c
    • [DH] tests/ref/fate/hls-fmp4_ac3

  • svq3 : make slice type value unsigned to match svq3_get_ue_golomb return type

    8 décembre 2012, par Janne Grunau

    svq3 : make slice type value unsigned to match svq3_get_ue_golomb return type

Navigation