Reply to thread

Message

<blockquote data-quote="Marcus Venturi" data-source="post: 1171113" data-attributes="member: 121570">There is something wrong with the audio code itself.In VolumeHandler.cs the CreateInstance() medhod has the following statement:if (GUIGraphicsContext.DeviceAudioConnected &gt; 0){...}The if-case is not entered, because GUIGraphicsContext.DeviceAudioConnected is 0 at that time.It is initialized later (at least on my PC).Therefore always the VolumeHandlerCustom is created, which is wrong, because I have selected the Vista/Win7 volume handler.In the base constructor of VolumeHandler there is the same comparision that prevents theVolumeOSD.HideOSD();from being called. If I jump there manually, the Volume OSD is hidden on my PC.[USER=60104]@Sebastiii[/USER] : Can you reproduce this behavior? Does this happen only on my PC?Looks like the Scale setting in the configuration is irrelevant, always the custom volume handler is taken.</blockquote>

[QUOTE="Marcus Venturi, post: 1171113, member: 121570"] There is something wrong with the audio code itself. In VolumeHandler.cs the CreateInstance() medhod has the following statement: if (GUIGraphicsContext.DeviceAudioConnected > 0) { ... } The if-case is not entered, because GUIGraphicsContext.DeviceAudioConnected is 0 at that time. It is initialized later (at least on my PC). Therefore always the VolumeHandlerCustom is created, which is wrong, because I have selected the Vista/Win7 volume handler. In the base constructor of VolumeHandler there is the same comparision that prevents the VolumeOSD.HideOSD(); from being called. If I jump there manually, the Volume OSD is hidden on my PC. [USER=60104]@Sebastiii[/USER] : Can you reproduce this behavior? Does this happen only on my PC? Looks like the Scale setting in the configuration is irrelevant, always the custom volume handler is taken. [/QUOTE]

Verification