Recherche avancée

Sur d’autres sites (5942)

• Senior Software Engineer for Enterprise Analytics Platform

  28 janvier 2016, par Matthieu Aubry — Jobs

  We’re looking for a lead developer to work on Piwik Analytics core platform software. We have some exciting challenges to solve and need you !

  You’ll be working with both fellow employees and our open-source community. Piwik PRO staff lives in New Zealand, Europe (Poland, Germany) and in the U.S. We do the vast majority of our collaboration online.

  We are a small, flexible team, so when you come aboard, you will play an integral part in engineering. As a leader you’ll help us to prioritise work and grow our community. You’ll help to create a welcoming environment for new contributors and set an example with your development practices and communications skills. You will be working closely with our CTO to build a future for Piwik.

  Key Responsibilities

  • Strong competency coding in PHP and JavaScript.
  • Scaling existing backend system to handle ever increasing amounts of traffic and new product requirements.
  • Outstanding communication and collaboration skills.
  • Drive development and documentation of internal and external APIs (Piwik is an open platform).
  • Help make our development practices better and reduce friction from idea to deployment.
  • Mentor junior engineers and set the stage for personal growth.

  Minimum qualifications

  • 5+ years of experience in product development, security, usable interface design.
  • 5+ years experience building successful production software systems.
  • Strong competency in PHP5 and JavaScript application development.
  • Skill at writing tests and reviewing code.
  • Strong analytical skills.

  Location

  • Remote work position !
  • or you can join us in our office based in Wellington, New Zealand or in Wrocław, Poland.

  Benefits

  • Competitive salary.
  • Equity in Piwik PRO.
  • Remote work is possible.
  • Yearly meetup with the whole team abroad.
  • Be part of a successful open source company and community.
  • In our Wellington (NZ) and Wroclaw (PL) offices : snacks, coffee, nap room, Table football, Ping pong…
  • Regular events.
  • Great team of people.
  • Exciting projects.

  Learn more

  Learn more what it’s like to work on Piwik in our blog post

  About Piwik

  At Piwik and Piwik PRO we develop the leading open source web analytics platform, used by more than one million websites worldwide. Our vision is to help the world liberate their analytics data by building the best open alternative to Google Analytics.

  The Piwik platform collects, stores and processes a lot of information : hundreds of millions of data points each month. We create intuitive, simple and beautiful reports that delight our users.

  About Piwik PRO company

  At Piwik PRO we’re solving hard problems with simple solutions that make our users and customers happy. We practise agile methodology, test driven development and fast release cycles. Our backend is mostly built in modern PHP with a bit of Python. We use MySQL/MariaDB and Redis as data stores. Our frontends is built in JavaScript using AngularJS and jQuery. Our tools include Github, Travis CI, PhpStorm and Slack.

  As a Lead Software Developer for Piwik PRO, you will be writing open source code that will run on more than 200,000 servers and be used in 200+ countries and 50 languages !

  Apply online

  To apply for this position, please Apply online here. We look forward to receiving your applications !

