Recherche avancée

To our valued team and community,

Well, we have moved fast and achieved so much during the past few months. Relentlessly releasing major version after major version… We got a lot done including several major new features !

The speed of adding new features was a great showcase of how agile our small teams and the larger community are. And I’m so proud to see automated testing becoming common practice among everyone hacking on Piwik !

For the next few months until the new year we will focus on making what we have better. We will fix those rare but longstanding critical bugs, and aim to solve all Major issues and other must-have performance and general improvements. The core team and Piwik PRO will have the vision of making the existing Piwik and all plugins very stable and risk free. This includes edge cases, general bugs but also specific performance issues for high traffic or issues with edge case data payloads.

We’ll be more pro-active and take Piwik platform to the next level of Performance, Security, Privacy & Reliability ! We will prove to the world that Free/Libre Web software can be of the highest standard of quality. By focusing on quality we will make Piwik even easier to maintain and improve in the future. We are building the best open platform that will let every user liberate their data and keep full control of it.

If you have any feedback or questions get in touch or let’s continue the discussion in the forum.

Thank you for your trust and for liberating your data with Piwik,

Matthieu Aubry
Piwik founder

More information

• How long is each release of Piwik maintained for ? (FAQ)
• When is the next release of Piwik ? What is the release schedule ? (FAQ)
• Pulse of Piwik : our monthly pulse report shows 27 different people contributed to Piwik core in the last month !

This is an amazing testament of the power of free/libre software and yet we think this is just the beginning. We hope more developers will join and contribute to the Piwik project !

I have a strange problem trying to execute ffmpeg command using Popen.
I have the following piece of code, which I use for executing an external commands in Python :

from subprocess import Popen, PIPE

from datetime import datetime





class Executor(object):



    @classmethod

    def execute(cls, command):

        """

        Executing a given command and

        writing into a log file in cases where errors arise.

        """

        p = Popen(command, stdin=PIPE, stdout=PIPE, stderr=PIPE)

        output, err = p.communicate()

        if p.returncode:

            with open("failed_commands.log", 'a') as log:

                now = datetime.now()

                log.write('{}/{}/{} , {}:{}:{}\n\n'.format(now.day, now.month,

                                                           now.year, now.hour,

                                                           now.minute,

                                                           now.second))



                log.write("COMMAND:\n{}\n\n".format(" ".join(command)))

                log.write("OUTPUT:\n{}\n\n".format(output.decode("utf-8")))

                log.write("ERRORS:\n{}\n".format(err.decode("utf-8")))

                log.write('-'*40)

                log.write('\n')



            return ''



        if not output:

            output += ' '



        return output

I’ve tested it with others commands, but when I try to execute ffmpeg command - it fails.
I’m trying to convert some audio format to mp3 format.
Here is an example of my command :

ffmpeg -i "/path/old_song.m4a" "/path/new_song.mp3"

...simple as that.When I run it in terminal it works fine, but when I try to execute it using the above function it fails.
Here is the exact error :

----------------------------------------

21/9/2014 , 19:48:50



COMMAND:

ffmpeg -i "/path/old_song.m4a" "/path/new_song.mp3"



OUTPUT:





ERRORS:

ffmpeg version 2.2.3 Copyright (c) 2000-2014 the FFmpeg developers

  built on Jun  9 2014 08:01:43 with gcc 4.9.0 (GCC) 20140521 (prerelease)

  configuration: --prefix=/usr --disable-debug --disable-static --enable-avisynth --enable-avresample --enable-dxva2 --enable-fontconfig --enable-gnutls --enable-gpl --enable-libass --enable-libbluray --enable-libfreetype --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libv4l2 --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid --enable-pic --enable-postproc --enable-runtime-cpudetect --enable-shared --enable-swresample --enable-vdpau --enable-version3 --enable-x11grab

  libavutil      52. 66.100 / 52. 66.100

  libavcodec     55. 52.102 / 55. 52.102

  libavformat    55. 33.100 / 55. 33.100

  libavdevice    55. 10.100 / 55. 10.100

  libavfilter     4.  2.100 /  4.  2.100

  libavresample   1.  2.  0 /  1.  2.  0

  libswscale      2.  5.102 /  2.  5.102

  libswresample   0. 18.100 /  0. 18.100

  libpostproc    52.  3.100 / 52.  3.100

"/path/old_song.m4a": No such file or directory

Conversion failed!



----------------------------------------

...and as you can think of - the file exists.

I think there is something in passing the command to Popen.communicate but I don’t know exactly.

Kind regards,

Teodor D.
PS : I’m passing the command to Executor.execute as Python list.

PSS : Calling the Executor.execute :

def process_conversion(self):

    for song in self.files_to_convert:

        current_format = song.rsplit('.', 1)[-1]



        old_file = '"{}{}{}"'.format(self.target_dir, os.sep, song)

        new_file = '"{}{}{}"'.format(self.target_dir, os.sep,

                                     song.replace(current_format, 'mp3'))



        command = ["ffmpeg", "-i", old_file, new_file]

        Executor.execute(command)