Recherche avancée

Médias (0)

Mot : - Tags -/serveur

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

Autres articles (46)

  • Qualité du média après traitement

    21 juin 2013, par

    Le bon réglage du logiciel qui traite les média est important pour un équilibre entre les partis ( bande passante de l’hébergeur, qualité du média pour le rédacteur et le visiteur, accessibilité pour le visiteur ). Comment régler la qualité de son média ?
    Plus la qualité du média est importante, plus la bande passante sera utilisée. Le visiteur avec une connexion internet à petit débit devra attendre plus longtemps. Inversement plus, la qualité du média est pauvre et donc le média devient dégradé voire (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

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

Sur d’autres sites (8537)

  • avformat/mpegts : respect program number when merging streams

    9 juillet 2019, par Marton Balint
    avformat/mpegts : respect program number when merging streams
    

    merge_pmt_versions was not usable if multiple programs were present because
    when it was searching for candidate streams it did not make sure that the PMT was
    of the same program. This caused the streams of all programs to get merged into
    a single (garbled) program.

    This patch makes sure that the program number (service ID) is also matching
    with the old streams when parsing the PMT making the feature useful for multi
    program streams.

    This change might cause issues for single program streams if the program number
    changes, but I think it is acceptable because the goal of the option is to make
    the parsing resilient to PID changes, and that is still working as expected.

    Signed-off-by : Marton Balint <cus@passwd.hu>

    • [DH] libavformat/mpegts.c
  • video uploading from app using ffmpeg showing error

    9 juillet 2020, par Dhananjay Acharya

    I am trying to implement video upload from app using ffmpeg. when I m trying to upload video showing this errors. sometime video upload keep on loading. any help.

    &#xA;

    sometimes app freezes and for some videos showing out of memory error

    &#xA;

    when i run in a real device logcat details

    &#xA;

    2020-07-09 12:48:14.240 5226-7065/com.mik I/OMXClient: MuxOMX ctor&#xA;2020-07-09 12:48:14.369 5226-5226/com.mik I/Choreographer: Skipped 32 frames!  The application may be doing too much work on its main thread.&#xA;2020-07-09 12:48:14.377 5226-5857/com.mik D/AudioManager: getStreamVolume isRestricted mode = 0&#xA;2020-07-09 12:48:14.401 5226-7067/com.mik D/AudioManager: getStreamVolume isRestricted mode = 0&#xA;2020-07-09 12:48:14.468 5226-7065/com.mik E/ACodec: [OMX.qcom.video.encoder.avc] storeMetaDataInBuffers (output) failed w/ err -1010&#xA;2020-07-09 12:48:14.468 5226-7065/com.mik I/ExtendedACodec: setupVideoEncoder()&#xA;2020-07-09 12:48:14.469 5226-7065/com.mik W/ACodec: do not know color format 0x7fa30c04 = 2141391876&#xA;2020-07-09 12:48:14.471 5226-7065/com.mik W/ACodec: do not know color format 0x7f000789 = 2130708361&#xA;2020-07-09 12:48:14.521 5226-7065/com.mik I/ACodec: setupAVCEncoderParameters with [profile: Baseline] [level: Level1]&#xA;2020-07-09 12:48:14.543 5226-7065/com.mik I/ACodec: [OMX.qcom.video.encoder.avc] cannot encode HDR static metadata. Ignoring.&#xA;2020-07-09 12:48:14.543 5226-7065/com.mik I/ACodec: setupVideoEncoder succeeded&#xA;2020-07-09 12:48:14.544 5226-7065/com.mik I/ExtendedACodec: [OMX.qcom.video.encoder.avc] configure, AMessage : AMessage(what = &#x27;conf&#x27;, target = 13) = {&#xA;      int32_t width = 720&#xA;      int32_t height = 1280&#xA;      int32_t bitrate = 2073600&#xA;      string mime = "video/avc"&#xA;      int32_t frame-rate = 30&#xA;      int32_t i-frame-interval = 1&#xA;      int32_t color-format = 2130708361&#xA;      int32_t encoder = 1&#xA;    }&#xA;2020-07-09 12:48:14.549 5226-7065/com.mik W/ACodec: do not know color format 0x7f000789 = 2130708361&#xA;2020-07-09 12:48:14.556 5226-6625/com.mik D/FA: Connected to remote service&#xA;2020-07-09 12:48:14.557 5226-6625/com.mik V/FA: Processing queued up service tasks: 1&#xA;2020-07-09 12:48:14.877 5226-7104/com.mik I/OMXClient: MuxOMX ctor&#xA;2020-07-09 12:48:14.946 5226-7103/com.mik I/MediaCodec: [OMX.qcom.video.decoder.avc] setting surface generation to 5351428&#xA;2020-07-09 12:48:14.948 5226-7104/com.mik I/ExtendedACodec: setupVideoDecoder()&#xA;2020-07-09 12:48:14.948 5226-7104/com.mik I/ExtendedACodec: vpp-enable search is 0 and value is 0&#xA;2020-07-09 12:48:14.955 5226-7104/com.mik I/ExtendedACodec: Decoder will be in frame by frame mode&#xA;2020-07-09 12:48:14.980 5226-7104/com.mik D/SurfaceUtils: set up nativeWindow 0x7f84499e10 for 352x640, color 0x7fa30c06, rotation 0, usage 0x2002900&#xA;2020-07-09 12:48:15.065 5226-7028/com.mik D/resp: 0&#xA;2020-07-09 12:48:15.072 5226-7104/com.mik D/SurfaceUtils: set up nativeWindow 0x7f84499e10 for 352x640, color 0x7fa30c06, rotation 0, usage 0x2002900&#xA;2020-07-09 12:48:15.152 5226-7065/com.mik D/ACodec: dataspace changed to 0x10c10000 (R:2(Limited), P:3(BT601_6_625), M:3(BT601_6), T:3(SMPTE170M)) (R:2(Limited), S:1(BT709), T:3(SMPTE_170M))&#xA;&#xA;2020-07-09 12:48:15.469 5226-7028/com.mik V/MuxRender: Added track #0 with video/avc to muxer&#xA;2020-07-09 12:48:15.469 5226-7028/com.mik V/MuxRender: Added track #1 with audio/mp4a-latm to muxer&#xA;2020-07-09 12:48:15.646 5226-7028/com.mik I/MPEG4Writer: limits: 4294967295/0 bytes/us, bit rate: -1 bps and the estimated moov size 3195 bytes&#xA;2020-07-09 12:48:15.647 5226-7028/com.mik V/MuxRender: Output format determined, writing 15 samples / 6054 bytes to muxer.&#xA;2020-07-09 12:48:15.647 5226-7140/com.mik I/MPEG4Writer: setStartTimestampUs: 0&#xA;2020-07-09 12:48:15.647 5226-7140/com.mik I/MPEG4Writer: Earliest track starting time: 0&#xA;2020-07-09 12:48:15.650 5226-7139/com.mik I/MPEG4Writer: setStartTimestampUs: 0&#xA;2020-07-09 12:48:27.318 5226-7028/com.mik D/MPEG4Writer: Video track stopping&#xA;2020-07-09 12:48:27.318 5226-7139/com.mik I/MPEG4Writer: Received total/0-length (401/1) buffers and encoded 401 frames. - Video&#xA;2020-07-09 12:48:27.326 5226-7140/com.mik I/MPEG4Writer: Received total/0-length (641/1) buffers and encoded 641 frames. - Audio&#xA;2020-07-09 12:48:27.326 5226-7140/com.mik I/MPEG4Writer: Audio track drift time: 0 us&#xA;2020-07-09 12:48:27.327 5226-7028/com.mik D/MPEG4Writer: Audio track stopped&#xA;2020-07-09 12:48:27.327 5226-7028/com.mik D/MPEG4Writer: Duration from tracks range is [14850005, 14883989] us&#xA;2020-07-09 12:48:27.327 5226-7028/com.mik D/MPEG4Writer: Stopping writer thread&#xA;2020-07-09 12:48:27.329 5226-7138/com.mik D/MPEG4Writer: 1 chunks are written in the last batch&#xA;2020-07-09 12:48:27.329 5226-7028/com.mik D/MPEG4Writer: Writer thread stopped&#xA;2020-07-09 12:48:27.332 5226-7028/com.mik I/MPEG4Writer: The mp4 file will not be streamable.&#xA;2020-07-09 12:48:27.378 5226-7104/com.mik E/BufferQueueProducer: [SurfaceTexture-1-5226-2] cancelBuffer: BufferQueue has been abandoned&#xA;2020-07-09 12:48:27.465 5226-7028/com.mik D/MPEG4Writer: Video track stopping&#xA;2020-07-09 12:48:27.494 5226-5226/com.mik I/Timeline: Timeline: Activity_launch_request time:148842468 intent:Intent { cmp=com.mik/.Video_Recording.GallerySelectedVideo.GallerySelectedVideo_A (has extras) }&#xA;2020-07-09 12:48:27.541 5226-6625/com.mik V/FA: Recording user engagement, ms: 13774&#xA;2020-07-09 12:48:27.561 5226-6625/com.mik V/FA: Connecting to remote service&#xA;2020-07-09 12:48:27.578 5226-5857/com.mik D/AudioManager: getStreamVolume isRestricted mode = 0&#xA;2020-07-09 12:48:27.584 5226-6625/com.mik V/FA: Activity paused, time: 160261301&#xA;2020-07-09 12:48:27.652 5226-6625/com.mik V/FA: Connection attempt already in progress&#xA;2020-07-09 12:48:27.727 5226-5226/com.mik I/ExoPlayerImpl: Init d0eca9e [ExoPlayerLib/2.11.1] [oxygen, MI MAX 2, Xiaomi, 25]&#xA;

    &#xA;

  • avformat/mpegtsenc : fix PCR generation intervals

    4 août 2019, par Marton Balint
    avformat/mpegtsenc : fix PCR generation intervals
    

    PCR generation was based on counting packets for both CBR and VBR streams.
    Couting packets might have worked for CBR streams (when muxrate was specified)
    but it only took into account the packets of a service (or the packets of the
    PCR stream lately), so even that was problematic for multi program streams.

    The new code works on actual timestamps for both CBR and VBR streams. For VBR
    streams the behaviour of the old code is simulated by selecting a PCR interval
    which is the highest multiple of the frame duration but still less than 100 ms.

    It should be trivial to add support for setting the PCR interval for VBR
    streams as well in a later patch.

    The accuracy of PCR packets for CBR streams was greatly improved by preemtively
    sending them at PCR intervals even if sending the payload of another stream
    is in progress.

    This may fix these tickets :
    - #5750
    - #7524

    Signed-off-by : Marton Balint <cus@passwd.hu>

    • [DH] libavformat/mpegtsenc.c