• Building ffmpeg on Windows from Chromium - make : *** No rule to make target 'libavcodec\avcodec-57.dll'. Stop

  14 septembre 2016, par Catalin Fratila

  I am trying to compile ffmpeg on a Windows machine, using mingw64 and msys2.

  But when I run : "build_ffmpeg.py win ia32" (same result with x64), I get :

  /c/libchromiumcontent/src/third_party/ffmpeg/chromium/scripts
  
  $ ./build_ffmpeg.py win ia32
  
  install prefix            /usr/local
  
  source path               /c/libchromiumcontent/src/third_party/ffmpeg
  
  C compiler                gcc
  
  C library                 mingw64
  
  ARCH                      x86 (generic)
  
  big-endian                no
  
  runtime cpu detection     yes
  
  yasm                      yes
  
  MMX enabled               yes
  
  MMXEXT enabled            yes
  
  3DNow! enabled            yes
  
  3DNow! extended enabled   yes
  
  SSE enabled               yes
  
  SSSE3 enabled             yes
  
  AESNI enabled             yes
  
  AVX enabled               yes
  
  XOP enabled               yes
  
  FMA3 enabled              yes
  
  FMA4 enabled              yes
  
  i686 features enabled     yes
  
  CMOV is fast              yes
  
  EBX available             yes
  
  EBP available             yes
  
  debug symbols             yes
  
  strip symbols             yes
  
  optimize for size         no
  
  optimizations             yes
  
  static                    yes
  
  shared                    no
  
  postprocessing support    no
  
  new filter support        no
  
  network support           no
  
  threading support         w32threads
  
  safe bitstream reader     yes
  
  SDL support               no
  
  opencl enabled            no
  
  texi2html enabled         no
  
  perl enabled              no
  
  pod2man enabled           no
  
  makeinfo enabled          no
  
  makeinfo supports HTML    no
  
  
  
  Enabled programs:
  
  
  
  External libraries:
  
  
  
  Enabled decoders:
  
  pcm_alaw                  pcm_f32le                 pcm_mulaw                 pcm_s16be                 pcm_s16le                 pcm_s24be                 pcm_s24le                 pcm_s32le                 pcm_u8                    vorbis
  
  
  
  Enabled encoders:
  
  
  
  Enabled hwaccels:
  
  
  
  Enabled parsers:
  
  opus                      vorbis
  
  
  
  Enabled demuxers:
  
  matroska                  ogg                       wav
  
  
  
  Enabled muxers:
  
  
  
  Enabled protocols:
  
  
  
  Enabled filters:
  
  
  
  Enabled bsfs:
  
  
  
  Enabled indevs:
  
  
  
  Enabled outdevs:
  
  
  
  License: LGPL version 2.1 or later
  
  Creating config.mak, config.h, and doc/config.texi...
  
  make: *** No rule to make target 'libavcodec\avcodec-57.dll'.  Stop.
  
  System information:
  
  Host OS       : win
  
  Target OS     : win
  
  Host arch     : x64
  
  Target arch   : ia32
  
  Parallel jobs : 4
  
  
  
  Chromium configure/build:
  
  Running ['sh.exe', 'C:\\libchromiumcontent\\src\\third_party\\ffmpeg\\configure', '--disable-everything', '--disable-all', '--disable-doc', '--disable-htmlpages', '--disable-manpages', '--disable-podpages', '--disable-txtpages', '--disable-static', '--enable-avcodec', '--enable-avformat', '--enable-avutil', '--enable-fft', '--enable-rdft', '--enable-static', '--disable-bzlib', '--disable-error-resilience', '--disable-iconv', '--disable-lzo', '--disable-network', '--disable-schannel', '--disable-sdl', '--disable-symver', '--disable-xlib', '--disable-zlib', '--disable-securetransport', '--disable-d3d11va', '--disable-dxva2', '--disable-vaapi', '--disable-vda', '--disable-vdpau', '--disable-videotoolbox', '--enable-decoder=vorbis', '--enable-decoder=pcm_u8,pcm_s16le,pcm_s24le,pcm_s32le,pcm_f32le', '--enable-decoder=pcm_s16be,pcm_s24be,pcm_mulaw,pcm_alaw', '--enable-demuxer=ogg,matroska,wav', '--enable-parser=opus,vorbis', '--optflags="-O2"', '--enable-decoder=theora,vp8', '--enable-parser=vp3,vp8', '--toolchain=msvc', '--cpu=opteron', '--enable-yasm', '--extra-cflags=-IC:\\libchromiumcontent\\src\\third_party\\ffmpeg\\chromium/include/win', '--target-os=mingw32', '--enable-memalign-hack', '--cc=gcc-sjlj']
  
  Running ['make', '-j4', 'libavcodec\\avcodec-57.dll', 'libavformat\\avformat-57.dll', 'libavutil\\avutil-55.dll']
  
  Traceback (most recent call last):
  
    File "./build_ffmpeg.py", line 631, in <module>
  
      sys.exit(main(sys.argv[1:]))
  
    File "./build_ffmpeg.py", line 596, in main
  
      configure_args)
  
    File "./build_ffmpeg.py", line 588, in do_build_ffmpeg
  
      options.config_only, branding, configure_flags)
  
    File "./build_ffmpeg.py", line 217, in BuildFFmpeg
  
      ['make', '-j%d' % parallel_jobs] + libraries, cwd=config_dir)
  
    File "./build_ffmpeg.py", line 92, in PrintAndCheckCall
  
      subprocess.check_call(argv, *args, **kwargs)
  
    File "C:\Python27\lib\subprocess.py", line 541, in check_call
  
      raise CalledProcessError(retcode, cmd)
  
  subprocess.CalledProcessError: Command '['make', '-j4', 'libavcodec\\avcodec-57.dll', 'libavformat\\avformat-57.dll', 'libavutil\\avutil-55.dll']' returned non-zero exit status 2
  
  </module>

  Has anyone seen this issue before ? Have all the pre-requisites from here : https://trac.ffmpeg.org/wiki/CompilationGuide/MinGW

  Thanks.

