
Recherche avancée
Autres articles (78)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...) -
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.
Sur d’autres sites (9470)
-
ffmpeg filters order rotate scale with overlay
13 décembre 2017, par Sebastián Márquez LutfyI’m trying to render an image over a video. I use the following command after some research
ffmpeg -y -i "my_video.mp4" -i "my_image.jpg" -filter_complex "color=color=blue:size=711x400:rate=25[container];[0:v]scale=w=400:h=400,setpts=expr=PTS-STARTPTS[vidscaled];[container][vidscaled]overlay=eval=init:shortest=1:x=155:y=0[overlay0];[1:v]scale=w=123:h=123,rotate=a=323.7*PI/180:c=black@0:oh='roth(323.7*PI/180)':ow='rotw(323.7*PI/180)':bilinear=1[imgproc];[overlay0][imgproc]overlay=eval=init:x=18:y='237-abs(123*sin(323.7*PI/180))'[overlay1]" -map "[overlay1]" -map 0:a -strict -2 -preset ultrafast -g 120 output.mp4
The problem with this approach is a low image’s quality since scaling is applied before rotate. So i tried to apply the rotation before scaling, (see next command)
ffmpeg -y -i "my_video.mp4" -i "my_image.jpg" -filter_complex "color=color=blue:size=711x400:rate=25[container];[0:v]scale=w=400:h=400,setpts=expr=PTS-STARTPTS[vidscaled];[container][vidscaled]overlay=eval=init:shortest=1:x=155:y=0[overlay0];[1:v]rotate=a=323.7*PI/180:c=black@0:oh='roth(323.7*PI/180)':ow='rotw(323.7*PI/180)':bilinear=1,scale=w=173:h=173[imgproc];[overlay0][imgproc]overlay=eval=init:x=18:y='237-abs(123*sin(323.7*PI/180))'[overlay1]" -map "[overlay1]" -map 0:a -strict -2 -preset ultrafast -g 120 output.mp4
And the problem : c=black@0 is not working anymore, the bounding box around the rotated image is not transparent.
Anyone please help this soul.
pd : Using c=none doesn’t work too, got a green background
-
avformat/mpegtsenc : Fix mpegts_write_pes() for private_stream_2 and other types
25 avril 2021, par zheng qianavformat/mpegtsenc : Fix mpegts_write_pes() for private_stream_2 and other types
According to the PES packet definition defined in Table 2-17 of ISO_IEC_13818-1
specification, some fields like PTS/DTS or pes_extension could only appears if
the stream_id meets the condition :if (stream_id != 0xBC && // program_stream_map
stream_id != 0xBE && // padding_stream
stream_id != 0xBF && // private_stream_2
stream_id != 0xF0 && // ECM
stream_id != 0xF1 && // EMM
stream_id != 0xFF && // program_stream_directory
stream_id != 0xF2 && // DSMCC_stream
stream_id != 0xF8) // ITU-T Rec. H.222.1 type E streamAnd the following stream_id types don't have fields like PTS/DTS :
else if ( stream_id == program_stream_map
|| stream_id == private_stream_2
|| stream_id == ECM
|| stream_id == EMM
|| stream_id == program_stream_directory
|| stream_id == DSMCC_stream
|| stream_id == ITU-T Rec. H.222.1 type E stream )
for (i = 0 ; i < PES_packet_length ; i++)
PES_packet_data_byte
Current implementation skipped the check of stream_id causing some kind of
streams like private_stream_2 to be incorrectly written with actually a
private_stream_1-like PES header with PTS/DTS field. For example, Japan DTV
transmits news and alerts through ARIB superimpose that utilizes
private_stream_2 still could not be remuxed correctly for now.This patch set fixes the remuxing for private_stream_2 and
other stream_id types.Signed-off-by : zheng qian <xqq@xqq.im>
Signed-off-by : Marton Balint <cus@passwd.hu> -
Why won’t this mp4 play in a video-js tag any longer
18 octobre 2019, par VelocedgeI’m using ffmpeg to convert files to MP4. I’ve made some modifications to the ffmpeg string but now it seems no matter what I use, the video won’t play in an HTML5 tag (Chrome browser). Normally, I just used "-vcodec libx264 -s 1280x720 -ar 22050". When I try to load it in the video tag, I get the following error on http://family.gotsport.net/lmw/GotSport/videoPlayer.asp?WS=1&URL=/VideoFiles/2/4_70_highlight :
The media could not be loaded, either because the server or network failed or because the format is not supported.
No matter what parameters I use (or don’t use), it still won’t play. However, if you just call the url directly, it will play in Chrome (http://family.gotsport.net/videofiles/2/2_70_highlight.mp4). I’m using the 7.0.0 version of video-js from their CDN (although older versions give the same result).
Video tag looks like :
<video class="video-js vjs-default-skin" autoplay="autoplay" controls="controls" preload="auto">
<source src="/VideoFiles/2/4_70_highlight.mp4" type="video/mp4"></source>
</video>Here is the MediaInfo output from the file that won’t play :
General
Complete name : E:\VideoFiles\2\2_70_highlight.mp4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/avc1/mp41)
File size : 5.87 MiB
Duration : 27 s 60 ms
Overall bit rate : 1 820 kb/s
Writing application : Lavf58.29.100
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L3.1
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 4 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 27 s 60 ms
Bit rate : 1 685 kb/s
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 (29970/1000) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.061
Stream size : 5.44 MiB (93%)
Writing library : x264 core 158 r2984 3759fcb
Encoding settings : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=12 / lookahead_threads=2 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=crf / mbtree=1 / crf=23.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00
Codec configuration box : avcC
Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 27 s 22 ms
Duration_LastFrame : -6 ms
Bit rate mode : Constant
Bit rate : 128 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 22.05 kHz
Frame rate : 21.533 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 423 KiB (7%)
Default : Yes
Alternate group : 1Do you see anything that would keep this format from playing in an HTML5 video tag ?