Recherche avancée

Médias (91)

Autres articles (98)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Les vidéos

    21 avril 2011, par

    Comme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
    Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
    Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

Sur d’autres sites (5874)

  • How to change metadata with ffmpeg/avconv ?

    14 juillet 2012, par tampis

    I am writing a python script for producing audio and video podcasts. There are a bunch of recorded media files (audio and video) and text files containing the meta information.

    Now I want to program a function which shall add the information from the meta data text files to all media files (the original and the converted ones). Because I have to handle many different file formats (wav, flac, mp3, mp4, ogg, ogv...) it would be great to have a tool which add meta data to arbitrary formats.

    My Question :

    How can I change the metadata of a file with ffmpeg/avconv without changing the audio or video of it and without creating a new file ? Is there another commandline/python tool which would do the job for me ?

    What I tried so far :

    I thought ffmpeg/avconv could be such a tool, because it can handle nearly all media formats. I hoped, that if I set -i input_file and the output_file to the same file, ffmpeg/avconv will be smart enough to leave the file unchanged. Then I could set -metadata key=value and just the metadata will be changed.

    But I noticed, that if I type avconv -i test.mp3 -metadata title='Test title' test.mp3 the audio test.mp3 will be reconverted in another bitrate.

    So I thought to use -c copy to copy all video and audio information. Unfortunately also this does not work :

    :~$ du -h test.wav # test.wav is 303 MB big
    
303M    test.wav
    

    
:~$ avconv -i test.wav -c copy -metadata title='Test title' test.wav
    
avconv version 0.8.3-4:0.8.3-0ubuntu0.12.04.1, Copyright (c) 2000-2012 the
    
Libav    developers
    
built on Jun 12 2012 16:37:58 with gcc 4.6.3
    
[wav @ 0x846b260] max_analyze_duration reached
    
Input #0, wav, from 'test.wav':
    
Duration: 00:29:58.74, bitrate: 1411 kb/s
    
    Stream #0.0: Audio: pcm_s16le, 44100 Hz, 2 channels, s16, 1411 kb/s
    
File 'test.wav' already exists. Overwrite ? [y/N] y
    
Output #0, wav, to 'test.wav':
    
Metadata:
    
    title           : Test title
    
    encoder         : Lavf53.21.0
    
    Stream #0.0: Audio: pcm_s16le, 44100 Hz, 2 channels, 1411 kb/s
    
Stream mapping:
    
Stream #0:0 -> #0:0 (copy)
    
Press ctrl-c to stop encoding
    
size=     896kB time=5.20 bitrate=1411.3kbits/s    
    
video:0kB audio:896kB global headers:0kB muxing overhead 0.005014%
    

    
:~$ du -h test.wav # file size of test.wav changed dramatically
    
900K    test.wav

    You see, that I cannot use -c copy if input_file and output_file are the same. Of course I could produce a temporarily file :

    :-$ avconv -i test.wav -c copy -metadata title='Test title' test_temp.mp3
    
