72 replies to this topic

[WanWizard]

Compared to what? An image is made of out of an awful lot of components.

 

For the three major ones, the OS, the BSP and the application, you could check and compare the commit history.

 

As to Solo SE drivers, you'll have to go back to 6.2-release to find older drivers, current releases use the same drivers as in OpenPLi 7.

[linus]

Yeah, nothing happens when I change audio track.

I'm pretty sure it contains "something" that triggers a race condition in the drivers, which means trying other distro's won't really fix things, as all use the same drivers, and they haven't changed in many years. You'll have to go back to 2018 or so to find an image with other drivers...

Hello.
The problem happen at the begining for me.
I succeed to watch full but with just play to be sure it would not jump.
And try to fast forward and back forward wheras i was near the end of the last episode and all was ok, if you do it in the middle or at the end it seems to be ok in this file. Same for langage.

The problem for me is at the begging, i fast forward until the start of the first episode, i could not, it jump to the end at a moment.
So if you try after 90 minutes of play then do the same it should be ok, but it's the same for me too.

Compared to what? An image is made of out of an awful lot of components.

For the three major ones, the OS, the BSP and the application, you could check and compare the commit history.

As to Solo SE drivers, you'll have to go back to 6.2-release to find older drivers, current releases use the same drivers as in OpenPLi 7.

The version i use ( openpli 9.0 202407) with the actual.


I try to find the commit history but could not find it. Do you have a link?

Edited by linus, 1 November 2024 - 23:15.

[linus]

Ok, i found the link:
https://github.com/O...ts/release-9.0/
and
https://github.com/O...ts/release-9.0/

 

So nothing new in enigma2.
On oe-core there is change and something related to vu plus:
https://github.com/O...528f220b82a91e7
But i should already have it on my image

 

So nothing that could help but well it cost nothing to test the upgrade.

Edited by linus, 2 November 2024 - 09:54.

[linus]

Ok, so i have upgraded the vu+ to the lattest stable version of 9.0 today.
Will see if the AC3 pb come back.

If it come again, will try to switch on the only channel where i got mpeg audio and not AC3 to see if there is sound or if not and all the audio is dead.
If it come again will try to switch audio to passthrough to see if audio come back or not. (as my tv could play AC3)

 

And just for information, i play the record on openAtv 5.1, and got the same result then on openPli 9.0, it jump at the end if i fast forward from the begining. But jump key works like on open pli, and after i pass the corrupt point it works again (like on openPli 9.0).
I do not know what happen for this record but for the playing part it the same.

[WanWizard]

As I wrote, I couldn't reproduce it, not on my Octagon SF8008, not on the VU+ Solo 4K.

 

I can do nothing but repeat that all images use the same drivers ( as nobody has the source, they are supplied as binaries by VU+ ). This is most likely a race condition in the drivers for this specific box, trigged by corruption in the MPEG stream. Which makes it unique to that particular box and that particular file.

 

Anything from OpenPL 7.0 onwards has the same drivers, as VU+ never released updates past 2019. And as VU+ is no more, this will never change.

 

If you are interested in driver information,

• go to https://github.com/O...penpli-oe-core/, and select the version you're intrested in from the dropdown (default = develop).
• scroll down and click on "meta-vuplus", this is the hardware support layer for VU+
• click on "recipes-bsp"
• click on "drivers"
• scroll down to the "vuplus-dvb-modules" or "vuplus-dvb-proxy" recipe for the required box (older use modules, newer use proxy)
• click to open, the variable "SRCDATE" tells you the version of the drivers for the selected OpenPLi release
• if you click on "History" upper-right, to can see the commits that lead up to the selected version

[linus]

Yep, lets forget this record pb, it's seems it's not related to the AC3 pb.
This corrupted record happen once, other are correct so it's not an always point, something add happen, let's forget that, i will try over driver if it happen again and often.

The AC3 pb is more problematic and seems to be recent, so perhaps a solution could be found moreover if it happen on over hardware then vu+.
 

Edited by linus, 2 November 2024 - 17:58.

[linus]

hello.

So the problem appear this evening.
The vu + is in shutdown mode when not used (so not in sleep mode), so it was a fresh start.
As i said, openpli was updated at the latest stable version today.

We watch 30 minutes of live TV, then I could watch one record file with no problem (something like 2h of watch). When i jump the publicity, i had always used the jump key (so not related to fast forward key, just to add information).
Everything was ok.

I start a second record files, use the jump key to jump the plublicity and sound stop working, so it happen in record too not only in live TV.

 

So here is the result:
I stop the record, and switch to a channel that have MPEG audio and not AC3:  there is sound, but the sound is bad, it's a crackling sound (don t know if it's really the correct word) that is not good. It's the sound of the channel but totally bad. So a degraded sound.
No ac3 channel work, but when i switch from mpeg channel (with sound but bad) to AC3 channel, i got a cracking loop sound that stop after a short moment (but it's not the sound of the channel, it's a sort of loop) then no sound like before.
If i switch to passthrough for AC3, sound work normally (don t know if it's usefull). If i switch back to AC3, no sound again.

 

After the reboot, sound is back, i have played the record again and could see the first part with no problem (so it's a record problem as i could watch the same part where sound stop working).

 

 

Don t know if it's usefull?
 

[linus]

Rectification:
"so it's a record problem as i could watch the same part where sound stop working)."

====>
"so it's NOT a record problem as i could watch the same part where sound stop working)."

The soud stop working immediatly after a jump.

Edited by linus, 3 November 2024 - 08:14.

[s3n0]

The sound stop working immediatly after a jump.

 

Hi there.

 

Again, I always had this specific problem on YouTube or when watching videos from an external drive. However, this does not apply to Vu+. Once upon a time, I used the Formuler F4-Turbo and not the Vu+Solo SE V2.

 

I solved it by installing ServiceApp and setting ExtEplayer3 as the default player instead of Gstreamer. This solved the problem. In this case, it was a problem with the Gstreamer software player.

Edited by s3n0, 3 November 2024 - 14:41.

[WanWizard]

That is only relevant for downloaded or streaming media. DVB recordings are MPEG/TS files, and are not played by gstreamer, the are send directly to the SoC ( i.e. they are type 1, not 4097 ).

[linus]

I found perhaps a settings that i do not set like that before:
3D surround was enabled in HDMI in audio settings whereas it was off for me in my old OpenATV. So i disable it to see if it change the problem or not.

Other settings that is on is multi PCM near Downmix in audio settings.
For the moment i let it on but i will try to disable it too see if it change something, i am not sure this settings exist in my old openAtv 5.1 i will take a look to see what i was using.


 

Edited by linus, 3 November 2024 - 15:04.

[linus]

Hello, to give some more information.
For the moment since i turn off 3D surround in HDMI, the problem never come back.

Not totally sure it's totally solved, but in fact since it happen really fast before and twice where as it never happen for the time now, i think it's solved.

[s3n0]

Nice. Thanks for new info.

 

Better test it for a few days or weeks @linus. Then try turning on 3D surround in HDMI again to see if anything changes.

 

In the sound settings for HDMI, I personally have this 3D Surround always disabled (default setting - disabled), on my Vu+ Solo SE V2.
 

But the fact... that it could be some kind of error in HDMI communication ... or cables ... or connectors, I also mentioned. I had the feeling that in my case the problem concerns the audio-amplifier in the subwoofer, which is only about 30 cm away from my Vu+ Solo SE V2 set-top box. It may or may not be related. But it's strange... when after turning on the subwoofer (power), in my case, the sound stopped working (there was silence) in the set-top box, but the video continued to play correctly.

Edited by s3n0, 16 November 2024 - 13:35.