
Recherche avancée
Autres articles (48)
-
Qu’est ce qu’un masque de formulaire
13 juin 2013, parUn masque de formulaire consiste en la personnalisation du formulaire de mise en ligne des médias, rubriques, actualités, éditoriaux et liens vers des sites.
Chaque formulaire de publication d’objet peut donc être personnalisé.
Pour accéder à la personnalisation des champs de formulaires, il est nécessaire d’aller dans l’administration de votre MediaSPIP puis de sélectionner "Configuration des masques de formulaires".
Sélectionnez ensuite le formulaire à modifier en cliquant sur sont type d’objet. (...) -
La file d’attente de SPIPmotion
28 novembre 2010, parUne 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 (...) -
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 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 (3256)
-
video uploading from app using ffmpeg showing error
9 juillet 2020, par Dhananjay AcharyaI 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.


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


when i run in a real device logcat details


2020-07-09 12:48:14.240 5226-7065/com.mik I/OMXClient: MuxOMX ctor
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.
2020-07-09 12:48:14.377 5226-5857/com.mik D/AudioManager: getStreamVolume isRestricted mode = 0
2020-07-09 12:48:14.401 5226-7067/com.mik D/AudioManager: getStreamVolume isRestricted mode = 0
2020-07-09 12:48:14.468 5226-7065/com.mik E/ACodec: [OMX.qcom.video.encoder.avc] storeMetaDataInBuffers (output) failed w/ err -1010
2020-07-09 12:48:14.468 5226-7065/com.mik I/ExtendedACodec: setupVideoEncoder()
2020-07-09 12:48:14.469 5226-7065/com.mik W/ACodec: do not know color format 0x7fa30c04 = 2141391876
2020-07-09 12:48:14.471 5226-7065/com.mik W/ACodec: do not know color format 0x7f000789 = 2130708361
2020-07-09 12:48:14.521 5226-7065/com.mik I/ACodec: setupAVCEncoderParameters with [profile: Baseline] [level: Level1]
2020-07-09 12:48:14.543 5226-7065/com.mik I/ACodec: [OMX.qcom.video.encoder.avc] cannot encode HDR static metadata. Ignoring.
2020-07-09 12:48:14.543 5226-7065/com.mik I/ACodec: setupVideoEncoder succeeded
2020-07-09 12:48:14.544 5226-7065/com.mik I/ExtendedACodec: [OMX.qcom.video.encoder.avc] configure, AMessage : AMessage(what = 'conf', target = 13) = {
 int32_t width = 720
 int32_t height = 1280
 int32_t bitrate = 2073600
 string mime = "video/avc"
 int32_t frame-rate = 30
 int32_t i-frame-interval = 1
 int32_t color-format = 2130708361
 int32_t encoder = 1
 }
2020-07-09 12:48:14.549 5226-7065/com.mik W/ACodec: do not know color format 0x7f000789 = 2130708361
2020-07-09 12:48:14.556 5226-6625/com.mik D/FA: Connected to remote service
2020-07-09 12:48:14.557 5226-6625/com.mik V/FA: Processing queued up service tasks: 1
2020-07-09 12:48:14.877 5226-7104/com.mik I/OMXClient: MuxOMX ctor
2020-07-09 12:48:14.946 5226-7103/com.mik I/MediaCodec: [OMX.qcom.video.decoder.avc] setting surface generation to 5351428
2020-07-09 12:48:14.948 5226-7104/com.mik I/ExtendedACodec: setupVideoDecoder()
2020-07-09 12:48:14.948 5226-7104/com.mik I/ExtendedACodec: vpp-enable search is 0 and value is 0
2020-07-09 12:48:14.955 5226-7104/com.mik I/ExtendedACodec: Decoder will be in frame by frame mode
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
2020-07-09 12:48:15.065 5226-7028/com.mik D/resp: 0
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
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))

