Recherche avancée

Sur d’autres sites (15748)

• Join us for the Piwik Community Meetup 2015 !

  25 juin 2015, par Piwik Core Team — Community, Meta

  

  We’re excited to announce that our third Piwik Community Meetup will be held in Berlin on Tuesday, the 4th of August, 2015. Don’t miss this great opportunity to connect with other users and meet the core team behind Piwik. It’s free, so REGISTER TODAY ! And maybe you would like to share your Piwik use case ? We’re also waiting for your presentation ideas.

  We will cover some of the upcoming features, discuss the future of Piwik, share tricks and hacks to help you get the most out of your Piwik platform, and socialise. If you use Piwik to improve your websites and apps, or are just generally curious about digital analytics and marketing – this event is not to be missed. As our core team is scattered all over the world, this will be a rare opportunity for you to meet and talk to us all at once – especially for those of you interested in the platform, integrating your app with Piwik, and building plugins.

  After the official part, we would like to enjoy drinks with all the participants in the nearby bars. We hope you will be able to join us !

  All Piwik community members are warmly invited to take part in the meetup !

  Piwik Community Meetup 2015

  When ?

  Tuesday, the 4th of August, from 5-9pm

  Where ?

  Kulturbrauerei
  Schönhauser Allee
  Prenzlauer Berg area
  Berlin, Germany
  exact directions tbc.

  Languages :

  English and German

  Book tickets :

  BOOK YOUR FREE INVITATION HERE

  Open call for YOUR presentation ideas

  We would also like to hear how you use Piwik – we’ll be delighted if you’d share your interesting use case during the Meetup. Please send your presentation ideas (speaking time : 5 to 7 minutes) to : meetup@piwik.pro ! Deadline : 20th of July 2015.

  Contact the organisers :

  meetup@piwik.pro

• Documentation #3972 : template variants and possible bug ?

  6 juillet 2017, par Kamran Mir Hazar

  I have SPIP 3.1.6 [23444].

  On Thu, Jul 6, 2017 at 8:20 PM, <redmine@spip.org> wrote :

  La demande #3972 a été mise à jour par nico d_.

  Hi,
  which version of SPIP are you using ?

  ---

  Anomalie #3972 : template variants and possible bug ?

  Auteur : Kamran Mir Hazar
  Statut : Nouveau
  Priorité : Normal
  Assigné à :
  Catégorie :
  Version cible :
  Resolution :
  Navigateur :

  Hello,
  The following template variants do not work for me :
  I have section number 101, with articles in fa and en languages in it.
  I have also files article.html for the main site’s language which is fa, and
  article.en.html for the en language articles. Both work fine in general. I
  created two other variants to apply articles in section 101 with two
  separate languages. They are : article=101.fa.html and article=101.en.html .
  SPIP ignores these two variants and proceeds article.html for fa language
  articles, and article.en.html for en language articles in section 101, like
  the other sections. I added also article=101.html to see if it works, but
  didn’t.
  I asked this in French and English mailing lists, but couldn’t find any
  solution.
  Thank you
  Kamran

  PS : I tried based of the following article :
  https://www.spip.net/en_article4363.html

  ---

  Vous recevez ce mail car vous êtes impliqués sur ce projet.
  Pour changer les préférences d’envoi de mail, allez sur
  http://core.spip.org/my/account

• Ffmpeg only receives a piece of information from the pipe

  4 juillet 2017, par Maxim Fedorov

  First of all - my english is not very good, i`m sorry for that.

  I use ffmpeg from c# to convert images to video. To interact with ffmpeg, I use pipes.

  public async Task ExecuteCommand(
  
          string arguments,
  
          Action<namedpipeserverstream> sendDataUsingPipe)
  
      {
  
          var inStream = new NamedPipeServerStream(
  
              "from_ffmpeg",
  
              PipeDirection.In,
  
              1,
  
              PipeTransmissionMode.Byte,
  
              PipeOptions.Asynchronous,
  
              PipeBufferSize,
  
              PipeBufferSize);
  
  
  
          var outStream = new NamedPipeServerStream(
  
              "to_ffmpeg",
  
              PipeDirection.Out,
  
              1,
  
              PipeTransmissionMode.Byte,
  
              PipeOptions.Asynchronous,
  
              PipeBufferSize,
  
              PipeBufferSize);
  
  
  
          var waitInConnectionTask = inStream.WaitForConnectionAsync();
  
          var waitOutConnectionTask = outStream.WaitForConnectionAsync();
  
  
  
          byte[] byteData;
  
  
  
          using (inStream)
  
          using (outStream)
  
          using (var inStreamReader = new StreamReader(inStream))
  
          using (var process = new Process())
  
          {
  
              process.StartInfo = new ProcessStartInfo
  
              {
  
                  RedirectStandardOutput = true,
  
                  RedirectStandardError = true,
  
                  RedirectStandardInput = true,
  
                  FileName = PathToFfmpeg,
  
                  Arguments = arguments,
  
                  UseShellExecute = false,
  
                  CreateNoWindow = true
  
              };
  
  
  
              process.Start();
  
  
  
              await waitOutConnectionTask;
  
  
  
              sendDataUsingPipe.Invoke(outStream);
  
  
  
              outStream.Disconnect();
  
              outStream.Close();
  
  
  
              await waitInConnectionTask;
  
  
  
              var logTask = Task.Run(() => process.StandardError.ReadToEnd());
  
              var dataBuf = ReadAll(inStream);
  
  
  
              var shouldBeEmpty = inStreamReader.ReadToEnd();
  
              if (!string.IsNullOrEmpty(shouldBeEmpty))
  
                  throw new Exception();
  
  
  
              var processExitTask = Task.Run(() => process.WaitForExit());
  
              await Task.WhenAny(logTask, processExitTask);
  
              var log = logTask.Result;
  
  
  
              byteData = dataBuf;
  
  
  
              process.Close();
  
              inStream.Disconnect();
  
              inStream.Close();
  
          }
  
  
  
          return byteData;
  
      }
  
  </namedpipeserverstream>

  Action "sendDataUsingPipe" looks like

  Action<namedpipeserverstream> sendDataUsingPipe = stream =>
  
          {
  
              foreach (var imageBytes in data)
  
              {
  
                  using (var image = Image.FromStream(new MemoryStream(imageBytes)))
  
                  {
  
                      image.Save(stream, ImageFormat.Jpeg);
  
                  }
  
              }
  
          };
  
  </namedpipeserverstream>

  When I send 10/20/30 images (regardless of the size) ffmpeg processes everything.
  When I needed to transfer 600/700 / .. images, then in the ffmpeg log I see that it only received 189-192, and in the video there are also only 189-192 images.
  There are no errors in the logs or exceptions in the code.

  What could be the reason for this behavior ?