Multi-stream update @ 5 west

[dreambox1959]

We are talking about OSmio4K in the screenshots, SF8008 is a different receiver.

i know ! osmio4k is edision ! isnt it ?
i would like to know if your receiver can detect MIS and T2mi with his hardware or by software (satdreamgr )
does octagon sf8008 can have this feature or not .

BR

 

[moonraker 1]

How many satellites transmit multi streams

 

[william-1]

MIS Multistream Multi Input Stream by satellites E33C, E21B, E10A, E9B, Astra 4A, E5WA, E12WB, Hispasat

List of satellites and transponders broadcasting MIS technology.

en.satexpat.com

 

[william-1]

How many satellites transmit multi streams

Seven, see the link above.

 

[satesco]

MIS Multistream Multi Input Stream by satellites E33C, E21B, E10A, E9B, Astra 4A, E5WA, E12WB, Hispasat

List of satellites and transponders broadcasting MIS technology.

en.satexpat.com

The satexpat list with MIS frequencies at 5.0 W should be updated.Only four MIS transponders in the upper band.
12585 H,35500,2/3,8PSK-PLP 1,PLS 20-Diver

 

[moonraker 1]

thank you,is that why i cant tdf channels on 5w

 

[Laser]

5 West 12522V Stream 111 Mediaset 2. Anyone else notice the channels have disappeared from here? Or is it me??!!

 

[SimonE]

It may be you, Laser. They are all present and correct here. Maybe try a rescan to update your list??

 

[Laser]

Thanks Simon. Is Mediasat 20 still present?

 

[SatSearcher]

I get them on stream 222, not 111. Always chopping & changing on this transponder!

 

[SimonE]

Thanks Simon. Is Mediasat 20 still present?

Laser,
I've just re scanned 12522V and i get three "20 Mediaset" channels-all work without jumping.
SimonE

 

[Laser]

Thank you both very much. Changed to Stream 222 and all Ok now. Was on 111 before I'm sure!

 

[william-1]

France multi-stream has left 11509 H
New frequency 12732 V (Has been active since May 2021)
https://www.flysat.com/e5wab.php

 

[satesco]

I tried to scan transponders with Tvheadend at 5.0W that have symbol rates below 1000 Ks. I couldn't lock any of them even though I use a card that knows how to lock such a parameter under Windows?
Did anyone manage to lock low symbol rate with this application, or does she not have the ability to do this on Linux?
Thanks.

 

[deeptho]

I used to be able to get Alouette (11465.2H symbol rate 668) and Nostalgie (11458.4H, 514 kSamples/s )
but not anymore. I think it these services have moved.

Today I managed to lock 11457.6H at a symbol rate of 320 kS/s

This is with TBS6909X-version 1 and my neumodvb software. The spectrum scan does not
automatically detect it, and there is nothing useful on the transponder, but it locks easly.
It also seems to have physical layer scrambling. The peak at 11465 looks like an empty carrier
(or the driver refuses to lock)

This is on linux and after removing the limit of 1MS/s limit in the drivers (I think I replaced it with 100 instead)

One problem in locking such transponders is inaccurate local oscillators in LNBs. NeumoDVB learns
about such offsets and compensates for them, making tuning easier.

 

[deeptho]

Just found Nostalgie as well.
11454H 627 kS/s. Again not found by blindscan, perhaps because it is raining right now. I am pretty sure I found
it earlier by blindscan. This one takes 20 sconds to lock

 

[deeptho]

And in case you are wondering: Nostalgie is producing actual audio as well.
I have made a few small changes to neumodvb because it did not wait long enough for a lock.

 

[satesco]

I used to be able to get Alouette (11465.2H symbol rate 668) and Nostalgie (11458.4H, 514 kSamples/s )
but not anymore. I think it these services have moved.

Today I managed to lock 11457.6H at a symbol rate of 320 kS/s

This is with TBS6909X-version 1 and my neumodvb software. The spectrum scan does not
automatically detect it, and there is nothing useful on the transponder, but it locks easly.
It also seems to have physical layer scrambling. The peak at 11465 looks like an empty carrier
(or the driver refuses to lock)

This is on linux and after removing the limit of 1MS/s limit in the drivers (I think I replaced it with 100 instead)

One problem in locking such transponders is inaccurate local oscillators in LNBs. NeumoDVB learns
about such offsets and compensates for them, making tuning easier.



View attachment 138801

Thanks @deeptho for the tests you did on 5.0W with your application. But I'm just surprised by the symbol rates your application found.For example,11457.2 has a symbol rate of 260 ks, and at 11453 it has 543 ks.I rechecked these transponders with IQmonitor and it found the same parameters as Crazyscan.
And on Ubuntu I also found these parameters with the tune-s2. I hope it's not a bug on your app?
But unfortunately I didn't manage the same thing with Tvheadend. Can you lock these transponders with Tvheadend?

 

[deeptho]

The information comes from the drivers, and agrees typically with what is on kingofsat.net,
so I do not have reasons to doubt it (there is more doubt on other reported parameters. Eg. the
PLS code reported in the figure may be a bug). Of course for 5.0W that website is a bit out of date right now.

One thing to be careful of: some programs (also mine) make an initial estimate for symbolrate
to help the driver. In blindscan the driver then finds the correct symbolrate. One possible bug is
that the driver just reports back what you put as the initial value and not the real value locked on to.
This then affects all programs.

Such bugs really depend on the driver and not the end user program. Windows drivers are by crazycat,
but in the end it is likely that they come from the same source as the linux drivers.

I am curious: which card did you use under linux and which drivers?

About tvheadend:
1. the standard drivers impose a minimum symbolrate of 1000 KSamples/second. So unless you change to my drivers or edit the tbs sources, tvheadend (and no other program) will never be able to lock them.

2 Even then it will be a matter of luck: if the transponder takes a long time to lock, tvheadend will timeout and try to retune. tvheadend also has nasty bugs which render some muxes impossible to tune (they
stop working and work again after restarting tvheadend)

Locking or not locking depends on a lot of factors. I have tried a lot to improve locking in the drivers, but when going to extremes there are always compromises (+documentation is unclear), and some
transponders with low symbolrates take a while to lock.

There is also the issues of frequency offsets of the LNB. Some LNBs
have errors up to 2 Mhz (I have one of thise). So if you just enter the frequency, it will be 2Mhz wrong, which is much more than the transponder bandwidth, and this makes it a lot harder to catch a narrow band signal (even though the TBS drivers have some tolerances built in)

 

[satesco]

Thanks for the clarifications you bring to Tvheadend. I tried again to scan symbol rates below 1000 Ks, all failed. Neither Astra Cesbo does not accept such low rates. So there is no chance to use such parameters on these applications.
For low symbol rates I used the tbs6983 and tbs6903x cards under Ubuntu 20.04 and with the 5.11.0-37 kernel.