70 replies to this topic

[PolarBear4711]

Hi *all

 

I use 2 VU receivers:

- VU+ Duo2

- VU+ Solo2

 

My brother is using this VU receiver:

- VU+ Solo SE

 

Didn't update since about 1 year. Everything always worked perfect, no sound issues.

 

Now updated all 3 receivers with version 9.0. Used several 9.0 versions now version 2024-05-19 .

 

All 3 receivers have this problem:

AC3 sound stops after a while. 

Only MPEG-sound is working. 

After reboot all is ok again but sound stops again after a while.

 

A/V setting "AC3 downmix" is set to "downmix". 

If i use "passthrough" there are issues with recordings and the volume on the VU+-remote is not working. 

Small hangers on the recordings, have to switch tone if possible. So passthrough is not the solution.

 

Is it possible to fix this ?  Would be nice.

 

Thank you for any help.

 

Regards,

Marc

[WanWizard]

You should only use AC3 passthrough when your box is connected to an Amplifier or Soundbar that supports AC3 and is used to control the volume.
In all other cases, use downmix, which converts AC3 to PCM stereo (or multichannel if the box supports it), which you can control on the box.

 

Downmix is processed in completely in hardware, so I have no clue what could cause this. Definitely not a software issue, as otherwise 99.999% of all users whould have this problem, virtually everyone uses AC3 downmix.

 

Also, there is no relation between audio settings and recording, when you record the digital data received is written to disk as it is received, without any processing. Audio settings are totally irrelevant for recording, so what "issues" are you exactly experiencing?

[PolarBear4711]

Thank you for your answer.

AC3 stops:
OK, i always used downmix, no problems until the latest updates. Now the AC3 sounds stops after a while. As mentioned: problem exists on 3 different VU+-boxes. 1 Box is operated on a different AV-receiver.
It takes a while until the AC3 sound stops, when switching to an MPEG-track sound works, after reboot AC3 comes back.
So i see that using downmix (as i did for years) is correct. Hope this problem can be solved.

Recording with passthrough:
I believe you that there is a 1:1 copy to the harddisk. When playback the recording there are short hangers until switched audio to an MPEG-track (if possible). 



 

[WanWizard]

I doubt we can do anything to solve it, as I can only repeat that audio downmix is a hardware function, inside the SoC, there is no software (ours or VU+) involved.

 

I have never heard of any issue like this, and I can't imagine what it would be, other than cable, TV or AV device. But having the issue on multiple locations rules that out.

 

So, I don't know.

 

Does it happen on all channels? Only some? On downloaded media with an AC3 soundtrack? Not by any chance channels using AAC or some other new codec, that your old hardware has trouble processing?

[PolarBear4711]

OK thank you for the hints.

AC3 sound is also not working on other channels, sound comes back if audio track is switched to MPEG.
I don't think AAC is used, in the selection of audio tracks i never see AAC, only AC3 and MPEG.
Recorded movies also not working with AC3 track, only MPEG or when restarted the box.
 

I will wait until it happens again and will bypass the AV-receiver and if this not helps take another HDMI-cable to track down the error.

[WanWizard]

What you also can try, when the audio has cut out, connect to the web interface of the box, and stream the channel currently on to your PC, and see if you have sound then.

 

If so, the problem is between the SoC and the speaker, if not, the problem is between reception and the SoC.

[PolarBear4711]

Hi, i tried all. Nothing helped. So i went back to OpenPli version 8.1 about 1 month ago.

 

After the downgrade, the problems are gone on all 3 boxes.

 

No idea what it was, but the downgrade helped.

 

 

Greetings

Marc

[David Jegust]

I have exactly the same problem. AC3 not working, exactly same symptoms as you describe. Openpli 9.0 2024-08-11.

It has worked but stopped working yesterday.  I suspected AudioSync plugin. Removed, Rebooted, still same problem.  But then after some minutes Ac3 started working again..

[tonskidutch]

I have none of these problems on my Zero 4K and I use a AVreceiver for sound.

Did you both have an update for the TV firmware?

explain more regarding your home cinema connections and if possible the Brand and specific models

 

It can't be OpenPli 9.x otherwise the hell would have broken loose by all users!!!

Edited by tonskidutch, 16 September 2024 - 11:57.

[PolarBear4711]

My setup:

---------

VU receivers:

- VU+ Duo2

- VU+ Solo2

Both connected with HDMI

 

AV-Receiver:

Onkyo TX-SR707

 

TV:

LG OLED65C17LB

Does updates all the time. I don't need these updates. Use it only as a monitor with HDMI

 

 

My brothers setup:

------------------

VU receivers:

- VU+ Solo SE

Connected with HDMI

 

AV-Receiver:

Sony STR-DH700

 

TV:

Samsung NeoQLED QN85B

About the updates: i don't konw. It is only used as a monitor with HDMI .

 

 

We both had the same issue with AC3 sound.

Since the downgrade all is OK, sound never stopped again.

 

Thank you.

 

Regards

Marc

[WanWizard]

Nothing has changed to drivers for VU+ first and second generation boxes in many, many years...

 

Solo SE is from 2015, the Duo 2 from 2019.

 

Is this with DVB broadcasts, or with "other" media? Does the problem stil exist if you connect the box directly to the TV?

[PolarBear4711]

Hi,

 

The audio loss came after a while. I can not say how long it took.

I have only see this with DVB broadcast. After reboot it was OK again until the next dropout.

 

The VU+ was never connected without AV-receiver, terrible sound ....

 

As i told already: after the downgrade in May 2024, all is OK, no audio loss again.

[teo1966]

Did you use autobackup when restoring? Install the latest openpli without autobackup. I had the same problem here with my ultimo 4k and amplifier.

[WanWizard]

That suggests you made a configuration that was incompatible with your amp. Things that are fixed with reinstallation usually are.

[PolarBear4711]

I'm not sure i understood the question from "teo1966" about "autobackup" correct ?

When i changed to version 9.x in May 2024 i didn't install from scratch.

Used "flash image" with backup, all with the remote control. Update worked without an errormsg.

Never installed version 9.x from scratch because there is an upgrade path from version 8.x without reconfigure all the stuff.

[PolarBear4711]

It is strange that the audio dropouts where on 3 different VU+'s and 2 different AV-receivers.

[WanWizard]

It was I think a remark related to yours saying "a downgrade solved the problem".

 

Given the fact that anything hardware related for these boxes haven't changed since OpenPLi 7, and DVB is completely processed in hardware, the only things that may be of influence are AV configuration settings, and the hardware itself.

 

And if you downgraded without restoring a backup of a newer version, chances are that would have reset your AV configuration.

[PolarBear4711]

Thank you WanWizard

What you recommend to do ?

[tonskidutch]

 

My setup:

---------

VU receivers:

- VU+ Duo2

- VU+ Solo2

Both connected with HDMI

Does updates all the time. I don't need these updates. Use it only as a monitor with HDMI

 

 

I had some issues with HDMI old cables und HDMI plugs. After I bought myself new ones (Ultra speed HDMI 2.1 a ) which also felt better plugin in / not wiggeling in the HDMI ports the troubles were over.

 

[WanWizard]

I was watching some recordings from earlier this week, both from the same channel, and I had something similar, audio suddenly cut out. Toggling from AC3 to MPEG audio and back via the audio menu restored it again.

 

I have no digital amp, HDMI is directly connected to the TV. Recording was made on a Duo 4K, playback was on a Solo 4K.

 

And it got weirder. I also had video cut-out, so the image suddenly froze. Initially I thought about smartcard issues, but it went on for over 20 minutes, and meanwhile audio continued, so it was not a decoding issue.