Recherche avancée

Médias (21)

Mot : - Tags -/Nine Inch Nails

Autres articles (74)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

  • 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 ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

Sur d’autres sites (9502)

  • Bump dates to 2019

    31 janvier 2019, par Henrik Gramner
    Bump dates to 2019
    
    • [DH] autocomplete.c
    • [DH] common/aarch64/asm-offsets.c
    • [DH] common/aarch64/asm-offsets.h
    • [DH] common/aarch64/asm.S
    • [DH] common/aarch64/bitstream-a.S
    • [DH] common/aarch64/bitstream.h
    • [DH] common/aarch64/cabac-a.S
    • [DH] common/aarch64/dct-a.S
    • [DH] common/aarch64/dct.h
    • [DH] common/aarch64/deblock-a.S
    • [DH] common/aarch64/deblock.h
    • [DH] common/aarch64/mc-a.S
    • [DH] common/aarch64/mc-c.c
    • [DH] common/aarch64/mc.h
    • [DH] common/aarch64/pixel-a.S
    • [DH] common/aarch64/pixel.h
    • [DH] common/aarch64/predict-a.S
    • [DH] common/aarch64/predict-c.c
    • [DH] common/aarch64/predict.h
    • [DH] common/aarch64/quant-a.S
    • [DH] common/aarch64/quant.h
    • [DH] common/arm/asm.S
    • [DH] common/arm/bitstream-a.S
    • [DH] common/arm/bitstream.h
    • [DH] common/arm/cpu-a.S
    • [DH] common/arm/dct-a.S
    • [DH] common/arm/dct.h
    • [DH] common/arm/deblock-a.S
    • [DH] common/arm/deblock.h
    • [DH] common/arm/mc-a.S
    • [DH] common/arm/mc-c.c
    • [DH] common/arm/mc.h
    • [DH] common/arm/pixel-a.S
    • [DH] common/arm/pixel.h
    • [DH] common/arm/predict-a.S
    • [DH] common/arm/predict-c.c
    • [DH] common/arm/predict.h
    • [DH] common/arm/quant-a.S
    • [DH] common/arm/quant.h
    • [DH] common/base.c
    • [DH] common/base.h
    • [DH] common/bitstream.c
    • [DH] common/bitstream.h
    • [DH] common/cabac.c
    • [DH] common/cabac.h
    • [DH] common/common.c
    • [DH] common/common.h
    • [DH] common/cpu.c
    • [DH] common/cpu.h
    • [DH] common/dct.c
    • [DH] common/dct.h
    • [DH] common/deblock.c
    • [DH] common/frame.c
    • [DH] common/frame.h
    • [DH] common/macroblock.c
    • [DH] common/macroblock.h
    • [DH] common/mc.c
    • [DH] common/mc.h
    • [DH] common/mips/dct-c.c
    • [DH] common/mips/dct.h
    • [DH] common/mips/deblock-c.c
    • [DH] common/mips/deblock.h
    • [DH] common/mips/macros.h
    • [DH] common/mips/mc-c.c
    • [DH] common/mips/mc.h
    • [DH] common/mips/pixel-c.c
    • [DH] common/mips/pixel.h
    • [DH] common/mips/predict-c.c
    • [DH] common/mips/predict.h
    • [DH] common/mips/quant-c.c
    • [DH] common/mips/quant.h
    • [DH] common/mvpred.c
    • [DH] common/opencl.c
    • [DH] common/opencl.h
    • [DH] common/osdep.c
    • [DH] common/osdep.h
    • [DH] common/pixel.c
    • [DH] common/pixel.h
    • [DH] common/ppc/dct.c
    • [DH] common/ppc/dct.h
    • [DH] common/ppc/deblock.c
    • [DH] common/ppc/deblock.h
    • [DH] common/ppc/mc.c
    • [DH] common/ppc/mc.h
    • [DH] common/ppc/pixel.c
    • [DH] common/ppc/pixel.h
    • [DH] common/ppc/ppccommon.h
    • [DH] common/ppc/predict.c
    • [DH] common/ppc/predict.h
    • [DH] common/ppc/quant.c
    • [DH] common/ppc/quant.h
    • [DH] common/predict.c
    • [DH] common/predict.h
    • [DH] common/quant.c
    • [DH] common/quant.h
    • [DH] common/rectangle.c
    • [DH] common/rectangle.h
    • [DH] common/set.c
    • [DH] common/set.h
    • [DH] common/tables.c
    • [DH] common/tables.h
    • [DH] common/threadpool.c
    • [DH] common/threadpool.h
    • [DH] common/vlc.c
    • [DH] common/win32thread.c
    • [DH] common/win32thread.h
    • [DH] common/x86/bitstream-a.asm
    • [DH] common/x86/bitstream.h
    • [DH] common/x86/cabac-a.asm
    • [DH] common/x86/const-a.asm
    • [DH] common/x86/cpu-a.asm
    • [DH] common/x86/dct-32.asm
    • [DH] common/x86/dct-64.asm
    • [DH] common/x86/dct-a.asm
    • [DH] common/x86/dct.h
    • [DH] common/x86/deblock-a.asm
    • [DH] common/x86/deblock.h
    • [DH] common/x86/mc-a.asm
    • [DH] common/x86/mc-a2.asm
    • [DH] common/x86/mc-c.c
    • [DH] common/x86/mc.h
    • [DH] common/x86/pixel-32.asm
    • [DH] common/x86/pixel-a.asm
    • [DH] common/x86/pixel.h
    • [DH] common/x86/predict-a.asm
    • [DH] common/x86/predict-c.c
    • [DH] common/x86/predict.h
    • [DH] common/x86/quant-a.asm
    • [DH] common/x86/quant.h
    • [DH] common/x86/sad-a.asm
    • [DH] common/x86/sad16-a.asm
    • [DH] common/x86/trellis-64.asm
    • [DH] common/x86/util.h
    • [DH] common/x86/x86inc.asm
    • [DH] common/x86/x86util.asm
    • [DH] encoder/analyse.c
    • [DH] encoder/analyse.h
    • [DH] encoder/api.c
    • [DH] encoder/cabac.c
    • [D
  • Today we celebrate Data Privacy Day 2019

    28 janvier 2019, par Jake Thornton — Privacy

    Today we celebrate Data Privacy Day 2019 !!!

    What is Data Privacy Day ?

    Wikipedia tells us that : The purpose of Data Privacy Day is to raise awareness and promote privacy and data protection best practices.

    Our personal data is our online identity. When you think what personal data means – our phone records, credit card transactions, GPS position, IP addresses, browsing history and so much more. All so valuable and personal to us as human beings.

    That’s why we cannot take our personal data online for granted. We have a right to know which websites collect our data and how it’s then used, something that’s often not visible or easily recognisable when browsing.

    What Data Privacy Day means to Matomo

    Every year the team at Matomo uses this day as a chance to reflect on how far the Matomo (formerly Piwik) project has come. But then also reflect how far we still have to go in spreading the message that our data and personal information online matters.

    2018 saw the introduction of the EU General Data Protection Regulation (GDPR) to protect people’s data online. As a team, Matomo was at the forefront of this development in the analytics space and have since built a GDPR Manager to ensure our users can be fully compliant with the GDPR.

    With every new release of Matomo, we are ensuring that security continues to be at the highest standard and we will continue to be committed to our bug bounty program. Our most recent release of Matomo 3.8.0 alone added a Two Factor Authentication (2FA) feature and a password brute force prevention.

    What next for Matomo and data privacy ?

    As always, security is a top priority for every new release of Matomo and continues to only get better and better. We have a duty to spread our message further that the protection of personal data matters and today is a vital reminder of that. We are, and forever will be, the #1 open-source (and free to use) web analytics platform in the world that fully respects user privacy and gives our users 100% data ownership.

    In 2018 we changed our name, we updated our logo and website, and advanced our platform to compete with the most powerful web analytics tools in the world, all so we can spread our message further and continue our mission.

    Come with us on this exciting journey. Now is the time to take back control of your data and let’s continue creating a safer web for everyone.

    Please help us spread this message.

  • c# how to capture audio from nvlc and raise Accord.Audio.NewFrameEventArgs

    30 septembre 2018, par MATRIX81

    I’m working on the application in c# that record video stream from IP cameras.

    I’m using Accord.Video.FFMPEG.VideoFileWriter and nVLC C# wrapper.
    I have a class that captures audio from the stream using nVLC, which should implement the IAudioSource interface, so I’ve used CustomAudioRendere to capture sound data, then raised the event NewFrame that contains the signal object.
    The problem is when saving the signal to video file, the sound is terrifying(discrete) when the record from RTSP stream, but in good quality when the record from the local mic(from the laptop).
    Here is the code that raises the event :

    public void Start()
       {
           _mFactory = new MediaPlayerFactory();
           _mPlayer = _mFactory.CreatePlayer<iaudioplayer>();
           _mMedia = _mFactory.CreateMedia<imedia>(Source);
           _mPlayer.Open(_mMedia);

           var fc = new Func(SoundFormatCallback);
           _mPlayer.CustomAudioRenderer.SetFormatCallback(fc);
           var ac = new AudioCallbacks { SoundCallback = SoundCallback };
           _mPlayer.CustomAudioRenderer.SetCallbacks(ac);

           _mPlayer.Play();
       }

       private void SoundCallback(Sound newSound)
       {

           var data = new byte[newSound.SamplesSize];
           Marshal.Copy(newSound.SamplesData, data, 0, (int)newSound.SamplesSize);

           NewFrame(this, new Accord.Audio.NewFrameEventArgs(new Signal(data,Channels, data.Length, SampleRate, Format)));
       }

       private SoundFormat SoundFormatCallback(SoundFormat arg)
       {


           Channels = arg.Channels;
           SampleRate = arg.Rate;
           BitPerSample = arg.BitsPerSample;

           return arg;

       }
    </imedia></iaudioplayer>

    And here is the code that captures the event :

    private void source_NewFrame(object sender, NewFrameEventArgs eventArgs)
       {
           Signal sig = eventArgs.Signal;

           duration += eventArgs.Signal.Duration;
           if (videoFileWrite == null)
           {


               videoFileWrite = new VideoFileWriter();
               videoFileWrite.AudioBitRate = sig.NumberOfSamples*sig.NumberOfChannels*sig.SampleSize;
               videoFileWrite.SampleRate = sig.SampleRate;
               videoFileWrite.FrameSize = sig.NumberOfSamples/sig.NumberOfFrames;


               videoFileWrite.Open("d:\\output.mp4");
           }
           if (isStartRecord)
           {
               DoneWriting = false;

               using (MemoryStream ms = new MemoryStream())
               {
                   encoder = new WaveEncoder(ms);
                   encoder.Encode(eventArgs.Signal);
                   ms.Seek(0, SeekOrigin.Begin);
                   decoder = new WaveDecoder(ms);
                   Signal s = decoder.Decode();
                   videoFileWrite.WriteAudioFrame(s);

                   encoder.Close();
                   decoder.Close();

               }
               DoneWriting = true;
           }
       }