Recherche avancée

Sur d’autres sites (9369)

• How to grap voice and vedio in ffmpeg \ mplayer\mencoder ?

  4 février 2013, par Kill Kill

  My target is to grap voice and vedio via webcamera,there are three ways to do :

  1.ffmpeg -f oss -i /dev/dsp -f video4linux2 -r 25 -b 500000 -s 320x240 -i /dev/video0 out.mpg
  WARNING : gnome-keyring: : couldn't connect to : /home/debian/.cache/keyring-4Hzs4r/pkcs11 : No such file or directory
  ffmpeg version 0.8.5-6:0.8.5-1, Copyright (c) 2000-2012 the Libav developers
  built on Jan 13 2013 16:02:15 with gcc 4.7.2
  * THIS PROGRAM IS DEPRECATED *
  This program is only provided for compatibility and will be removed in a future release. Please use avconv instead.
  [oss @ 0x9d63c60] /dev/dsp : No such file or directory
  /dev/dsp : Input/output error

  in my computer how to revise it ?

  2.mplayer tv :// -tv driver=v4l2:input=0:width=640:height=480:fps=25 -vo x11
  i can see the veido when the command run ,how can l save the output into a file and grap the voice ?

  3.mencoder tv :// -tv driver=v4l2:width=800:height=600:device=/dev/video0:fps=30:outfmt=yuy2:forceaudio:alsa:adevice=hw.2,0 -ovc lavc -lavcopts vcodec=mpeg4:vbitrate=1800 -ffourcc xvid -oac mp3lame -lameopts cbr=128 -o output.avi

  MEncoder svn r34540 (Debian), built with gcc-4.7 (C) 2000-2012 MPlayer Team
  success : format : 9 data : 0x0 - 0x0
  TV file format detected.
  Selected driver : v4l2
  name : Video 4 Linux 2 input
  author : Martin Olschewski
  comment : first try, more to come
  v4l2 : your device driver does not support VIDIOC_G_STD ioctl, VIDIOC_G_PARM was used instead.
  Selected device : PC Camera
  Capabilities : video capture read/write streaming
  supported norms :
  inputs : 0 = zc3xx ;
  Current input : 0
  Current format : unknown (0x4745504a)
  tv.c : norm_from_string(pal) : Bogus norm parameter, setting default.
  v4l2 : ioctl enum norm failed : Inappropriate ioctl for device
  Error : Cannot set norm !
  Selected input hasn't got a tuner !
  ALSA lib pcm_hw.c:1401 :(_snd_pcm_hw_open) Invalid value for card
  Error opening audio : No such file or directory
  ALSA lib pcm_hw.c:1401 :(_snd_pcm_hw_open) Invalid value for card
  Error opening audio : No such file or directory
  ALSA lib pcm_hw.c:1401 :(_snd_pcm_hw_open) Invalid value for card
  Error opening audio : No such file or directory
  v4l2 : ioctl set mute failed : Invalid argument
  v4l2 : 0 frames successfully processed, 0 frames dropped.
  ============ Sorry, this file format is not recognized/supported =============
  === If this file is an AVI, ASF or MPEG stream, please contact the author ! ===
  Cannot open demuxer.

  Exiting...

• Trying to open file with PHP-FFMpeg after it was encoded once

  19 mai 2016, par Shillo Ben David

  in the same PHP process I’m trying to open a file that was manipulated and saved, and then I’m trying to open it with as a new FFMpeg\Video. For example, in the same process :

  Open -> original.MOV
  
    Manipulate & save to -> new.mp4
  
      Open -> new.mp4

  However when I’m trying to open the manipulated file I get this InvalidArgumentException exception :

  InvalidArgumentException: Unable to detect file format, only audio and video supported

  It’s thrown by the FFMpeg::open() after it could not detect that it’s a either Video or Audio stream.

  FFMpeg::open()

  public function open($pathfile)
  
  {
  
      if (null === $streams = $this->ffprobe->streams($pathfile)) {
  
          throw new RuntimeException(sprintf('Unable to probe "%s".', $pathfile));
  
      }
  
  
  
      if (0 < count($streams->videos())) {
  
          return new Video($pathfile, $this->driver, $this->ffprobe);
  
      } elseif (0 < count($streams->audios())) {
  
          return new Audio($pathfile, $this->driver, $this->ffprobe);
  
      }
  
  
  
      throw new InvalidArgumentException('Unable to detect file format, only audio and video supported');
  
  }

  The filters I applied to the video are audio mute and speedup (setpts).

  So I wonder, why FFMpeg doesn’t recognise it as video ?

