PDA

View Full Version : 'No sound' bug is back in 5.1.004


robby2k9
19-12-17, 16:17
Having had sound problems with the later 5.0 releases I haven't bothered to update for a while.
Today I tried to load the latest image (5.1.004) only to find the infamous 'no sound' bug, I tried 2 flashes & system resets but to no avail.
I then flashed the previous version (5.1.003) & the sound is ok, so it looks like the buggy driver has crept back in to this latest release somehow.
Sicilian
19-12-17, 16:21
Try set A/V to 2160p, then make sure downmix is set to yes.

Please send a report to:


support@octagon-germany.de

Provide them with a video of your settings, make and model of tv and ensure the video shows clearly theres not audio.
robby2k9
19-12-17, 17:28
I checked all the settings & confirmed everything is as it should be.
I would have thought that this is a VIX problem as the original bug in 5.0.027 was fixed in later releases right up to 5.1.003, it suggests that whoever made 5.1.004 used the wrong driver during the build?
Sicilian
19-12-17, 17:30
I checked all the settings & confirmed everything is as it should be.
I would have thought that this is a VIX problem as the original bug in 5.0.027 was fixed in later releases right up to 5.1.003, it suggests that whoever made 5.1.004 used the wrong driver during the build?

No its not a ViX bug, its a bug in the drivers, all teams use the same latest drivers.
ccs
19-12-17, 17:31
Which driver is you box using? menu/information/about (or something similar).

You''ll then be able to compare 003 and 004
twol
19-12-17, 18:03
Judging by the really angry posts on another forum (to which Octagon are/were active), they have never fixed this issue.
aldo2332
20-12-17, 16:04
same problem on some channels since latest 004 release. Challenge tv for example. Was working before
robby2k9
13-02-18, 22:32
Just tried the latest release (013) select screen resolution to 2160 in initial setup & no sound, updated via web to 016, still no sound.
The problem seems to relate to the resolution, if initial setup after flash is 720 or 1080 all is well, selecting 2160 kills the audio.
Strangely, if the initial setup is 720 or 1080 & it's then changed later to 2160 it not only kills the audio for that resolution but all resolutions, go back to 1080 or 720 & still no sound.
The only fix I can find is to re-flash, Factory reset is not an option at this time (see next line below)
Also now have another bug (in both releases), after performing a factory reset VIX crashes at the point the setup asks if you want to adjust the screen alignment.
(Using Sony TV KD-65XD8599)
Willo3092
13-02-18, 22:45
I have a similar TV (Sony Bravia 65XE8596) and I've also never managed to get audio on 2160 although other people say the latest drivers have cured the problem.
I wonder if it's something to do with the TV or HDMI?
robby2k9
13-02-18, 23:10
The old drivers worked fine, the last image to work flawlessly was 5.0.26 (drivers dated 2017-09-05)
I've reported the problem (again) to Octagon support, they didn't even reply last time!
I don't suppose it's possible to get a new VIX release using the old drivers is it?
ccs
13-02-18, 23:16
Also now have another bug (in both releases), after performing a factory reset VIX crashes at the point the setup asks if you want to adjust the screen alignment.

See here....
http://www.world-of-satellite.com/showthread.php?58944-OpenVix-5-1-014-not-available-on-the-website&p=466319&viewfull=1#post466319
Ashley69
14-02-18, 09:34
For 2160 to work correctly the Tv, the set top box, and the hdmi leads must all be 4K compatible.
robby2k9
19-02-18, 13:56
For 2160 to work correctly the Tv, the set top box, and the hdmi leads must all be 4K compatible.

Not really relevant as I have a Sony 4K tv - Octagon SF4008 + HDMI lead supplied with Octagon, box set to 2160
It all works fine with VIX builds up to 5.0.26 but not on any later build.
As I said previously, the drivers changed after this build.