
Recherche avancée
Autres articles (53)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
Le plugin : Podcasts.
14 juillet 2010, parLe problème du podcasting est à nouveau un problème révélateur de la normalisation des transports de données sur Internet.
Deux formats intéressants existent : Celui développé par Apple, très axé sur l’utilisation d’iTunes dont la SPEC est ici ; Le format "Media RSS Module" qui est plus "libre" notamment soutenu par Yahoo et le logiciel Miro ;
Types de fichiers supportés dans les flux
Le format d’Apple n’autorise que les formats suivants dans ses flux : .mp3 audio/mpeg .m4a audio/x-m4a .mp4 (...) -
Gestion des droits de création et d’édition des objets
8 février 2011, parPar défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;
Sur d’autres sites (6412)
-
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 -
FFMPEG : Get the Scene Change Detection value for all frame
14 novembre 2022, par celacantoI'm trying to measure how much a movies is "fast" (more action in the screen and quick scene chances). I don't want just a single value for the movie, but values along the movie to see how the action varies during it. After normalize the frame rate of the movies (10 fps), my idea is to compare each frame with the previous. I'm not only interest if the scene has changed, but also, if there was no cut, how much movement there is. Not only people/object movement but also, camera movement. In summary the paced (I think that the term) of the scenes.



My idea was to use the
scene
function from ffmpeg as a metric. But looking at the document and examples online I'm thinking I can only use the value of the Scene Change Detection as a threshold to return frames informations, but I can't get ffmpeg to return the value. Is that right ? There is any way I can make it return the value ?

-
rtpenc : Avoid brittle switch fallthroughs
18 décembre 2014, par Martin Storsjörtpenc : Avoid brittle switch fallthroughs
Instead explicitly jump to the default case in the cases where
it is wanted, and avoid fallthrough between different codecs,
which could easily introduce bugs if people editing the code
aren’t careful.Signed-off-by : Martin Storsjö <martin@martin.st>