
Recherche avancée
Autres articles (48)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Contribute to a better visual interface
13 avril 2011MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community. -
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)
Sur d’autres sites (9636)
-
audio/mp4 ; codecs="mp4a.40.2" not playing in Chrome and Firefox
19 octobre 2020, par Stefan FalkIt seems I want to convert audios, which I want to stream on my website, to
audio/mp4; codecs="mp4a.40.2"
.

Using
ffmpeg-cli-wrapper
, I am converting my uploaded audio files with this command here :

ffmpeg -i /tmp/input.any -acodec aac -b:a 256000 /tmp/output.aac



On the client I am creating a SourceBuffer like this :


this.sourceBuffer = this.mediaSource.addSourceBuffer('audio/mp4; codecs="mp4a.40.2"');



The errors are :


Chrome :


NotSupportedError: Failed to load because no supported source was found.



Firefox :


NotSupportedError: The media resource indicated by the src attribute or assigned media provider object was not suitable.



Here comes the fun part :


If I create the SourceBuffer using
audio/aac
as mime-type :

this.sourceBuffer = this.mediaSource.addSourceBuffer('audio/aac');



the audio gets played correctly on Chrome but Firefox says :


MediaSource.addSourceBuffer: Type not supported in MediaSource




Update


After changing the command to


ffmpeg -i /tmp/input.any -acodec aac -b:a 256000 /tmp/output.mp4
 ^^^ 



Chrome/Firefox do not give an error when using
audio/mp4; codecs="mp4a.40.2"
, but the audio is not being played.


See


- 

- https://stackoverflow.com/a/64432478/826983




-
ffmpeg errors out with Error initializing output stream 0:0 for the setting `-profile:v main`
17 octobre 2020, par Vishwasa Navada KWe are using ffmpeg for generating HSL streaming files (.m3u8, .ts) from multiple type of input video and audio like avi, mp4, mp3, mkv, m4a etc. We are trying to encode everything into h264 streams to support modern browsers. But we are facing issues in converting few videos of type avi and mp4 (not all). Below is the ffmpeg command (it's using ffmpeg fluent on NodeJS).


ffmpeg(fileName)
 .outputOptions([
 '-c:v h264',
 '-profile:v main',
 `-vf scale=1280:-2`,
 '-hls_list_size 0',
 '-start_number 0',
 '-hls_time 10',
 '-loglevel error',
 ])
 .output(output_file_path)



When we try to run this with some set of specific avi and mp4 samples, it errors out saying

Error: ffmpeg exited with code 1: Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
.

I tried changing few commands (like providing crf value) and tried to run them, The only time it successfully converted converted them was when I removed the output option
-profile:v main
. I am not sure about the reason behind it.

I ran ffprobe to get the information from the videos that were not able to generate streams. I have them uploaded to gist here : https://gist.github.com/vishwasnavadak/91b5c978e2a3cb7a7c7a2bb505487263


Is there something I am missing ? What is the reason for it to error out when
-profile:v main
option is present ?

-
VP9 Profile 2 VDPAU support
8 octobre 2020, par ManojGuptaBonda