Rob van der Does
ViX Beta Tester
Nope, it's not. They have always done that. the so called 'nightly's.
ViX doesn't do that: we only build a new image when we have made changes; so that's fard from daily.
Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...
[VU+ Duo2] hades dead?
- Thread starter 2stein
- Start date
ViX doesn't do that: we only build a new image when we have made changes; so that's fard from daily.
abu baniaz
Moderator
Also worth pointing out that some changes are by other team members.
casuk
New member
- Joined
- May 7, 2013
- Messages
- 280
- Reaction score
- 0
- Points
- 0
- Age
- 47
Well thats my next question why so many changes does it not make sense to future proof all images so there is no need for changes or updates, i dont mind the updates its the reflashing of images mostly just for the feeds to work that bothers me and i dont think im alone here, im not putting the boot in im glad of the the work thats put into these images im just wondering why so many changes
Well I guess I had my 1st box somewhat before you, and OpenPli have been doing daily updates. openXta also do daily updates.
Relatively speaking, OpenVix is relatively stable, producing updates due to fixes in the Vix Enigma2 code (not daily!) and from what I see (as I build from the Vix Git) they batch the OE-alliiance updates (which are often daily or even multiple changes in a day) .... So not daily updates.
The changes to a new Greek god, usually are when the OE-Alliance branch changes from say 3.0 (Hades) to 3.2 (whatever).
... But you can stay exactly where you are with your installed image ... And not worry, alll the hard work is done for you by the OpenVix team!
Last edited:
Andy_Hazza
Moderator
A fresh re-flash takes 10 to 15 mins max to setup from scratch.
Sent from my iPhone using Tapatalk
Larry-G
V.I.P ,
- Joined
- May 19, 2010
- Messages
- 32,540
- Reaction score
- 405
- Points
- 0
- Age
- 48
When ViX only released updates every six months or so people bitched and moaned that they wanted access to updates, features and fixes as soon as they were released, now that they have such access people still bitch and moan. and people wonder why the likes of Andy black no longer work full time on enigma2. Just because you dont see changes to the GUI does not mean there are no new changes, not every single update needs to have a new skin or feature
Last edited by a moderator:
abu baniaz
Moderator
There are various reasons.
Changing OE-Core
Last two have been mainly GStreamer changes
Overhaul of how things are done and sometimes revert. An example is that Andy had coded for single feed. One plugin for all machines unless they are different. So insted of building lackags for all machines, you have one package shared for all machines (exception code is there). other team members did now wnat to do this/appreciate it. So had to be changed back.
The last server was running out of space before it died. This is why the feeds were deleted. There are a few machines that some beta testers have, no public image are relased for them, they were stopped for a while too.
We have even slowed down the frequency of "updates" or to be precise "builds". A bit ironic that some changes we make for the benfit of users are not in our image, but are in other team members images. For example, the changes to ABM will only com into effect when it is rebuilt. So if you are using Hades, that will never happen. But using any nightly build from other team members, will have them.
And sometimes it is to keep up with other team members. If they are building on branch 3.2, we would have to keep importing things down. The whole point of the OE-A as as E2 openplugins is that we share enhancements. Sometimes what works well for one, does not work for other team members.
It really is not hard to set your image how you want. We all have our personal preferances. For example, I prefer my recordings to be event name. If you set these up as a bare minimum, the "settings" file will contain just those values. You can then save this to your PC together with Cam config files which are also unique. The other common items are timer.xml and autotimer.xml. Flash new image, put enigma to sleep. Transfer the files/folders, restart and almost everything is back to how it was. You will still need to install plugins.
Changing OE-Core
Last two have been mainly GStreamer changes
Overhaul of how things are done and sometimes revert. An example is that Andy had coded for single feed. One plugin for all machines unless they are different. So insted of building lackags for all machines, you have one package shared for all machines (exception code is there). other team members did now wnat to do this/appreciate it. So had to be changed back.
The last server was running out of space before it died. This is why the feeds were deleted. There are a few machines that some beta testers have, no public image are relased for them, they were stopped for a while too.
We have even slowed down the frequency of "updates" or to be precise "builds". A bit ironic that some changes we make for the benfit of users are not in our image, but are in other team members images. For example, the changes to ABM will only com into effect when it is rebuilt. So if you are using Hades, that will never happen. But using any nightly build from other team members, will have them.
And sometimes it is to keep up with other team members. If they are building on branch 3.2, we would have to keep importing things down. The whole point of the OE-A as as E2 openplugins is that we share enhancements. Sometimes what works well for one, does not work for other team members.
It really is not hard to set your image how you want. We all have our personal preferances. For example, I prefer my recordings to be event name. If you set these up as a bare minimum, the "settings" file will contain just those values. You can then save this to your PC together with Cam config files which are also unique. The other common items are timer.xml and autotimer.xml. Flash new image, put enigma to sleep. Transfer the files/folders, restart and almost everything is back to how it was. You will still need to install plugins.
Larry-G
V.I.P ,
- Joined
- May 19, 2010
- Messages
- 32,540
- Reaction score
- 405
- Points
- 0
- Age
- 48
LMFAO seriously ?. For the first two years of ViX's life updates were released only as part of a new image and often took a good six months or so, This was true of all ViX 1.XX images as well as most if not all of the 2.xx image series. If you dont believe me look back through the forum for users moaning that they wanted more frequent updates. It was only with ViX 3.0 that we introduced the system we now use where updates could be pushed via the feeds without the need for a complete new image.
If you want to have a moan go on but please get your facts straite first, so as not to look like a complete dick.
Larry-G
V.I.P ,
- Joined
- May 19, 2010
- Messages
- 32,540
- Reaction score
- 405
- Points
- 0
- Age
- 48
That is EXACTLY what we did for the first two years of the images life and you know what ?, morons like you still bitched and moaned about how and when updates were released, so it seems we cant win no matter how we present updates to users.
DaMacFunkin
Forum Supporter
- Joined
- Sep 17, 2013
- Messages
- 2,704
- Reaction score
- 2
- Points
- 0
- Age
- 54
You only need to fresh flash usually when there are changes to the OE core, when other groups change their core you will need to do this, the other reason for a fresh flash is usually because a manufacturer releases a new kernel, vix supports so many models with bug fixes almost always being needed for a model, black hole only supports VU+ receivers so hardly ever needs updating, it's swings and roundabouts, the plus side to supporting more manufacturers and models is you get more of a scene with more people involved and contributing... That is why vix has the best features...
Larry-G
V.I.P ,
- Joined
- May 19, 2010
- Messages
- 32,540
- Reaction score
- 405
- Points
- 0
- Age
- 48
The get your facts strait before you gob off, every thing you have complained about here was already in operation for two years before ViX 3.0 and people still moaned about how they received access to updates.
Guys tone it down please.
Rob van der Does
ViX Beta Tester
That will depends very much on your setup.
Making all the settings from scratch takes me at least 15 mins, and I do it almost blindfolded. Luckily settings can virtually always be used from previous images and even from other boxes.
Installing all plugins takes another 15 minutes.
So a fresh setup takes me roughly 30 minutes.
Andy_Hazza
Moderator
Yeah I agree Rob. [emoji4]
Sent from my iPhone using Tapatalk
Sent from my iPhone using Tapatalk
When i did a fresh re-flash from Apollo to Hades i had no problem setting everything back up plugins etc.
But one thing did bug me is i had to re-scan all my satellites back in (Im on a motorised setup) My vbox saved the positions thank god, but can i get away next time without having to re-scan to find all available channels?
But one thing did bug me is i had to re-scan all my satellites back in (Im on a motorised setup) My vbox saved the positions thank god, but can i get away next time without having to re-scan to find all available channels?
abu baniaz
Moderator
You can always save your channel datat before flashing and then restoring it afterwards.
Use Webif interface or programs such as echannlizer/dremaboxedit/dreamset
Use Webif interface or programs such as echannlizer/dremaboxedit/dreamset
Here is my personal view....
When updates aren't done for ages then users moan and when they are done regularly users moan then!
Now from my point of view, the way things are now are a happy medium. If one doesn't want to keep updating can simply choose not to (ie set updates notification to no) and those that don't mind updating can do so.
Vix maintains a changelog which has basic details of what changes/fixes have been done between builds. I'm not aware of OpenATV/PLi, having such information. Using this, I then choose whether to update my box or not (ie does it really effect me).
I agree with @Abu as well, I have a backup of my timers.xml, autotimers.xml and settings file. All of which are stored in, "/etc/enigma2". So just do a channel scan/epg and any plugins. I only use 28.2 so it's easy for me to do this.
I realise it wouldn't be this easy when using motorised setup but @Abu suggestion could help there.
When updates aren't done for ages then users moan and when they are done regularly users moan then!
Now from my point of view, the way things are now are a happy medium. If one doesn't want to keep updating can simply choose not to (ie set updates notification to no) and those that don't mind updating can do so.
Vix maintains a changelog which has basic details of what changes/fixes have been done between builds. I'm not aware of OpenATV/PLi, having such information. Using this, I then choose whether to update my box or not (ie does it really effect me).
I agree with @Abu as well, I have a backup of my timers.xml, autotimers.xml and settings file. All of which are stored in, "/etc/enigma2". So just do a channel scan/epg and any plugins. I only use 28.2 so it's easy for me to do this.
I realise it wouldn't be this easy when using motorised setup but @Abu suggestion could help there.
