[Zgemma H7] [ZGemma H7S] Play a paused timeshift not working most of the time

[ccs]

Can someone point me in the right direction on how to find out whether there is a bug report for this please.

It's a known issue, the cause is now understood and a fix is being looked into.

 

[smipx]

Just for my info. Where can we see a list of all the outstanding issues/bugs and their status?

Thanks
Paul

 

[ccs]

Just for my info. Where can we see a list of all the outstanding issues/bugs and their status?

Thanks
Paul

I don't think there is one, I've certainly not seen one.

Try

https://www.world-of-satellite.com/showthread.php?63359-OpenVix-5-4-Change-log
http://www.openvix.co.uk/feeds/openvix/release/5.4/e2-git.log
http://www.openvix.co.uk/feeds/openvix/release/5.4/oe-git.log

 

[smipx]

Thanks CSS.

It's a shame (from my point of view) that there is not a nice list of reported "bugs" that are being worked on / been acknowleged.
I have come across a few bugs but I don't currently have the time to gather logs and create a post each time (if I am not sure its not already been reported and/or acknowleged).

e.g. one bug I found yesterday was when inside the list of recordings I wanted to change the action of the yellow button to "select" so I could select a bunch of recordings. I made the change in the menu and then next time I went into the movie list the box crashed and kept crashing. No way to remove the "not working assignment" other than to go into the config file, find the offending line and remove the setting. I did this - rebooted and it was fine again. It would take me hours to log that as a problem, try to gather the logs and submit them and then, after all of that effort get someone telling me "it's a known issue and is in the fix list". I just don't have the time but - on the other hand I do want to try and help iron out the bugs.

Another issue was that I was using the MovieOrganizer plugin previously (and it worked very well) but when I installed 5.4.014 I decided to avoid any 3rd party plugins that were not tested and maintained in the Downloads section and instead try to use the built-in "Enable Automatic Collections". Now at the moment I have the list of movies sorted (done by MovieOrganizer) into folders at the top (by the date the folder was created I think) and then individual recordings at the bottom by date (newest at the top of the list of individual files). When I tried to use "collections" the "virtual folders" were interspersed with the individual files and there seemed to be no sort option to make all of the "virtual folders" appear at the top and then individual files by date ascending under them. I just gave up and installed MovieOrganizer manually from an IPK and got back to what I am used to.

 

[ccs]

