Recherche avancée

Sur d’autres sites (9146)

• FFmpeg cant convert mov to flv [migrated]

  26 février 2013, par 5et

  When i try to convert .mov file to .flv i get this type of output. I get error "Invalid sample format '(null)' Error opening filters !". When i convert .avi or .mp4 i get no errors. Im on windows

      error: ffmpeg -i C:/wamp/www/\ds_uploads\62\video\23c4a54cbf8bc73056cb370ae7371848.mov -y -f flv -ar 44100 -q:v 0 C:/wamp/www/\ds_uploads\62\video\23c4a54cbf8bc73056cb370ae7371848.flv 2>&1
  
  ffmpeg version N-47062-g26c531c Copyright (c) 2000-2012 the FFmpeg developers
  
    built on Nov 25 2012 12:21:26 with gcc 4.7.2 (GCC)
  
    configuration: --enable-gpl --enable-version3 --disable-pthreads --enable-runtime-cpudetect --enable-avisynth --enable-bzlib --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-libnut --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libutvideo --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib
  
    libavutil      52.  9.100 / 52.  9.100
  
    libavcodec     54. 77.100 / 54. 77.100
  
    libavformat    54. 37.100 / 54. 37.100
  
    libavdevice    54.  3.100 / 54.  3.100
  
    libavfilter     3. 23.102 /  3. 23.102
  
    libswscale      2.  1.102 /  2.  1.102
  
    libswresample   0. 17.101 /  0. 17.101
  
    libpostproc    52.  2.100 / 52.  2.100
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 01f8b200] multiple edit list entries, a/v desync might occur, patch welcome
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 01f8b200] max_analyze_duration 5000000 reached at 5015510
  
  Guessed Channel Layout for  Input Stream #0.1 : mono
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'C:/wamp/www/\ds_uploads\62\video\23c4a54cbf8bc73056cb370ae7371848.mov':
  
    Metadata:
  
      creation_time   : 1998-11-04 16:40:13
  
    Duration: 00:01:00.83, start: 0.000000, bitrate: 110 kb/s
  
      Stream #0:0(eng): Video: svq1 (SVQ1 / 0x31515653), yuv410p, 160x120, 90 kb/s, 7.51 fps, 7.50 tbr, 600 tbn, 600 tbc
  
      Metadata:
  
        creation_time   : 1998-11-04 16:40:13
  
        handler_name    : Apple Alias Data Handler
  
      Stream #0:1(eng): Audio: qdmc (QDMC / 0x434D4451), 44100 Hz, mono
  
      Metadata:
  
        creation_time   : 1998-11-04 16:40:13
  
        handler_name    : Apple Alias Data Handler
  
  [graph 1 input from stream 0:1 @ 02b5f040] Invalid sample format '(null)'
  
  Error opening filters!