:-$ mv test_tmp.mp3 test.mp3

    But this solution would create (temporarily) a new file on the filesystem and is therefore not preferable.

  • Premium Plugins now available on the Piwik Analytics Marketplace

    2 novembre 2016, par Piwik Core Team — Community, Press Releases

    We are super excited to announce the launch of three new premium plugins which are now available on the Piwik Marketplace : A/B Testing, Media Analytics, and Activity Log.

    All three plugins are easy to use and come with 100% data ownership, documentation, integration with Piwik, powerful data exports and no data limits.

    These first premium plugins and the new Marketplace capabilities have been designed and built with love by InnoCraft – the new company brought to you by the makers of Piwik.

    1. A/B Testing

    A/B Testing helps you grow your business by comparing different versions of your website or app to detect the most successful version that increases your sales, revenue, conversions, pageviews, and more.

    A/B tests are also known as experiments or split tests. In an A/B test you show two or more different variations to your users (visitors) and the variation that performs better wins. When a user enters the experiment, a variation will be randomly chosen and the user will see this variation for all subsequent visits. Piwik A/B testing uses advanced statistical analysis to detect which variation performs better for your conversion goals and success metrics. Even small tests can increase your sales and conversions massively !

    Learn more here :

    2. Media Analytics

    Do you have videos or audio on your website, or in an app ? Media Analytics gives you powerful insights into how your audience watches your videos and listens to your audio, to ultimately maximize your success.

    Learn all about your audience. Which media your users are playing, for how long, how often, and where they dropped off ? Where are your users located around the world ? Who your audience are and what did people do before and after watching a video or listening to audio ? Many of the reports are also available in Real time, so you can gain insights and react quickly.

    Learn more here :

    3. Activity log

    Keep an eye on everything that is happening on your Piwik platform with the Activity Log plugin.

    The activity log, also known as audit log or audit trail, improves your Piwik’s security and diagnostic by showing a chronological set of entries that provides documentary evidence of activities that happened in your Piwik. It allows Piwik Super Users to quickly review the actions performed by members of your organization or clients, and also lets every user review details of their own actions.

    Learn more in the Activity Log FAQ or see a list of all the features on the Marketplace : Activity Log plugin.

    The Piwik Marketplace guarantees

    Purchasing on the Piwik Marketplace is easy and safe. Check out our guarantees :

    Why premium plugins ?

    Researching, building, documenting, testing and maintaining quality products take years of experience and months of work. When you purchase a premium plugin from the Marketplace, you get a fully working product, with free updates for the duration of the license and you stay in full control of your analytics data. When purchasing premium plugins you also directly help the Piwik core engineers to continue to grow and innovate ! That’s because a % of earnings on premium plugin license sales directly fund new Piwik versions and more amazing features. Learn more in the FAQ : What are premium plugins ?.

    About InnoCraft

    These first three premium plugins have been designed and built with love by InnoCraft. InnoCraft is a new company founded by the creator of Piwik along with the lead engineers of Piwik based in Wellington, New Zealand. At InnoCraft, product experts, designers and engineers are passionate about crafting high quality and innovative products to help grow your business and to maximize your success.

    Learn more on the company website : www.innocraft.com

    To stay updated on their releases, follow InnoCraftHQ on Twitter or Like InnoCraft on Facebook.

    Is the Piwik Marketplace open to all ?

    Yes, our marketplace allows other companies and developers to sell their plugins to all Piwik Analytics users. If you are a developer or a company interested in selling your plugin(s) on our Marketplace please contact us. As a developer selling plugins, you will get paid every month for your earnings, and you will be able to see detailed reports about your sales, upload new plugin updates, respond to pre-sales enquiries, etc.

    Resources

    Learn more :

    We are looking forward to your continued support with the Piwik project as we expand and offer you more ways to maximize your success.

    Please contact the Marketplace team with any questions or feedback.

    Wishing you a warm : Happy Analytics !

  • Winamp and the March of GUI

    1er juillet 2012, par Multimedia Mike — General, ars technica, gui, user interface, winamp

    Ars Technica recently published a 15-year retrospective on the venerable Winamp multimedia player, prompting bouts of nostalgia and revelations of "Huh ? That program is still around ?" from many readers. I was among them.



    I remember first using Winamp in 1997. I remember finding a few of these new files called MP3s online and being able to play the first 20 seconds using the official Fraunhofer Windows player— full playback required the fully licensed version. Then I searched for another player and came up with Winamp. The first version I ever used was v1.05 in the summer of 1997. I remember checking the website often for updates and trying out every single one. I can’t imagine doing that nowadays— programs need to auto-update themselves (which Winamp probably does now ; I can’t recall the last time I used the program).

    Video Underdog
    The last time Winamp came up on my radar was early in 2003 when a new version came with support for a custom, proprietary multimedia audio/video format called Nullsoft Video (NSV). I remember the timeframe because the date is indicated in the earliest revision of my NSV spec document (back when I was maintaining such docs in a series of plaintext files). This was cobbled together from details I and others in the open source multimedia community sorted out from sample files. It was missing quite a few details, though.

    Then, Winamp founder Justin Frankel — introduced through a colleague on the xine team — emailed me his official NSV format and told me I was free to incorporate details into my document just as long as it wasn’t obvious that I had the official spec. This put me in an obnoxious position of trying to incorporate details which would have been very difficult to reverse engineer without the official doc. I think I coped with the situation by never really getting around to updating my doc in any meaningful way. Then, one day, the official spec was released to the world anyway, and it is now mirrored here at multimedia.cx.

    I don’t think the format ever really caught on in any meaningful way, so not a big deal. (Anytime I say that about a format, I always learn it saw huge adoption is some small but vocal community.)

    What’s Wrong With This Picture ?
    What I really wanted to discuss in this post was the matter of graphical user interfaces and how they have changed in the last 15 years.

    I still remember when I first downloaded Winamp v1.05 and tried it on my Windows machine at the time. Indignantly, the first thought I had was, "What makes this program think it’s so special that it’s allowed to violate the user interface conventions put forth by the rest of the desktop ?" All of the Windows programs followed a standard set of user interface patterns and had a consistent look and feel... and then Winamp came along and felt it could violate all those conventions.

    I guess I let the program get away with it because it was either that or only play 20-second clips from the unregistered Fraunhofer player. Though incredibly sterile by comparison, the Fraunhofer player, it should be noted, followed Windows UI guidelines to the letter.

    As the summer of 1997 progressed and more Winamp versions were released, eventually one came out (I think it was v1.6 or so) that supported skins. I was excited because there was a skin that made the program look like a proper Windows program— at least if you used the default Windows color scheme, and had all of your fonts a certain type and size.

    Skins were implemented by packaging together a set of BMP images to overlay on various UI elements. I immediately saw a number of shortcomings with this skinning approach. A big one was UI lock-in. Ironically, if you skin an app and wish to maintain backwards compatibility with the thousands of skins selflessly authored by your vibrant community (seriously, I couldn’t believe how prolific these things were), then you were effectively locked into the primary UI. Forget about adding a new button anywhere.

    Another big problem was resolution-independence. Basing your UI on static bitmaps doesn’t scale well with various resolutions. Winamp had its normal mode and it also had double-sized mode.

    Skins proliferated among many types of programs in the late 1990s. I always treasured this Suck.com (remember them ? that’s a whole other nostalgia trip) essay from April, 2000 entitled Skin Cancer. Still, Winamp was basically the standard, and the best, and I put away my righteous nerd rage and even dug through the vast troves of skins. I remember settling on Swankamp for a good part of 1998, probably due to the neo-swing revival at the time.



    Then again, if Winamp irked me, imagine my reaction when I was first exposed to the Sonique Music Player in 1998 :



    The New UI Order
    Upon reflection, I realize now that I had a really myopic view of what a computer GUI should be. I thought the GUIs were necessarily supposed to follow the WIMP (windows, icons, mouse, pointer) paradigm and couldn’t conceive of anything different. For a long time, I couldn’t envision a useful GUI on a small device (like a phone) because WIMP didn’t fit well on such a small interface (even though I saw various ill-fated attempts to make it work). This thinking seriously crippled me when I was trying to craft a GUI for a custom console media player I was developing as a hobby many years ago.

    I’m looking around at what I have open on my Windows 7 desktop right now. Google Chrome browser, Apple iTunes, Adobe Photoshop Elements, and VMware Player are 4 programs which all seem to have their own skins. Maybe Winamp doesn’t look so out of place these days.

Navigation