Recherche avancée

Médias (0)

Mot : - Tags -/signalement

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

Autres articles (41)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

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

Sur d’autres sites (7478)

  • Fatal signal 11 (SIGSEGV), code 1, fault addr 0x9 in tid 31051

    20 juillet 2021, par 林聖達

    I building project ,I able login my account and it is unable to living stream .
Camera is ok. When the program is execution to Ffmpeg_init() that will be error.
I get a few of question,

    



    Question1.
E/ACDB-LOADER : Error : ACDB AudProc vol returned = -19
Error : ACDB AFE returned = -19
I don't know this error what happened.

    



    Question2.
I use addr2line (NDK-TOOLTAIONS) to debug , I get some message.
pc 0050c99c /data/app/com.cmore.youtube-2/lib/arm/libffmpeg.so (avcodec_get_context_defaults3+56)
I didn't never modify this file.

    



    10-15 18:39:17.848 31051-31051/com.cmore.youtube A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x9 in tid 31051 (m.cmore.youtube)
10-15 18:39:17.898 430-430/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
10-15 18:39:17.898 430-430/? A/DEBUG: Build fingerprint: 'htc/htc_asia_tw/htc_a51dtul:6.0.1/MMB29M/738098.3:user/release-keys'
10-15 18:39:17.898 430-430/? A/DEBUG: Revision: '0'
10-15 18:39:17.898 430-430/? A/DEBUG: ABI: 'arm'
10-15 18:39:17.898 430-430/? A/DEBUG: pid: 31051, tid: 31051, name: m.cmore.youtube >>> com.cmore.youtube <<<
10-15 18:39:17.898 430-430/? A/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x9
10-15 18:39:17.898 433-31603/? E/ACDB-LOADER: Error: ACDB AudProc vol returned = -19
10-15 18:39:17.898 433-31603/? E/ACDB-LOADER: Error: ACDB AFE returned = -19
10-15 18:39:17.908 430-430/? A/DEBUG: r0 ab36b9a0 r1 00000000 r2 00000000 r3 d6a225c0
10-15 18:39:17.908 430-430/? A/DEBUG: r4 d6a35d18 r5 00000001 r6 ab36b6f0 r7 ab36aac0
10-15 18:39:17.908 430-430/? A/DEBUG: r8 ab36b9a0 r9 00000001 sl 12c590f0 fp 000001e0
10-15 18:39:17.908 430-430/? A/DEBUG: ip 00000000 sp ffcb4778 lr d6440980 pc d644099c cpsr 200f0010
10-15 18:39:17.918 430-430/? A/DEBUG: backtrace:
10-15 18:39:17.918 430-430/? A/DEBUG: #00 pc 0050c99c /data/app/com.cmore.youtube-2/lib/arm/libffmpeg.so (avcodec_get_context_defaults3+56)


    


  • lavf : deprecate compute_pkt_fields2

    7 octobre 2015, par Anton Khirnov
    lavf : deprecate compute_pkt_fields2

    All encoders set pts and dts properly now (and have been doing that for
    
a while), so there is no good reason to do any timestamp guessing in the
    
muxer.
    

    The newly added AVStreamInternal will be later used for storing all the
    
private fields currently living in AVStream.
    • [DBH] libavformat/avformat.h
    • [DBH] libavformat/internal.h
    • [DBH] libavformat/mux.c
    • [DBH] libavformat/utils.c
    • [DBH] libavformat/version.h

  • Dreamcast Track Sizes

    1er mars 2015, par Multimedia Mike — Sega Dreamcast

    I’ve been playing around with Sega Dreamcast discs lately. Not playing the games on the DC discs, of course, just studying their structure. To review, the Sega Dreamcast game console used special optical discs named GD-ROMs, where the GD stands for “gigadisc”. They are capable of holding about 1 gigabyte of data.

    You know what’s weird about these discs ? Each one manages to actually store a gigabyte of data. Each disc has a CD portion and a GD portion. The CD portion occupies the first 45000 sectors and can be read in any standard CD drive. This area is divided between a brief data track and a brief (usually) audio track.

    The GD region starts at sector 45000. Sometimes, it’s just one humongous data track that consumes the entire GD region. More often, however, the data track is split between the first track and the last track in the region and there are 1 or more audio tracks in between. But the weird thing is, the GD region is always full. I made a study of it (click for a larger, interactive graph) :


    Dreamcast Track Sizes

    Some discs put special data or audio bonuses in the CD region for players to discover. But every disc manages to fill out the GD region. I checked up on a lot of those audio tracks that divide the GD data and they’re legitimate music tracks. So what’s the motivation ? Why would the data track be split in 2 pieces like that ?

    I eventually realized that I probably answered this question in this blog post from 4 years ago. The read speed from the outside of an optical disc is higher than the inside of the same disc. When I inspect the outer data tracks of some of these discs, sure enough, there seem to be timing-sensitive multimedia FMV files living on the outer stretches.

    One day, I’ll write a utility to take apart the split ISO-9660 filesystem offset from a weird sector.

Navigation