?? intf-vcd.txt
字號:
NAVIGATE DOWN DEFAULTNAVIGATE LEFT PREVIOUSNAVIGATE RIGHT NEXTAlso this plugin understand numeric input. Since the hot-keys don'thave assignments for numbers, the digits on the keyboard (alsoavailable from the keypad if num-lock is on) are hard-coded. Eventhough this isn't customizable, it's probably what most people wouldexpect and want.The enter a number just type the digits of the number. To finishspecifying a number use the whatever key is bound to vlc's"ACTIVATE" hot key - the default value is the "Enter" key.However the next/previous/return buttons can be prefaced with a numberand that has the effect of hitting that button that many times. Solet's say you want to go forward 5 "Chapters" and hitting the "Next"key 5 times would do that Instead, you could just enter the digit 5followed by the key that is assigned to "NAVIGATE RIGHT", probably theright-arrow key.If you have better suggestions as to what functions the VCD buttonswould be better bound to how what fixed algorithm to use when not inPBC, let me know.-----------------------------------------------------------------Configuration settings:-----------------------------------------------------------------Configuration settings in xine are generally put in ~/.vlc/vlcrc, butcan be configured via a vlc GUI. A description of the ones specific toVCDX are listed below.- -vcdx-deviceThis specifies the name of the video device that will be used by default.If you don't specify anything, the plugin scan for a suitable CD-ROMdevice containing a Video CD in it.The default device in a MRL when none is listed. The default isdetermined by the appropriate name for the OS that you are running.- - vcd-debugAn integer (interpreted as a bit mask) which shows additionaldebugging information see the Debugging Section below for moreinformation about the bits that can be set.-----------------------------------------------------------------Troubleshooting Guide-----------------------------------------------------------------The VCD plugin leaves a bit to be desired and has many bugs. I expectthat there will not be covered below. But the below is a start.This gives higher-level troubleshooting. More detailed andlower-level information is given in the next section DEBUGGING. Problem: something doesn't work. Start at step -1.Problem: The program gets a SEGFAULT or gives core dump. Start at step0.Problem: I don't get anything playing. I can't even get information listed in "Media and Stream Information" or the playlist.Determination: start at step 1.Problem: Okay, I something plays menu now. But I don't see informationabout the CD in the playlist.Determination: start at step 5.-1. (Something doesn't work.) A lot of what is put here really is applicable to reporting problems and troubleshooting in vlc and the concepts really apply to any sort of bug reporting. When reporting a problem it's helpful to have facts: a) the version of vlc) you are using b) the OS you are running on c) the version of libcdio and/or libcddb you are using versions of libcdio and libcddb can be obtained by running pkg-config --modversion libcdio pkg-config --modversion libvcdinfo d) what you input or requested (e.g. the full command line entered - if it is possible to reproduce the problem by giving a commandline that is desirable since it is probably the simplest way to convey exactly what was requested) People often give (some part) of an error message neglecting to also include what was requested or entered that led to the output. e) The setting for this plugin. That is the values of the variables that start cddax- listed above. On Unix this can generally be found in ~/.vlc/vlcrc f) Exactly the messages that were what given. You can turn increase the verbosity level by setting "verbosity=2" in the vlc preferences files. On Unix the preferences file is generally in ~/vlc/.vlcrc but there are GUI ways to set this too. Give everything that is in the message log.0. (The program gets a SEGFAULT or gives core dump.) Get and send a stack trace. In addition to -1. Make sure the program has been compiled with debugging symbols put into the code. This is usually done by having the "-g" flag set when compiling the program. You can get a strack trace the GNU debugger using the "where" command. For example on this might work: gdb vlc *name-of-corefile* where1. (I don't get anything playing. I can't even get information listed in "Media and Stream Information" or the playlist) Do you even have the plugin loaded? When you run the vlc GUI, under Settings/Preferences you should see a "plugins" expandable list and under that another "access" list do you see a expandalbe entry under "access" labeled "vcdx"? If so, skip on to step 2. a) If no "vcdx" expandable list, thent the VCDX plugin isn't loaded. Does a shared object exist? The plugin shared object is called "libvcdx_plugin.so" It should be in the directory that has ...vlc/access. If this isn't around you need to build and install the VCDX plugin. b) if libvcdx_plugin.so is in the fileystem, there might be a loader error; perhaps libcdio or libvcdinfo are not installed or are the wrong version. Use ldd on the file to see that it has all of the libraries dependencies satisfied. Also you might be able check if there was an attempt to load it by tracking system calls. On Linux and other OS's) "strace" can be used to see if the file gets accessed. On Solaris use "truss". For example on Linux, amonst the many line of output when I run "strace -e trace=file vlc" I see this amongst lots of other output: ... stat64("/usr/local/lib/vlc/access/libvcdx_plugin.so", {st_mode=S_IFREG|0755, st_size=302990, ...}) = 0 open("/usr/local/lib/vlc/access/libvcdx_plugin.so", O_RDONLY) = 5 The parameters inside the calls may be different depending on where vlc is installed and what release is installed. If the the file is found and "opened", There may also be a message may under "setup/logs".2. (There plugin was loaded and preferences found). In the "vcdx" tab of preference. An important selection is "vcdx-device." If this is set to the empty string, VCDX will try to scan your drives for a suitable device if the driver has the capability to scan for drives. However you can set the device to something of your choosing. On GNU/Linux, this may be "/dev/cdrom" and on Solaris it may be "/vol/dev/aliases/cdrom0". If you set this field, make sure these are correct for your particular setup. For example, I generally play out of the DVD device and this is called /dev/dvd rather than /dev/cdrom.3. (Video CD Setup devices seems correct and there is a CD in the drive). when you run vlc vcdx:// you should see your CD disk light go on if you have one. And the CD should be read. a. If not something's wrong like step 2. Another tack may be to try to read a disk image of a Video CD and thus elimate any problems with hardware. You can get a test Video CD disk image to test here: http://www.vcdimager.org/pub/vcdimager/examples/test_svcd/test_svcd_pal.zip After unzipping this run there should be files test_svcd_pal.cue and test_svcd_pal.bin. Get out of xine and run from the directory that contains those files: vcdx://test_svcd_pal.cue@E0 If you see something playing then this is a hardware problem. -----------------------------------------------------------------Debugging-----------------------------------------------------------------**General vlc debugging...Before delving to things specific to this plugin, some preparation maybe in order. You'll probably want to configure vlc with "--enable-debug".plugin with debug information. Instead of "make'ing" with "make", use"make debug" and instead of installing using "make install" use "makeinstall-debug". I use gdb to debug. Debugging vlc with the entire suite of pluginsunder gdb is slow because it has to read in symbol tables from all theplugins. There are two ways to make loading faster when debugging. Thesimplest is just to go to the plugin directory and remove unusedplugins. Another approach is create a new directory and make(symbolic) links into the complete plugin directory. Another way tospeed up gdb loading is to attach the debugger after vlc has started upvia a command like: gdb -p *pid-of-vlc-process***vcdx debugging...It's a fact of life that this plugin is in an incomplete state and hasbugs. So to facilitate tracking down problems we let you see what'sgoing on dynamically. Various debugging settings will cause output toappear on vlc plugin log and/or "standard error" (assuming you've runxine in a way that you can capture this).You think of debug switches as a bit mask, that you specifiy as anintegers the various "bit" values (given in decimal) are listed below. name value description ------ ---------- ----------- meta info 1 Trace Meta information event info 2 Trace keyboard events MRL 4 Things involved getting lists of what's in the VCD ext call 8 Trace vlc calls to the plugin routines all calls (10) 16 Trace all calls LSN (20) 32 Trace updates to the Logical sector number (basically reads) PBC (40) 64 Trace things involved with playback control libcdio (80) 128 Turn on CDIO debugging seek-set (100) 256 Trace "seek set" calls seek-cur (200) 512 Trace "seek cur" calls still (400) 1024 Trace Still-frames vcdinfo (800) 2048 Turn on VCDINFO debugging**Video CD debugging...The tool vcd-info from the cdio branch of vcdimager can be used toshow the entire contents of a Video CD or selected portions ofthat. Until the cdio branch of vcdimager is completely merged withvcdimager, the cd-info branch vresion has a few morefeatures. (However consult vcdimager for complete of the program).vcdxrip can be used to extract portions of a Video CD and or create anXML description file of the Video CD. This XML file and the extractedfiles can be used by vcdxbuild to recreate another Video CD.And finally see also tools cd-info an cd-read from libcdio.-----------------------------------------------------------------Other references-----------------------------------------------------------------http://www.vcdhelp.com/http://www.vcdimager.org/http://www.vcdimager.org/guides/#guides$Id$
?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -