747 replies to this topic

[SpaceRat]

The problem here:
Normal timeshift, activated by pressing "Pause": Seems to work.
Unpause by pressing "Play": Sometimes works, but more likely returns to "live".
Rewind/Ffwd within timeshift: Works, but Multi-Quickbutton pops up uselessly in foreground and needs to be "exit"ted manually.

Behaviour came up some days, maybe one or two weeks ago.

Before, it was alright:
"Pause" started timeshift and paused instantly, "Play" resumed playback from the time when timeshift was started and Rwd/Ffwd just worked like you would expect.

Vu+ Ultimo. Timeshift on local harddisk.

Sadly I do not have an image as of end of December, else I would revert to one of those builds.

[greatred]

Thanks SpaceRat for reporting the issue. So now we have seen problem confirmations from 4 different VU+ Boxes:
ULTIMO@SpaceRat, DUO@blzr, SOLO@Nikei and I have the same with my UNO Box.

sarcasm ON

Now let`s wait for the SOLO2 firmware to be released and probably the same will be reported by it`s users ...
Then we will hear again that it is caused by bad VU drivers

sarcasm OFF

[Rob van der Does]

Now I hope that the solurion wont be to wait for vu drivers update or swapping the uno for a ET box ...

Did you try Vu's 20130111 drivers to see if this problem has been fixed (see http://archive.vuplu...d/drivers/beta/)?

[greatred]

Many thanks SatKierd for pointing out that new BETA drivers have been released recently.

20130111
- Fix CI problem in dual tuner(ultimo)
- Support bypass edid
- Improve graphics2D
- Support hardware audio PCM codec(will be used in the upcoming new OE)
- Fix EOS detection in media playback

The last changelog entry sounded very promising.

But unfortunately new BETA drivers are still affected by the same issue.

Just to confirm that I have installed the drivers:

root@vuuno:/lib/modules/3.1.1/extra# ls -la
drwxr-xr-x	2 root	 root		   448 Jan 15 20:31 .
drwxr-xr-x	4 root	 root		  1488 Jan  7 04:51 ..
-rw-rw-r--	1 1000	 1000		  5117 Jan 11 10:05 brcmfb.ko
-rw-rw-r--	1 1000	 1000	   5819276 Jan 11 10:05 dvb-bcm7413.ko
-rw-rw-r--	1 1000	 1000		105860 Jan 11 10:05 fpga_directc.ko
-rw-rw-r--	1 1000	 1000		  4199 Jan 11 10:05 procmk.ko

Edited by greatred, 15 January 2013 - 20:38.

[ivos83]

Will this stay an unsolved issue? Does anyone have a copy of the Vu+ Duo firmware of 30/31 December ?
I do only have a copy of the 20121101 firmware (vuduo).

Thanks in advance!

[SpaceRat]

Will this stay an unsolved issue?

Same question here ...

Does anyone have a copy of the Vu+ Duo firmware of 30/31 December ?

A version for the Vu+ Ultimo would be appreciated too.

[greatred]

