Recherche avancée

Médias (29)

Mot : - Tags -/Musique

Autres articles (54)

  • (Dés)Activation de fonctionnalités (plugins)

    18 février 2011, par

    Pour gérer l’ajout et la suppression de fonctionnalités supplémentaires (ou plugins), MediaSPIP utilise à partir de la version 0.2 SVP.
    SVP permet l’activation facile de plugins depuis l’espace de configuration de MediaSPIP.
    Pour y accéder, il suffit de se rendre dans l’espace de configuration puis de se rendre sur la page "Gestion des plugins".
    MediaSPIP est fourni par défaut avec l’ensemble des plugins dits "compatibles", ils ont été testés et intégrés afin de fonctionner parfaitement avec chaque (...)

  • Soumettre bugs et patchs

    10 avril 2011

    Un logiciel n’est malheureusement jamais parfait...
    Si vous pensez avoir mis la main sur un bug, reportez le dans notre système de tickets en prenant bien soin de nous remonter certaines informations pertinentes : le type de navigateur et sa version exacte avec lequel vous avez l’anomalie ; une explication la plus précise possible du problème rencontré ; si possibles les étapes pour reproduire le problème ; un lien vers le site / la page en question ;
    Si vous pensez avoir résolu vous même le bug (...)

  • Installation en mode standalone

    4 février 2011, par

    L’installation de la distribution MediaSPIP se fait en plusieurs étapes : la récupération des fichiers nécessaires. À ce moment là deux méthodes sont possibles : en installant l’archive ZIP contenant l’ensemble de la distribution ; via SVN en récupérant les sources de chaque modules séparément ; la préconfiguration ; l’installation définitive ;
    [mediaspip_zip]Installation de l’archive ZIP de MediaSPIP
    Ce mode d’installation est la méthode la plus simple afin d’installer l’ensemble de la distribution (...)

