Recherche avancée

Sur d’autres sites (14398)

• Malformed header from CGI script

  13 janvier 2014, par user3188518

  This message is driving me crazy :

  Malformed header from CGI script:
  
  ffmpeg version 1.2.1 Copyright (c) 2000-2013 the FFmpeg developers
  
    built on May 10 2013 16:31:05 with gcc 4.8.0 (GCC) 20130502 (prerelease)
  
    configuration: --prefix=/usr --disable-debug --disable-static --enable-avresample --enable-dxva2 --enable-fontconfig --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-libxvid --enable-postproc --enable-runtime-cpudetect --enable-shared --enable-vdpau --enable-version3 --enable-x11grab
  
    libavutil      52. 18.100 / 52. 18.100
  
    libavcodec     54. 92.100 / 54. 92.100
  
    libavformat    54. 63.104 / 54. 63.104
  
    libavdevice    54.  3.103 / 54.  3.103
  
    libavfilter     3. 42.103 /  3. 42.103
  
    libswscale      2.  2.100 /  2.  2.100
  
    libswresample   0. 17.102 /  0. 17.102
  
    libpostproc    52.  2.100 / 52.  2.100
  
  Guessed Channel Layout for  Input Stream #0.0 : stereo
  
  Input #0, wav, from '/projekt/aplikacja/app/92ed9478ecfa4a4dfb176f417d4ef66c/2014-01-12-220148_sample_1.wav':
  
    Duration: 00:02:35.62, bitrate: 1411 kb/s
  
      Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 44100 Hz, stereo, s16, 1411 kb/s
  
  Output #0, wav, to '/projekt/aplikacja/app/webroot/files/preview/2014-01-12-234038_52d327f6b2939.wav':
  
    Metadata:
  
      ISFT            : Lavf54.63.104
  
      Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 44100 Hz, stereo, 1411 kb/s
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (copy)
  
  Press [q] to stop, [?] for help
  
  size=     864kB time=00:00:05.01 bitrate=1411.3kbits/s    
  
  video:0kB audio:864kB subtitle:0 global headers:0kB muxing overhead 0.009042%
  
  Status: 302
  
  Location: http://www.example.org/
  
  Content-type: text/html

  After executing this function :

     public function createpreview(){
  
           if ($this->request->is('post')) {
  
             foreach($this->request->data['TrackId'] as $key => $value){
  
                  $TrackId[] = $key;
  
              }
  
              $this->Track->recursive = -1;
  
              $view =  $this->Track->find('all', array(
  
                                'conditions' => array(
  
                                "Track.id" => $TrackId
  
                                 )));
  
              ini_set('date.timezone', 'Europe/London');
  
  
  
             foreach ($view as $v){
  
                $comand_1 = 'ffmpeg -i '.APP.'92ed9478ecfa4a4dfb176f417d4ef66c'.DS. $v['Track']['filename'].' 2>&1';
  
                $time_data = shell_exec($comand_1);
  
                $search = '/Duration: (.*?),/';
  
                $duration = preg_match($search, $time_data, $matches, PREG_OFFSET_CAPTURE, 3);
  
                $time = explode('.', $matches[1][0]);
  
                $time = explode(":", $time[0]);
  
                $seconds = $time[0]*3600 + $time[1]*60 + $time[2];
  
                if ($seconds >= 30){
  
  
  
               $now = date('Y-m-d-His');
  
                   $prew_file_name = $now .'_'. uniqid().'.wav';
  
                   $comand_2 = 'ffmpeg  -ss 00:00:25.000 -analyzeduration 99999999  -i '.APP.'92ed9478ecfa4a4dfb176f417d4ef66c'.DS. $v['Track']['filename'].' -t 5 -c:v copy -c:a copy '.WWW_ROOT.'files'.DS.'preview'.DS.$prew_file_name;
  
                      $t = shell_exec($comand_2);
  
                      $this->Track->updateAll(array('Track.preview' => "'.$prew_file_name.'"), array('Track.id' => $v['Track']['id']));
  
                    }
  
                 }
  
  
  
          }
  
           header('Location: http://www.example.org/');
  
         // $this->redirect(array('controller'=>'albums', 'action'=>'menage_index'));
  
     }

  As far as i know this shell_exec($comand_2) couses error (after i comment it out, it redirects me correctly).Googling this didn't gave me answers, the wierd part is previews aka shell_exec($comand_2) are made and fine, i just can't get it to redirect me. I tried non cake way but it doesn't work either.

  What I'm doing wrong ?

