[VU+ Duo2] Playback recording->suspend->power on-> No audio!!!

[panch]

This is a possible bug I have noticed through a lot of build - may even be versions. When I have a recording playing and i put the box into suspend directly without stopping the playback. Then, when I power back on, I get no audio on either recordings nor live TV.
Anyone else with that problem?

 

[judge]

Yep, a VU driver issue.

 

[panch]

Yep, a VU driver issue.

Will it be resolved?

 

[abu baniaz]

Will it be resolved?

You will have to ask Vu that question.

 

[Fuzzy]

It happens on my Duo2 but the sound is only muted (although the mute icon isn't there). If you press 'mute' twice, the sound should come back.

 

[Rob van der Does]

PLi has found a work-around for this issue; we might be able to embed that in ViX.
Otherwise jumping back/forward 15 seconds or mute/unmute is a work-around you can use right away.

 

[2stein]

why is vu not able to fix this (and other) driver issue? i assume that you have reported the bug to vu...

 

[Rob van der Does]

VU doesn't have the best reputation when it comes to the quality of drivers. Whether this is a matter of laziness or lack of competence is something we don't know.
What we do know is that they create a lot of work-arounds for driver-issues; as they (and VTi & BH) only support VU-hardware, that is something they can do, but as you'll understand other image-builders can't (as that would have a negative influence on the correct functioning of other brands).

But your assumption is correct

 

[birdman]

What we do know is that they create a lot of work-arounds for driver-issues; as they (and VTi & BH) only support VU-hardware, that is something they can do, but as you'll understand other image-builders can't (as that would have a negative influence on the correct functioning of other brands).

"Negative influence" surely isn't unavoidable, given that you can determine what hardware you are running on.
It might be a bit of a PITA, but since it only needs to be done once, it's not that much of a P.

 

[Rob van der Does]

It's not a good coding practise to work-around driver issues via E2-hacks. It's only a last resort, and then only for very important issues.

 

[birdman]

It's not a good coding practise to work-around driver issues via E2-hacks. It's only a last resort, and then only for very important issues.

Whereas I reckon it is always good practice to make things work as they should do from the viewpoint of the end user.

 

[twol]

Whereas I reckon it is always good practice to make things work as they should do from the viewpoint of the end user.

Up to a point, I agree ....but not if it messes up other receivers.
Also from the other side, I am not mad about typical Korean companies that only care about selling their boxes and not providing good service. VU+ take your money and then wave goodbye ... they think THEY are the customer
If it was only ViX that complained about their driver support, I would wonder .... but it isn't

 

[birdman]

Up to a point, I agree ....but not if it messes up other receivers.

Well no, as that would be a failing from the viewpoint of the end user of those boxes.

But perhaps that is where getBoxType() can help?

 

[Rob van der Does]

That's part of many work-arounds, and not good coding practise. And besides it's a hell of a job to maintain software that's full of this kind of 'hacks'.
VU should learn to do a proper job, and not depend on 'hacking image teams' to take care of their flaws. If all teams would do that, more customers would claim problems at VU and make them think twice.

 

[2stein]

what's the best way to report driver problems to vu?
is there a support email adress?

 

[birdman]

That's part of many work-arounds, and not good coding practise.

It is when some boxes have hardware features which others don't.

 

[Rob van der Does]

It is when some boxes have hardware features which others don't.

Nope: that should be handled by drivers/features (proc-entries), not by 'if box=xyz then box has abc'.

 

[Rob van der Does]

what's the best way to report driver problems to vu?
is there a support email adress?

See

http://vuplus.com/sub/sub0203.php

 

[twol]

That's part of many work-arounds, and not good coding practise. And besides it's a hell of a job to maintain software that's full of this kind of 'hacks'.
VU should learn to do a proper job, and not depend on 'hacking image teams' to take care of their flaws. If all teams would do that, more customers would claim problems at VU and make them think twice.

Agree, unfortunately until people stop buying their hardware, they will only see fixing issues as a waste of resources costing them money :smash:

 

[birdman]

Nope: that should be handled by drivers/features (proc-entries), not by 'if box=xyz then box has abc'.

Still labelled as a driver bug, and therefore untouched.