[VU+ Solo2] Problems with PiP

[rbaltutis]

Installed latest image 3.2.026
Tried activate PiP:
1. Select Free of Air program TEST 1
2. Press Blue Button on remote control
3. Again Press Blue Button (Activate PiP)
I see PiP function working (see same program on big and small window).
4. Press Blue Button
Missing sound
5. Press Blue Button (Disable PiP)
Still missing sound
6. Change channel.
Sound start working

1. Select another Free of air program TEST 2
2. Press Blue Button on remote control
3. Again Press Blue Button (Activate PiP)
I see PiP function working. TEST 2 on big screen TEST 1 on small screen.
4. Press Blue Button
Sound working fine
5. Press Blue Button (Disable PiP)
Sound working fine

1. Select paid program TEST 3
2. Press Blue Button on remote control
3. Again Press Blue Button (Activate PiP)
I see PiP function working. TEST 3 on big screen TEST 2 on small screen.
4. Press Blue Button
Sound working fine
5. Press Blue Button (Disable PiP)
Sound working fine

Please check why sometimes sound stopping work (mostly if during PiP see same channel and try disable PiP).

 

[judge]

Long standing VU driver issues...

 

[rbaltutis]

Never had similar problems with an old Vix Apollo 023 (August 2014) image.
No sound issues.
When activate PiP in main screen and PiP screen always show same program just with remote control later can change program on main screen.
New image 3.2.026 when activate PiP sometimes show same program like on main screen, sometimes when activate PiP ir both screens show different programs.

P.S. now updating to 3.2.027. Test PiP function after update.

P.P.S. tested new 3.2.027 image - same problem with PiP.

View attachment Enigma2-02-12-2015_09-16-00.log

 

[:-)]

Have same annoying problem on Vu+ Duo2 see

http://www.world-of-satellite.com/s...ur-LCD-no-longer-shows-current-progarmme-name

PiP Problem still ongoing on openvix 3.2.027 BUT tried putting the current latest original manufacturer Vu+ image on my receiver and PiP then works perfectly - so as the latest Vu+ original image has the latest drivers the problem is not the Vu+ drivers but openvix

Anyway look at all the driver updates in the openvix version log (read through from 3.2.011 till .027) - driver updates for Vu+ left right and centre - but still the PiP bug mysteriously goes on

To get to the bottom of this "driver" business why not post links to details of the offending drivers (if they are still even the same version) that way people can take it up with Vu+

But Vu+ attitude is "PiP works on our image" so Vu+ think the coders who write the images have got something wrong while the coders counterclaim it is Vu+ "drivers" progress to resolve the PiP problem is what is really needed - not a blame game.

 

[IAmATeaf]

Does it work using 'their' image using the same drivers as in ViX?

 

[:-)]

Does it work using 'their' image using the same drivers as in ViX?

Yes.

Are you saying you know how many / which different versions of "drivers" are in use? Please specify which exact one has the "issues"?

But....

Long standing VU driver issues...

As nobody ever says exactly which driver version or exact driver file they are talking about with "issues" it is impossible to say until more useful and exact information is supplied.

Which is why it looks like a big pass the blame game between vix coders to Vu+ who write all the drivers (that the vix coders use in their vix image) who then blame the vix coders again.

So can you shed some light on which driver and why PIP is perfect on Vu+ Factory image which is why Vu+ think openvix image coders are getting it wrong.

i.e. It is not constructive to say only that a computer has "driver issues" - which driver? Chipset, Ethernet, Audio, Video, Storage Controller........ lets get Vu+/Vix driver/file & version specific and resolve all of this.

 

[abu baniaz]

Menu > Information > About
That will tell you the driver details and kernel version.

Please continue to use the factory image which works perfectly fine for you.

Stop your insults at the ViX team. Nobody forces you to use the Vix image.

 

[judge]

Yes.

Are you saying you know how many / which different versions of "drivers" are in use? Please specify which exact one has the "issues"?

But....



As nobody ever says exactly which driver version or exact driver file they are talking about with "issues" it is impossible to say until more useful and exact information is supplied.

Which is why it looks like a big pass the blame game between vix coders to Vu+ who write all the drivers (that the vix coders use in their vix image) who then blame the vix coders again.

So can you shed some light on which driver and why PIP is perfect on Vu+ Factory image which is why Vu+ think openvix image coders are getting it wrong.

i.e. It is not constructive to say only that a computer has "driver issues" - which driver? Chipset, Ethernet, Audio, Video, Storage Controller........ lets get Vu+/Vix driver/file & version specific and resolve all of this.

No matter what VU say, they have some driver issues.
The same code is being used on other manufacturers boxes without issue (not that they don't have their own driver issues too).

 

[rbaltutis]

If drivers cause problem why you not use old drivers? Users report about problems, but you not sort problems.
Current problems:
Problem with PiP - old images working fine.
Problem with IPTV recording - old images working fine.
Problems when watch recorded program (Fast forward, rewind) - not problems on old images.
Some other minor problems.
I reported these problems, but no changes.
At this moment use old VIX image (August 2014), because all new images come with bugs.

 

[judge]

At this moment use old VIX image (August 2014), because all new images come with bugs.

You can be sure Aug 2014 VU builds have driver issues with sound too, probably just easier to reproduce using a different method.

 

[judge]

If drivers cause problem why you not use old drivers? Users report about problems, but you not sort problems.

ViX use drivers supplied by VU+. As drivers are closed source, only VU can fix any issues reported & they are reported...

Problem with PiP - old images working fine.

Driver issues, outside of ViX control.

Problem with IPTV recording - old images working fine.

GStreamer issues & being updated regularly.

Problems when watch recorded program (Fast forward, rewind) - not problems on old images.

Driver issues, outside of ViX control (although I've not noticed this in any recent builds)?

Some other minor problems.

Could be anything. No idea what your minor problems are.

 

[abu baniaz]

IPTV recordings are fine. Service reference must be 4097 though.

 

[rbaltutis]

IPTV recordings are fine. Service reference must be 4097 though.

Do you tried watch recorded IPTV program? Fast forward and rewind working fine? Already sorted this problem?

http://www.world-of-satellite.com/showthread.php?49266-Problems-with-IPTV