Advertisement
Guest User

Untitled

a guest
Jun 26th, 2017
61
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.73 KB | None | 0 0
  1. /usr/bin/mplayer -noquiet -nofs -nomouseinput -lavdopts threads=2 -sub-fuzziness 1 -identify -slave -vo xv -ao pulse -nokeepaspect -framedrop -nodr -double -input nodefault-bindings:conf=/dev/null -stop-xscreensaver -wid 94372187 -monitorpixelaspect 1 -ass -embeddedfonts -ass-line-spacing 0 -ass-font-scale 1 -ass-styles /home/pcg/.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 1 -subpos 100 -volume 100 -cache 2000 -ss 126 -osdlevel 0 -vf-add pp -autoq 6 -vf-add screenshot -slices -channels 2 -af scaletempo /home/skap/Peep Show/Season 1/Peep Show s01e01.avi
  2.  
  3. MPlayer SVN-r1.0~svn-r32568-4.4.5 (C) 2000-2010 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/skap/Peep Show/Season 1/Peep Show s01e01.avi.
  10.  
  11. Cache fill: 0.00% (0 bytes)
  12.  
  13. AVI file format detected.
  14. ID_VIDEO_ID=0
  15. [aviheader] Video stream found, -vid 0
  16. ID_AUDIO_ID=1
  17. [aviheader] Audio stream found, -aid 1
  18.  
  19.  
  20. MPlayer interrupted by signal 8 in module: demux_open
  21. ID_SIGNAL=8
  22. - MPlayer crashed by bad usage of CPU/FPU/RAM.
  23. Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
  24. disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
  25. - MPlayer crashed. This shouldn't happen.
  26. It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
  27. gcc version. If you think it's MPlayer's fault, please read
  28. DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
  29. won't help unless you provide this information when reporting a possible bug.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement