
Recherche avancée
Médias (2)
-
SPIP - plugins - embed code - Exemple
2 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
Publier une image simplement
13 avril 2011, par ,
Mis à jour : Février 2012
Langue : français
Type : Video
Autres articles (44)
-
Pas question de marché, de cloud etc...
10 avril 2011Le vocabulaire utilisé sur ce site essaie d’éviter toute référence à la mode qui fleurit allègrement
sur le web 2.0 et dans les entreprises qui en vivent.
Vous êtes donc invité à bannir l’utilisation des termes "Brand", "Cloud", "Marché" etc...
Notre motivation est avant tout de créer un outil simple, accessible à pour tout le monde, favorisant
le partage de créations sur Internet et permettant aux auteurs de garder une autonomie optimale.
Aucun "contrat Gold ou Premium" n’est donc prévu, aucun (...) -
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 (...) -
Amélioration de la version de base
13 septembre 2013Jolie sélection multiple
Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)
Sur d’autres sites (8045)
-
Serving rtmp on port 1935
22 mai 2020, par JJ The SecondI've been trying to get ffmpeg to stream in rtmp but connection to port 1935 is always refused. I really don't know what else I can do to allow this connection.



Here is what specs I'm running.



- 

- Ubuntu 18.04 (tried with 19.04) however same issue - here is why I think I've made a mistake
- No Nginx installation at the moment
- FFMPEG "ffmpeg version 3.4.6-0ubuntu0.18.04.1 Copyright (c) 2000-2019 the FFmpeg developers built with gcc 7 (Ubuntu 7.3.0-16ubuntu3)"









This is the script I run :



ffmpeg -i "test.mp4" -c:v copy -c:a copy -f flv "rtmp://127.0.0.1/stream/test"




Error I get is :



[tcp @ 0x55ff05ab8ce0] Connection to tcp://127.0.0.1:1935 failed: Connection refused




I've done some research and been across many posts about ffserver.conf and I have made those changes but still no luck. Here is my config file. I also have ran ffserver once using this config.






HTTPPort 8090
HTTPBindAddress 127.0.0.1
MaxHTTPConnections 2000
MaxClients 1000
MaxBandwidth 1000
CustomLog -

<feed>

File /tmp/feed1.ffm
FileMaxSize 200K

# Only allow connections from localhost to the feed.
ACL allow 127.0.0.1
ACL allow localhost 
ACL allow 192.168.0.0 192.168.255.255
</feed>

<stream>

# coming from live feed 'feed1'
Feed feed1.ffm

Format mpeg
AudioBitRate 32

# Number of audio channels: 1 = mono, 2 = stereo
AudioChannels 2
AudioSampleRate 44100

# Bitrate for the video stream
VideoBitRate 64

# Ratecontrol buffer size
VideoBufferSize 40

# Number of frames per second
VideoFrameRate 3


</stream>


<stream>
Feed feed1.ffm
Format asf
VideoFrameRate 15
VideoSize 352x240
VideoBitRate 256
VideoBufferSize 40
VideoGopSize 30
AudioBitRate 64
StartSendOnKey
</stream>

# Special streams

# Server status

<stream>
Format status

ACL allow localhost
ACL allow 127.0.0.1
ACL allow 192.168.0.0 192.168.255.255

#FaviconURL http://pond1.gladstonefamily.net:8080/favicon.ico
</stream>

<redirect>
URL http://www.ffmpeg.org/
</redirect>




Here is my ufw status :



-- ------ ----
22/tcp ALLOW Anywhere
22 ALLOW Anywhere
1935/tcp ALLOW Anywhere
22/tcp (v6) ALLOW Anywhere (v6)
22 (v6) ALLOW Anywhere (v6)
1935/tcp (v6) ALLOW Anywhere (v6)




but still nothing, I've also opened ports in iptables but no luck. Here is how this is done :



iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 1935 -j ACCEPT

and

iptables -A OUTPUT -m state --state NEW -m tcp -p tcp --dport 1935 -j ACCEPT




and still nothing, every time I run ffmpeg I get connection refused. I have previously installed nginx just to test but no luck.



What am I doing wrong here ? Isn't this port suppose to be open now ?



Thanks


-
Revision ebb583d291 : Add a test vector for loopfilter The test vector exercises the loopfilter behav
4 décembre 2013, par Jingning HanChanged Paths :
Modify /test/test.mk
Modify /test/test_vector_test.cc
Add a test vector for loopfilterThe test vector exercises the loopfilter behavior at frame boundary.
blue_sky_1080p25.y4m —good —cpu-used=2 —threads=0 —profile=0
— lag-in-frames=25 —limit=300 —min-q=0 —max-q=63 —cq-level=20
— end-usage=0 —auto-alt-ref=1 -p 2 —kf-max-dist=9999 —kf-min-dist=0
— drop-frame=0 —static-thresh=0 —bias-pct=50 —minsection-pct=0
— maxsection-pct=2000 —arnr-maxframes=7 —arnr-strength=5
— arnr-type=3 —sharpness=0 —undershoot-pct=100 —target-bitrate=6000Change-Id : Ibd0807395d2fe87f24f81f990369678df3de7c23
-
avformat_write_header() changes my stream's time_base
12 avril 2023, par grekenI have a high framerate camera which can capture >2000 fps. My plan was to assign actual capture timestamps with µs resolution to the frames and encode with H.264 in a matroska file.


So I set the
time_base
of both theAVStream
and theAVCodecContext
to{1, 1'000'000}
. But after callingavformat_write_header(avFormatContext, nullptr)
I notice that the stream'stime_base
is{1, 1'000}
. Now, since my framerate is double this resolution, I get identical consecutive timestamps and half my frames get lost when I extract them from the video file.

Does anyone have an idea why this is happening and what I can do about it ? Preferably in a way that preserves the correct timestamps.