Testers required for OpenViX Python 3 images

[carpcat]

Apologies, they changed the variable name in one of the calls (they are using 2 that are basically the same thing)

That’s fixed the issue. Much appreciated :thumbsup:

 

[twol]

No it wasn't paused as I couldn't do anything when it booted it played for a few seconds then crashed. I don't think the stream is the issue as your second py file is fine on vskin 1080 (KiddaC uses his own custom components though) It only crashes on vix skin. I might not get chance to test any further till later or tomorrow.

I was looking at this...640> 11:57:53.9146 [eServiceMP3] state transition READY -> PAUSED which why (I think ) Navigation came in. Anyway if its a stream I don't think it should be going through this code.

Thanks for your help.

 

[twol]

deleted............................

 

[dsayers]

Apologies, they changed the variable name in one of the calls (they are using 2 that are basically the same thing)

Ive just tested this and that seems to fix it for me as well even on a stream or Satellite channels

 

[Huevos]

Can you please try with this version:

 

[dsayers]

Can you please try with this version:

That seems ok here

 

[carpcat]

Can you please try with this version:

Good here too :thumbsup:

 

[birdman]

Something is seriously screwed up with restoring backed up settings that include timers.
Power timers get doubled up!
Finished recording timers get doubled up!
I don't really understand how something this barmy can possibly be happening.
What can go this wrong with just restoring the saved files from the backup and rebooting?

I had duplicated power timers recently. The most obvious result was having to cancel two queries if I didn't want to put the box into standby.

And I did have to do a restore several weeks ago after failing to flash an image.

Perhaps it's related to timers being kept in memory and then finding they are out of sync with the on-file data?

 

[Huevos]

So you obviously didn't do a full factory reset before restoring. How can a restore work properly if the current image has some settings already loaded?

 

[birdman]

So you obviously didn't do a full factory reset before restoring. How can a restore work properly if the current image has some settings already loaded?

The only time I do a restore is if I have just flashed a "standard" downloaded image.
Any other flash (of my own backup) wouldn't need a restore.

Still ended up with duplicated Power Timers recently, and I did have to do a flash+restore after something (I forget what) went wrong with one dev release.

 

[BrokenUnusableAccount]

So you obviously didn't do a full factory reset before restoring. How can a restore work properly if the current image has some settings already loaded?

Good grief.
Are you seriously saying it's reasonable to include a restore function but require a factory erase before using it?
The is them most ludicrous thing you have ever said.

 

[ccs]

A factory reset gets rid of all your settings so you can (successfully) restore them again from a backup.

 

[Joe_90]

The issue may be that settings restore is appending to existing settings, rather than replacing them. It would be reasonable to expect a "settings restore" function to replace existing. There may be some settings where appending data is more reasonable, but I can't think of any at the moment

 

[ccs]

Current timers are not lost if you restore settings from a week or 2 ago, you may get some finished timers duplicated, which is no big deal.

Power timers have always been a problem.

Deleting them when enigma2 is stopped is another way of restoring them without duplicates, but you then run the risk of losing power timers which weren't in the backup.

 

[BrokenUnusableAccount]

Current timers are not lost if you restore settings from a week or 2 ago

Possibly nice in some cases but useless if the Restore function is called Restore because nobody would know that's what's going to happen.
When I restore from more than a few hours ago I have always run Autotimers and checked any recurring normal timers are still present because I would never in a hundred years have guessed that the Restore function might actually be a Merge some settings in a weird way while restoring others function.

you may get some finished timers duplicated, which is no big deal.

I guess it should ultimately be harmless.
But when I'm testing, like this thread has called for, I'm sometimes restoring settings many times in just one day because I'm trying to excercise lots of weird and wonderful parts of OpenViX that I don't always 100% know how to use to see if I can make it crash.

Power timers have always been a problem.
Deleting them when enigma2 is stopped is another way of restoring them without duplicates, but you then run the risk of losing power timers which weren't in the backup.

 

[ccs]

..... do what I do, take an image backup before you start messing about, and restore it when you've finished, then there's no need to worry about restoring settings.

 

[BrokenUnusableAccount]

..... do what I do, take an image backup before you start messing about, and restore it when you've finished, then there's no need to worry about restoring settings.

An image backup takes over 10 minutes and I don't want to wear out the flash memory in my box every time I restore.

 

[ccs]

An image backup takes over 10 minutes and I don't want to wear out the flash memory in my box every time I restore.

You're stuck then, unless you use the workarounds already mentioned.

 

[BrokenUnusableAccount]

If I really must I will try and remember to go to 'Reset to factory settings' when I want to restore my settings.
Just seems dumb that I'm required to do that.
I'm already telling my friends I wouldn't really recommend OpenViX to non technical types.
Now I have to tell them that even if you're good with tech you have to watch out for things that just are not what they're labelled as.

Any idea why someone has closed my thread here: https://www.world-of-satellite.com/showthread.php?64470-FAV-screen-sorting-broken

Huevos did ask for version number etc. but I didn't answer because I assumed he'd soon realise how dumb he was to ask that in a section of the forum where I am required to fill that in before posting, which I had done.

 

[twol]

An image backup takes over 10 minutes and I don't want to wear out the flash memory in my box every time I restore.

" I don't want to wear out the flash memory in my box every time I restore" - no chance. I always flash a new image and have done on every box without issues and I build and flash the boxes regularly(sometimes several times a day, especially where C++ code is involved)