• Adding C64 SID Music

  1er novembre 2012, par Multimedia Mike — General

  I have been working on adding support for SID files — the music format for the Commodore 64 — to the game music website for awhile. I feel a bit out of my element since I’m not that familiar with the C64. But why should I let that slow me down ? Allow me to go through the steps I have previously outlined in order to make this happen.

  
  
  

  I need to know what picture should represent the system in the search results page. The foregoing picture should be fine, but I’m getting way ahead of myself.

  Phase 1 is finding adequate player software. The most venerable contender in this arena is libsidplay, or so I first thought. It turns out that there’s libsidplay (originally hosted at Geocities, apparently, and no longer on the net) and also libsidplay2. Both are kind of old (libsidplay2 was last updated in 2004). I tried to compile libsidplay2 and the C++ didn’t agree with current version of g++.

  However, a recent effort named libsidplayfp is carrying on the SID emulation tradition. It works rather well, notwithstanding the fact that compiling the entire library has a habit of apparently hanging the Linux VM where I develop this stuff.

  Phase 2 is to develop a testbench app around the playback library. With the help of the libsidplayfp library maintainers, I accomplished this. The testbench app consistently requires about 15% of a single core of a fairly powerful Core i7. So I look forward to recommendations that I port that playback library to pure JavaScript.

  Phase 3 is plug into the web player. I haven’t worked on this yet. I’m confident that this will work since phase 2 worked (plus, I have a plan to combine phases 2 and 3).

  One interesting issue that has arisen is that proper operation of libsidplayfp requires that 3 C64 ROM files be present (the, ahem, KERNAL, BASIC interpreter, and character generator). While these are copyrighted ROMs, they are easily obtainable on the internet. The goal of my project is to eliminate as much friction as possible for enjoying these old tunes. To that end, I will just bake the ROM files directly into the player.

  Phase 4 is collecting a SID song corpus. This is the simplest part of the whole process thanks to the remarkable curation efforts of the High Voltage SID Collection (HVSC). Anyone can download a giant archive of every known SID file. So that’s a done deal.

  Or is it ? One small issue is that I was hoping that the first iteration of my game music website would focus on, well, game music. There is a lot of music in the HVSC that are original compositions or come from demos. The way that the archive is organized makes it difficult to automatically discern whether a particular SID file comes from a game or not.

  Phase 5 is munging the metadata. The good news here is that the files have the metadata built in. The not-so-great news is that there isn’t quite as much as I might like. Each file is tagged with title, author, and publisher/copyright. If there is more than one song in a file, they all have the same metadata. Fortunately, if I can import them all into my game music database, there is an opportunity to add a lot more metadata.

  Further, there is no play length metadata for these files. This means I will need to set each to a default length like 2 minutes and do something like I did before in order to automatically determine if any songs terminate sooner.

  Oddly, the issue I’m most concerned about is character encoding. This is the first project for which I’m making certain that I understand character encoding since I can’t reasonably get away with assuming that everything is ASCII. So far, based on the random sampling of SID files I have checked, there is a good chance of encountering metadata strings with characters that are not in the lower ASCII set. From what I have observed, these characters map to Unicode code points. So I finally get to learn about manipulating strings in such a way that it preserves the character encoding. At the very least, I need Python to rip the strings out of the binary SID files and make sure the Unicode remains intact while being inserted into an SQLite3 database.