> -----Original Message----- > From: video4linux-list-admin@xxxxxxxxxx > [mailto:video4linux-list-admin@xxxxxxxxxx] On Behalf Of Rob Nielsen > > Christian Hack wrote: > > > > OK - I re-read your original post and now understand what > you're saying. > > That's very strange not being able to go back to the old version and > > have it work. Are you definitely removing and reloading the module? > > > Yeah, it's definately being removed and installed properly as > everytime > the old compiled versions are installed it works and > everytime the new > compiled versions are installed it doesn't work, even after a reboot. > > > >>That'd be great. My wife is getting a bit annoyed :) > >>Trouble is that > >>we seem to be the only ones with the problem so it might be > >>specific to > >>the Flyvideo 3000 (or even the PAL BG/DK version of the Flyvideo) > >> > > That is very possible. It's possible the audio tuner part > for PAL BG/DK > > isn't working quite correctly. Have you ever experience > varying volume > > levels? i.e. Sometimes I get what I assume is 100% volume, sometimes > > about 70%, sometimes 30% and regularly 0%. > > Yes, that sounds about right. It's annoying but livable > (when there is > some sound at least). > > > > BTW: How are you handling having the two cards and assigning them > > appropriate /dev/video and /dev/dsp devices? I am finding > it basically > > impossible to specify these options with the multiple > cards. It simply > > uses the first option for both cards which fails on the second card. > > > Not an optimal solution but I do an 'aplay -d1 /dev/dsp' > first to initialise > the sound card and get it to grab '/dev/dsp', then 'modprobe saa7134 > oss=1' which assigns /dev/dsp1 and /dev/video0 to the first card and > /dev/dsp2 and /dev/video1 to the second. I imagine there's a > better way > but it works for now. > I downloaded the latest snapshot on the weekend (20030724) and it now supports multiple card options in /etc/modules.conf. i.e. you can now have : "options saa7134 dsp_nr=1,2 video_nr=1,2" etc and it will assign them correctly. Thanks Gerd. Are you following this thread silently? I also am now 99.9% certain that the no sound bug is due to a mute toggle in the driver. I can't explain the random volume levels, but it does appear the volume level written to one of the card's registers is random (but usually 2) possibly explaining the different volume levels - from memory I have seen -2,0,1 and 2. I've also discovered that the audio rescan (for stereo, mono, lang1 and lang2) isn't always happening. This may be due to Myth not opening the device the same way each time. It only works correctly after actually setting the frequency. Myth remembers the last channel and thus doesn't always retune every time you select to watch live TV. Something to do with saa7134_tvaudio_do_scan not being called. I am still trying to get a programming manual from Philips so everything I've discovered is from mucking around with the driver so far. As I also know little about Linux Device Drivers, I'm kinda guessing to some extent too. Christian
