Changes between Initial Version and Version 1 of Ticket #16335, comment 4


Ignore:
Timestamp:
Jul 2, 2020, 7:15:04 PM (4 years ago)
Author:
ttcoder

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #16335, comment 4

    initial v1  
    1 Actually nope, the "output 0" in the Media Prefs is related to multi-channel audio, and to something called "jack re-tasking". We use that in our installs of Haiku, to make _one_ HDA chipset (the Analog one of course, not HDMI) output two different audio feeds to two different applications : with some special tweaks you can make MediaPlayer get hooked up to "output 0" and send a song for preview to e.g. the (analog) green jack, and have another application get hooked up to "output 1" and send another song to e.g. the (still analog) orange jack. Completely unrelated to HDMI.
     1Actually nope, the "output 0" in the Media Prefs is related to multi-channel audio, and to something called "jack re-tasking". We use that in our installs of Haiku, to make _one_ HDA codec (the Analog codec of course, not HDMI codec) output two different audio feeds to two different applications : with some special tweaks you can make MediaPlayer get hooked up to "output 0" and send a song for preview to e.g. the (analog) green jack, and have another application get hooked up to "output 1" and send another song to e.g. the (still analog) orange jack. Completely unrelated to HDMI.
    22
    33I'm out of my depth for analysing your problem any further (korli will have to volunteer :-) but on the analog vs HDMI side, I'm fairly positive that your log contains the usual (sane/sensible) scenario : the driver attempts to talk to the HDMI codec, fails (returns playback 0x00000..), then attempts to talk to the Analog codec, and "succeeds" (apart from some minor warning about failing to look up display labels).