Recherche avancée

Sur d’autres sites (4706)

• Game Music Appreciation

  16 juillet 2012, par Multimedia Mike — Game Hacking

  A little over a year ago, I was prototyping a method to leverage Google Chrome’s Native Client technology in order to play old chiptunes (video game music) directly in a web browser. The last time I posted on the matter, I said that I might have something ready for public consumption by the time Google Chrome 21 rolled around. I thought I was being facetious but I wasn’t too far off. Chrome 20 is the current release version as I write this.

  Anyway, I did it : I created a chiptune music player in Native Client by leveraging existing C/C++ libraries such as Game Music Emu, Audio Overload SDK, and Vio2sf. Then I packaged up the player into into a Google Chrome extension and published it on the Chrome Web Store. Then I made a website cataloging as many chiptunes as I could find for 7 different systems :

  http://gamemusic.multimedia.cx/
  

  Check it out if you have any affinity for old game music or you want to hear how music was made using a limited range of bleeps and bloops. Thus far, the site catalogs NES, SNES, Game Boy, Nintendo DS, Genesis, Saturn, and Dreamcast songs. I’m hoping to add support and catalogs for many more systems, though, eventually bringing support in line with the Chipamp plugin for Winamp.

• How can I figure out the optimized number of parallel running encoding jobs with the x264 encoder library

  30 janvier 2024, par Dani

  I'm batch converting hundreds of videos to mp4 and trying to optimize my method.

  



  I have written a node script, which spawns FFMPEG processes to convert the videos.

  



  From my understanding both FFMPEG and the libx264 encoder are already optimized for multithreaded support. I'm using the default threading option in the encoder.

  



  I'm trying to find the optimal number of FFMPEG spawned processes I should make. There seems to be a balance between having too many and slowing down the encoding of all jobs vs too few process going through the job queue too slowly.

  



  I'm also wondering if dedicating a specific number of threads to each encode job would help rather than using the default setting ?

  



  For my setup I'm on a dated 12-core Mac Pro with 24-threads, though this question is about finding the optimal balance in general.

  


• Install ffmpeg-light with cabal

  20 septembre 2016, par WirflBirfl

  I want to install the ffmpeg-light library from hackage via cabal on Windows 10 (64 bit). So I downloaded ffmpeg and extracted it to C :\FFmpeg.

  At first pkg-config was complaining that it could not find various packages. I solved this problem with .pc files.

  When I tried to use the command : cabal install ffmpeg-light cabal complained about missing C-libraries, being exactly those for which I created the .pc files.

  Then I tried the command : cabal install ffmpeg-light --extra-lib-dirs=C:\FFmpeg\lib. Now I have a different error message, which says :

  Enums.hsc:7:32: fatal error: libavcodec/avcodec.h: No such file or directory

  Edit :
  Then I tried the following command :

  cabal install ffmpeg-light --extra-lib-dirs=C:\FFmpeg\lib \
  
                             --extra-include-dirs=C:\FFmpeg\include

  Now first the compiler gives some warnings about deprecated functions in ffmpeg and redundant imports in ffmpeg-light, but compiles 11 of 11. But the build is still not successfull.

  In-place registering ffmpeg-light-0.11.1...
  
  setup-Simple-Cabal-1.22.5.0-x86_64-windows-ghc-7.10.3.exe:
  
  'C:\Haskell\bin\ghc-pkg.exe' exited with an error:
  
  ffmpeg-light-0.11.1: Warning: haddock-interfaces:
  
  C:\Users\HOLEYC~1\AppData\Local\Temp\cabal-tmp-2824\ffmpeg-light-0.11.1\dist\doc\html\ffmpeg-light\ffmpeg-light.haddock
  
  doesn't exist or isn't a file
  
  ffmpeg-light-0.11.1: Warning: haddock-html:
  
  C:\Users\HOLEYC~1\AppData\Local\Temp\cabal-tmp-2824\ffmpeg-light-0.11.1\dist\doc\html\ffmpeg-light
  
  doesn't exist or isn't a directory
  
  ffmpeg-light-0.11.1: library-dirs: C:FFmpeglib is a relative path which makes
  
  no sense (as there is nothing for it to be relative to). You can make paths
  
  relative to the package database itself by using ${pkgroot}. (use --force to
  
  override)
  
  ffmpeg-light-0.11.1: include-dirs: C:FFmpeginclude is a relative path which
  
  makes no sense (as there is nothing for it to be relative to). You can make
  
  paths relative to the package database itself by using ${pkgroot}. (use
  
  --force to override)
  
  cabal: Error: some packages failed to install:
  
  ffmpeg-light-0.11.1 failed during the building phase. The exception was:
  
  ExitFailure 1

  Some additional information :

  cabal version: cabal-install version 1.22.6.0
  
  using version 1.22.5.0 of the Cabal library
  
  gcc version of my installed Haskell platform: 5.2.0

  Example .pc file I used for pkg-config :

  Name: libavcodec
  
  Description: Library for ffmpeg
  
  Version: 57
  
  Cflags: -IC:\FFmpeg\include
  
  Libs: -LC:\FFmpeg\lib -llibavcodec