• Vedanti and Max Sound vs. Google

  14 août 2014, par Multimedia Mike — Legal/Ethical

  Vedanti Systems Limited (VSL) and Max Sound Coporation filed a lawsuit against Google recently. Ordinarily, I wouldn’t care about corporate legal battles. However, this one interests me because it’s multimedia-related. I’m curious to know how coding technology patents might hold up in a real court case.

  Here’s the most entertaining complaint in the lawsuit :

  Despite Google’s well-publicized Code of Conduct — “Don’t be Evil” — which it explains is “about doing the right thing,” “following the law,” and “acting honorably,” Google, in fact, has an established pattern of conduct which is the exact opposite of its claimed piety.

  I wonder if this is the first known case in which Google has been sued over its long-obsoleted “Don’t be evil” mantra ?

  Researching The Plaintiffs
  
  I think I made a mistake by assuming this lawsuit might have merit. My first order of business was to see what the plaintiff organizations have produced. I have a strong feeling that these might be run of the mill patent trolls.

  VSL currently has a blank web page. Further, the Wayback Machine only has pages reaching back to 2011. The earliest page lists these claims against a plain black background (I’ve highlighted some of the more boisterous claims and the passages that make it appear that Vedanti doesn’t actually produce anything but is strictly an IP organization) :

  The inventions key :
  The patent and software reduced any data content, without compressing, up to a 97% total reduction of the data which also produces a lossless result. This physics based invention is often called the Holy Grail.

  Vedanti Systems Intellectual Property
  Our strategic IP portfolio is granted in all of the world’s largest technology development and use countries. A major value indemnification of our licensee products is the early date of invention filing and subsequent Issue. Vedanti IP has an intrinsic 20 year patent protection and valuation in royalties and licensing. The original data transmission art has no prior art against it.

  Vedanti Systems invented among other firsts, The Slice and Partitioning of Macroblocks within a RGB Tri level region in a frame to select or not, the pixel.

  Vedanti Systems invention is used in nearly every wireless chipset and handset in the world

  Our original pixel selection system revolutionized wireless handset communications. An example of this system “Slice” and “Macroblock Partitioning” is used throughout Satellite channel expansion, Wireless partitioning, Telecom – Video Conferencing, Surveillance Cameras, and 2010 developing Media applications.

  Vedanti Systems is a Semiconductor based software, applications, and IP Continuations Intellectual Property company.

  Let’s move onto the other plaintiff, Max Sound. They have a significantly more substantive website. They also have an Android app named Spins HD Audio, which appears to be little more than a music player based on the screenshots.

  Max Sound also has a stock ticker symbol : MAXD. Something clicked into place when I looked up their ticker symbol : While worth only a few pennies, it was worth a few more pennies after this lawsuit was announced, which might be one of the motivations behind the lawsuit.

  Here’s a trick I learned when I was looking for a new tech job last year : When I first look at a company’s website and am trying to figure out what they really do, I head straight to their jobs/careers page. A lot of corporate websites have way too much blathering corporatese that can be tough to cut through. But when I see what mix of talent and specific skills they are hoping to hire, that gives me a much better portrait of what the company does.

  The reason I bring this up is because this tech company doesn’t seem to have jobs/careers page.

  The Lawsuit
  The core complaint centers around Patent 7974339 : Optimized data transmission system and method. It was filed in July 2004 (or possibly as early as January 2002), issued in July 2011, and assigned (purchased ?) by Vedanti in May 2012. The lawsuit alleges that nearly everything Google has ever produced (or, more accurately, purchased) leverages the patented technology.

  The patent itself has 5 drawings. If you’ve ever seen a multimedia codec patent, or any whitepaper on a multimedia codec, you’ve seen these graphs before. E.g., “Raw pixels come in here -> some analysis happens here -> more analysis happens over here -> entropy coding -> final bitstream”. The text of a patent document isn’t meant to be particularly useful. I’ve tried to understand this stuff before and it never goes well. Skimming the text, I just see a blur of the words data, transmission, pixel, and matrix.

  So I read the complaint to try to figure out what this is all about. To summarize the storyline as narrated by the lawsuit, some inventors were unhappy with the state of video compression in 2001 and endeavored to create something better. So they did, and called it the VSL codec. This codec is so far undocumented on the MultimediaWiki, so it probably has yet to be seen “in the wild”. Good luck finding hard technical data on it now since searches for “VSL codec” are overwhelmed by articles about this lawsuit. Also, the original codec probably wasn’t called VSL because VSL is apparently an IP organization formed much later.

  Then, the protagonists of the lawsuit patented the codec. Then, years later, Google wanted to purchase a video codec that they could open source and use to supplant H.264.

  The complaint goes on to allege that in 2010, Google specifically contacted VSL to possibly license or acquire this mysterious VSL technology. Google was allegedly allowed to study the technology, eventually decided not to continue discussions, and shipped back the proprietary materials.

  Here’s where things get weird. When Google shipped back the materials, they allegedly shipped back a bunch of Post-It notes. The notes are alleged to contain a ton of incriminating evidence. The lawsuit claims that the notes contained such tidbits as :

  • Google was concerned that its infringement could be considered “recklessness” (the standard applicable to willful infringement) ;
  • Google personnel should “try” to destroy incriminating emails ;
  • Google should consider a “design around” because it was facing a “risk of litigation.”

  Actually, given Google’s acquisition of On2, I can totally believe that last one (On2’s codecs have famously contained a lot of weirdness which is commonly suspected to be attributable to designing around known patents).

  Anyway, a lot of this case seems to hinge on the authenticity of these Post-It notes :

  “65. The Post-It notes are unequivocal evidence of Google’s knowledge of the ’339 Patent and infringement by Defendants”

  I wish I could find a stock photo of a stack of Post-It notes in an evidence bag.

  I’ve worked at big technology companies. Big tech companies these days are very diligent about indoctrinating employees about IP liability issues. The reason this Post-It situation strikes me as odd is because the alleged contents of the notes basically outline everything the corporate lawyers tell you NOT to do.

  Analysis
  I’m trying to determine what specific algorithms and coding techniques. I guess I was expecting to see a specific claim that, “Our patent outlines this specific coding technique and here is unequivocal proof that Google A) uses the same technique, and B) specifically did so after looking at our patent.” I didn’t find that (well, a bit of part B, c.f., the Post-It note debacle), but maybe that’s not how these patent lawsuits operate. I’ve never kept up before.

  Maybe it’s just a patent troll. Maybe it’s for the stock bump. I’m expecting to see pump-n-dump stock spam featuring the stock symbol MAXD anytime now.

  I’ve never been interested in following a lawsuit case carefully before. I suddenly find myself wondering if I can subscribe to the RSS feed for this case ? Too much to hope for. But I found this item through Pando and maybe they’ll stay on top of it.