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

[realdannys]

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

Sorry Huevos, i've been really busy, but i'll take a look at this. Im going to have to download archive images to figure out when it worked. But I can 100% say it did, up till about November time. I used to be able to use full timeshift either on the USB or on a mounted NFS share with network streaming - the Zero has never had a turner connected to it.

But i'll have to look at the archives and see roughly what was out around early November. If you could give an indication what numbers were released around then i'll download them and test.

 

[realdannys]

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.

If you mean recording a program you're watching via a stream to either USB or an NFS share - it doesn't work. Ive tried it - it creates the name on the NFS shared box when you you try and play the recording back it fails.

In vague relation to this, the RemoteRecord plugin has been broken since at least 2011, you enter your boxes IP and set it so your client box would trigger and record on your server box and not itself and it triggers the timer event, but its missing vital information (there is a thread here which discusses this already and I forget whats missing but I think its the device path) so the remote record just falls as well. It was a identified then but no one has updated the plugin so I assume its a dead project the original dev no longer touches.

 

[realdannys]

Secondly, the segmentation fault is usually driver related.

That being said at least something has been discovered here - though it may be as someone alluded to a driver issue

Seems unlikely, given that rewinding is done in software.

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.

So which is it Huevos because in this thread alone its been a driver fault, then dismissed as a driver fault and now a driver fault again. Is Timeshift a driver issue or not?? Also play/pause at least works now regardless of whats causing it, so it seems silly to go backwards and take that ability away.

 

[abu baniaz]

are you trying to suggest play/pause is not timeshift?

 

[Huevos]

So which is it Huevos because in this thread alone its been a driver fault, then dismissed as a driver fault and now a driver fault again. Is Timeshift a driver issue or not?? Also play/pause at least works now regardless of whats causing it, so it seems silly to go backwards and take that ability away.

The problem is everyone in this thread is testing on different STBs and as it is a driver issue across several manufacturers we are getting inconsistent results.

My testing is on Solo2 as the client.
3.2.023 (2015-11-23) is faulty.
3.2.021 (2015-11-03) pauses and plays.
Extract drivers from 021 and insert into 023... and 023 pauses and plays fine.

 

[abu baniaz]

I hope people appreciate the work gone into tracking this issue. Huevos spent many hours testing images. This is to test a feature that he does not use. Nor any of the testers as far as I know.

 

[realdannys]

The problem is everyone in this thread is testing on different STBs and as it is a driver issue across several manufacturers we are getting inconsistent results.

My testing is on Solo2 as the client.
3.2.023 (2015-11-23) is faulty.
3.2.021 (2015-11-03) pauses and plays.
Extract drivers from 021 and insert into 023... and 023 pauses and plays fine.

Interesting because my results are the opposite. (well not the exact opposite but) pause and play has always worked on every image i've had (since I got the box) - its rewind and fast forward on timeshift that hasn't worked - although i'll need to test to pin down exactly when it did work for me in the past it DEFINITELY worked at some point. Now only play/pause works.

 

[joysleep1]

i was hoping timeshift can work using remotestream plug in but it seems like it struggles. My vu solo2 is in the extension room using feeds from my main xtrend receiver. The solo 2 has its own hardrive too. I hit pause on a remote stream channel. It pauses ok but then after a few seconds when you hit play it scrambles up and gets all fuzzy. It struggles to play smoothly. That is also with everything being connected by ethernet cable and my lan speeds are 72mb download and 18mb upload.
I guess i am asking too much for features like that. So it does not really concern me. Video playback files stored on remote hardrive plays fine with no problems tho.

 

[Huevos]

i was hoping timeshift can work using remotestream plug in but it seems like it struggles. My vu solo2 is in the extension room using feeds from my main xtrend receiver. The solo 2 has its own hardrive too. I hit pause on a remote stream channel. It pauses ok but then after a few seconds when you hit play it scrambles up and gets all fuzzy. It struggles to play smoothly. That is also with everything being connected by ethernet cable and my lan speeds are 72mb download and 18mb upload.
I guess i am asking too much for features like that. So it does not really concern me. Video playback files stored on remote hardrive plays fine with no problems tho.

That is Solo2 driver issue too. Got the same here over gigabit lan.

 

[joysleep1]

That is Solo2 driver issue too. Got the same here over gigabit lan.

but i do not think it is the vu solo2 fault. I just think that would happen with any box. It just seems like there is not enough bandwidth or power or whatever to have this feature working smoothly.
I will try it with my edison box in the living room tomorrow but it will definitely struggle on that too.

 

[Huevos]

Nothing to do with your flaky lan. The box was streaming fine. It just falls over when you press pause.

The more boxes that are tested the more varied the results will appear due to each and every box using different drivers.

 

[joysleep1]

Yh it streams fine. But i think it is asking too much for timeshift to work on a remote stream. I have tried this with the hardrive not used as a replacement and hardrive used as a replacement.

 

[realdannys]

but i do not think it is the vu solo2 fault. I just think that would happen with any box. It just seems like there is not enough bandwidth or power or whatever to have this feature working smoothly.

Its nothing to do with bandwidth at all - gigabit LAN far outweights anything that comes down your Sat Dish, HD streams are 2MB/s, Gigabit Lan can easily handle in the real world about 75MB/s. Hence why streaming recording (and skipping through them minutes at a time with the number buttons) works perfectly over LAN.

@Huevos - I plan to grab a few Oct/Nov 3.2 images for the Zero tonight after the LFC game and see if I can recreate the timeshift again. If I do, i'll be sure to export as much useful data as I can for you and others - debug logs, (video evidence if I get it working again?) but maybe I just wont! Lets see.

 

[abu baniaz]

@Huevos - I plan to grab a few Oct/Nov 3.2 images for the Zero tonight after the LFC game and see if I can recreate the timeshift again. If I do, i'll be sure to export as much useful data as I can for you and others - debug logs, (video evidence if I get it working again?) but maybe I just wont! Lets see.

Charming !

 

[bbbuk]

@realdannys, can I make a suggestion?

As you know @Huevos looked into this (spent a lot of time) and has said it's a driver issue therefore can I suggest you try this yourself if you don't think its true and then you would know whether it is/isnt a driver issue.

Looking at VU+ website, new drivers were released around 17/11/15 and therefore 023 will have contained these drivers but the 021 contained drivers from 23/06/15 (no other drivers were released between these dates).

Therefore, if you flashed with Vix 3.2 021 and extracted drivers from it and then flashed back to the current up-to-date image you're using then replaced drivers in this current image with that from vix 3.2 021.

The drivers can be found in "/lib/modules/3.13.5/extra".

Can I suggest you that put box to sleep (telnet/putty command "init 4") after you have flashed back to current image and before replacing these new drivers with the older ones.

Once done, wake box back up with telnet/putty command "init 6".

 

[realdannys]

Charming !

Think you misread Abu, I meant "maybe I just wont" as in be able to get in working again like it was before...not "maybe I just won't bother".

Not sure why you appear to be looking to cause trouble with your last 3-4 arsey replies considering everyone is conversing like adults and actually you know, trying to solve bugs that need fixing in an image...i'm not particularly bothered about this feature anymore either, but when you release software, open source or not, you want to fix things if you can.