#9430 closed bug (duplicate)
media preference looks strange for HDA
Reported by: | jahaiku | Owned by: | korli |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Drivers/Audio/HDA | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | #11592 | Blocking: | |
Platform: | All |
Description
- In the Output-Tab only "Fro" is written. Attachment: media_hda.png
- Input-Tab is completely empty. Attachment: Media1.png
- In the General-Tab is 96kHz as frequency for Input and Output. Attachment: Media2.png
Is this OK? So High? I have tried to change to 48kHz or 44.1kHz, but this results in strange noise with max volume (perhaps can destroy speakers) and audio stopped working after the change.
This is a gcc4 build from hrev45227.
Attachments (3)
Change History (9)
by , 12 years ago
Attachment: | Media1.png added |
---|
by , 12 years ago
Attachment: | Media2.png added |
---|
by , 12 years ago
Attachment: | media_hda.png added |
---|
comment:1 by , 12 years ago
Component: | Preferences/Media → Drivers/Audio/HDA |
---|---|
Owner: | changed from | to
Status: | new → assigned |
Version: | R1/alpha4.1 → R1/Development |
comment:2 by , 12 years ago
I have now rechecked with real Hardware and there the TABs look correct. Only in qemu it looks that strange.
The only strange thing is that the frequenz is 96kHz on real Hardware, too.
comment:3 by , 12 years ago
You missed mentioning that you tested with Qemu, before :-)
The 96kHz is another topic, though. It currently uses the "best" mode available, no matter if this makes actually sense or not. Anyway, switching the frequencies sounds indeed awful, but it should go back to normal once you restart the media server. IOW this is a problem of the mixer, and not driver related.
comment:4 by , 6 years ago
Milestone: | R1 → R1/beta2 |
---|
comment:5 by , 6 years ago
Blocked By: | 11592 added |
---|---|
Resolution: | → duplicate |
Status: | assigned → closed |
Seems there is a more general case of this in #11592.
comment:6 by , 5 years ago
Milestone: | R1/beta2 |
---|
Remove milestone for tickets with status = closed and resolution != fixed
Could potentially be a problem in BMediaTheme but I don't see it with HDA over here. Assigning to the driver for now until the actual culprit is found.