Pastebin launched a little side project called VERYVIRAL.com, check it out ;-) Want more features on Pastebin? Sign Up, it's FREE!
Guest

Untitled

By: a guest on Oct 24th, 2011  |  syntax: None  |  size: 3.43 KB  |  views: 114  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. MPlayer SVN-r34186-4.4.3 (C) 2000-2011 MPlayer Team
  2.  
  3. Playing 8317_20111024144000.mpg.
  4. Cache fill:  0.00% (0 bytes)  
  5.  
  6. libavformat file format detected.
  7. [mpegts @ 0x88bc380]max_analyze_duration reached
  8. [NULL @ 0x89322a0]start time is not set in estimate_timings_from_pts
  9. [NULL @ 0x89322a0]start time is not set in estimate_timings_from_pts
  10. [NULL @ 0x89322a0]start time is not set in estimate_timings_from_pts
  11. [NULL @ 0x89322a0]start time is not set in estimate_timings_from_pts
  12. [NULL @ 0x89322a0]start time is not set in estimate_timings_from_pts
  13. [NULL @ 0x89322a0]start time is not set in estimate_timings_from_pts
  14. [NULL @ 0x89322a0]start time is not set in estimate_timings_from_pts
  15. [NULL @ 0x89322a0]start time is not set in estimate_timings_from_pts
  16. [NULL @ 0x89322a0]start time is not set in estimate_timings_from_pts
  17. [NULL @ 0x89322a0]start time is not set in estimate_timings_from_pts
  18. [NULL @ 0x89322a0]start time is not set in estimate_timings_from_pts
  19. [NULL @ 0x89322a0]start time is not set in estimate_timings_from_pts
  20. [NULL @ 0x89322a0]start time is not set in estimate_timings_from_pts
  21. [mpegts @ 0x88bc380]PES packet size mismatch
  22. [mpegts @ 0x88bc380]PES packet size mismatch
  23. [lavf] stream 0: video (mpeg2video), -vid 0
  24. [lavf] stream 1: audio (mp2), -aid 0, -alang eng
  25. [lavf] stream 2: audio (mp2), -aid 1, -alang NAR
  26. [lavf] stream 3: subtitle (dvb-teletext), -sid 0, -slang eng
  27. [lavf] stream 8: subtitle (dvbsub), -sid 1, -slang eng
  28. LAVF: Program 1
  29. VIDEO:  [MPG2]  720x576  0bpp  25.000 fps  15000.0 kbps (1831.1 kbyte/s)
  30. Load subtitles in ./
  31. Cache not responding! [performance issue]
  32. ==========================================================================
  33. Forced video codec: ffmpeg12vdpau
  34. Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
  35. Selected video codec: [ffmpeg12vdpau] vfm: ffmpeg (FFmpeg MPEG-1/2 (VDPAU))
  36. ==========================================================================
  37. ==========================================================================
  38. Forced audio codec: fftruehd
  39. Forced audio codec: ffdca
  40. Forced audio codec: ffeac3
  41. Forced audio codec: ffac3
  42. Forced audio codec: fflpcm
  43. Trying to force audio codec driver family ffmpeg...
  44. Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
  45. AUDIO: 48000 Hz, 2 ch, floatle, 256.0 kbit/8.33% (ratio: 32000->384000)
  46. Selected audio codec: [ffmp2float] afm: ffmpeg (FFmpeg MPEG layer-1 and layer-2 audio)
  47. ==========================================================================
  48. AO: [pulse] 48000Hz 6ch floatle (4 bytes per sample)
  49. Starting playback...
  50. [VD_FFMPEG] XVMC-accelerated MPEG-2.
  51. Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
  52. VO: [vdpau] 720x576 => 1024x576 MPEG2 VDPAU acceleration  [fs]
  53. A:47279.1 V:47279.1 A-V:  0.000 ct: -0.398   0/  0  0% 92%  1.8% 3919 0 0%
  54. [mpegts @ 0x88bc380]PES packet size mismatch
  55. [mp2float @ 0x89322a0]incomplete frame
  56. A:47279.9 V:47279.9 A-V: -0.000 ct: -0.398   0/  0  0% 92%  1.8% 3919 0 0%
  57.  
  58. Assertion 'm' failed at pulse/thread-mainloop.c:172, function pa_threaded_mainloop_lock(). Aborting.
  59.  
  60.  
  61. MPlayer interrupted by signal 6 in module: unknown
  62. - MPlayer crashed. This shouldn't happen.
  63.   It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
  64.   gcc version. If you think it's MPlayer's fault, please read
  65.   DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
  66.   won't help unless you provide this information when reporting a possible bug.
  67.