
Recherche avancée
Autres articles (103)
-
Keeping control of your media in your hands
13 avril 2011, parThe vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...) -
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...) -
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...)
Sur d’autres sites (9405)
-
Using FFMPEG with QT
7 mai 2018, par DearChildI’m having a problem with linking FFmpeg libraries to Qt 5.10 Projects.
I downloaded the source code from the official website and successfully compiled and installed to my Ubuntu. I used :./configure --enable-libvpx --disable-x86asm
them :make && make install
I’m able to find the installed libraries in/usr/local/lib
(which are .a libs).my .pro looks like this :
INCLUDEPATH += /usr/local/include
LIBS += -L/usr/local/lib -lavformat -lavcodec -lavutilbut i get the output :
/usr/bin/x86_64-linux-gnu-ld:
/usr/loca/lib/libavformat.a(http.o):undefined reference to symbol 'inflateEnd'
//lib/x86_64-linux-gnu/libz.so.1: error adding symbols: DSO missing from command lineDoes anyone know how to solve it ? Thanks for the attention !
Note : I would like to static link it to my project
-
Does ffmpeg rtp_mpegts muxer support setting DVB triplet ?
19 février 2021, par drake7It seems ffmpeg lets you set the DVB triplet with UDP but not with RTP.


FYI : This is a followup on my findings about the
rtp_mpegts
muxer compared to thempegts
muxer : Question

In my tests I was using
ffmpeg version 4.3.1-2021-01-01-full_build-www.gyan.dev
on windows.

findings


I analyzed my streams with
dectec
's "StreamXpert" :

- 

-
With UDP and it's
mpegts
muxer, the DVB triplet can be set (1)

-
With RTP and it's
rtp_mpegts
muxer, the DVB triplet is ignored (3) (Note that 3a and 3b create very similar results in "StreamXpert".)

-
Using UDP with DVB triplet as input and output with RTP ignores the DVB triplet (2)











Interestingly, leaving out the following options...


-pcr_period 20 -pat_period 0.10 -sdt_period 0.25 -metadata:s:a:0 language=nya \
-mpegts_flags +pat_pmt_at_frames -mpegts_flags system_b



... the
rtp_mpegts
muxer (3b) creates a valid DVB transport stream, while the thempegts
muxer (4) does not.

ffmpeg params :


- 




muxer :
mpegts
(udp)

ffmpeg -f lavfi -i testsrc -r 25 -c:v libx264 -pix_fmt yuv420p -profile:v main -level 3.1 -preset veryfast -vf scale=1280:720,setdar=dar=16/9 -an -bsf:v h264_mp4toannexb -b:v 4M -muxrate 8M \
-pcr_period 20 -pat_period 0.10 -sdt_period 0.25 -metadata:s:a:0 language=nya -mpegts_flags +pat_pmt_at_frames \
-mpegts_transport_stream_id 0x005A \
-mpegts_original_network_id 0x005B \
-mpegts_service_id 0x005C \
-mpegts_pmt_start_pid 0x005D -mpegts_start_pid 0x005E -mpegts_service_type advanced_codec_digital_hdtv \
-metadata service_provider="Provider foo" \
-metadata service_name="Service bar" \
-mpegts_flags system_b -flush_packets 0 \
-f mpegts "udp://239.10.33.10:1234?pkt_size=1316"



- 




muxer :
rtp_mpegts
(rtp)

ffmpeg -i "udp://239.10.33.10:1234" -map 0 -c copy \
-f rtp_mpegts "rtp://239.10.33.11:1234?pkt_size=1316"



- 




a) muxer :
rtp_mpegts
(rtp)

ffmpeg -f lavfi -i testsrc -r 25 -c:v libx264 -pix_fmt yuv420p -profile:v main -level 3.1 -preset veryfast -vf scale=1280:720,setdar=dar=16/9 -an -bsf:v h264_mp4toannexb -b:v 4M -muxrate 8M \
-pcr_period 20 -pat_period 0.10 -sdt_period 0.25 -metadata:s:a:0 language=nya -mpegts_flags +pat_pmt_at_frames \
-mpegts_transport_stream_id 0x005A \
-mpegts_original_network_id 0x005B \
-mpegts_service_id 0x005C \
-mpegts_pmt_start_pid 0x005D -mpegts_start_pid 0x005E -mpegts_service_type advanced_codec_digital_hdtv \
-metadata service_provider="Provider foo" \
-metadata service_name="Service bar" \
-mpegts_flags system_b -flush_packets 0 \
-f rtp_mpegts "rtp://239.10.33.10:1234?pkt_size=1316"



b) muxer :
rtp_mpegts
(rtp) (omitting some options)

ffmpeg -f lavfi -i testsrc -r 25 -c:v libx264 -vf scale=1280:720,setdar=dar=16/9 -b:v 4M -muxrate 8M \
-mpegts_transport_stream_id 0x005A \
-mpegts_original_network_id 0x005B \
-mpegts_service_id 0x005C -mpegts_pmt_start_pid 0x005D -mpegts_start_pid 0x005E \
-mpegts_service_type advanced_codec_digital_hdtv \
-metadata service_provider="Provider foo" \
-metadata service_name="Service bar" \
-f rtp_mpegts "rtp://239.10.33.10:1234"



- 




muxer :
mpegts
(udp) (omitting some options)

ffmpeg -f lavfi -i testsrc -r 25 -c:v libx264 -vf scale=1280:720,setdar=dar=16/9 -b:v 4M -muxrate 8M \
-mpegts_transport_stream_id 0x005A \
-mpegts_original_network_id 0x005B \
-mpegts_service_id 0x005C -mpegts_pmt_start_pid 0x005D -mpegts_start_pid 0x005E \
-mpegts_service_type advanced_codec_digital_hdtv \
-metadata service_provider="Provider foo" \
-metadata service_name="Service bar" \
-f mpegts "udp://239.10.33.10:1234"



Analyzing the transport stream




-
-
Restream IP camera Feed [closed]
4 janvier 2024, par Reenath Reddy ThummalaI possess several IP cameras linked to a shared network. Although I intend to leverage each camera stream across multiple microservices, the network faces challenges in managing the bandwidth load. Unfortunately, I lack control over the network and cannot augment its bandwidth. Despite attempting to create a restreaming service using GStreamer, Live555, FFMPEG, and OpenCV, stability remains an issue. Are there any paid services accessible that can accept the source feed as input and provide scalable restream feed URLs ?