Timeshifting has been broken for the VU+ Boxes and I see only 5 people reporting the presence of the issue.
I`m wondering if TImeshifting is now old-school or what ??? Even if I had a MultiTuner STB I would use Timeshift.
How does it look like on the SOLO2?
Do we really have to wait for VU+ Driver update? How long should it take ? 1 month, 1 year or eventually will never happen ...
Please revert the commit and we will see how many people will miss the function introduced with the commit from December 31st.

[littlesat]

I think we will not revert that commit... At is solves another anoying thing for all other boxes....

[ivos83]

That i can understand, but it would be helpfull to have the possibility to go back to the firmware of 30/31 December.....

[SpaceRat]

That i can understand, but it would be helpfull to have the possibility to go back to the firmware of 30/31 December.....

Either that or I'll have to drop OpenPLi entirely, because it gets f*cked up more and more.
First they broke TimeShift, the most important feature of a hard disk receiver, now decoding HD+ channels is partly broken too ...
Since a few builds, after some operating hours HD+ doesn't get decoded anymore (real card, operated by cccam).


Based on the last 24 builds, I would guess there was a saboteur inside the team:

1. There were several new builds of OpenWebIf, none of them fixing the dominant bug inside (Can't zap to alternatives/can't edit timers on alternatives), so that I have to re-apply the existing patch again and again and again ...
2. OpenPLI crashes due to bad tuner usage (If you got two cables, one connected to only one tuner and the other one looped-through the other two (Three tuners in total)), take for granted E2/OpenPLI will try to record the same sat level (e.g. vertical high) on those tuners that are connected to independent cables and then the other sat/sat level (e.g. horicontal high) on the looped through tuner ...
3. It still fails to detect intermediate connection losses for a CIFS share and will hang ages when you try to access it rather than re-connecting quickly
and as if that wasn't enough, now we got those additional two bugs
4. timeshift f*cked
5. decoding broken

[littlesat]

1. What OpenWebIf patch?

[SpaceRat]

I think we will not revert that commit... At is solves another anoying thing for all other boxes....

Maybe we can have the working tstools as an option then?

As in
opkg install tstools-vu-old
?

[littlesat]

First VU does need to make good drivers - Not always create work-a-rounds.... You're asking for another if VU then....

Edited by littlesat, 23 January 2013 - 08:53.

[SpaceRat]

I'm not sure the developers get this right:

My wife is kicking my ass again and again because the most basic functionality of a hdd sat receiver is NOT working on a 600 EUR box. If I want to be a married man for longer, I either need to get SOME of the bugs fixed or I have to drop E2 and get a decent sat receiver like an iCord HD, where I currently don't have the money for the second option.

"A recording with dicontinuities, such as when you've cut out commercials
or when there were big dropouts during recording, did not account for those
when the length was requested."

I can not see where this patch is vital. Noone I know does cutting of recordings on the box and I never had any problems with recordings properly cut with PC software like TSDoctor. If you get big dropouts in recordings, fix your dish ...

Timeshift however is one of the two basic functionalities of a hdd receiver.

[SpaceRat]

First VU does need to make good drivers - Not always create work-a-rounds.... You're asking for another if VU then....

Fact: It was all working before.

If it's not broken, don't fix it.

[littlesat]

Did you already bother VU+??????????????????????????????

It was a fix for ALL other boxes.... except for VU... so I'm sorry....

Edited by littlesat, 23 January 2013 - 09:02.

[SpaceRat]

Did you already bother VU+??????????????????????????????

It was a fix for ALL other boxes.... except for VU... so I'm sorry....

I don't have ALL other boxes, but a Vu+ Ultimo.

My wife doesn't care if I tell her: Yeah, timeshift is not working anymore, but hey, it's not a bug, it's a feature.

[littlesat]

It is most likely a VU bug.... so please bother VU not us....

Edited by littlesat, 23 January 2013 - 09:19.

[BuGless]

I don't have ALL other boxes, but a Vu+ Ultimo.

My wife doesn't care if I tell her: Yeah, timeshift is not working anymore, but hey, it's not a bug, it's a feature.

As a workaround:
What if you simply start recording the channel, and then go to the recorded programs list and play it from there?
It should allow you to do exactly the same (and more) as when timeshifting.

[blzr]

My wife doesn't care if I tell her: Yeah, timeshift is not working anymore, but hey, it's not a bug, it's a feature.

actually it's not that timeshift on vu boxes doesn't work at all,
it's 'sorta' working
problem is only /?/ with resuming paused playback - you have to rewind/skip back to the point of pausing
//most of the times, on unpausing, playback starts 'live' (however ts is written to the disk as it should, from the beginning)
---
and btw. concerning this tstools fix - looks that (not surprisingly ) on vuduo its intetnded goal is not met either, cut recording's length it's still showed incorrect...