2012-05-16, 10:25
@DDDamian
First, i must appologise for a not very nice behavior. I must have thank you for your time and help me solved problem instead of a simple "i don't like it".
I'll nevertheless explain why i've been a little upset, about my problem of VIA vs nVidia.
I've got no problem with DirectSound when i was under Windows XP.
After upgrading to Windows7 (after you've telling me a lot of time to do this to have the behavior i wanted), i've got no problem with either DirectSound or Wasapi with all builds and the last build i've done (and keeping for now), by chance, just just before the merge of the new AE.
Suddenly, with the new AE, there is a problem of the VIA highjacking the nVidia with Wasapi... For me, there is an issue in the AE, and not on my end. I would have got the problem since the upgrade to Windows 7 (even on the situation of only Wasapi and not DirectSound) with both versions, it may have been a problem on my end, but in this situation, i don't think it is. So, telling me that the problem is in my end the solution is to disable VIA, period ! ....
If you had said that, for now, this is the fix, this problem is not a priority (as i have a fix), i would not have react like that.
But my question is : What's your statement about it ?
From my point of view, resuming :
- No issues with Directsound under Windows XP.
- No issues with either DirectSound or Wasapi under Windows 7 before new AE.
- Issues after merge of the new AE.
=> Problem is not on my end, but with something on the new AE.
Now, if you think otherwise, i would like a little explaination of "why".
Is there any debug log code i could had somewhere (maybe trace the raw data from EDID or others things) to help trace to find out why xbmc detect only 2 channels when everyone else seems to detect more...
As i don't know the specs, the following may be stupid questions, but, if xbmc read EDID, are devices :
- Report all the supported numbers audio channels or only the maximum ?
- If they report more than one information, is it supposed to have a specific order ?
- Can the informations be mixed (in a total mess), or are they packed (for exemple all sampling rates are in the same packet, you can't have an audio format mixed in the middle).
I'm asking about only and only the specs, not the usual behavior devices may have.
First, i must appologise for a not very nice behavior. I must have thank you for your time and help me solved problem instead of a simple "i don't like it".
I'll nevertheless explain why i've been a little upset, about my problem of VIA vs nVidia.
I've got no problem with DirectSound when i was under Windows XP.
After upgrading to Windows7 (after you've telling me a lot of time to do this to have the behavior i wanted), i've got no problem with either DirectSound or Wasapi with all builds and the last build i've done (and keeping for now), by chance, just just before the merge of the new AE.
Suddenly, with the new AE, there is a problem of the VIA highjacking the nVidia with Wasapi... For me, there is an issue in the AE, and not on my end. I would have got the problem since the upgrade to Windows 7 (even on the situation of only Wasapi and not DirectSound) with both versions, it may have been a problem on my end, but in this situation, i don't think it is. So, telling me that the problem is in my end the solution is to disable VIA, period ! ....
If you had said that, for now, this is the fix, this problem is not a priority (as i have a fix), i would not have react like that.
But my question is : What's your statement about it ?
From my point of view, resuming :
- No issues with Directsound under Windows XP.
- No issues with either DirectSound or Wasapi under Windows 7 before new AE.
- Issues after merge of the new AE.
=> Problem is not on my end, but with something on the new AE.
Now, if you think otherwise, i would like a little explaination of "why".
(2012-05-16, 00:41)DDDamian Wrote: @jpsdr - yes DTS-HDMA is supported. Your driver has to support it. If you right-click on the speaker icon in the right side of the taskbar, select Playback Devices, and on the HDMI device select properties, it will show you the supported formats. If DTS-HD is in there it will play DTS-MA.It reports DTS-HD. But, I've done this (before reading this post) indeed to check something else, and to go back to another hot subject, it also reports 8 supported audio channels...
Is there any debug log code i could had somewhere (maybe trace the raw data from EDID or others things) to help trace to find out why xbmc detect only 2 channels when everyone else seems to detect more...
As i don't know the specs, the following may be stupid questions, but, if xbmc read EDID, are devices :
- Report all the supported numbers audio channels or only the maximum ?
- If they report more than one information, is it supposed to have a specific order ?
- Can the informations be mixed (in a total mess), or are they packed (for exemple all sampling rates are in the same packet, you can't have an audio format mixed in the middle).
I'm asking about only and only the specs, not the usual behavior devices may have.
