
Recherche avancée
Médias (1)
-
Richard Stallman et le logiciel libre
19 octobre 2011, par
Mis à jour : Mai 2013
Langue : français
Type : Texte
Autres articles (53)
-
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
Support audio et vidéo HTML5
10 avril 2011MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...) -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)
Sur d’autres sites (10485)
-
Create MP4 for HTML5 video with FFMPEG
7 août 2013, par KrisI'm trying to create an MP4 file with FFMPEG to play with a HTML5 video tag.
I found some sample codes that use libx264, but when I tried, FFMPEG gave me an "unknown encoder libx264" error.
I asked my host to install it on my server, and got the following reply :
After review from our L3 group I am informed that x264 is not supported with FFMPEG any longer. That was a library that went with FFMPEG-PHP that is not supported at all by anyone.
In order to get that to work with FFMPEG you would need to contact the developers of the FFMPEG software to get assistance with that as it is outside our scope of support.
I looked everywhere online, but can't seem to find an answer to this. If libx264 is not supported anymore, how is everyone else doing it ? Still libx264 with an older FFMPEG version, or some other way ?
-
fatal Error Issues - jhotovy's version of android-ffmpeg-x264 - github.com/jhotovy/android-ffmpeg.git
3 août 2012, par user1545779The following is the output for issuing
init-submodules.sh
. I keep receiving thiserror:fatal error:
Unable to checkout '15e02184e136e47ecff01bf56aca
The49d8e2646fb4' in submodule path 'Project/jni/ffmpeg'<br />Has anyone run jhotovy's version of halfninja's code successfully so far ? Any help in resolving this issue will be greatly appreciated
My screen output :
gipsyblues@android-general:~/android-ffmpeg$ ./init-submodules.sh <br />
ls: cannot access ./jni/ffmpeg/*: No such file or directory<br />
Submodule 'ffmpeg' (git://git.videolan.org/ffmpeg.git) registered for path Project/jni /ffmpeg'<br />
Submodule 'x264' (git://git.videolan.org/x264.git) registered for path 'Project/jni /x264'<br />
user.name=xxxxxxx <br />
user.email=yyyyyyy <br />
core.repositoryformatversion=0<br />
core.filemode=true<br />
core.bare=false<br />
core.logallrefupdates=true<br />
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*<br />
remote.origin.url=git://github.com/jhotovy/android-ffmpeg.git
branch.master.remote=origin<br />
branch.master.merge=refs/heads/master<br />
submodule.ffmpeg.url=git://git.videolan.org/ffmpeg.git<br />
submodule.x264.url=git://git.videolan.org/x264.git<br />
Initialized empty Git repository in /home/gipsyblues/android-ffmpeg/Project/jni/ffmpeg /.git/<br />
remote: Counting objects: 237417, done.<br />
remote: Compressing objects: 100% (57251/57251), done.<br />
remote: Total 237417 (delta 186957), reused 228690 (delta 179782)<br />
Receiving objects: 100% (237417/237417), 59.89 MiB | 5.22 MiB/s, done.<br />
Resolving deltas: 100% (186957/186957), done.<br />
fatal: reference is not a tree: 15e02184e136e47ecff01bf56aca49d8e2646fb4<br />
Unable to checkout '15e02184e136e47ecff01bf56aca49d8e2646fb4' in submodule path 'Project/jni/ffmpeg'<br />
gipsyblues@android-general:~/android-ffmpeg$ <br />I have successfully run the original halfninja version which is also at
githuib.com/halfninja/android-ffmpeg-x264.<
br> I have searched all over the Internet and i am not finding any reference to this issue. Anyone had any success with that implementation -
RTP Timestamps Are Not Monotonically increasing
25 août 2019, par Fr0styI am finding it a bit difficult trying to understand whether or not the hack around with FFmpeg and OpenCV really provided a RTP timestamp. My last post helped a little bit but got me stuck in trying to validate the timestamps obtained through this work around by modifying ffmpeg and opencv.
FFmpeg version : 4.1.0
OpenCV version : 3.4.1import cv2
import time
from datetime import datetime, date
uri = 'rtsp://admin:password@192.168.1.66:554/Streaming/Channels/101'
cap = cv2.VideoCapture(uri)
'''One is the offset between the two epochs. Unix uses an epoch located at 1/1/1970-00:00h (UTC) and NTP uses 1/1/1900-00:00h.
This leads to an offset equivalent to 70 years in seconds (there are 17 leap years between the two dates so the offset is'''
time_offset = 2208988800 # (70*365 + 17)*86400 = 2208988800 (in seconds)
# offset = 3775484294
days = 43697
pdat = "1900-01-01 00:00:00:00"
mdat = "2019-08-23 22:02:44:00" # str(datetime.now()) + str(datetime.now().time())
pdate = datetime.strptime(pdat, "%Y-%m-%d %H:%M:%S:%f").date()
mdate = datetime.strptime(mdat, "%Y-%m-%d %H:%M:%S:%f").date()
delta = (mdate - pdate).days
offset = delta * 86400
def time_delta(s):
return (s - time_offset)
while True:
frame_exists, curr_frame = cap.read()
if frame_exists:
seconds = cap.getRTPTimeStampSeconds()
fraction = cap.getRTPTimeStampFraction()
timestamp = cap.getRTPTimeStampTs()
unix_offset = seconds - time_offset
msec = int((int(fraction) / 0xFFFFFFFF) * 1000.0)
ts = float(str(unix_offset) + "." + str(msec))
# print("Timestamp per Frame:%i" % timestamp)
print((datetime.fromtimestamp(float(ts) + offset)))
cap.release()My Output :
On August 23, 2019 at 22:02
...
2019-08-23 13:59:52.781000
2019-08-23 13:59:52.726000
2019-08-23 13:59:52.671000
2019-08-23 13:59:52.616000
2019-08-23 13:59:52.561000
2019-08-23 13:59:52.506000
2019-08-23 13:59:52.451000
2019-08-23 13:59:52.396000
2019-08-23 13:59:52.342000
2019-08-23 13:59:52.287000
2019-08-23 13:59:52.232000
2019-08-23 13:59:52.177000
2019-08-23 13:59:52.122000
2019-08-23 13:59:52.067000
2019-08-23 13:59:52.012000
2019-08-23 13:59:53.570000
2019-08-23 13:59:53.020000
2019-08-23 13:59:53.847000
2019-08-23 13:59:53.792000I’ve noticed how the time increments weirdly (that’s not suppose to happen in the real, current time), such as the last two lines and a few others in between in the output. A bit flabbergasted as to what went wrong. Also trying this out on multiple IP cameras, with each showing a different timestamp probably related to when they were turned on.