• Diamond Rio Artifacts

  30 août 2012, par Multimedia Mike — Multimedia History

  Remember the Diamond Rio PMP300 ? It’s credited with being the very first portable MP3 player, released all the way back in 1998 (I say ‘credited’ because I visited an audio museum once which exhibited a Toshiba MP3 player from 1997). I recently rescued a pristine set of Rio artifacts from a recycle pile.

  
  
  

  I wondered if I should scan the manual for posterity. However, a Google search indicates that a proper PDF (loaded with pleas to not illegally copy music) isn’t very difficult to come by. Here are the other items that came with the unit :

  
  
  Click for larger image
  

  Ah, more memories (of dialup internet) : A tie-in with another Diamond product, this time a modem which claims to enable the user to download songs at up to 112 kilobits per second. I wonder if that was really possible. I remember that 56k modems were a stretch and 33.6k was the best that most users could hope for.

  There is also a separate piece of paper that advises the buyer that the parallel port adapter might look a bit different than what is seen in the printed copy. Imagine the age of downloading to your MP3 player via parallel port while pulling down new songs via dialup internet.

  The artifacts also included not one, but two CD-ROMs :

  
  
  Click for larger image
  

  One is a driver and software disc, so no big surprise there. The other has a selection of MP3 files for your shiny new MP3 player. I’m wondering if these should be proactively preserved. I was going to process the files’ metadata and publish it here, for the benefit of search engines. However, while metadata is present, the files don’t conform to any metadata format that FFmpeg/Libav recognize. The files mention Brava Software Inc. in their metadata sections. Still, individual filenames at the end of this post.

  Leftovers :
  A few other miscellaneous multimedia acquisitions :

  
  
  

  I still want to study all of these old multimedia creation programs in depth some day. Theatrix Hollywood is a creative writing game, Wikipedia alleges (I’m a bit rigid with my exact definition of what constitutes a game). Here is an example movie output from this software. Meanwhile, the Mad Dog Multimedia CD-ROM apparently came packaged with a 56X CD-ROM drive (roughly the pinnacle of CD-ROM speeds). I found it has some version of Sonic Foundry’s ACID software, thus making good on the “applications” claim on the CD-ROM copy.

  Diamond Rio MP3 Sampler
  These are the names of the MP3 files found on the Diamond Rio MP3 sampler for the benefit of search engines.

  13_days.mp3
  albert_einstein_dreams.mp3
  a_man_of_many_colours.mp3
  anything_for_love.mp3
  a_secret_place.mp3
  bake_sale.mp3
  bigger_than_the_both_of_us.mp3
  boogie_beat.mp3
  bring_it_on.mp3
  buskersoundcheck_hippo.mp3
  charm.mp3
  chemical_disturbance.mp3
  coastin.mp3
  credit_is_due.mp3
  dance_again.mp3
  destiny.mp3
  dig_a_little_deeper.mp3
  diplomat6_bigmouthshut.mp3
  dirty_littlemonster.mp3
  dirty.mp3
  drivin.mp3
  Eric_Clapton_Last_Train.mp3
  etude_in_c_sharp_minor_op_42_n.mp3
  everybody_here.mp3
  freedom_4_all.mp3
  grandpas_advice.mp3
  groove.mp3
  heartland.mp3
  he_loved_her_so.mp3
  highway_to_hell.mp3
  hit_the_ground_runnin.mp3
  i_feel_fine_today.mp3
  im_not_lost_im_exploring.mp3
  into_the_void.mp3
  its_alright.mp3
  i_will_be_there.mp3
  i_will_pass_this_way_again.mp3
  juiceboxwilly_hepcat.mp3
  just_an_illusion.mp3
  keepin_time_by_the_river.mp3
  king_of_the_brooklyn_delta.mp3
  lovermilou_ringingbell.mp3
  middle_aged_rock_and_rollers.mp3
  midnight_high.mp3
  mr_schwinn.mp3
  my_brilliant_masterpiece.mp3
  my_gallery.mp3
  on_the_river_road.mp3
  pouring_rain.mp3
  prayer.mp3
  rats_in_my_bedroom.mp3
  razor_serpent_and_the_dub_mix.mp3
  ruthbuzzy_pleasestophangin.mp3
  secret_love.mp3
  ships.mp3
  silence_the_thunder.mp3
  sleeping_beauty.mp3
  slow_burn.mp3
  standing_in_my_own_way.mp3
  take_no_prisoners.mp3
  takin_up_space.mp3
  Taylor_Dayne_Unstoppable.mp3
  the_laundromat_song.mp3
  the_old_dun_cow.mp3
  the_people_i_meet.mp3
  trip_trigger_avenue.mp3
  tru-luv.mp3
  unfortunate_man.mp3
  vertigo.mp3
  when_she_runs.mp3
  where_do_we_go_from_here.mp3
  words_of_earnest.mp3
  

