
Recherche avancée
Médias (2)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
-
Carte de Schillerkiez
13 mai 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Texte
Autres articles (40)
-
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 (...) -
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 (...) -
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 (7915)
-
RTMP_ReadPacket, failed to read RTMP packet header rtmp ://a.rtmp.youtube.com/live2 : Unknown error occurred
3 novembre 2018, par OrophixHere is the script I am trying to run, I believe the issue is in here :
#!/bin/bash
GIF=/home/stream1/85012216.gif
STREAM_KEY=thisisasecret
URL=rtmp://a.rtmp.youtube.com/live2
FPS=30
KEYINT=$(expr $FPS \* 3)
$FFMPEG -f alsa -ac 2 -i hw:Loopback,1,0 -fflags +genpts -r $FPS -i $GIF \
-vcodec libx264 -x264opts keyint=$KEYINT:min-keyint=$KEYINT:scenecut=-1 -b:v 1000k \
-preset veryfast -pix_fmt yuv420p -s 854x480 \
-c:a libfdk_aac -b:a 96k -ar 44100 \
-f flv $URLThe error :
ffmpeg version N-92337-g8e50215b5e Copyright (c) 2000-2018 the FFmpeg
developers built with gcc 7 (Ubuntu 7.3.0-27ubuntu1 18.04)
configuration : —enable-shared —enable-gpl —enable-nonfree
—enable-pthreads —enable-postproc —enable-libtheora —enable-version3 —enable-libx264 —enable-libfdk-aac —disable-stripping —disable-encoder=libschroedinger —enable-librtmp —enable-gnutls —enable-avfilter —enable-libfreetype —disable-decoder=amrnb —enable-fontconfig —disable-mips32r2 —disable-mipsdspr2 —disable-htmlpages —disable-podpages —disable-altivec —enable-libass —enable-omx —enable-omx-rpi libavutil 56. 23.100 / 56. 23.100 libavcodec 58. 36.100 /
58. 36.100 libavformat 58. 21.100 / 58. 21.100 libavdevice 58. 6.100 / 58. 6.100 libavfilter 7. 43.100 / 7. 43.100 libswscale 5. 4.100 / 5. 4.100 libswresample 3. 4.100 /
3. 4.100 libpostproc 55. 4.100 / 55. 4.100 Guessed Channel Layout for Input Stream #0.0 : stereo Input #0, alsa, from
’hw:Loopback,1,0’ : Duration : N/A, start : 1541258646.286883, bitrate :
1536 kb/s
Stream #0:0 : Audio : pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s Input #1, gif, from ’/home/stream1/85012216.gif’ : Duration : N/A,
bitrate : N/A
Stream #1:0 : Video : gif, bgra, 500x281, 16.67 fps, 16.67 tbr, 100 tbn, 100 tbc RTMP_ReadPacket, failed to read RTMP packet header
rtmp ://a.rtmp.youtube.com/live2 : Unknown error occurredSystem details :
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic -
Matomo’s new story : our stronger vision for the future
31 octobre 2018, par Matthieu Aubry — CommunityOver the past year, the team here at Matomo have been working on a very exciting project we’d love to share with you.
It’s to do with the impact we hope for Matomo to have.
As you all know, the world changes at too fast a pace. New technologies, new phones, new everything in the blink of an eye. That’s not what will be happening here.
Instead, we’d like to believe it’s a refresh. Taking stock of how far we’ve come, what we’ve achieved so far, and how far we still have to go.
So we’re rebranding.
The rebrand
Like a caterpillar emerging from a cocoon, we hope to be a reborn analytics butterfly.
As a result of some careful planning and reflection we’ll be updating our logo, website and reasserting our voice.
It’s our chance to look at ourselves in a new light. We are a mighty analytics platform and it should be known we’re comparable to the likes of Google Analytics 360.
Along with the refresh of imagery, we listened to your feedback about the confusion between our two identities, so we’re also taking this opportunity to unite both the business brand of Innocraft with the community brand Matomo into one website.
It makes it easier for people from all walks of life, either as individuals or in large companies, to see us as being able to get down to business with a powerful analytics tool, as well as think on behalf of our community.
We’re the same, but with slight changes in our appearance and a stronger vision for the future.
How far we’ve come …
When we started out, it was about building a community around a movement. From the beginning we were concerned about data ownership, privacy and all things that came with that.
With the help of our community and contributors, we turned Matomo (formerly Piwik) into the trusted #1 open source analytics tool it is today. We’re committed to our community. But we also need to do more.
We’ve been niche and happy staying small, but now we need to take action and start shouting far and wide about what we do.
We once said we need : “To create, as a community, the leading international open source digital analytics platform, that gives every user full control of their data.”
We believe we’ve done that, so we’ll take it one step further.
A web analytics revolution has begun …
Begun ?
The line signifies a new beginning.
This is us standing up and reasserting our voice.
Our new chapter.
The rebrand is our chance to show that, yes, the world is changing, but when it comes to privacy, there are matters meant to be sacred. Privacy is a human right.
What makes it worse in this ever-changing landscape, with data breaches and stolen information, is that losing control of our data is scary, we have a right to know what’s going on with our information and this must start with us.
We know we need to champion this cause for privacy and data ownership.
We came together as a community and built something powerful, a free open-source analytics platform, that kept the integrity of the people using it.
It’s important for us now to feel more empowered to believe in our right to privacy, information and our ability to act independently of large corporations.
The time is here for us to speak up and take back control.
Once more, we need to come together to build something even more powerful, a safer online society.
Join us.
Sincerely,
Matthieu Aubry on behalf of the Matomo team -
Need help : Can i get ffmpeg to burn in the source timecode of my file ?
6 novembre 2018, par MylesI have a .mov file that contains original source timecode metadata but i can’t figure out a way to get ffmpeg to burn the original timecode into the picture.
If i open the original file in QuickTime Player we can see it displays the true timecode on the far left :
I can also see that ffprobe is able to see the metadata when i run the following :
Command :
ffprobe -i test.mov -show_streams
Abbreviated Result :
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'test.mov':
Metadata:
major_brand : qt
minor_version : 537199360
compatible_brands: qt
creation_time : 2018-11-05T14:20:51.000000Z
timecode : 09:59:53:00
Duration: 00:16:37.64, start: 0.000000, bitrate: 1680 kb/sSo i can see that ffprobe is able to determine the start timecode of the file in its metadata results. The question is how to i pass that information into an ffmpeg command so that the timecode seen by ffprobe is what gets used when i convert the file for timecode burn-in ?
An example of a standard burnt in timecode command would be this :
ffmpeg -i test.mov -vcodec libx264 -cmp 22 -vf
"drawtext=fontfile=DroidSansMono.ttf : timecode=’09:59:53:00’ : r=25 :
x=(w-tw)/2 : y=h-(2*lh) : fontcolor=white : box=1 : boxcolor=0x00000099"
-y test_bitc.movThe only problem there though is that i’ve had to manually put the timecode in myself. I want the command to use the existing timecode metadata as the timecode input value so the same command can be used on multiple files.
Does anyone know how to do this ?