... changing the yellow button to "toggle mark" in movielist crashes 5.4.014 (didn't take long)......

12:31:09.7532 [eRCDeviceInputDev] emit: 0
12:31:09.7601 [InfoBarGenerics] Key: 399 (Break) KeyID='KEY_GREEN' Binding='('GREEN',)'.
12:31:09.7741 [Trashcan] Debug path /media/hdd/movie/ => /media/hdd/movie/.Trash
12:31:10.0006 Traceback (most recent call last):
12:31:10.0008   File "/usr/lib/enigma2/python/Components/MovieList.py", line 312, in selectionChanged
12:31:10.0012   File "/usr/lib/enigma2/python/Screens/MovieSelection.py", line 1063, in updateButtons
12:31:10.0018 TypeError: can_mark() takes exactly 1 argument (2 given)
12:31:10.0019 [ePyObject] (CallObject(<bound method MovieList.selectionChanged of <Components.MovieList.MovieList object at 0x71aac7d0>>,()) failed)5.4.014

 

[smipx]

not if you know what you're doing and do it often. For me it's a mission each time I have to get debug logs etc. Bit of a noob on that

 

[Tkr001]

not if you know what you're doing and do it often. For me it's a mission each time I have to get debug logs etc. Bit of a noob on that

Problem is that this software is maintained by unpaid volunteers. If we all decided it took too long to document and submit a bug report potentially nothing would ever get fixed. Easy way is to create a post and ask if it is a known problem. If it isn't then you should take the time to submit logs and any other diagnostic information. We get the software free so we should all try to help out where we can.

 

[smipx]

Problem is that this software is maintained by unpaid volunteers. If we all decided it took too long to document and submit a bug report potentially nothing would ever get fixed. Easy way is to create a post and ask if it is a known problem. If it isn't then you should take the time to submit logs and any other diagnostic information. We get the software free so we should all try to help out where we can.

Hi Tkr001,

I hadn't appreciated or understood that fact so I unreservedly apologise to all the volunteers who work so hard to make OpenVIX.

I will do as you suggest. The idea of a list of already "being worked on" or "acknowleged" bugs/behaviours in a format/place that the "less technical" of us can look at (and have ahope of understanding) is still a good idea though. In some ways it might take the pressure off the hard working volunteers (rather than create more work) and avoid what must be annoying posts about things that are already known about. Sometimes a bug can take many forms and one symptom may not be immediately obvious by trawling through previous posts so it would help on that side too.

Just an idea.

Apologies again,

Paul

 

[Mick Seymour]

As the OP, I'm very happy that the problem is being looked at and fully understand the devs are volunteers and passionate about what they do. I love my ZGemma with OpenVIX.

 

[Huevos]

... changing the yellow button to "toggle mark" in movielist crashes 5.4.014 (didn't take long)......

12:31:09.7532 [eRCDeviceInputDev] emit: 0
12:31:09.7601 [InfoBarGenerics] Key: 399 (Break) KeyID='KEY_GREEN' Binding='('GREEN',)'.
12:31:09.7741 [Trashcan] Debug path /media/hdd/movie/ => /media/hdd/movie/.Trash
12:31:10.0006 Traceback (most recent call last):
12:31:10.0008   File "/usr/lib/enigma2/python/Components/MovieList.py", line 312, in selectionChanged
12:31:10.0012   File "/usr/lib/enigma2/python/Screens/MovieSelection.py", line 1063, in updateButtons
12:31:10.0018 TypeError: can_mark() takes exactly 1 argument (2 given)
12:31:10.0019 [ePyObject] (CallObject(<bound method MovieList.selectionChanged of <Components.MovieList.MovieList object at 0x71aac7d0>>,()) failed)5.4.014

Have a go with this:
https://github.com/OpenViX/enigma2/commit/5f380b06109431ce9e34e41d8ccf4faf9043f5ba

 

[ccs]

Have a go with this:
https://github.com/OpenViX/enigma2/commit/5f380b06109431ce9e34e41d8ccf4faf9043f5ba

.. yes, "toggle mark" now working as expected in 5.4.014.

Py3 will have to wait until tomorrow.

 

[ccs]

.... Py3 fine. :thumbsup:

 

[smipx]

Many thanks (toggle mark issue) and apologies for not doing the "right thing" and for hijacking this post to the OP.
Off to find a flagellation whip for myself.

 

[Huevos]

@CCS, is this problem related to the missing channel numbers issue?

 

[ccs]

@CCS, is this problem related to the missing channel numbers issue?

No, it's current status is here (timeshift is affected as well).....

https://www.world-of-satellite.com/...ng-a-recording&p=517317&viewfull=1#post517317

 

[Mick Seymour]

This looks like it was fixed in 5.4.016 or 5.4.015. Thanks devs :thumbsup:

 

[smipx]

I just wanted to update on the Timeshift "occasionally" freezes issue and you cannot press play.
I had this again yesterday - problem is that I don't know the exact steps prior. I was watching BBC1 and pressed pause. It paused okay but play (and OK) would not get it playing from the point of pausing. 19 times out of 20 the pause works just fine but just occasionally this still happens. The only option I had was to stop the timeshift. I chose "stop the timeshift and continue recording" (as I actually wanted to watch the program I paused. I then left the program and went into recordings. I could see two recordings of the program. the 1st one (which was a "completed" recording was about 2 minutes long and was the section of program between pressing pause and ending the pause with the "stop the timeshift and continue recording" The second recording was the continuation of the recording. Both were perfectly watch-able.

I'm on 5.4.016 (2021-10-09)

Thanks
Paul