• Spotlight : Alwaysdata.com the company behind Piwik.org web hosting [Interview]

  11 avril 2013, par matt — About, Community

  Piwik is the result of the work of many talented individuals and companies. Today we’d like to showcase Alwaysdata.com, the awesome web hosting company providing managed hosting for all Piwik.org websites and services.

  I recently met and asked a few questions to Cyril, co-founder of Alwaysdata.com and Piwik core developer. Learn more in the interview below !

  

  1. What is Alwaysdata ?
  2. Who are your customers and what kind of work do you do ?
  3. What sets Alwaysdata apart from the large web hosting competition ?
  4. Are you using Piwik internally or with customers ? If so, how are you using Piwik ?
  5. What is the next big thing for Alwaysdata ?
  6. Learn more

  What is Alwaysdata ?

  We are a French web hosting company created in 2006. If you need to host a website — a Piwik installation, for example — or even your domains/emails, we provide infrastructure and maintenance services.

  Who are your customers and what kind of work do you do ?

  We have several types of clients :

  • Individuals who need hosting for their personal site and who benefit from storage space with direct SSH access.
  • Web agencies who need hosting for their clients’ sites.
  • The largest customers, often on dedicated servers, for hosting their site/infrastructure.

  Our work falls into three categories :

  1. Support (via administration, telephone, Twitter, IRC, etc.)
  2. Development (in Python), primarily to add new features
  3. System administration, either for maintenance (e.g. adding servers), or for preparing new features

  What sets Alwaysdata apart from the large web hosting competition ?

  Two things :

  • Availability. We are a small team and often know our customers quite well. We are all on IRC, so you can contact us directly if you need any assistance.
  • Features. We are halfway between traditional web hosting and the cloud, combining the advantages of both.

  Are you using Piwik internally or with customers ? If so, how are you using Piwik ?

  All of our customers can view statistics for their sites via our global Piwik installation, without having to configure anything.

  To provide these analytics reports to our customers, we implemented import of the raw access logs in Piwik. The Log import toolkit is now a feature included in Piwik.

  What is the next big thing for Alwaysdata ?

  We are going to upgrade our pricing : instead of fixed costs, each of our clients will now pay exactly what they consume. This allows our clients the benefit of a very high quality service for the lowest possible price.

  We are also going to add native support for more technologies : Java, Node.js, ZeroMQ, etc.

  Thank you for your time and all the best to Alwaysdata for the future !

  —

  Note from Matt, Piwik founder : Cyril and the team at Alwaysdata.com have been consistently great in their system administration work for Piwik.org services, providing a fast and reliable web hosting experience with top notch support and security practises. They also handled the migration of all services from our old servers with total piece of mind.

  Alwaysdata contributed to Piwik the popular Log Analytics toolkit. They are great software developers and system administrators with a passion for their work. Since 2006, they have been maintaining optimized hosting services for the entire web infrastructure (websites, domains, emails, databases, etc.), from the simplest to the most exotic. We do recommend their managed hosting services.

  Learn more

  • Visit their website at Alwaysdata.com
  • Learn more about their Managed hosting on dedicated servers
  • Learn more about other companies and individuals who make a difference in Piwik.

