Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Page 2 of 2 FirstFirst 12
Results 16 to 27 of 27

Thread: OpenViX 5.4 - Mut@nt HD2400 plugins?

  1. #16
    Willo3092's Avatar
    Title
    ViX Beta Tester
    Join Date
    Oct 2016
    Location
    East Midlands
    Posts
    907
    Thanks
    686
    Thanked 352 Times in 263 Posts
    OpenATV 6.4 is end of life at the end of December and will no longer be maintained so looks like everyone will have to move over to python 3 eventually.
    Willo
    #######################
    GigaBlue UHD UE 4K
    Octagon SF8008 4K UHD
    Zgemma H9 Twin
    Xtrend ET8500
    AX HD61 4K UHD Twin (test box)
    Vu+ Uno4K
    GT-Sat GT-S3DCSS24 Unicable II LNB
    GT-Sat GT-dLNB1-DY Unicable II LNB
    #######################

  2. The Following User Says Thank You to Willo3092 For This Useful Post:

    cactikid (12-11-22)

  3. #17

    Title
    Junior Member
    Join Date
    Jul 2015
    Posts
    17
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by Huevos View Post
    2) If OpenATV want to maintain 2 versions that is up to them, but in our opinion that is just prolonging the pain and allowing the lazy plugin authors to pit one distro against another.

    4) Do you think it is fair that people demand us to maintain feeds that are years old at our own expense?
    I have downloaded the 6.0 on 03/05/2022 (the image content is 02/26/2022), then after testing it for cca. one week on 03/16/2022 I went back to the last 5.4 (the image content is 10/12/2021).
    That isn't really "years old", is it ?

    I did not "demand" anything. ViX displayed, that
    There has been an error, please try again later.
    If this issue persists, please check openvix.co.uk or world-of-satellite.com

    I asked a question. There is a question mark in the topic issue.

    If "people" do not like that if the support of a barely one year old distribution is ceased on day to the next (I suppose without any previos warning or temporary period), then it is a rather "unfriendly" step.
    And it is downright offensive to call as "lazy plugin authors" people, who create plugins for use and pleasure of other people (I assume for free!), just because they are not following immediately and absolutely the "Python policy".

    "...our own expense" vs "...we are forced by the python people to move everything to python 3"
    Everyone can decide, what the real reason is.

    P.s. There is still an OpenViX Archives link - which is empty of course.
    Will it exist sometimes again ?
    Last edited by malvin1; 11-11-22 at 11:12.

  4. #18
    twol's Avatar
    Title
    Moderator
    Join Date
    Apr 2012
    Posts
    7,733
    Thanks
    931
    Thanked 2,678 Times in 2,052 Posts
    Quote Originally Posted by malvin1 View Post
    I have downloaded the 6.0 on 03/05/2022 (the image content is 02/26/2022), then after testing it for cca. one week on 03/16/2022 I went back to the last 5.4 (the image content is 10/12/2021).
    That isn't really "years old", is it ?

    I did not "demand" anything. ViX displayed, that
    There has been an error, please try again later.
    If this issue persists, please check openvix.co.uk or world-of-satellite.com

    I asked a question. There is a question mark in the topic issue.

    If "people" do not like that if the support of a barely one year old distribution is ceased on day to the next (I suppose without any previos warning or temporary period), then it is a rather "unfriendly" step.
    And it is downright offensive to call as "lazy plugin authors" people, who create plugins for use and pleasure of other people (I assume for free!), just because they are not following immediately and absolutely the "Python policy".

    "...our own expense" vs "...we are forced by the python people to move everything to python 3"
    Everyone can decide, what the real reason is.

    P.s. There is still an OpenViX Archives link - which is empty of course.
    Will it exist sometimes again ?
    @malvin1 I have sent you a PM.......

    unlike some other images, we are not paid to do this and server costs limit what we can store, especially when the feeds created by the OE-A 5.1 image build are significantly bigger - like everything costs keep rising and software takes up more storage.
    The MP3player plugin that I am looking at uses some functionality that is already marked as depreciated by the python 3 bunch and at some stage will have to be replaced - this is nothing that we can control ....... that also applies to the core elements used to build the images, so not just python 3.
    Gigablue Quad 4K & UE 4K
    .........FBC Tuners:
    ------------------> DUR-Line DCR 5-1-8-L4 Multiswitch to 1.5M dish(28.2E)
    ------------------> Spaun SUS 5581/33 NFA Multiswitch to 80 cm dish(19.2E)
    .......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
    AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 using Legacy ports on multiswitches
    Zgemma H9 C/S into Giga4K

  5. #19
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    12,456
    Thanks
    1,942
    Thanked 4,402 Times in 2,905 Posts
    Quote Originally Posted by malvin1 View Post
    "...our own expense" vs "...we are forced by the python people to move everything to python 3"
    Everyone can decide, what the real reason is.

    P.s. There is still an OpenViX Archives link - which is empty of course.
    Will it exist sometimes again ?
    You are mixing things up.

    From January 1st 2020 Python 2 is dead. No bug fixes whatsoever. Nothing. Zilch.
    https://www.python.org/doc/sunset-python-2/

    Saving old feeds costs money. We were out of space and changes would cost money. No user or manufacturer pays anything towards our servers. Each machine's is around 2 GB, plus the image files themselves. We maintain more than 60 machines. So that is around 120 GB for each version. And feeds are currently maintained for 6.0, 6.1 and 6.2. Only 5.4 and older feeds were removed.
    Code:
    [root@ns3324542 ~]# df
    Filesystem      1K-blocks       Used Available Use% Mounted on
    /dev/root        20026236    2333960  16651944  13% /
    devtmpfs          4032384          0   4032384   0% /dev
    tmpfs             4032868          0   4032868   0% /dev/shm
    tmpfs             4032868     427532   3605336  11% /run
    tmpfs             4032868          0   4032868   0% /sys/fs/cgroup
    /dev/sda3      1902052484 1542032348 263378448  86% /var
    tmpfs              806576          0    806576   0% /run/user/0
    [root@ns3324542 ~]#
    And like I already said, if you want 5.4 feeds you can build and maintain them yourself. Nothing stopping you.

  6. #20

    Title
    Junior Member
    Join Date
    Jul 2015
    Posts
    17
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by Huevos View Post
    Saving old feeds costs money. We were out of space and changes would cost money.

    And like I already said, if you want 5.4 feeds you can build and maintain them yourself. Nothing stopping you.
    It is then 60*120 GB = 7.2TB regarding all "last Pithon2 5.4".
    I'm sorry that the ecclesia is poor.
    (I have here at home more than 10TB connected to the boxes, only for archiving recordings and torrent films)

    Concerning the several time mention "really practical" advice, that "you can build and maintain them yourself":
    I have not done such a thing, but I assume that:
    1. I needs a Linux - I have it
    2. It needs a development environment - I assume it is available somewhere. But not sure, it is exactly that Linux what I have (Ubuntu).

    But presuming I can "put it together".
    In ATV 6.0 I checked the plugin (it has a feed for this as well!) because of which I killed ViX 5.3:
    Package: enigma2-plugin-drivers-ntfs-3g
    Version: 1.0-r0
    Description: Allow writes to NTFS file systems Allow writes to NTFS file systems.
    Section: base
    Priority: optional
    Maintainer: OE-Core Developers <openembedded-core@lists.openembedded.org>
    License: GPLv2+
    Architecture: mips32el
    OE: enigma2-plugin-drivers-ntfs-3g
    Depends: ntfs-3g
    Source: None
    Filename: enigma2-plugin-drivers-ntfs-3g_1.0-r0_mips32el.ipk
    Size: 656
    MD5Sum: c1c5be269a9516899eec3566c8d2c2ce

    Source: None
    Then how should I "do it by yourself"?
    It can not be found the link suggested by you in the past (https://github.com/OpenViX/enigma2/t...v-old-20211224) either:
    We couldn’t find any code matching 'ntfs-3g'

  7. #21

    Title
    ViX Beta Tester
    Join Date
    Apr 2011
    Location
    Ireland
    Posts
    2,000
    Thanks
    401
    Thanked 650 Times in 531 Posts
    Build instructions are here https://github.com/OpenViX/enigma2/tree/Developer - you will just have to edit to use the correct branch

    Stop expecting others to spend money on server space just for you - you didn't pay anything for openvix
    Zgemma H7S running OpenVIX 6.2, Darkmotor, Triax TD110 dish, Inverto Black Ultra dual lnb
    LG 50UM7450 4K TV, Pioneer VSX-534 Atmos AVR , Panasonic UB820 region free 4K Bluray & a PS4.

  8. #22

    Title
    Junior Member
    Join Date
    Jul 2015
    Posts
    17
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by ronand View Post
    Stop expecting others to spend money on server space just for you - you didn't pay anything for openvix
    "just for me"
    Maybe you should read other forums as well, a lot of people mourn for Python2.

    "you didn't pay anything for openvix"
    There are a lot of things in the world you don't pay either, but somehow it "is worth" for those who give it "by free".

    ViX is a very nice system (thanks to the developer), but if support is such, one must consider, not only "not to pay for it", but do not use it anymore.
    There are a lot of other systems ....

  9. #23

    Title
    Junior Member
    Join Date
    Jul 2015
    Posts
    17
    Thanks
    0
    Thanked 0 Times in 0 Posts
    p.s.
    Dear ronand (VX Beta Tester)!
    Did you recognize, that BoxBrandingTest.py is missing from ViX 6.2.?
    That is the cause, why some Python3 plugin is not installing.
    It is a fortune, that they can be "copied" from ATV, and without any extra knowledge can made to Python3 (by including some brackets).
    After this everything is o.k.

    And just noticed!
    You are using ViX 5.4 as well: Zgemma H7S running OpenVIX 5.4
    Last edited by malvin1; 12-11-22 at 16:32.

  10. #24
    deltec's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Jan 2014
    Posts
    314
    Thanks
    228
    Thanked 9 Times in 8 Posts
    What is the man on about the vid image is excellent and it works great

  11. #25

    Title
    ViX Beta Tester
    Join Date
    Apr 2011
    Location
    Ireland
    Posts
    2,000
    Thanks
    401
    Thanked 650 Times in 531 Posts
    Quote Originally Posted by malvin1 View Post
    p.s.
    Dear ronand (VX Beta Tester)!
    Did you recognize, that BoxBrandingTest.py is missing from ViX 6.2.?
    That is the cause, why some Python3 plugin is not installing.
    It is a fortune, that they can be "copied" from ATV, and without any extra knowledge can made to Python3 (by including some brackets).
    After this everything is o.k.

    And just noticed!
    You are using ViX 5.4 as well: Zgemma H7S running OpenVIX 5.4
    Deary me. You might have noticed that this is an open source project - you are more than welcome to fix the bugs yourself. No amount of whining is going to get the dev team to build and maintain an old image and feeds for you.
    Zgemma H7S running OpenVIX 6.2, Darkmotor, Triax TD110 dish, Inverto Black Ultra dual lnb
    LG 50UM7450 4K TV, Pioneer VSX-534 Atmos AVR , Panasonic UB820 region free 4K Bluray & a PS4.

  12. #26
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    12,456
    Thanks
    1,942
    Thanked 4,402 Times in 2,905 Posts
    Quote Originally Posted by malvin1 View Post
    Did you recognize, that BoxBrandingTest.py is missing from ViX 6.2.?
    That is the cause, why some Python3 plugin is not installing.
    It is a fortune, that they can be "copied" from ATV, and without any extra knowledge can made to Python3 (by including some brackets).
    Blah blah, other image works better, blah, blah
    OpenViX has a box branding inspector built in.
    Menu > Information > Boxbranding

  13. The Following User Says Thank You to Huevos For This Useful Post:

    deltec (12-11-22)

  14. #27
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    12,456
    Thanks
    1,942
    Thanked 4,402 Times in 2,905 Posts
    Quote Originally Posted by malvin1 View Post
    "you didn't pay anything for openvix"
    There are a lot of things in the world you don't pay either, but somehow it "is worth" for those who give it "by free".
    If we charged you 1000 for it you would probably complain less.

    Quote Originally Posted by malvin1 View Post
    ViX is a very nice system (thanks to the developer), but if support is such, one must consider, not only "not to pay for it", but do not use it anymore.
    There are a lot of other systems ....
    If you are not happy with it you are welcome to move on.

    We improve things by moving forwards not backwards. If you have something constructive to add that involves moving forward we'll be happy to listen.

  15. The Following User Says Thank You to Huevos For This Useful Post:

    deltec (12-11-22)

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.