Recherche avancée

Sur d’autres sites (4512)

• using FFMPEG to convert to MP4 with maximum browsers compatibilty

  6 mars 2016, par Karim

  I’m converting from WMV to FLV using FFMPEG, and my problem is that the FLV videos are so big ! the 15 minutes video’s size ranges between 150MB and 1GB !
  I’m using the following FFMPEG command to convert and split WMV videos :

  nohup nice -1 ffmpeg -y -ss 00:00:00 -t 00:15:00 -async 1 -i INPUT.WMV -acodec libmp3lame OUTPUT.FLV

  And I’ve tried converting to MP4 before and the video size was much smaller than the FLV video.

  So my questions are :
  

  • Would the MP4 videos have any
    compatibility issues browsers ?
  • Would it work on iPhone, iPad ? (I
    know FLV videos doesn’t work on
    iPhones or iPads)
  • What is the best FFMPEG command to
    convert to MP4 without losing the
    quality of the video ?

• libx264 performances on iOS

  8 mai 2012, par Gilad

  I was wondering whether someone has some experience using libx264 on iPhone.

  How does it perform ? What framerate can I expect ? Will it work for simultaneous encoding & decoding (video call) or the CPU can't handle it ? I'm mainly interested with iPhone 4 and above (iPhone4/iPad 2)

  Are there any precompiled universal binaries I can use ?

• Cloaked Archive Wiki

  16 mai 2011, par Multimedia Mike — General

  Google’s Chrome browser has made me phenomenally lazy. I don’t even attempt to type proper, complete URLs into the address bar anymore. I just type something vaguely related to the address and let the search engine take over. I saw something weird when I used this method to visit Archive Team’s site :

  
  
  

  There’s greater detail when you elect to view more results from the site :

  
  
  

  As the administrator of a MediaWiki installation like the one that archiveteam.org runs on, I was a little worried that they might have a spam problem. However, clicking through to any of those out-of-place pages does not indicate anything related to pharmaceuticals. Viewing source also reveals nothing amiss.

  I quickly deduced that this is a textbook example of website cloaking. This is when a website reports different content to a search engine than it reports to normal web browsers (humans, presumably). General pseudocode :

  PLAIN TEXT

  C :

  1. if (web_request.user_agent_string == CRAWLER_USER_AGENT)
  2.  return cloaked_data ;
  3. else
  4.  return real_data ;

  You can verify this for yourself using the wget command line utility :

  <br />
$ wget --quiet --user-agent="<strong>Mozilla/5.0</strong>" \<br />
 http://www.archiveteam.org/index.php?title=Geocities -O - | grep \&lt;title\&gt;<br />
&lt;title&gt;GeoCities - Archiveteam&lt;/title&gt;

  $ wget —quiet —user-agent="Googlebot/2.1"
  http://www.archiveteam.org/index.php?title=Geocities -O - | grep \<title\>
  <title>Cheap xanax | Online Drug Store, Big Discounts</title>
  

  I guess the little web prank worked because the phaux-pharma stuff got indexed. It makes we wonder if there’s a MediaWiki plugin that does this automatically.

  For extra fun, here’s a site called the CloakingDetector which purports to be able to detect whether a page employs cloaking. This is just one humble observer’s opinion, but I don’t think the site works too well :