
Recherche avancée
Médias (1)
-
MediaSPIP Simple : futur thème graphique par défaut ?
26 septembre 2013, par
Mis à jour : Octobre 2013
Langue : français
Type : Video
Autres articles (28)
-
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 (...)
-
List of compatible distributions
26 avril 2011, parThe table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...) -
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...)
Sur d’autres sites (4126)
-
ffmpeg watermark to mp4
20 octobre 2013, par user2899426Trying to add a png graphic as watermark to an existing mp4 video with audio.
But each time I produce an ouputfile there is no audio included / encoded ?
For testing pupose i only want a small 30 second clipffmpeg -t 0:0:30.0 -i 'input.mp4' -i 'logo.png' -filter_complex '[0:v][1:v]overlay[out]' -map '[out]' -b:v 5842k -c:a copy out.mp4
have managed to extract audio to seperate mp3 file to check codec works
FYI built ffmpeg from gitclone
Thanks this is driving me nuts. -
Ffmpeg http slow Startup Delay
16 mars 2018, par JanI need a http stream output with very fast start up Delay (100ms) And Constant Traffic. And I only want to use the http stream with vlc... so not for Browser usage. My input stream has a Bitrate 3-4mbit. With hls I get the 100ms switching time but not constant traffic. I already have traffic eruption... in one second high traffic and then nothing. But I need a constant output.
So I tried it with nodejs and ffmpeg fluent but the starting time is not so good(Not so fast like hls)
This is my
// How to Use
// 1. Create package.json with `npm init`
// 2. Install dependencies with `npm i fluent-ffmpeg express`
// 3. Start with `node ffmpegToWeb.js`
// 4. Open VLC and "Open Network Stream".
// 5. Input the following without quotes : `http://127.0.0.1:8001` and start.
const ffmpeg = require('fluent-ffmpeg')
const config = {
port: 8001,
url: 'url here'
}
let ffmpegObj = ffmpeg(config.url)
.videoCodec('copy')
.audioCodec('copy')
.outputOptions([
'-y',
'-ac 2',
'-sn',
'-f mpegts'
])
.inputOptions([
'-re',
'-nostdin',
'-hide_banner',
'-probesize 5000000',
'-analyzeduration 15000000'
])
.on('start', function (commandLine) {
console.log('Starting ffmpeg with command: ' + commandLine)
})
.on('error', (err) => {
console.log('ffmpeg error', err)
})
.on('end', () => {
console.log('ffmpeg end')
})
.on('progress', (stats) => {
// console.log(stats)
})
let currentChunk = {}
let ffstream = ffmpegObj.pipe()
ffstream.on('data', (buffer) => {
currentChunk = buffer
process.emit('ffmpeg-data', buffer)
})
// web app
console.log('Starting Express Web Server on Port ' + config.port)
const express = require('express')
const app = express()
const http = require('http')
const httpServer = http.createServer(app)
app.get('/', function (req, res) {
console.log('client connected:', req.headers['user-agent'])
let contentWriter = (buffer) => {
res.write(buffer)
}
res.setHeader('Connection', 'close')
res.setHeader('Cache-Control', 'no-cache')
res.setHeader('Pragma', 'no-cache')
res.setHeader('Content-Type', 'video/mp2t')
// write current chunk before the first data event occurs
if (currentChunk.length > 0) {
res.write(currentChunk)
}
process.on('ffmpeg-data', contentWriter)
req.on('close', function () {
console.log('client disconnected:', req.headers['user-agent'])
process.removeListener('ffmpeg-data', contentWriter)
})
})
httpServer.listen(config.port) -
Why can't Chrome 83 play this AV1 encoded video ?
25 mai 2020, par SlboxThe file plays great in VLC.



I've tried adding the
codecs="av01.0.05M.08"
to the video source, but no luck - no browser will play it, despite what's stated here : https://caniuse.com/#feat=av1


The video was encoded like so :



ffmpeg -i input.avi -pix_fmt yuva420p -f nut -c:v libaom-av1 -minrate 1k -b:v 350k -maxrate 2000k -strict experimental output.mp4




Browser console :



- 

-
Chrome gives no hint whatsoever as to why it won't play. Firefox gives some minor clues.
-
Firefox shows the below







Media resource https://example.com/example.mp4 could not be decoded. example.mp4




Media resource https://example.com/example.mp4 could not be decoded, error: Error Code: NS_ERROR_DOM_MEDIA_METADATA_ERR (0x806e0006)
Details: static MP4Metadata::ResultAndByteBuffer __cdecl mozilla::MP4Metadata::Metadata(mozilla::ByteStream *): Cannot parse metadata




Any advice on where I'm going wrong, either in understanding or in encoding arguments, would be greatly appreciated !


-