2020-07-09 12:48:15.469 5226-7028/com.mik V/MuxRender: Added track #0 with video/avc to muxer
2020-07-09 12:48:15.469 5226-7028/com.mik V/MuxRender: Added track #1 with audio/mp4a-latm to muxer
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
2020-07-09 12:48:15.647 5226-7028/com.mik V/MuxRender: Output format determined, writing 15 samples / 6054 bytes to muxer.
2020-07-09 12:48:15.647 5226-7140/com.mik I/MPEG4Writer: setStartTimestampUs: 0
2020-07-09 12:48:15.647 5226-7140/com.mik I/MPEG4Writer: Earliest track starting time: 0
2020-07-09 12:48:15.650 5226-7139/com.mik I/MPEG4Writer: setStartTimestampUs: 0
2020-07-09 12:48:27.318 5226-7028/com.mik D/MPEG4Writer: Video track stopping
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
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
2020-07-09 12:48:27.326 5226-7140/com.mik I/MPEG4Writer: Audio track drift time: 0 us
2020-07-09 12:48:27.327 5226-7028/com.mik D/MPEG4Writer: Audio track stopped
2020-07-09 12:48:27.327 5226-7028/com.mik D/MPEG4Writer: Duration from tracks range is [14850005, 14883989] us
2020-07-09 12:48:27.327 5226-7028/com.mik D/MPEG4Writer: Stopping writer thread
2020-07-09 12:48:27.329 5226-7138/com.mik D/MPEG4Writer: 1 chunks are written in the last batch
2020-07-09 12:48:27.329 5226-7028/com.mik D/MPEG4Writer: Writer thread stopped
2020-07-09 12:48:27.332 5226-7028/com.mik I/MPEG4Writer: The mp4 file will not be streamable.
2020-07-09 12:48:27.378 5226-7104/com.mik E/BufferQueueProducer: [SurfaceTexture-1-5226-2] cancelBuffer: BufferQueue has been abandoned
2020-07-09 12:48:27.465 5226-7028/com.mik D/MPEG4Writer: Video track stopping
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) }
2020-07-09 12:48:27.541 5226-6625/com.mik V/FA: Recording user engagement, ms: 13774
2020-07-09 12:48:27.561 5226-6625/com.mik V/FA: Connecting to remote service
2020-07-09 12:48:27.578 5226-5857/com.mik D/AudioManager: getStreamVolume isRestricted mode = 0
2020-07-09 12:48:27.584 5226-6625/com.mik V/FA: Activity paused, time: 160261301
2020-07-09 12:48:27.652 5226-6625/com.mik V/FA: Connection attempt already in progress
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]



-
no difference between h264 and h264_cuvid
10 juillet 2020, par Ruslan AblyazovI use libav to decode an RTSP stream. I tried two code options : with auto codec selection and with hardcoded codec.


pCodec = avcodec_find_decoder (pFormatCtx->streams[p_InputVideoStreamIndex]->codecpar->codec_id);
//pCodec = avcodec_find_decoder_by_name ("h264_cuvid");

LOG (info) << "Video codec name" << pCodec->name << ". Full name:" << (pCodec->long_name? PCodec->long_name: "<null>");
</null>


The avcodec_find_decoder() function returns h264 codec. The problem is that the speed and load on the CPU when using h264 is no different from h264_cuvid. What could be the reason ? When I use h264_cuvid, the video card is loaded by 2-3% more.


Video stream : 1920x1080 25 FPS (main and high profile).
Video card : NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1).
Processor : Intel (R) Core (TM) i5-8400 CPU @ 2.80GHz.


Compilation config ffmpeg :


ffmpeg version 4.3 Copyright (c) 2000-2020 the FFmpeg developers
 built with gcc 8 (Debian 8.3.0-6)
 configuration: --enable-gpl --enable-ladspa --enable-libpulse --enable-libsoxr --enable-libspeex --enable-avfilter --enable-avresample --enable-postproc --enable-pthreads --enable -libass --enable-libfreetype --enable-libmp3lame --enable-nonfree --disable-ffplay --enable-libxvid --enable-cuda --enable-cuda-nvcc --enable-cuda-sdk --enable- cuvid --enable-nvenc --enable-nonfree --enable-libnpp --enable-shared --extra-cflags = -I/usr/local/cuda/include --extra-ldflags = -L/usr/local/cuda/lib64



-
Nomenclature #4519 (Nouveau) : Renommage de terminologie (blacklist / whitelist)
13 juillet 2020En lisant la compilation [PHP Annotated – June 2020](https://blog.jetbrains.com/phpstorm/2020/06/php-annotated-june-2020/) on tombe sur ce point :
[[RFC] Change terminology to ExcludeList](https://wiki.php.net/rfc/change-terminology-to-excludelist) — The topic of renaming offensive terms has not been overlooked by the PHP world either. There have been [heated discussions](https://externals.io/message/110515) in the Internals.
In the PHP core, the change affects only one thing : the configuration directive `opcache.blacklist_filename` should be renamed to `opcache.exclude_list_filename`.
Many other PHP tools have already made changes in this regard : [PHPUnit](https://github.com/sebastianbergmann/phpunit/blob/master/ChangeLog-9.3.md#930---2020-08-07), [Drupal](https://www.drupal.org/project/drupal/issues/2993575), [Xdebug](https://github.com/xdebug/xdebug/commit/63b43b51e43b794cf8cd740e54089b2b7320fbe1), [Yii](https://github.com/yiisoft/yii2/pull/18104), [Composer](https://github.com/composer/composer/pull/8957) (+ [working with non-master Git branches](https://blog.packagist.com/composer-and-default-git-branches/)).C’est certainement intéressant aussi de songer à ces renommages chez nous également, utilisés à quelques endroits.