Re: How do I get digital audio out to my headphones?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Feb 11, 2010 at 8:40 PM, Marko Vojinovic <vvmarko@xxxxxxxxx> wrote:
> On Thursday 11 February 2010 22:23:34 Marcel Rieux wrote:

>> As I already said, the only sound I can get at the present time is
>> analog sound on my computer. I suppose my HD TV doesn't accept analog
>> sound, at least not through an HDMI cable. But, if I plug headphones
>> in my computer, then the video card and the S/PDIF wire are not
>> involved.
>
> Do your headphones support digital audio? I've never seen any headphone model
> that has an integrated digital-to-analog converter (the so-called DAC), and I
> also believe such a thing would require some power to operate (batteries?).
>
> You won't hear anything if you try to use standard headphones or speakers on a
> digital-out jack.

According to Wikipedia:

The term "digital" or "digital-ready" is often used for marketing
purposes on speakers or headphones, but these systems are not digital
in the sense described above. Rather, they are conventional speakers
intended for use with digital sound sources (e.g., optical media, MP3
players, etc).

http://en.wikipedia.org/wiki/Loudspeaker#Digital_speakers

So, if digital output depends on digital speakers or headphones, it
seems digital output doesn't exist.

Still, digital sound exists... it seems.

> Rather, open a terminal and start pavucontrol (if you use pulseaudio, and I
> think it's a good idea). Then go to "output devices" tab (I see no "hardware"
> anything in pavucontrol either), and click on the "port" chooser.

I have no port chooser. all I can do under Input is move the Front
Left and Right sliders, which slide as a pair, not independantly.

> My hardware
> doesn't support digital audio, so I have only a couple of "analog this" and
> "analog that" devices. But if your audio card supports digital audio, then I
> guess there should be a "digital this/that" option somewhere among the
> choices. Select it. Then go to the "configuration" tab and check that any
> options there are also set to "digital whatever".

What you have under configuration is what I said I have under Hardware.

> I guess that should be enough. But before that you should probably play some
> music in analog way to make sure nothing is muted and there are no additional
> problems.
>
> Finally, you need some equipment connected to the computer that will receive
> digital audio, decode it back to analog and hopefully play it for you.

If Wikipedia is right, and that's also what I thought, plugging the
headphones in the computer should do it. It doesn't, for digital.

> And what is being
> used as a digital-out jack depends on the details of your sound card,

I don't have a sound card. I have an integrated sound chip.

> I
> suggest reading the manual for it. Usually it is the S/PDIF jack, a female
> cinch/RCA jack on the soundcard/motherboard, colored orange. If there isn't
> one like that, some other connector may be used for digital-out. Look it up in
> the manual that came with your card/motherboard.

I already explained how I installed the S/PDIF cable. On the mobo,
there's a S/PDIF Out pin and the other is labelled... ground, if I
remember well. On the video card, one pin is labelled J8, the other
has no labelling. I connected the J8 pin to S/PDIF out pin.

>> There was a bug report for "no sound" Fedora 12 rawhide, but it was
>> supposed that kernel 2.6.30 fixed the problem. Was the problem really
>> fixed?
>
> Well, what was actually the problem that was reported? What is the bugzilla
> number?

Sorry, I meant to leave the URL but forgot:

<https://bugzilla.redhat.com/show_bug.cgi?id=499524>

>> Here's (part of) what Cameron Jenkins  wrote on  2009-05-06:
>>
>> "I recently had Ubuntu Jaunty 9.04 on this very same laptop, and I'm pretty
>>  sure I had to use "options snd-hda-intel model=hp-dv4" to get sound to
>>  work, but I have tried that in /etc/modprobe.d/sound and ***nothing shows
>>  up in boot logs indicating the codec has selected that card to use.***"
>
> This has nothing to do with your sound card, he apparently has Intel hardware.

I noticed this but maybe my hardwae has the same problem.

>> I see nothing in boot.log pertaining to sound, alsa, codec, sb, snd,
>> Realtek, ALC888, etc.
>
> Why do you expect to see such things in boot.log?

I was surprised too but that's what the guy who filled the bug suggests.

> I would rather look up in
> dmesg and /var/log/messages for anything related to audio, sound, alsa,
> pulseaudio and such.

output relating to sound in dmesg:

HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
hda_codec: Unknown model for ALC888, trying auto-probe from BIOS...
ALSA sound/pci/hda/hda_codec.c:3862: autoconfig: line_outs=4
(0x14/0x15/0x16/0x17/0x0)
ALSA sound/pci/hda/hda_codec.c:3866:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3870:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3871:    mono: mono_out=0x0
ALSA sound/pci/hda/hda_codec.c:3874:    dig-out=0x1e/0x0
ALSA sound/pci/hda/hda_codec.c:3882:    inputs: mic=0x18, fmic=0x19,
line=0x1a, fline=0x0, cd=0x1c, aux=0x0
ALSA sound/pci/hda/hda_codec.c:3884:    dig-in=0x1f
ALSA sound/pci/hda/patch_realtek.c:1197: realtek: Enabling init
ASM_ID=0xe601 CODEC_ID=10ec0888
input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:14.2/input/input5

output relating to sound in /var/log/messages:

Feb  7 16:34:15 localhost rtkit-daemon[1394]: Sucessfully made thread
1392 of process 1392 (/usr/bin/pulseaudio) owned by '42' high priority
at nice level -11.
Feb  7 16:34:16 localhost rtkit-daemon[1394]: Sucessfully made thread
1401 of process 1392 (/usr/bin/pulseaudio) owned by '42' RT at
priority 5.
Feb  7 16:34:16 localhost rtkit-daemon[1394]: Sucessfully made thread
1402 of process 1392 (/usr/bin/pulseaudio) owned by '42' RT at
priority 5.

(...)

Feb  7 16:34:43 localhost rtkit-daemon[1394]: Sucessfully made thread
1534 of process 1534 (/usr/bin/pulseaudio) owned by '500' high
priority at nice level -11.
Feb  7 16:34:43 localhost kernel: fuse init (API version 7.12)
Feb  7 16:34:44 localhost rtkit-daemon[1394]: Sucessfully made thread
1544 of process 1534 (/usr/bin/pulseaudio) owned by '500' RT at
priority 5.
Feb  7 16:34:45 localhost rtkit-daemon[1394]: Sucessfully made thread
1571 of process 1571 (/usr/bin/pulseaudio) owned by '500' high
priority at nice level -11.
Feb  7 16:34:45 localhost pulseaudio[1571]: pid.c: Daemon already running.

Hope this helps.
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux