Recherche avancée
Autres articles (17)
-
Use, discuss, criticize
13 avril 2011, parTalk 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. -
MediaSPIP Player : problèmes potentiels
22 février 2011, parLe lecteur ne fonctionne pas sur Internet Explorer
Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...) -
MediaSPIP Player : les contrôles
26 mai 2010, parLes contrôles à la souris du lecteur
En plus des actions au click sur les boutons visibles de l’interface du lecteur, il est également possible d’effectuer d’autres actions grâce à la souris : Click : en cliquant sur la vidéo ou sur le logo du son, celui ci se mettra en lecture ou en pause en fonction de son état actuel ; Molette (roulement) : en plaçant la souris sur l’espace utilisé par le média (hover), la molette de la souris n’exerce plus l’effet habituel de scroll de la page, mais diminue ou (...)
Sur d’autres sites (5798)
-
android ffmpeg concatenate multiple m4a files
19 janvier 2017, par margieI need help in concatenating audio files in android using ffmpeg
My source of audio files is from recording result (container .m4a, encoder aac).
When I concat them using ffmpeg, the result file length(duration) is only of the 1st file.ie. FileA length = 1:00, FileB length = 0:14. Expected FileResult length = 1:14, but actual result is 1:00).
I also tried the command I used in desktop ffmpeg and it give the same result.
This is my command :
[-i,
concat:storage/emulated/0/Music/Recordings/REC_20170119_162023.m4a|/storage/emulated/0/Music/Recordings/REC_20170119_162042.m4a,
-c,
copy,
/storage/emulated/0/Music/Recordings/REC_20170119_162047.m4a]and the ffmpeg result is :
D/FFmpeg: onSuccess: ffmpeg version n3.0.1 Copyright (c) 2000-2016 the FFmpeg developers
built with gcc 4.8 (GCC)
configuration: --target-os=linux --cross-prefix=/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi- --arch=arm --cpu=cortex-a8 --enable-runtime-cpudetect --sysroot=/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-libass --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-fontconfig --enable-pthreads --disable-debug --disable-ffserver --enable-version3 --enable-hardcoded-tables --disable-ffplay --disable-ffprobe --enable-gpl --enable-yasm --disable-doc --disable-shared --enable-static --pkg-config=/home/vagrant/SourceCode/ffmpeg-android/ffmpeg-pkg-config --prefix=/home/vagrant/SourceCode/ffmpeg-android/build/armeabi-v7a --extra-cflags='-I/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all' --extra-ldflags='-L/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-libs='-lpng -lexpat -lm' --extra-cxxflags=
libavutil 55. 17.103 / 55. 17.103
libavcodec 57. 24.102 / 57. 24.102
libavformat 57. 25.100 / 57. 25.100
libavdevice 57. 0.101 / 57. 0.101
libavfilter 6. 31.100 / 6. 31.100
libswscale 4. 0.100 / 4. 0.100
libswresample 2. 0.101 / 2. 0.101
libpostproc 54. 0.100 / 54. 0.100
[mov,mp4,m4a,3gp,3g2,mj2 @ 0xf58d7000] Found duplicated MOOV Atom. Skipped it
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'concat:/storage/emulated/0/Music/Recordings/REC_20170119_162023.m4a|/storage/emulated/0/Music/Recordings/REC_20170119_162042.m4a':
Metadata:
com.android.version: 6.0
major_brand : mp42
minor_version : 0
creation_time : 2017-01-19 09:20:30
compatible_brands: isommp42
Duration: 00:00:07.18, start: 0.000000, bitrate: 21 kb/s
Stream #0:0(eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 10 kb/s (default)
Metadata:
creation_time : 2017-01-19 09:20:30
handler_name : SoundHandle
Output #0, ipod, to '/storage/emulated/0/Music/Recordings/REC_20170119_162047.m4a':
Metadata:
com.android.version: 6.0
major_brand : mp42
minor_version : 0
compatible_brands: isommp42
encoder : Lavf57.25.100
Stream #0:0(eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, mono, 10 kb/s (default)
Metadata:
creation_time : 2017-01-19 09:20:30
handler_name : SoundHandle
Stream mapping:
Stream #0:0 -> #0:0 (copy)
Press [q] to stop, [?] for help
size= 11kB time=00:00:07.17 bitrate= 13.1kbits/s speed= 230x
video:0kB audio:10kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 20.181986%also tried this command, but still give the same result
[-y, -i, /storage/emulated/0/Music/Recordings/REC_20170119_165440.m4a, -i, /storage/emulated/0/Music/Recordings/REC_20170119_165445.m4a, -acodec, aac, /storage/emulated/0/Music/Recordings/REC_20170119_165448.m4a] -
tcp : set socket buffer sizes before listen/connect/accept
9 janvier 2017, par Joel Cunninghamtcp : set socket buffer sizes before listen/connect/accept
From e24d95c0e06a878d401ee34fd6742fcaddeeb95f Mon Sep 17 00:00:00 2001
From : Joel Cunningham <joel.cunningham@me.com>
Date : Mon, 9 Jan 2017 13:37:51 -0600
Subject : [PATCH] tcp : set socket buffer sizes before listen/connect/acceptAttempting to set SO_RCVBUF and SO_SNDBUF on TCP sockets after connection
establishment is incorrect and some stacks ignore the set call on the socket at
this point. This has been observed on MacOS/iOS. Windows 7 has some peculiar
behavior where setting SO_RCVBUF after applies only if the buffer is increasing
from the default while decreases are ignored. This is possibly how the incorrect
usage has gone unnoticedUnix Network Programming Vol. 1 : The Sockets Networking API (3rd edition, seciton 7.5) :
"When setting the size of the TCP socket receive buffer, the ordering of the
function calls is important. This is because of TCP’s window scale option,
which is exchanged with the peer on SYN segments when the connection is
established. For a client, this means the SO_RCVBUF socket option must be
set before calling connect. For a server, this means the socket option must
be set for the listening socket before calling listen. Setting this option
for the connected socket will have no effect whatsoever on the possible window
scale option because accept does not return with the connected socket until
TCP’s three-way handshake is complete. This is why the option must be set on
the listening socket. (The sizes of the socket buffers are always inherited from
the listening socket by the newly created connected socket)"Signed-off-by : Joel Cunningham <joel.cunningham@me.com>
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc> -
Merge commit 'bd6496fa07e32fd09ceb79404f9af43df959bcb2'
5 mai 2017, par Clément BœschMerge commit 'bd6496fa07e32fd09ceb79404f9af43df959bcb2'
* commit 'bd6496fa07e32fd09ceb79404f9af43df959bcb2' :
interplayvideo : Convert to the new bitstream reader
adx : Convert to the new bitstream reader
dvbsubdec : Convert to the new bitstream reader
motionpixels : Convert to the new bitstream readerThis merge is a noop, see
http://ffmpeg.org/pipermail/ffmpeg-devel/2017-April/209609.htmlMerged-by : Clément Bœsch <u@pkh.me>
Syndiquer tout le site
