
Recherche avancée
Médias (3)
-
MediaSPIP Simple : futur thème graphique par défaut ?
26 septembre 2013, par
Mis à jour : Octobre 2013
Langue : français
Type : Video
-
GetID3 - Bloc informations de fichiers
9 avril 2013, par
Mis à jour : Mai 2013
Langue : français
Type : Image
-
GetID3 - Boutons supplémentaires
9 avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
Autres articles (62)
-
L’agrémenter visuellement
10 avril 2011MediaSPIP est basé sur un système de thèmes et de squelettes. Les squelettes définissent le placement des informations dans la page, définissant un usage spécifique de la plateforme, et les thèmes l’habillage graphique général.
Chacun peut proposer un nouveau thème graphique ou un squelette et le mettre à disposition de la communauté. -
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 -
Contribute to translation
13 avril 2011You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
MediaSPIP is currently available in French and English (...)
Sur d’autres sites (7613)
-
Decoding H.264 UDP stream
24 février 2019, par user2422659I have to work with ’FFMPEG’ in order to decode ’UDP’ streaming(Not ’RTP’ or ’RTSP’) of raw ’h264’ video.address.
So far i have compiled and make ’ffplay’ decode successfully a local ’h264’ file.
Now i have to add support of that ’UDP’ listener who will get chunks of data.
As far as i understand ’AVFormatContext.fileName’ gets a file name or ’RTSP’
Any help ?
what is the proper way to do this ?Thanks in advanced.
-
sdp : Add an option for sending RTCP packets to the source of the last packets
13 août 2013, par Martin Storsjösdp : Add an option for sending RTCP packets to the source of the last packets
An SDP description normally only contains the target IP address
and port for the packets. This means that we don’t really have
any clue where to send the RTCP RR packets - previously they’re
sent to the destination IP written in the SDP (at the same port),
which rarely is the actual peer. And if the source for the packets
is on a different port than the destination, it’s never correct.With a new option, we can choose to send the packets to the
address that the latest packet on each socket arrived from.
— -
Some may even argue that this should be the default - perhaps,
but I’d rather keep it optional at first. Additionally, I’m not
sure if sending RTCP RR directly back to the source is
desireable for e.g. multicast.Signed-off-by : Martin Storsjö <martin@martin.st>
-
Disk [videos] does not have a configured driver
25 septembre 2024, par oshakabI am trying to create a thumbnail using laravel and ffmpeg. But am getting this error.



Disk [videos] does not have a configured driver.



My code



public function index()
{
 FFMpeg::fromDisk('videos')
 ->open('steve_howe.mp4')
 ->getFrameFromSeconds(10)
 ->export()
 ->toDisk('thumnails')
 ->save('FrameAt10sec.png');
 // $videos = Videos::where('user_email', Auth::user()->email)->get();
 // return view('instructor.videos')->with('videost', $videos);
}




What could be the solution. Thanks