Dear Wiki user, You have subscribed to a wiki page or wiki category on "Freevo Wiki" for change notification.
The following page has been changed by 65.49.70.167: http://freevo.sourceforge.net/cgi-bin/moin.cgi/FrequentlyAskedQuestions ------------------------------------------------------------------------------ @@ -41,7 +41,7 @@ From the shell type: mount /mnt/dvd -now ls /mnt/dvd (if the mount was successful). If you see files there you are halfway there. If the mount failed then you need to setup your /etc/fstab to have an entry for your dvd drive, like: +now ls /mnt/dvd (if the mount was successful). If you see files there you are halfway there. If the mount failed then you need to setup your /etc/fstab to have an entry for your dvd drive, like: /dev/hdc /mnt/dvd iso9660 defaults,user,noauto,ro 0 0 @@ -89,7 +89,7 @@ == Compiling Freevo (optional) == -You do not have to compile Freevo unless you try the CVS version. You definitely +You do not have to compile Freevo unless you try the CVS version. You definitely do not have to compile the freevo_runtime package, please see the DocumentationPage/InstallDeps for more info. @@ -118,7 +118,7 @@ = If I watch a movie that has a different aspect ratio than the TV/monitor (i.e. is letter-boxed, e.g. 16:9), the movie is displayed at the top of the screen. In other words, it is not vertically centered. = This is a known problem with the X11/Xv display in MPlayer, -hopefully this will be fixed later. UPDATE: This info is misleading, or perhaps just outdated. In the freevo_config.py file (/usr/local/freevo/freevo_config.py) change the option from MPLAYER_USE_WID = 1 to MPLAYER_USE_WID = 0 that should fix the problem. I don't know the advantage for using window mode, but disabling it fixes the "window at the top" problem. +hopefully this will be fixed later. UPDATE: This info is misleading, or perhaps just outdated. In the freevo_config.py file (/usr/local/freevo/freevo_config.py) change the option from MPLAYER_USE_WID = 1 to MPLAYER_USE_WID = 0 that should fix the problem. I don't know the advantage for using window mode, but disabling it fixes the "window at the top" problem. = /dev/dsp doesn't work under KDE, it complains that the sound device is busy. = @@ -215,7 +215,7 @@ {{{ su root -c "./blanking" }}} -from within the Freevo helpers directory. It will disable screen blanking in the kernel for all the virtual terminals. +from within the Freevo helpers directory. It will disable screen blanking in the kernel for all the virtual terminals. = How do I use the btaudio kernel module to play or capture sound? = @@ -224,9 +224,9 @@ to the tv card and the other end to the line-in jack on a sound card. This way there is always audio data being pumped to the sound card's line-in. Any programs used to play or record this audio must be configured to get the stream -from the line-in channel of the sound card's DSP resource (ie: /dev/dsp0). The +from the line-in channel of the sound card's DSP resource (ie: /dev/dsp0). The btaudio kernel module provides an alternate method of recording or playing -sound from bt878 tv-tuner cards. +sound from bt878 tv-tuner cards. From the linux kernel documentation: {{{ @@ -235,26 +235,26 @@ Function 0 does the video stuff (bt848 compatible), function 1 does the same for audio data. This is a driver for the audio part of the chip. If you say 'Y' here you get a oss-compatible dsp device - where you can record from. + where you can record from. }}} Please also read Documentation/sound/btaudio from the linux kernel source! It has some valuable information. So, if you think your tv card has this capability then try it out. You will -probably have to build your own kernel / this module yourself but may be +probably have to build your own kernel / this module yourself but may be lucky enough to have it included in your linux distribution. There is another module that is called tvmixer which provides access to the sound mixer capabilities of these cards as well. Both of these modules can be found in the sound section of the linux kernel configuration. Once you have these modules compiled it is time to try them out. The btaudio -module has some important options. If you read 'Documentation/sound/btaudio -from the linux kernel source' you will see that btaudio may provide access to +module has some important options. If you read 'Documentation/sound/btaudio +from the linux kernel source' you will see that btaudio may provide access to both a digital and analog audio source. My tv card is capable of 16 bit stereo sound so I use the digital one. For the record I am using an ATI TV-Wonder -(regular edition) as my tv card. Btaudio also has a 'rate' option which -defaults to 32kHz so you will most likely not need to change this option but +(regular edition) as my tv card. Btaudio also has a 'rate' option which +defaults to 32kHz so you will most likely not need to change this option but you should be aware of it. To load btaudio I do the following: @@ -287,7 +287,7 @@ out. If you have a silly audio patch cable going from your tv card to your sound card remove now because you won't be needing it! -Not all programs are capable of capturing audio using btaudio. A few +Not all programs are capable of capturing audio using btaudio. A few requirements come to mind. You must be able to tell the program to capture at a sample rate equal to what btaudio is providing. The default for btaudio is a rate of 32000 Hz. Most programs will try to capture at a rate of @@ -296,7 +296,7 @@ to capture from, and sometimes which channel (line-in). For me the DSP for my digital btaudio device is /dev/dsp1 as shown in the above kernel messages. There are also some other problems that occur when it comes to programs using -a btaudio device. Programs use functions called ioctls to control hardware +a btaudio device. Programs use functions called ioctls to control hardware and the btaudio device does not have all of the same functions that an OSS or ALSA driver will provide. Therefore some programs will simply 'break' while attempting to access a btaudio device. Some of the time this can be worked @@ -308,10 +308,10 @@ 'freevo/WIP/Aubin/mp1e_btaudio.diff'. For encoding I am quite fond of the nvrec tools, http://nvrec.sf.net and -find that ffmpegrec and divx4rec both work great for use with btaudio. My +find that ffmpegrec and divx4rec both work great for use with btaudio. My command lines for each of these programs is as follows: {{{ -mp1e: mp1e -v -m3 -p/dev/dsp1 -r14,100 -S32 -a0 -c/dev/video0 -s640x480 \ +mp1e: mp1e -v -m3 -p/dev/dsp1 -r14,100 -S32 -a0 -c/dev/video0 -s640x480 \ -b3 -o file.mpeg key parameters: -p/dev/dsp1, the btaudio device @@ -337,8 +337,8 @@ -r 32000, the sample rate -b 16, 16-bit sound -s, stereo sound -}}} -If someone has btaudio working with mplayer and/or mencoder please add your +}}} +If someone has btaudio working with mplayer and/or mencoder please add your information to this document. The next step is to play the resulting mpeg or avi and see if you get correct @@ -362,3 +362,10 @@ Digital Cable in the United States has not been standardized. There are currently no support for tuning digital tv natively in freevo at the moment. Depending on your hardware (whether you have a serial or a port for recieving IR signals (looks like a headphone jack)) you might be able to use scripts to tune your digital cable box but these scripts will unfortuneately be hardware specific. Another option maybe an IR signal sender like IRblaster but again custom scripting will be required. Digital Cable users in Europe might be able to use linuxtv.org. + += Why is the audio out of sync for watching TV, but working ok everywhere else? = + +The problem is to do with how mplayer grabs video, versus audio for playing television. Mplayer grabs the video from the TV card and +runs it through it's own layer before putting it on the screen, the audio, on the other hand, is passed through a cable from the TV card to your sound card (in most cases) and thus there is a delay, depending on the speed of your machine between the audio, and the video showing up the screen since the video must pass through mplayer first. + +A number of solutions for this are being examined; if you have a fast machine, this probably won't occur, but for slower machines, we should have a workaround shortly. ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Freevo-wikilog mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-wikilog