Sur d’autres sites (6184)

  • Wowza : Live stream detected but does not play

    2 septembre 2016, par searcot jabali

    This is the command I use to being the stream on my hardware device
    ffmpeg -i /dev/video0 -f rtsp rtsp ://[user] :[password]@52.66.64.136:1935/test/myStream

    I can see that there is an input coming in from the Incoming Streams section of the Wowza Engine Manager.
    The IP, Stream name & Application name are correct.
    Wowza Engine Manager

    However when I try to play the stream using the Test Players, I dont see anything. Just a black screen.
    An error message at the bottom of Adobe HDS says Source stream or file could not be found or access was denied.

    Wowza Test Player

    When I try to use the RTSP wowza link on VLC I get an error stating that the "Input Cannot Be opened"

    Source security for RTSP has been set to open.

    When I stream through the GoCoder App there are no issues.
    This leads me to believe the server is functioning correctly.

    When I use the same command but change the output to write to file (ffmpeg -i /dev/video0 out.mp4) it works perfectly fine !!
    So even the base command is correct.

    Am I missing some arguments from the FFMPEG command ?
    Do I need to provide the username & password even though RTSP Source Security has been set to open ?

  • Piwik 3 Development Update #1 – New UI design, API changes & release date

    1er septembre 2016, par Thomas Steur — Community, Development

    Over the last months, we have been actively working on the Piwik 3 release and we want to introduce you to the changes that we have done so far. They include a new and modern UI redesign, new widgets for your dashboard, and technical improvements under the hood.

    New Piwik 3 UI

    Based on Material Design we have revamped the user interface which is now more responsive, more usable and faster. While the UI is not yet finished, we invite you to check it out already and to let us know what you think.

    This new Piwik material design is a visual language that synthesizes classic principles of good design with the innovation and possibility of technology and science.

    More responsive

    Piwik 3 will look and feel much better on your mobile phone and tablet. Many elements have been improved : the menus, the segment editor and dashboard selector, the widgets, the settings pages and most other pages so you can fully experience and enjoy Piwik on any device !

    Improved usability

    We have updated the menu structure, the dashboard selector as well as the footer in reports to make your life easier when using Piwik. We love to keep these complicated things simple. There are also many other tiny improvements that you will appreciate.

    The Zen Mode lets you view in full screen your analytics reports and dashboards. Users love this feature and it can now be accessed by pressing “z” key.

    Faster

    To make the Piwik interface faster, we have refactored most of our CSS, HTML and JavaScript and moved more and more of our code into the client. As a result, Piwik now needs to reload the page much less often ! For example when you change the date or change the segment, Piwik will now load the reports instantly. To improve performance even further, Piwik will now load multiple reports on a single page in parallel.

    Native fonts

    Over the last months more and more web services have started using system fonts, and so will Piwik 3. System fonts look better, improve language support and give you a more native, familiar feeling.

    For more details and screenshots have a look at the pull request for the Piwik 3 UI update.

    New widgets

    With the “Latest Piwik Plugin Updates” widget you won’t miss any newly added or updated plugin anymore. This will help you learn about and discover the useful plugins and themes available on the Marketplace.

    Super users can now see at a glance the current state of the Piwik system, thanks to the new “System Check” and “System Summary” widgets.

    API Changes

    Piwik is the leading open analytics platform, highly customisable and extensible thanks to a flexible plugins architecture and a design based on APIs. In this new major Piwik 3 release, we significantly improve the foundation of our open platform and several of its core APIs.

    The new Widgets and Reporting API makes it possible to add reports and widgets to any existing reporting page. In the past, reporting pages had to be created manually which was time consuming and it was hard to maintain a consistent look across different reporting pages. Now reporting pages are generated automatically by the Piwik platform.

    The Plugin Settings API was changed to improve performance and to let plugin developers customize the Websites Manager. This is one step towards our goal to let users not only manage websites but also mobile apps, cars, coffee machines or any other thing.

    To see a full list of changes in the Piwik 3 analytics platform, have a look at the developer changelog.

    Developer docs

    The Piwik Developer Zone is full of guides and API references to help developers understand, integrate and extend Piwik. As some APIs have changed in the Piwik 3 release it is now possible to select the Piwik version in the top right corner of the developer zone.

    We are updating guides for Piwik 3 and added a Piwik 2 -> Piwik 3 Migration Guide for plugin developers. Many other guides were updated such as Menus, Custom Report and Widgets.

    Release date

    The first Piwik 3 beta release will be available in the next four weeks. Beta testers automatically receive the update if they are subscribed to the “Latest Beta” release channel. The final Piwik 3 release will be ready before the end of the year. If you want to give it a try, you can either use Piwik from Git and check out the “3.x-dev” branch, or download Piwik 3 from GitHub.

    Closing thoughts

    With faster & more beautiful reports, better APIs and more stability, Piwik 3 is a big step forward for all Piwik users. As our mission is to create, as a community, the leading international open source web analytics platform that gives every user full control of their data, we are very excited to introduce you to this upcoming release.

    We now offer Custom Development services if you like to sponsor a new feature or bug fix, or if you have any custom requirements. And if you use Piwik Analytics to grow your business and need quality help, contact the Piwik analytics experts to get started.

    Until our next Piwik 3 dev update, Happy analysis !

  • compile ffmpeg decode only without audio codecs

    28 juillet 2016, par Rob

    I work on a media manager and use ffmpeg.exe to extract screenshots.
    With the latest size of ffmpeg.exe exceeding 35MB, I am attempting to build ffmpeg without the majority of its functions, to allow only saving of a frame of video.

    I had thought disabling many of the filters, Audio Codecs etc would shrink the size of ffmpeg to something more manageable.

    Following this guide
    https://pracucci.com/compile-ffmpeg-on-windows-with-visual-studio-compiler.html
    to allow building of ffmpeg using Visual Studio 2015, I have come to the part of ./configuration and hit a wall.
    With so many options and no idea what all of them mean or do, I am asking if someone in the community can give me laymans instructions.

    I also know that I need to build x264, and possible x265 (HEVC), but am not sure if there is anything other codecs needed.
    In the end, I and am hoping to just have the one file, ffmpeg.exe for use in the media manager project.

    The code I use to get a screenshot is as follows

    Public Shared Function CreateScreenShot(ByVal FullPathAndFilename As String, ByVal SavePath As String, ByVal sec As Integer, Optional ByVal Overwrite As Boolean = False) As Boolean
       If Not File.Exists(SavePath) Or Overwrite Then
           Try
               IO.File.Delete(SavePath)
           Catch
               Return False
           End Try
           If IO.File.Exists(FullPathAndFilename) Then
               Dim myProcess As Process = New Process
               Try
                   Dim seconds As Integer = sec
                   myProcess.StartInfo.WindowStyle = ProcessWindowStyle.Hidden
                   myProcess.StartInfo.CreateNoWindow = False
                   myProcess.StartInfo.FileName = Utilities.applicationPath & "\Assets\ffmpeg.exe"
                   Dim proc_arguments As String = "-ss " & seconds.ToString & " -i """ & FullPathAndFilename & """ -vframes:v 1 -an " & """" & SavePath & """"
                   myProcess.StartInfo.Arguments = proc_arguments
                   myProcess.Start()
                   myProcess.WaitForExit()
                   If File.Exists(SavePath) Then Return True
               Catch ex As Exception
                   Throw ex
               Finally
                   myProcess.Close()
               End Try
           End If
       End If
       Return False
    End Function

    I hope this is sufficient information, and appreciated any help or suggestions.