
Recherche avancée
Autres articles (13)
-
Emballe médias : à quoi cela sert ?
4 février 2011, parCe plugin vise à gérer des sites de mise en ligne de documents de tous types.
Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ; -
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. -
Other interesting software
13 avril 2011, parWe don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
We don’t know them, we didn’t try them, but you can take a peek.
Videopress
Website : http://videopress.com/
License : GNU/GPL v2
Source code : (...)
Sur d’autres sites (3084)
-
ffmpeg remove Non-Monotonous DTS frames
24 mars, par MiGu3XIs it possible to stream copy a .ts file to another .ts file by removing the Non-Monotonous DTS frames ? These frames usually also have a smaller resolution than the video I am trying to copy. I attempted this with VideoReDo but it did not work and I cannot seem to make it work.



Also, the MediaInfo for the video after remixed to Matrosks shows this :



Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L3.2
Format settings : CABAC / 2 Ref Frames
Format settings, CABAC : Yes
Format settings, RefFrames : 2 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 2 h 35 min
Nominal bit rate : 6 000 kb/s
Width : 896 pixels
Original width : 1 280 pixels
Height : 504 pixels
Original height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 30.000 FPS
Original frame rate : 60.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.443
Writing library : x264 core 148 r2579M 73ae2d1
Encoding settings : cabac=1 / ref=2 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=2 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=0 / me_range=16 / chroma_me=1 / trellis=0 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=0 / threads=4 / lookahead_threads=1 / sliced_threads=0 / nr=250 / decimate=1 / interlaced=0 / bluray_compat=0 / stitchable=1 / constrained_intra=0 / bframes=0 / weightp=1 / keyint=122 / keyint_min=12 / scenecut=40 / intra_refresh=0 / rc_lookahead=10 / rc=2pass / mbtree=1 / bitrate=6000 / ratetol=1.0 / qcomp=0.60 / qpmin=5 / qpmax=69 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=1:1.00
Default : Yes
Forced : No




Thanks for the help !


-
configure : speed up check_deps()
5 août 2018, par Avi Halachmi (:avih)configure : speed up check_deps()
x4 - x25 faster.
check_deps() recursively enables/disables components, and its loop is
iterated nearly 6000 times. It's particularly slow in bash - currently
consuming more than 50% of configure runtime, and about 20% with other
shells.This commit applies few local optimizations, most effective first :
Use $1 $2 ... instead of pushvar/popvar, and same at enable_deep*
Abort early in one notable case - empty deps, to avoid costly no-op.
Smaller changes which do add up :
- Handle $cfg_checking locally instead of via enable[d]/disable
- $cfg_checking : test done before inprogress - x2 faster in 50%+
- one eval instead of several at the empty-deps early abort path.The "actual work" part is unmodified - just its surroundings.
Biggest speedups (relative and absolute) are observed with bash.
Tested-by : Michael Niedermayer <michael@niedermayer.cc>
Tested-by : Helmut K. C. Tessarek <tessarek@evermeet.cx>
Tested-by : Dave Yeo <daveryeo@telus.net>
Tested-by : Reino Wijnsma <rwijnsma@xs4all.nl>
Signed-off-by : James Almer <jamrial@gmail.com> -
I don't know the time unit to use for av_dict_set to set a timeout
9 juin 2020, par ICYMYMI am confused. I am using the
av_dict_set
function to set a time-out, but when I searched for information aboutav_dict_set
, the time unit seems to be different. I don't know how to set it now. Can anyone help ?


I found some code like the following :



pFormatCtx = avformat_alloc_context();

av_dict_set(&opts, "rtsp_transport", "tcp", 0);
//av_dict_set(&opts, "timeout", "5000000", 0);
if(strncmp(stream_url, "rtmp:", sizeof("rtmp:")) == 0){
 av_dict_set(&opts, "timeout", "6", 0); // in secs
}
else if(strncmp(stream_url, "http:", sizeof("http:")) == 0){
 av_dict_set(&opts, "timeout", "6000", 0); // in ms
}

if(avformat_open_input(&pFormatCtx, stream_url, NULL, &opts)!=0)
{
 return 1;
}




Maybe it should set the time unit according to the different protocols (http or rtsp).



Is the code above right ?