[ViX_Misc] Can't rewind timeshift using remote stream/fallback tuner

[realdannys]

... but not necessarily with timeshift .... I don't for example

although the last 6 months I know I have used it during Wetek testing and don't remember issues, so think your posts have been positive and useful

Thanks Twol. To be honest I don't really use timeshift much either - in fact I barely watch TV! haha, I just like the technology and happen to noticed it suddenly stopped working a few months ago. Although the VU+ Zero does behave a lot better than your boxes thankfully. I can pause and it behaves just like the VU+ Duo2 does with timeshift, which is the same for everyone, it pauses does a bit of a visual skip and glitch as it enters timeshift mode but works fine.

But yeah pause is the main thing I guess really, and at least it pauses and unpauses.

One thing I will add rewind and fast forward works perfectly on non live streamed content from the Duo2 (eg recordings) so however it reports the bitrate for that is working perfectly and maybe should be emulated?

 

[realdannys]

The source files for the image is opensource and hosted on Github. Feel free to submit fixes.

More importantly, raise these issues there might be more beneficial? Whats the Github source?

 

[abu baniaz]

Raising issue on Github won't be beneficial. Which image did it last work properly for you?

 

[Huevos]

Whats the Github source?

https://github.com/OpenViX/enigma2/commit/df939a32f7f0599b465efe2fe295c25f9d3253a4

 

[realdannys]

https://github.com/OpenViX/enigma2/commit/df939a32f7f0599b465efe2fe295c25f9d3253a4

Does this mean we wont even be able to pause from now on though?

 

[Huevos]

Does this mean we wont even be able to pause from now on though?

Please tell us a specific image where timeshift worked while streaming, because as far as we know this has never been an option.

 

[birdman]

Please tell us a specific image where timeshift worked while streaming, because as far as we know this has never been an option.

Errr...it has been an option. People have been using it. That's why this thread exists.

 

[Huevos]

If it worked before and doesn't now we need to know where that happened.

 

[birdman]

If it worked before and doesn't now we need to know where that happened.

To pull in some quotes from this thread

#1 realdannys: "This [failing] has happened for me on multiple versions of 3.2, 4.0 and now 4.1."

#26 twol: "although the last 6 months I know I have used it during Wetek testing and don't remember issues"

So one-all (possibly...).

I'm also trying to think of what is involved. Using a remote tuner (which is actually just streaming from it) means you get what would be the same data as you filter out of a DVB stream (I think). For timeshift you just save this as a recording and then play that back in the same way you play-back a live recording. So it all looks as though it could be possible.

But the indications from the logs are almost as if the timeshift file gets opened, but nothing ever gets written to it?

Related to this (in the way I'm thinking about it) is how timeshift works at all. As has been mentioned in another thread, the ability to limit the length of the timeshift file no longer exists (it did at some point?). So does that mean someone using timeshift who never changes channel (only watches recordings) and never switches off the box ends up with a full-disk?
And if there were some way to limit this file, how would you handle the "circular file" nature of doing so.

 

[psykix]

Just to throw something else into the pot...

When I was using the Mutant HD2400, if we had it on timeshift, at the end of the programme, the programme would start again from the beginning. It was the wife that noticed it, and asked why they were showing the same episode of Coronation Street again

I've not noticed it on my Solo 4k, but probably haven't had the receiver long enough to notice.

 

[abu baniaz]

The timeshift feature used to have a maximum length option. When the file split at program change was introduced, that was removed. You are asked what to do on exit (default), usual option is to not save. Normal programs should not be a problem, but when watching events like the Marathon this could be an issue.

Not sure if anyone has tried recording and playing back instead of timeshift. referring to remote service instead of conventional usage.

 

[ccs]

Just to throw something else into the pot...

When I was using the Mutant HD2400, if we had it on timeshift, at the end of the programme, the programme would start again from the beginning. It was the wife that noticed it, and asked why they were showing the same episode of Coronation Street again

I've not noticed it on my Solo 4k, but probably haven't had the receiver long enough to notice.

... there is an option to define what to do when you reach the end of a programme.

I've found that hitting the end of a (timer) recorded programme, using skip or FF, before it has finished recording, can be a bit problematical.
Nothing drastic happens, but I'd need to check to give more details.

 

[twol]

The timeshift feature used to have a maximum length option. When the file split at program change was introduced, that was removed. You are asked what to do on exit (default), usual option is to not save. Normal programs should not be a problem, but when watching events like the Marathon this could be an issue.

Not sure if anyone has tried recording and playing back instead of timeshift. referring to remote service instead of conventional usage.

have just done so on between my ET8500's using fallback tuner and the recording plays to the end OK

 

[abu baniaz]

Can't rewind timeshift using remote stream/f

sorry, meant to say record and play at same time. Also go back and forth while it is still recording and playing.

In essence, timeshift by another method.

 

[abu baniaz]

These are logs from openATV 25/04/2016 Using manually activated timeshift using an RCSC service.

 

[Clabs]

sorry, meant to say record and play at same time. Also go back and forth while it is still recording and playing.

In essence, timeshift by another method.

I tried to do this just now - Duo2 server to Zero client via Fallback.

A recording appears in the recording list, but when I try and play it, the file is empty. I tried several times and always the same empty files are generated. So - fairly different behaviour than the ET8500.

To summarise what I am experiencing, pause/unpause works perfectly. Whilst paused, the timeshift seekbar appears but none of the info on it changes. Pressing FFW or RRW does nothing. I have attached a couple of debug logs where I paused/unpaused numerous times and also attempted to record and play back. I also experienced a crash when trying to exit timeshift so I have included that too. Hope they are of some use.

Later on, I will hook up the ET8500 again and also a Vu Ultimo and see how they differ. I also plan on flashing a few of the older images from the archive to see if I can find a point where it was working.

View attachment enigma2_crash_2016-04-25_17-46-08.logView attachment Enigma2-2016-04-25_17-29-41.logView attachment Enigma2-2016-04-25_17-46-27.log

 

[Huevos]

#1 realdannys: "This [failing] has happened for me on multiple versions of 3.2, 4.0 and now 4.1."

#26 twol: "although the last 6 months I know I have used it during Wetek testing and don't remember issues"

All pretty vague, which is why I am asking.

 

[twol]

All pretty vague, which is why I am asking.

You are correct - will try an older oe-a 3.2 image and see what happens.... tomorrow

 

[abu baniaz]

Host: LX3
Client: TM 3T Combo
Image on client: ApolloDev 147
Recording to: HDD on TM 3TC
Nothing installed apart from RCSC.

Timeshift started manually. Got spinner as soon as I started TS. This is the oldest image I can find for my test receiver.

 

[Huevos]

Surely if this happened on all boxes lots of people would have noticed by now though - I would have thought a lot of people with the VU+ Zero are using it as a tuner-less second box in bedrooms etc?

Its beginning to look more and more likely that this was broken at some point during development and no one noticed I guess.

Does this mean we wont even be able to pause from now on though?

Not a fault introduced during OpenViX development. It is faulty drivers. As this is out of our hands you are going to have to live with it, or take it up with the manufacturer.