• Winamp and the March of GUI

  1er juillet 2012, par Multimedia Mike — General, ars technica, gui, user interface, winamp

  Ars Technica recently published a 15-year retrospective on the venerable Winamp multimedia player, prompting bouts of nostalgia and revelations of "Huh ? That program is still around ?" from many readers. I was among them.

  
  
  

  I remember first using Winamp in 1997. I remember finding a few of these new files called MP3s online and being able to play the first 20 seconds using the official Fraunhofer Windows player— full playback required the fully licensed version. Then I searched for another player and came up with Winamp. The first version I ever used was v1.05 in the summer of 1997. I remember checking the website often for updates and trying out every single one. I can’t imagine doing that nowadays— programs need to auto-update themselves (which Winamp probably does now ; I can’t recall the last time I used the program).

  Video Underdog
  The last time Winamp came up on my radar was early in 2003 when a new version came with support for a custom, proprietary multimedia audio/video format called Nullsoft Video (NSV). I remember the timeframe because the date is indicated in the earliest revision of my NSV spec document (back when I was maintaining such docs in a series of plaintext files). This was cobbled together from details I and others in the open source multimedia community sorted out from sample files. It was missing quite a few details, though.

  Then, Winamp founder Justin Frankel — introduced through a colleague on the xine team — emailed me his official NSV format and told me I was free to incorporate details into my document just as long as it wasn’t obvious that I had the official spec. This put me in an obnoxious position of trying to incorporate details which would have been very difficult to reverse engineer without the official doc. I think I coped with the situation by never really getting around to updating my doc in any meaningful way. Then, one day, the official spec was released to the world anyway, and it is now mirrored here at multimedia.cx.

  I don’t think the format ever really caught on in any meaningful way, so not a big deal. (Anytime I say that about a format, I always learn it saw huge adoption is some small but vocal community.)

  What’s Wrong With This Picture ?
  What I really wanted to discuss in this post was the matter of graphical user interfaces and how they have changed in the last 15 years.
  
  I still remember when I first downloaded Winamp v1.05 and tried it on my Windows machine at the time. Indignantly, the first thought I had was, "What makes this program think it’s so special that it’s allowed to violate the user interface conventions put forth by the rest of the desktop ?" All of the Windows programs followed a standard set of user interface patterns and had a consistent look and feel... and then Winamp came along and felt it could violate all those conventions.

  I guess I let the program get away with it because it was either that or only play 20-second clips from the unregistered Fraunhofer player. Though incredibly sterile by comparison, the Fraunhofer player, it should be noted, followed Windows UI guidelines to the letter.

  As the summer of 1997 progressed and more Winamp versions were released, eventually one came out (I think it was v1.6 or so) that supported skins. I was excited because there was a skin that made the program look like a proper Windows program— at least if you used the default Windows color scheme, and had all of your fonts a certain type and size.

  Skins were implemented by packaging together a set of BMP images to overlay on various UI elements. I immediately saw a number of shortcomings with this skinning approach. A big one was UI lock-in. Ironically, if you skin an app and wish to maintain backwards compatibility with the thousands of skins selflessly authored by your vibrant community (seriously, I couldn’t believe how prolific these things were), then you were effectively locked into the primary UI. Forget about adding a new button anywhere.

  Another big problem was resolution-independence. Basing your UI on static bitmaps doesn’t scale well with various resolutions. Winamp had its normal mode and it also had double-sized mode.

  Skins proliferated among many types of programs in the late 1990s. I always treasured this Suck.com (remember them ? that’s a whole other nostalgia trip) essay from April, 2000 entitled Skin Cancer. Still, Winamp was basically the standard, and the best, and I put away my righteous nerd rage and even dug through the vast troves of skins. I remember settling on Swankamp for a good part of 1998, probably due to the neo-swing revival at the time.

  
  
  

  Then again, if Winamp irked me, imagine my reaction when I was first exposed to the Sonique Music Player in 1998 :

  
  
  

  The New UI Order
  Upon reflection, I realize now that I had a really myopic view of what a computer GUI should be. I thought the GUIs were necessarily supposed to follow the WIMP (windows, icons, mouse, pointer) paradigm and couldn’t conceive of anything different. For a long time, I couldn’t envision a useful GUI on a small device (like a phone) because WIMP didn’t fit well on such a small interface (even though I saw various ill-fated attempts to make it work). This thinking seriously crippled me when I was trying to craft a GUI for a custom console media player I was developing as a hobby many years ago.

  I’m looking around at what I have open on my Windows 7 desktop right now. Google Chrome browser, Apple iTunes, Adobe Photoshop Elements, and VMware Player are 4 programs which all seem to have their own skins. Maybe Winamp doesn’t look so out of place these days.