
Recherche avancée
Autres articles (28)
-
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 (...) -
Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs
12 avril 2011, parLa manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras. -
Les images
15 mai 2013
Sur d’autres sites (1646)
-
Transparent PNG to WEBM
5 avril 2018, par DanI am trying to make a partially transparent video for a Unity application, however, I can’t seem to get my commands to retain the alpha of the PNGs. Instead, it just makes the transparent parts white.
Currently the command I am using is
ffmpeg -r 30 -f image2 -s 2048x2048 -i frames%04d.png -vcodec vp8 -crf 63 -b:v 0 -pix_fmt yuva420p -auto-alt-ref 0 vid/output.webm
Whilst I am aware I could try the VP9 codec, AFAIK, this is not supported in Unity 2017.2, so I have to stick to VP8
The output this gives is
D:\development\batch - Copy>ffmpeg -r 30 -f image2 -s 2048x2048 -i frames%04d.png -vcodec vp8 -crf 63 -b:v 0 -pix_fmt yuva420p -auto-alt-ref 0 vid/output.webm
ffmpeg version N-90315-gf706cdda56 Copyright (c) 2000-2018 the FFmpeg developers
built with gcc 7.3.0 (GCC)
configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth
libavutil 56. 9.100 / 56. 9.100
libavcodec 58. 14.100 / 58. 14.100
libavformat 58. 10.100 / 58. 10.100
libavdevice 58. 2.100 / 58. 2.100
libavfilter 7. 13.100 / 7. 13.100
libswscale 5. 0.102 / 5. 0.102
libswresample 3. 0.101 / 3. 0.101
libpostproc 55. 0.100 / 55. 0.100
Input #0, image2, from 'frames%04d.png':
Duration: 00:00:03.50, start: 0.000000, bitrate: N/A
Stream #0:0: Video: png, pal8(pc), 2048x2048, 30 fps, 30 tbr, 30 tbn, 30 tbc
Stream mapping:
Stream #0:0 -> #0:0 (png (native) -> vp8 (libvpx))
Press [q] to stop, [?] for help
[libvpx @ 00000209d9a6e680] v1.7.0
Output #0, webm, to 'vid/output.webm':
Metadata:
encoder : Lavf58.10.100
Stream #0:0: Video: vp8 (libvpx), yuva420p, 2048x2048, q=-1--1, 30 fps, 1k tbn, 30 tbc
Metadata:
encoder : Lavc58.14.100 libvpx
Side data:
cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
frame= 105 fps=4.1 q=0.0 Lsize= 144kB time=00:00:03.46 bitrate= 339.6kbits/s speed=0.134x
video:94kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 52.357399% -
Matomo to end support for Internet Explorer 11
21 septembre 2021, par Matomo Core Team — CommunityA lot of the Matomo user interface is built on top of a programming framework called “Angular.js”. The support for this framework will end very soon, meaning we have to migrate the Matomo user interface to an alternative framework. The Matomo development team has chosen this new framework to be “Vue.js 3”.
Unfortunately, Vue.js does not support Internet Explorer 11 (IE 11). Therefore, we have to drop the support for IE 11. Many other popular services like Microsoft and WordPress recently did the same. This is happening because IE 11 was released about 8 years ago and is now used by less than 0.5% of the internet.
When will this change happen ?
Our next release (Matomo 4.5) will still support IE 11. It will show a notification in the user interface if you are using Internet Explorer to make you aware of this upcoming change.
When Matomo 4.6 is released around November 2021, then IE 11 will no longer be supported.
What does “end support” mean ?
The Matomo user interface will work less and less over time for people using IE 11 as a browser. While Matomo 4.6 might still mostly work with IE 11, once we migrate more of the user interface the functionality will stop working completely. It’s possible that even Matomo 4.6 will no longer be functional with IE 11 at all.
What should I do now ?
If you are impacted by this, then we strongly recommend that you switch to a more modern browser. Preferably a privacy-friendly browser like Mozilla Firefox or Brave. But any modern browser including Microsoft Edge, Safari and Google Chrome will work just fine.
If you can’t use a different browser and you are using Matomo On-Premise, then you can install and configure this new plugin which lets you only receive Matomo core updates that are compatible with IE 11. This will prevent you from accidentally upgrading to a Matomo core release that doesn’t work with IE 11, and you can still receive critical security updates and bug fixes until February 2022.
Will this affect the Matomo JavaScript tracker ?
No, all visitors using IE 11 will still be tracked and Matomo tracker will support the same browsers as before. Meaning also some older versions of Internet Explorer are still supported.
Have any questions about this ?
-
Implementing Live Streaming Webinar Architecture - Need Guidance
21 septembre 2023, par vishnugplQuestion : I'm working on a project to implement a live streaming webinar platform, and I'm looking for guidance on the architecture and technologies to use. I have some specific requirements and constraints, and I'd appreciate any advice or pointers on how to get started.


Context :
I'm tasked with building a live streaming webinar platform from scratch for our organization. Here are some key requirements and constraints :


- 

-
Live Video Streaming : We need to support live video streaming for
webinars, workshops, and conferences. Low latency is crucial for
real-time interaction between presenters and attendees.


-
Scalability : The platform should be able to handle a large number of concurrent attendees, potentially thousands or more,
without compromising performance.


-
Security : Security is a top priority. We need to ensure that only authorized users can access the webinars, and we must protect
against unauthorized recording or distribution of the content.


-
User Interaction : Attendees should be able to ask questions, participate in polls, and interact with presenters in real-time.


-
Recording and Playback : We also want to provide recorded versions of past webinars for on-demand viewing (HLS).














Current Tech Stack :


- 

- Frontend : React
- Backend : Node.js with Express
- Database : MongoDB
- Cloud Hosting : AWS










Questions :


- 

-
What technologies or services are best suited for handling live video streaming with low latency ?


-
How can I ensure scalability in terms of both video streaming and handling a large number of users ?


-
What security measures should I consider to protect the content and user data ?


-
Are there any recommended frameworks or libraries for building interactive features like real-time chat and polling ?


-
What's the best approach for recording and serving on-demand webinar content ?














Additional Information :


- 

-
Budget is a consideration, so cost-effective solutions are preferred.


-
Any open-source or third-party tools that can simplify development are welcome.


-
I have experience with AWS, but I'm open to other cloud providers if they offer advantages for this project.










-