
Recherche avancée
Autres articles (59)
-
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...) -
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
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 (9276)
-
Looking for a free alternative RTSP server for Node.js [closed]
2 juin 2020, par MaorationI'm looking at running my node.js server as an RTSP streaming server, as well as an http server. the ability to get some ffmpeg video output to stream as rtsp to 'localhost' (which will be the server listening), and for multiple clients to request a stream from the server via the rtsp ://... protocol



The most common online implementation is :
https://www.npmjs.com/package/rtsp-streaming-server



However, this is licensed under GPL-3.0, meaning my product would have to be open-source, or I'll be violating the terms of use. I'm afraid thats not possible..



Other common results when searching for a solution are :



https://www.npmjs.com/package/rtsp-server
which just seems to wrap to lower level rtsp protocol messages.



https://www.npmjs.com/package/node-media-server
which provides solutions to many use cases, but I couldnt figure out how to configure it as an RTSP server, or if this would even be possible.



So, any alternatives ? other suggestions ?


-
How do I set up FFmpeg on Laravel Forge ?
31 juillet 2022, par James StewartI have FFMPEG locally on my computer. It is working exactly as I need it to.


I want to use it in production. I deploy a Laravel 8/Vue application to AWS via Laravel Forge. I am using the
laravel-ffmpeg
package for FFMPEG.

I can't find any articles online and how to install FFMPEG on my server when using Laravel forge. I have added two binaries (ffmpeg [320kb], ffprobe [280kb]) to my project and I have used the suggested laravel-ffmpeg.php config file from that project's docs :


return [
 'ffmpeg' => [
 'binaries' => env('FFMPEG_BINARIES', 'usr/bin/ffmpeg'),
 'threads' => 12, // set to false to disable the default 'threads' filter
 ],
 'ffprobe' => [
 'binaries' => env('FFPROBE_BINARIES', 'usr/bin/ffprobe'),
 ],
 'timeout' => 3600,
 'log_channel' => env('LOG_CHANNEL', 'stack'), // set to false to completely disable logging
 'temporary_files_root' => env('FFMPEG_TEMPORARY_FILES_ROOT', sys_get_temp_dir()),
 'temporary_files_encrypted_hls' => env('FFMPEG_TEMPORARY_ENCRYPTED_HLS', env('FFMPEG_TEMPORARY_FILES_ROOT', sys_get_temp_dir())),
];



I've tried moving the binaries around (so not in usr/bin etc) but it doesn't seem to make a difference. I get errors like this :


Alchemy\BinaryDriver\Exception\ExecutionFailureException: ffprobe failed to execute command 'ffprobe' '-help' '-loglevel' 'quiet':

Error Output:

 sh: 1: exec: ffprobe: not found



Is there some 100% certain way to actually get ffmpeg up and running in Forge ? Am I missing something real obvious ?


-
Using ffmpeg native aac codec, but metadata says libvo_aacenc, and faststart not supported ?
8 juillet 2016, par Bob SI’m using ffmpeg and am trying to switch from using the ’libvo_aacenc’ encoder to the native aac encoder. It seems to work, but the metadata in the output seems to indicate that it’s still using the old encoder.
I changed the audio portion of my ffmpeg call from
-i out.wav -acodec libvo_aacenc
to
-i out.wav -acodec aac -strict experimental
But the output includes this :
Metadata :
encoder : Lavf53.21.1
Stream #0.0: Video: libx264, yuv420p, 432x256, q=-1--1, 30 tbn, 30 tbc
Stream #0.1: Audio: libvo_aacenc, 44100 Hz, 1 channels, s16, 200 kb/sI don’t understand where it is still getting the ’libvo_aacenc’ from ?
Another problem, maybe unrelated, is that when I try to add the "-movflags +faststart" option to my call, I get errors :
[mp4 muxer @ 0x49ad520] [Eval @ 0x3e59d37c6b0] Undefined constant or missing ’(’ in ’faststart’
[mp4 muxer @ 0x49ad520] Unable to parse option value "faststart"
[mp4 muxer @ 0x49ad520] Error setting option movflags to value +faststart.From looking online it would appear my ffmpeg version is old, pre faststart, but my ffmpeg version is 0.8.17-4:0.8.17-0ubuntu0.12.04.1, Copyright (c) 2000-2014 the Libav developers built on Mar 16 2015 13:26:50 with gcc 4.6.3
That seems like it should include faststart, which was introduced in 2013, right ?
Any ideas what could be going on ?Thanks very much,
Bob