Hi,

I seem to be stuck with my sound in MythTV liveTV.
I've installed KnoppMyth R5E50, and everything went smoothly. I can watch TV allright, record shows, but don't get any sound.
I do get sound from MP3 playback etc.

So it must have something to do with the audio settings of the video capture.

I have a terratec cinergy 400, which uses the SAA7134 chipset. I am not using an audio pass-through from capture-card to sound-card.
Looking in /dev only showed dsp and mixer of the onboard sound card. I therefore assume I need to get a dsp1 and mixer1 for the capture-card.

I tried the following:
modprobe saa7134 oss=1
-> no effect
modprobe saa7134-oss
-> dsp1 and mixer1 get created, but still no sound
modprobe saa7134-alsa
-> error (null pointer and stack trace in dmesg), dsp1 and mixer1 get created but no sound. Trying to set anything on them with alsamixer causes a hang.

I suspect I need to get the saa7134-alsa working, and started googling. Alas, I did not find any clues. Any help is more than welcome.

Thanks,

Bart

Have you tried running alsaconf?

I had the same issue, I use a patch cable though.
this is how I got it working.

Download xawtv

apt-get install xawtv

run this command

v4lctl volume mute

If that works for you then insert this line in your

/.fluxbox/apps file

[startup] {v4lctl volume mute}

Let me know if it works I am curious!


Craig

No need to apt-get, the newer version of that control utlity is already on the system. Just use v4l2-ctl rather than v4lctl. Use the following to get usage info:

the command did not work for me with the v4l2-ctl, at least I could not figure out the correct command. the -L seems to give me commands that would be appropriate but I am not sure how I would invoke the equivilant command.


Craig

feeling TSTL lately

I played around and this worked
v4l2-ctl -c mute=0

when I tried it before I had not played with alsa mixer yet.

Craig

I had been struggling to find my way around the v4l2-ctl options, so I tried the unmute right away (since so many people reported good results with unmuting through v4lctl in various forums). No luck for me though

I still suspect that the audio part of my capture card is not yet visible to Linux. I'll try the unmute in combination with 'sudo modprobe saa7134-oss' and post the results.

Bart

Still no luck

The modprobe saa7134-oss does result in /dev/dsp1 getting created, but even after unmuting with v4l2-ctl -c mute=0 there's still no sound.

I also tried running alsaconf, but there only my onboard audio shows up. The capture-card remains invisible.

Probably I need to get the saa7134-alsa module working, but I haven't found any pointers to what might be going wrong...

When I try adding it directly, there's a stack trace in dmesg (and hangs when I try to access the card through alsamixer).
I also changed the entry in /etc/modules from saa7134 to saa7134-alsa, but after rebooting I noticed that for some reason it does not want to load the module! The original saa7134 gets loaded allright

If I find something that works, I'll post it here...

Bart

I have a flyvideo 3000 which uses the same chip and I had the same problem when upgrading to r5D1. I am planning on upgrading to R5E50 tonight, so the new version may have other problems.

Yes, I do believe it has to do with getting saa7134-alsa or -oss working correctly. I was using oss previously, but switched to alsa with my last upgrade. I'm not sure where I found which index to use. Here is my entry in the modprobe.d directory:


options saa7134 card=2 tuner=5 oss=1
install saa7134 /sbin/modprobe --ignore-install saa7134; /sbin/modprobe saa7134 -alsa
options saa7134-alsa index=1

You will need a different card and tuner number in the first line (I'm sure you know those already). Hope that helps

That was one of my other gripes/issues. In which file in the modprobe.d dir to these options go?

Thx,

Bart

It can go into any file you like. I made a new file called "tv". Linux looks at all the files in this directory for settings. So you can call it "cinergy" if you want.

Here is what my whole file looks like:



I just upgraded to R5E50 today. I also just added a pvr-150 card (Christmas gift) so I haven't fiddled with the saa7134 stuff yet on the new install. I have the pvr-150 working, so next up is the old card. I'll let you know if I have any luck.

Heh, never stumbled upon that fact...
I put a file there, and lo and behold, it does try to load the alsa driver for the card. Unfortunately it still doesn't work out ok.

The dsp1 and mixer1 devices get created, but looks like they're merely placeholders. The stack trace in dmesg indicates something is still very wrong, and I have no idea where to look next

Curious if you can get things working after your upgrade.

Bart