|
|
#61 | |
|
Registered User
Join Date: Nov 2007
Posts: 12
|
Quote:
Code:
# cat /proc/asound/card*/eld* monitor_present 1 eld_valid 1 monitor_name SONY TV connection_type HDMI eld_version [0x2] CEA-861D or below edid_version [0x3] CEA-861-B, C or D manufacture_id 0xd94d product_id 0x8400 port_id 0x20000 support_hdcp 0 support_ai 0 audio_sync_delay 0 speakers [0x1] FL/FR sad_count 1 sad0_coding_type [0x1] LPCM sad0_channels 2 sad0_rates [0xe0] 44100 48000 88200 sad0_bits [0xe0000] 16 20 24 |
|
|
|
|
|
|
#62 | |
|
Registered User
Join Date: Nov 2007
Posts: 12
|
I discovered that adding '-srate 44100' or '-srate 48000' to mplayer run string, solves the problem of having no audio in the "problematic" files. This doesn't look like a good solution to me, though...
|
|
|
|
|
|
|
#63 | |
|
Registered User
Join Date: Oct 2004
Posts: 44
|
Quote:
On my system there are several 22050 Hz files in /usr/share/sounds/purple which won't produce sound from HDMI out. Only after upconversion to 44100 I get sound (tested with sndfile-resample). |
|
|
|
|
|
|
#64 | |
|
Registered User
Join Date: Nov 2007
Posts: 12
|
Quote:
Other question is what are the side effects of having an upconversion "by default". What will happen if I have a DD / DTS audio stream and try to upconvert it as well? EDIT: In my mplayer log I posted earlier, it looks like mplayer detects a 32000 Hz stream in the file, but outputs only a 22050Hz stream (if I do not specifically tell it to upconvert to 44100). I think this might be the key... How do I find out why mplayer does this 32000 --> 22050 conversion? |
|
|
|
|
|
|
#65 |
|
Moderator
Join Date: Aug 2005
Posts: 1,327
|
andrewju, from your description, it sounds like MPlayer simply gives up and doesn't output any sound if the HW doesn't support the sample rate of the audio in the file. Perhaps somebody more familiar with MPlayer's internals can confirm/deny this behaviour.
Your TV doesn't support 22050/32000 directly, which is relevant, because digital audio is being sent directly to it with your new card. I think with your 8600, you were using the analog output from your sound-card and looping that into the 8600 using a cable? In that case, the sound card may have supported those other sample rates, which the 8600 then digitized at one of the TV's supported sample rates? |
|
|
|
|
|
#66 | |||
|
Registered User
Join Date: Nov 2007
Posts: 12
|
Quote:
Quote:
Quote:
|
|||
|
|
|
|
|
#67 |
|
Moderator
Join Date: Aug 2005
Posts: 1,327
|
I wonder if the problem is this: From your "eld" file, your TV only supports 44100 48000 88200. However, from /proc/asound/card1/codec#1, the audio device exposes more rates: 32000 44100 48000 88200 96000 176400 192000. I guess for 22050/32000 audio, MPlayer or the ALSA library up-converts it to the lowest rate supported by the audio codec (32000) and the TV simply ignores any audio at this unsupported sample rate. I'll have to look into how this is meant to work...
Could you try one more test for me: Please try playing back a 96000Hz sample (use -srate to upconvert to that). I assume that'll also appear to succeed in MPlayer, but again you'll hear no audio? |
|
|
|
|
|
#68 |
|
Moderator
Join Date: Aug 2005
Posts: 1,327
|
andrewju, I asked on the ALSA developers mailing list, and the ALSA driver is supposed to limit the list of supported sample rates to those that really are; basically what I said just above. However, this code isn't implemented yet, and I believe should be part of the core ALSA audio driver, rather than something NVIDIA-specific:
http://mailman.alsa-project.org/pipe...st/030109.html Unfortunately, that probably means that NVIDIA isn't going to be able to do anything about this in the short-term. That said, given ALSA's flexible configuration files, I wonder if this problem could be solved there; you'd probably want to ask about that on the alsa-users mailing list. |
|
|
|
|
|
#69 |
|
Moderator
Join Date: Aug 2005
Posts: 1,327
|
andrewju, are you able to recompile the ALSA kernel driver yourself? If so, the patch linked below might help with your issue.
http://mailman.alsa-project.org/pipe...st/030209.html |
|
|
|
|
|
#70 | |
|
Registered User
Join Date: Nov 2007
Posts: 12
|
Quote:
Will post here my results afterward. |
|
|
|
|
|
|
#71 | |
|
Registered User
Join Date: Dec 2008
Posts: 145
|
Quote:
ie. I'd like to use HDMI audio to my AVR, but also send the front left+right of the same audio out the analog 2-ch output on the mobo rear connector for use in Zone 2 (speakers outside on the back deck). I have not been able to get *any* audio out that port... even when I specify speaker-test with 0,0. I wasn't sure if the .asoundrc and/or modprobe could be redirecting everything away from 0,0 to my HDMI on 1,3. I'm going to play with Alsa slave/copy over the weekend, but was surprised that 0,0 didn't work with speakertest (suggesting some more basic level issue) thanks, Mike |
|
|
|
|
|
|
#72 |
|
Moderator
Join Date: Aug 2005
Posts: 1,327
|
andrewju,
FYI, the patch I mentioned is now in ALSA git: http://git.kernel.org/?p=linux/kerne...3382644257cfc3 Also, it's in the very latest snapshot file at ftp://ftp.kernel.org/pub/linux/kerne...a/alsa-driver/ (alsa-driver-snapshot.tar.bz2, not any of the dated versions yet) |
|
|
|
![]() |
| Thread Tools | |
|
|