• Salty Game Music

  31 mai 2011, par Multimedia Mike — General

  Have you heard of Google’s Native Client (NaCl) project ? Probably not. Basically, it allows native code modules to run inside a browser (where ‘browser’ is defined pretty narrowly as ‘Google Chrome’ in this case). Programs are sandboxed so they aren’t a security menace (or so the whitepapers claim) but are allowed to access a variety of APIs including video and audio. The latter API is significant because sound tends to be forgotten in all the hullabaloo surrounding non-Flash web technologies. At any rate, enjoy NaCl while you can because I suspect it won’t be around much longer.

  After my recent work upgrading some old music synthesis programs to user more modern audio APIs, I got the idea to try porting the same code to run under NaCl in Chrome (first Nosefart, then Game Music Emu/GME). In this exercise, I met with very limited success. This blog post documents some of the pitfalls in my excursion.

  
  
  

  Infrastructure
  People who know me know that I’m rather partial — to put it gently — to straight-up C vs. C++. The NaCl SDK is heavily skewed towards C++. However, it does provide a Python tool called init_project.py which can create the skeleton of a project and can do so in C with the '-c' option :

  ./init_project.py -c -n saltynosefart
  

  This generates something that can be built using a simple ‘make’. When I added Nosefart’s C files, I learned that the project Makefile has places for project-necessary CFLAGS but does not honor them. The problem is that the generated Makefile includes a broader system Makefile that overrides the CFLAGS in the project Makefile. Going into the system Makefile and changing "CFLAGS =" -> "CFLAGS +=" solves this problem.

  Still, maybe I’m the first person to attempt building something in Native Client so I’m the first person to notice this ?

  Basic Playback
  At least the process to create an audio-enabled NaCl app is well-documented. Too bad it doesn’t seem to compile as advertised. According to my notes on the matter, I filled in PPP_InitializeModule() with the appropriate boilerplate as outlined in the docs but got a linker error concerning get_browser_interface().

  Plan B : C++
  Obviously, the straight C stuff is very much a second-class citizen in this NaCl setup. Fortunately, there is already that fully functional tone generator example program in the limited samples suite. Plan B is to copy that project and edit it until it accepts Nosefart/GME audio instead of a sine wave.

  The build system assumes all C++ files should have .cc extensions. I have to make some fixes so that it will accept .cpp files (either that, or rename all .cpp to .cc, but that’s not very clean).

  Making Noise
  You’ll be happy to know that I did successfully swap out the tone generator for either Nosefart or GME. Nosefart has a slightly fickle API that requires revving the emulator frame by frame and generating a certain number of audio samples. GME’s API is much easier to work with in this situation — just tell it how many samples it needs to generate and give it a pointer to a buffer. I played NES and SNES music play through this ad-hoc browser plugin, and I’m confident all the other supported formats would have worked if I went through the bother of converting the music data files into C headers to be included in the NaCl executable binaries (dynamically loading data via the network promised to be a far more challenging prospect reserved for phase 3 of the project).

  Portable ?
  I wouldn’t say so. I developed it on Linux and things ran fine there. I tried to run the same binaries on the Windows version of Chrome to no avail. It looks like it wasn’t even loading the .nexe files (NaCl executables).

  Thinking About The (Lack Of A) Future
  As I was working on this project, I noticed that the online NaCl documentation materialized explicit banners warning that my NaCl binaries compiled for Chrome 11 won’t work for Chrome 12 and that I need to code to the newly-released 0.3 SDK version. Not a fuzzy feeling. I also don’t feel good that I’m working from examples using bleeding edge APIs that feature deprecation as part of their naming convention, e.g., pp::deprecated::ScriptableObject().

  Ever-changing API + minimal API documentation + API that only works in one browser brand + requiring end user to explicitly enable feature = … well, that’s why I didn’t bother to release any showcase pertaining to this little experiment. Would have been neat, but I strongly suspect that this is yet another one of those APIs that Google decides to deprecate soon.

  See Also :

  • I eventually got a second wind and made this work using the C interface.