Seite 3 von 4 ErsteErste 1234 LetzteLetzte
Ergebnis 21 bis 30 von 34
  1. #21

    Registriert seit
    12.05.2015
    Beiträge
    118
    Thanks (gegeben)
    317
    Thanks (bekommen)
    31
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    More or less, Someone will have to buy the box and try it. I do think the HD51 is capable of APSK.

    •   Alt Advertising

       

  2. #22
    Mitglied
    Registriert seit
    28.07.2013
    Beiträge
    66
    Thanks (gegeben)
    3
    Thanks (bekommen)
    13
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Hello EB
    Do you know if this receiver Vu+ Uno 4K SE, UHD PVR, has the same capabilities as the Zero as far as the APSK functions, this one has more options.
    If it does I rather buy this one.
    They claim it has the S2X TUNERS.
    Regards.
    Chewie

  3. #23

    Registriert seit
    12.05.2015
    Beiträge
    118
    Thanks (gegeben)
    317
    Thanks (bekommen)
    31
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Vu+ Uno 4K SE I think has FBC tuner. That is not what we want.

    Try to wait a little bit and see what happens. The HD51 is being talked about kindly. Would be a good idea maybe to see what happens with it.

  4. #24
    +++Dev-MediaPortal+++ Avatar von dhwz
    Registriert seit
    04.11.2013
    Beiträge
    2.604
    Thanks (gegeben)
    295
    Thanks (bekommen)
    1860
    Total Downloaded
    19,26 MB
    Total Downloaded
    19,26 MB
    ReceiverDankeAktivitäten
    @chewie
    You don't need these options as the DVB-S2X tuners do auto search all parameters, that means you just select DVB-S2 and do scan the specific transponders. As DVB-S2X is not a new system itself but an extension of DVB-S2. Also LinuxAPI doesn't even know DVB-S2X which means selecting these options on Vu+ is only a cosmetic feature.

    HD51, DM900, DM920, SF4008 etc. doesn't matter which box you choose because for all of these boxes are DVB-S2X tuners available.

  5. #25
    Senior Mitglied
    Registriert seit
    19.08.2015
    Beiträge
    190
    Thanks (gegeben)
    87
    Thanks (bekommen)
    34
    Total Downloaded
    5,78 MB
    Total Downloaded
    5,78 MB
    ReceiverDankeAktivitäten
    Box 1:
    Octagon SF8008 4K
     
     
    Box 2:
    Azbox Me
     
     
    Box 3:
    Azbox MiniMe
     
     
    Zitat Zitat von 123sat Beitrag anzeigen
    I will make one video for you! Wait a few minutes


    The symbol rate just goes to 35000 in this box?

  6. #26
    Senior Mitglied
    Registriert seit
    13.02.2015
    Beiträge
    380
    Thanks (gegeben)
    87
    Thanks (bekommen)
    39
    Total Downloaded
    13,50 MB
    Total Downloaded
    13,50 MB
    ReceiverDankeAktivitäten
    Box 1:
    VU+ Duo 4K SE
     
     
    Box 2:
    VU+ Uno 4K SE
     
     
    Box 3:
    VU+ Zero 4K
     
     
    Box 4:
    Octagon SF4008
     
     
    Zitat Zitat von vladim Beitrag anzeigen
    The symbol rate just goes to 35000 in this box?
    No, it goes up to 45000.
    5° W 1,9° O / 9° 13° 19,2° O / 42° O
    Rotor 57° O bis 45° W
    123sat.de

  7. Thanks vladim, el bandido bedankten sich
  8. #27

    Registriert seit
    12.05.2015
    Beiträge
    118
    Thanks (gegeben)
    317
    Thanks (bekommen)
    31
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    DVB-S2X has a different set of fec parameters. Logging a DVB-S2X transponder will crash enigma2 unless the blindscan plugin is modified. My Vu+ Zero 4K is doing a great job in blindscan, but it is extremely slow as compared to closed source receivers. Here is a snippet of the Zero 4K blindscan log with 16APSK DVB-S2x transponder:

    [Blind scan] cnt : 8 , data : ['OK', 'HORIZONTAL', '10730549', '0', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_OFF', 'ROLLOFF_35']
    [Blind scan] cnt : 8 , data : ['OK', 'HORIZONTAL', '10803097', '0', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_OFF', 'ROLLOFF_35']
    [Blind scan] cnt : 8 , data : ['OK', 'HORIZONTAL', '10808471', '0', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_OFF', 'ROLLOFF_35']
    [Blind scan] cnt : 8 , data : ['OK', 'HORIZONTAL', '10843992', '0', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_OFF', 'ROLLOFF_35']
    [Blind scan] cnt : 8 , data : ['OK', 'HORIZONTAL', '10861162', '0', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_OFF', 'ROLLOFF_35']
    [Blind scan] cnt : 8 , data : ['OK', 'HORIZONTAL', '10866078', '0', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_OFF', 'ROLLOFF_35']
    [Blind scan] cnt : 8 , data : ['OK', 'HORIZONTAL', '10872697', '0', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_OFF', 'ROLLOFF_35']
    [Blind scan] cnt : 10 , data : ['OK', 'HORIZONTAL', '10907300', '20001000', 'DVB-S2X', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_7_9', '16APSK', 'ROLLOFF_35']
    [Blind scan] cnt : 14 , data : ['OK', 'HORIZONTAL', '10977423', '34001000', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_2_3', '8PSK', 'ROLLOFF_35', '3', '1', '3', '2']
    [Blind scan] cnt : 10 , data : ['OK', 'HORIZONTAL', '11012616', '18400000', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_2_3', '8PSK', 'ROLLOFF_35']
    [Blind scan] cnt : 10 , data : ['OK', 'HORIZONTAL', '11058622', '6150000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_7_8', 'QPSK', 'ROLLOFF_35']
    [Blind scan] cnt : 10 , data : ['OK', 'HORIZONTAL', '11067666', '4710000', 'DVB-S', 'INVERSION_AUTO', 'PILOT_OFF', 'FEC_3_4', 'QPSK', 'ROLLOFF_35']
    [Blind scan] cnt : 8 , data : ['OK', 'HORIZONTAL', '11099255', '0', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_OFF', 'ROLLOFF_35']
    [Blind scan] cnt : 8 , data : ['OK', 'HORIZONTAL', '11139428', '0', 'DVB-S2', 'INVERSION_AUTO', 'PILOT_OFF', 'ROLLOFF_35']
    [Blind scan] cnt : 0 , data : []
    [Blind scan] data : [2728][1][4164798][4750000][1][2][0][2][2][2]
    [Blind scan] data : [2728][1][4136486][29126000][1][2][0][4][2][2]
    [Blind scan] data : [2728][1][4099786][34001000][1][2][0][0][4][4]
    [Blind scan] data : [2728][1][4067673][34001000][1][2][0][4][4][4]
    [Blind scan] data : [2728][0][3992700][20001000][1][2][0][0][4][4]
    [Blind scan] data : [2728][0][3922577][34001000][1][2][0][2][2][2]
    [Blind scan] data : [2728][0][3887384][18400000][1][2][0][2][2][2]
    [Blind scan] data : [2728][0][3841378][6150000][0][2][0][5][1][1]
    [Blind scan] data : [2728][0][3832334][4710000][0][2][0][3][1][1]
    ----------Finish_Time = Friday, 13 of April 2018, 00:12:28
    The DVB-S2X transponder here returned a 'FEC_7_9', which will crash the system because enigma2 has no idea what 'FEC_7_9' is. As a work-around, I added all of the DVB-S2x FEC's to the blindscan plugin and set them to log as "FEC_Auto". Hopefully DVB-S2x parameters can be added to enigma2. Vu+ has added the DVB-S2X parameters in their image, but their ancient blindscan plugin has no option for c band.

    Mutant HD51, Octagon SF4008? Where is the blindscan for these receivers?

    It looks like DVB-S2X transponders are being used in North America. But the only way to find them is with blindscan. They are not listed in Lyngsat or any other website.

  9. Thanks fen bedankten sich
  10. #28
    +++Dev-MediaPortal+++ Avatar von dhwz
    Registriert seit
    04.11.2013
    Beiträge
    2.604
    Thanks (gegeben)
    295
    Thanks (bekommen)
    1860
    Total Downloaded
    19,26 MB
    Total Downloaded
    19,26 MB
    ReceiverDankeAktivitäten
    Too bad that Vu+ something patched into the kernel what officially does not exist, the LinuxAPI knows no DVB-S2X and therefore also not all the new FEC parameters.
    But that's botch and not a standard. If LinuxTV fixes something else in the future, then Vu+ may have incompatible channel lists, they should have just waited for LinuxTV to implement something officially in the kernel. Apparently, no one at Vu+ has a clue what they are doing and thought they would have to add something so they can use DVB-S2X, but thats nonsense because DVB-S2X runs without any changes with the current DVB-S2 code, as DVB-S2X is NOT a separate standard, but a supplement to DVB-S2.

    Zu dumm, dass Vu+ irgendwas in den Kernel rein gepatcht hat was es offiziell gar nicht gibt, die LinuxAPI kennt kein DVB-S2X und somit auch nicht die ganzen FEC Parameter, schön dass das bei Vu+ jetzt funktioniert.
    Aber das ist Pfusch und kein Standard. Legt LinuxTV jetzt etwas anderes zukünftig fest, dann hat Vu+ inkompatible Kanallisten, sie hätten einfach warten sollen bis LinuxTV etwas offiziell in den Kernel einbaut. Scheinbar hat aber keiner bei Vu+ eine Ahnung was sie da tun und dachten sie müssten das reinbasteln damit sie DVB-S2X nutzen können, was aber Unsinn ist denn DVB-S2X läuft ohne jegliche Änderungen mit dem aktuellen DVB-S2 Code, denn DVB-S2X ist KEIN eigener Standard, sonder eine Ergänzung zu DVB-S2.

  11. Thanks traceRx bedankten sich
  12. #29
    Avatar von Captain
    Registriert seit
    03.04.2013
    Beiträge
    13.383
    Thanks (gegeben)
    708
    Thanks (bekommen)
    18793
    Total Downloaded
    162,35 MB
    Total Downloaded
    162,35 MB
    ReceiverDankeAktivitäten
    vu say a 16APSK was dvb-s2x , but the infos was wrong, and possible the blindscan plugin send wrong infos you dont know have the tp "'FEC_7_9" or get the blindscan tool only wrong data

    have you compare the scan with other brand non e2 box get you the same infos ?


    openATV we are open Source

    Boykott GPL violator

  13. #30

    Registriert seit
    12.05.2015
    Beiträge
    118
    Thanks (gegeben)
    317
    Thanks (bekommen)
    31
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    I think the blindscan information from the Zero 4K is correct. I have logged 3 different DVB-S2X transponders at 87 West c band over a several week time. All 3 of these transponders have been 16 APSK, but have different DVB-S2X FEC's. My Edision OS Mini has not been able to find these DVB-S2X transponders or read a signal on them. My OS Mini is dual tuner, 16/32 APSK. Vu+ Zero 4K logs many other 16 APSK transponders on other satellites as DVB-S2. Some of these APSK transponders have channels and the Zero 4K plays them correctly.

    Two DVB-S2X transponders for Europe are listed here:
    Code:
    http://en.satexpat.com/dvb-s2x/
    Enigma2 receivers will crash if these DVB-S2X transponders are found in a blindscan because of the FEC. We know the DVB-S2X receivers can view these transponders if they are entered manually. But they will fail in a blindscan!

    I do not see Vu+ doing anything except adding what is needed to make DVB-S2X function correctly in their receiver as DVB-S2X. Similar additions were made to enigma2 for 16/32 APSK. There is just a lot more to add for DVB-S2X.

    Here are the changes Vu+ made for DVB-S2X:
    Code:
    http://code.vuplus.com/gitweb/?p=vuplus_dvbapp;a=commitdiff;h=faaf85f037e9d29dd9f5178016caf7c80776d55b
    Vu+ probably added that DVB-S2X stuff to keep their receiver from crashing if a DVB-S2X transponder was found in a blindscan. So I can see why they did not wait for LinuxTV to add it.

    Would be nice to see Mutant HD51 or Octagon SF4008 add blindscan. We know the tuners support it, and I would have a different receiver to test DVB-S2X blindscan.


Seite 3 von 4 ErsteErste 1234 LetzteLetzte

Stichworte

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •  
Alle Zeitangaben in WEZ +1. Es ist jetzt 09:29 Uhr.
Powered by vBulletin® Version 4.2.5 (Deutsch)
Copyright ©2021 Adduco Digital e.K. und vBulletin Solutions, Inc. Alle Rechte vorbehalten.
Resources saved on this page: MySQL 5,88%
Parts of this site powered by vBulletin Mods & Addons from DragonByte Technologies Ltd. (Details)
vBulletin Skin By: PurevB.com