RIVE - Realtek speaker fill issue

[izajasz]

Hello again my friends. I was off for 2+ months . Ive flashed BIOS from 4206 to 4802 and made clean install of windows 7 x64 (UEFI boot). I installed all latest drivers from intel/station-drivers.com/nvidia. But there is a problem with Realtek onboard Audio , which i never used. First when i connected the cables (3 analog jacks) , only 2 front speakers worked when i tested them i Realtek CP so i reinstalled the driver with plugs connected and it started to play all channels in CP. The problem is that when You play stereo source (for example music on youtube) it only works on 2 front speakers. As i recall , the option called "speaker fill" should send the stereo signal to all speakers but it DOES NOTHING! There is simply no diffrence in any game/music/movie when i tick speaker fill so i started to search on google and some guy wrote it works only when he chooses some sound effects in Realtek CP . I tried this and it WORKED even without speaker fill , even when i choose some sound effect preset , speaker fill does nothing. that makes another problem , when i want to watch some x264 movie with 5.1 sound effects make it expanded stereo instead of 5.1 , when i disable sound effects it gives me nice 5.1 output. SAme with Battlefield 3 - when i choose sound effect it just expands stereo but when i disable it it plays nice 5.1 (if "speaker fill" would work it should detect sound source and if its stereo it should automatically expand it to all speakers) . there is no diffrence if its off or on (i get stereo upmix when choosing any sound effect in Realtek CP tab when "speaker fill" is on or off) All of this suggests that Realtek drivers/software is crap. Now im using latest R2.73 6.0.1.7111 driver , i tried R2.73 6.0.1.7106, R2.72 6.0.1.7067 aswell as latest onbard audio driver from ASUS website and all of them give the same effect. This and the problems during "installing" analog cable seems really weird. Anyone has any ideas ?

[izajasz]

Turned out its a Chrome bug as described in https://productforums.google.com/forum/#!topic/chrome/bskC-dMyp7E . IT was some time ago but i have the same issue with latest (32.x) version of chrome. Tried the advices in the topic but it seems google "fixed" the workarounds and craped out the issue again. Via Ietab it works fine...