Advertisement
mightymouse2045

log from smplayer

Feb 6th, 2012
132
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.61 KB | None | 0 0
  1. mplayer -noquiet -nofs -nomouseinput -afm hwac3 -sub-fuzziness 1 -identify -slave -vo xv, -ao alsa:device=hw=1.7 -nokeepaspect -framedrop -nodr -double -input conf=/usr/share/smplayer/input.conf -stop-xscreensaver -wid 37749079 -monitorpixelaspect 1 -ass -embeddedfonts -ass-line-spacing 0 -ass-font-scale 1 -ass-styles /home/ph/.config/smplayer/styles.ass -fontconfig -font Arial -subfont-autoscale 0 -subfont-osd-scale 20 -subfont-text-scale 20 -subcp ISO-8859-1 -vid 0 -aid 0 -subpos 100 -nocache -osdlevel 0 -vf-add screenshot -slices -channels 2 -softvol -softvol-max 110 /home/ph/Music/Downloads/Test High Def/hd_dts_sfx_long_lossless.m2ts
  2.  
  3. MPlayer2 2.0-438-gfc6a9e4 (C) 2000-2012 MPlayer Team
  4. mplayer: could not connect to socket
  5. mplayer: No such file or directory
  6. Failed to open LIRC support. You will not be able to use your remote control.
  7. Terminal type `unknown' is not defined.
  8.  
  9. Playing /home/ph/Music/Downloads/Test High Def/hd_dts_sfx_long_lossless.m2ts.
  10. Detected file format: MPEG-2 transport stream format (libavformat)
  11. ID_VIDEO_ID=0
  12. [lavf] stream 0: video (h264), -vid 0
  13. ID_AUDIO_ID=0
  14. [lavf] stream 1: audio (dca), -aid 0
  15. LAVF: Program 1
  16. PROGRAM_ID=1
  17. VIDEO: [H264] 1920x1080 0bpp 29.970 fps 0.0 kbps ( 0.0 kbyte/s)
  18. Load subtitles in /home/ph/Music/Downloads/Test High Def/
  19. ID_FILENAME=/home/ph/Music/Downloads/Test High Def/hd_dts_sfx_long_lossless.m2ts
  20. ID_DEMUXER=lavfpref
  21. ID_VIDEO_FORMAT=H264
  22. ID_VIDEO_BITRATE=0
  23. ID_VIDEO_WIDTH=1920
  24. ID_VIDEO_HEIGHT=1080
  25. ID_VIDEO_FPS=29.970
  26. ID_VIDEO_ASPECT=1.7778
  27. ID_AUDIO_FORMAT=8193
  28. ID_AUDIO_BITRATE=1536000
  29. ID_AUDIO_RATE=48000
  30. ID_AUDIO_NCH=6
  31. ID_START_TIME=600.00
  32. ID_LENGTH=21.17
  33. ID_SEEKABLE=1
  34. ID_CHAPTERS=0
  35. [ass] auto-open
  36. Opening video filter: [screenshot]
  37. ==========================================================================
  38. Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
  39. Asking decoder to use 8 threads if supported.
  40. Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
  41. ==========================================================================
  42. ID_VIDEO_CODEC=ffh264
  43. ==========================================================================
  44. Trying to force audio codec driver family hwac3...
  45. Opening audio decoder: [hwac3] AC3/DTS pass-through S/PDIF
  46. hwac3: switched to DTS, 1536000 bps, 48000 Hz
  47.  
  48. AUDIO: 48000 Hz, 2 ch, ac3le, 1536.0 kbit/100.00% (ratio: 192000->192000)
  49. ID_AUDIO_BITRATE=1536000
  50. ID_AUDIO_RATE=48000
  51. ID_AUDIO_NCH=2
  52. Selected audio codec: [hwdts] afm: hwac3 (DTS through S/PDIF)
  53. ==========================================================================
  54. [AO_ALSA] alsa-lib: conf.c:4514:(parse_args) Unknown parameter AES0
  55. [AO_ALSA] alsa-lib: conf.c:4647:(snd_config_expand) Parse arguments error: No such file or directory
  56. [AO_ALSA] alsa-lib: pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM hw:1,7,AES0=6
  57. AO: [alsa] 48000Hz 2ch ac3le (2 bytes per sample)
  58. ID_AUDIO_CODEC=hwdts
  59. Starting playback...
  60.  
  61. [Mixer] No hardware mixing, inserting volume filter.
  62. [format] Sample format little-endian AC3 not yet supported
  63.  
  64.  
  65. MPlayer interrupted by signal 11 in module: flip_page
  66. ID_SIGNAL=11
  67. - MPlayer crashed by bad usage of CPU/FPU/RAM.
  68. Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
  69. disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
  70. - MPlayer crashed. This shouldn't happen.
  71. It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
  72. gcc version. If you think it's MPlayer's fault, please read
  73. DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
  74. won't help unless you provide this information when reporting a possible bug.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement