Recherche avancée

Médias (2)

Mot : - Tags -/doc2img

Autres articles (46)

  • Gestion générale des documents

    13 mai 2011, par

    MédiaSPIP ne modifie jamais le document original mis en ligne.
    Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
    Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • 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 (9931)

  • How to build ffmpeg as a Position independent executable (PIE) or PIC on Android ?

    22 avril 2016, par Parth Doshi

    I have checked out the latest source of ffmpeg from the official website. I now want to compile and build ffmpeg as a position independent executable.

    Here is what my configure command looks like

    ./configure --prefix=/usr/local --enable-gpl --enable-pic --enable-nonfree --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265

    I have added the option --enable-pic to make it a PIE. However when the build process completes successfully and when I do a hardening check as follows then I get below output

    hardening-check ffmpeg

    ffmpeg:
    
Position Independent Executable: no, normal executable!
    
Stack protected: yes
    
Fortify Source functions: yes (some protected functions found)
    
Read-only relocations: yes
    
Immediate binding: no, not found!

    This tells me that ffmpeg is still not a PIE. Can anyone tell me what am I missing here ? Is there any other changes that need to be done for adding PIE support.

  • How to fix this FFMPEG command to record audio as well ?

    19 mai 2018, par James Kowalski

    I am trying to fix this FFMPEG command to record audio.

    I have tried using the parts recommended on the official stackoverflow site but they didn’t work

    Orignal Command

    ffmpeg_stream = '/usr/bin/ffmpeg -f x11grab -s 1280x720 -r 24 -i :%d+nomouse -c:v libx264 -preset superfast -pix_fmt yuv420p -s 1280x720 -threads 0 -f flv "%s"' % (xvfb.new_display, info['destination'])

    Command with attempted audio

    ffmpeg_stream = '/usr/bin/ffmpeg -f x11grab -s 1280x720 -r 24 -i :%d+nomouse -c:v libx264 -preset superfast -pix_fmt yuv420p -s 1280x720 -threads 0 -f alsa -ac 2 -i hw:0 -f flv "%s"' % (xvfb.new_display, info['destination'])

  • SharedArrayBuffer for ffmpeg not working with React-Native

    31 août 2022, par Peter Garcia

    I am currently working on a React Native App using ffmpeg.wasm

    


    but for some reason, SharedArrayBuffer is still not working. My React version is "react" : "17.0.2", and React-dom is "17.0.2",. My Chrome version is Version 104.0.5112.101 (Official Build) (arm64)

    


    I've been racking my brain about why this isn't working on my React Native app since I did a test app and it works there but on this app, it doesn't.

    


    I am getting this error whenever I run ffmpeg.wasm :

    


    Uncaught (in promise) ReferenceError: SharedArrayBuffer is not defined
at aa35944d-451a-411f-bf18-4e42f7bbceb0:22:175
at Object.load (createFFmpeg.js:64:1)


    


    I cannot use Cross-Origin Opener headers :

    


    Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Embedder-Policy: require-corp


    


    because our app calls from a lot of outside APIs and it breaks them.

    


    Any help would be greatly appreciated.

    


Navigation