
Recherche avancée
Autres articles (4)
-
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. -
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users. -
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
Sur d’autres sites (1960)
-
Video Conferencing in HTML5 : WebRTC via Socket.io
1er janvier 2014, par silviaSix months ago I experimented with Web sockets for WebRTC and the early implementations of PeerConnection in Chrome. Last week I gave a presentation about WebRTC at Linux.conf.au, so it was time to update that codebase.
I decided to use socket.io for the signalling following the idea of Luc, which made the server code even smaller and reduced it to a mere reflector :
var app = require(’http’).createServer().listen(1337) ; var io = require(’socket.io’).listen(app) ;
io.sockets.on(’connection’, function(socket)
socket.on(’message’, function(message)
socket.broadcast.emit(’message’, message) ;
) ;
) ;Then I turned to the client code. I was surprised to see the massive changes that PeerConnection has gone through. Check out my slide deck to see the different components that are now necessary to create a PeerConnection.
I was particularly surprised to see the SDP object now fully exposed to JavaScript and thus the ability to manipulate it directly rather than through some API. This allows Web developers to manipulate the type of session that they are asking the browsers to set up. I can imaging e.g. if they have support for a video codec in JavaScript that the browser does not provide built-in, they can add that codec to the set of choices to be offered to the peer. While it is flexible, I am concerned if this might create more problems than it solves. I guess we’ll have to wait and see.
I was also surprised by the need to use ICE, even though in my experiment I got away with an empty list of ICE servers – the ICE messages just got exchanged through the socket.io server. I am not sure whether this is a bug, but I was very happy about it because it meant I could run the whole demo on a completely separate network from the Internet.
The most exciting news since my talk is that Mozilla and Google have managed to get a PeerConnection working between Firefox and Chrome – this is the first cross-browser video conference call without a plugin ! The code differences are minor.
Since the specification of the WebRTC API and of the MediaStream API are now official Working Drafts at the W3C, I expect other browsers will follow. I am also looking forward to the possibilities of :
- multi-peer video conferencing like the efforts around webrtc.io,
- the media stream recording API,
- and the peer-to-peer data API.
The best places to learn about the latest possibilities of WebRTC are webrtc.org and the W3C WebRTC WG. code.google.com has open source code that continues to be updated to the latest released and interoperable features in browsers.
The video of my talk is in the process of being published. There is a MP4 version on the Linux Australia mirror server, but I expect it will be published properly soon. I will update the blog post when that happens.
-
batch ffmpeg conversion (aspect, crop, and concatenate) and naming based on subfolder
3 avril 2015, par hordorTYIA for any help !
Seems I have a somewhat complicated, multi-step process. If you can help any part of it that would be appreciated.
What I hope to accomplish
- Example of folder/file is here : https://mega.co.nz/#F !RJRWRLTJ !c6b-z3Vl-Tlh0uGbCflx7Q
- I have many subfolders that each contain 7 files from a DVD (originally PAL-encoded I think). I only care about the VTS_01_1.VOB AND VTS_01_2.VOB files. The two files together are one match
- The videos are stretched (from 4:3 to 16:9) and letterboxed. I want to undo that
- The future title of the final MP4 video should be the name of the folder
- BONUS : title of the video should also include the folder before it (e.g. "Friday H2 G1 CAN - BEL.mp4")
I’d like to do this via batch file because there are a lot of folders.
What I have done :
dir/b/s *.vob | findstr /v VIDEO | findstr /v 01_ >list.txt
@echo off
for %%i in list.txt
do
ffmpeg -i VTS_01_1.VOB -aspect 4:3 "%%~pi\v1step1.mp4"
ffmpeg -i vob1.mp4 -vf "crop=704:432:10:72" "%%~pi\v1step2.mp4"
ffmpeg -i vob11.mp4 -c copy "%%~pi\v1step3.ts"
ffmpeg -i VTS_01_2.VOB -aspect 4:3 "%%~pi\v2step1.mp4"
ffmpeg -i vob2.mp4 -vf "crop=704:432:10:72" "%%~pi\v2step2.mp4"
ffmpeg -i vob22.mp4 -bsf h264_mp4toannexb -c copy "%%~pi\v2step3.ts"
ffmpeg -i "concat:v1step3.ts|v2step3.ts" -c copy file.mp4 "%%~pi\Match.mp4"
@echo on
pauseProblem with current code
- Doesn’t start converting (can’t see error message either)
- Doesn’t have the file naming that I want
- A lot of steps in conversation - can that be simplified ?
- Not sure why it wanted the -bsf command for the second conversion but not the first
Apologies if I’d made basic mistakes. I’m a big newbie and just to get this far has taken me hours of research. Thanks again !
-
Data Privacy Issues to Be Aware of and How to Overcome Them
9 mai 2024, par Erin