Multicast and all that stuff

A fellow on satguys got me sparked. He has a commercial rack mount receiver and was interested in using the GigE port to send a transport stream out directly to a client device. VLC, whatever.
Interesting because I've been extremely interested in fanning out to to play around with the different satellite data transponders. NOAAPort on 123W being the one that gets my attention.
I was looking for one of the Novra S300 receivers that pops up on eBay at times. New is a bit pricey and nobody can verify if a password has been set on them.
A call to the manufacturer, International Datacasting let me know that if a password was in fact set that I'd need to send it in. The OS is Linux. So my intuition tells me that perhaps capturing it in bootloader and peeking around would reveal something. But a chance I really don't want to take. And the send-in option to Canada...well, you know.
Then because the Novra can only send data from a single transponder but using different multicast ports. I got sparked by the rack mount ID receivers from them.
Their Superflex rack mount line looks more versatile and affordable to play with.

Multicast protocol. Just when I thought I had a pretty good handle on TCP/IP. Yaaa. I never understood why the machine vision section of my industrial equipment used "funky" IP addresses. Now I get it. Kind of. And it will be a whole new thing as a mission to understand. I suggested the guy use a private IP some several octets and port different from the management console IP in the 10.0.0.XXX range. Oops. That would be a no-go for multicasting a channel over GigE. Right? I think so.

The big one now. Can a receiver like the Osmio4k multicast? Is a plugin out there to try it? Searches come up with proxy stuff and having to compile the code.
Why in the hell does Linux need you to compile code found in places like Git and Sourceforge? I mean. Windows has installers, portable .exe's. Linux? Why?
They even sometimes make you....make, literally. An executable to use a Windows program.

The webif allows you to stream a channel. But it makes a m3u8 first and if use VLC or VLC on a pc. If you're lucky the video stream opens.
I guess when another receiver is a slave in client mode, it still needs to import the lamedb. But you cannot connect directly to the master without and watch channels.
Why can't you punch the IP and port in Open Network Stream in VLC and watch a channel?
Further. Looking in a m3u8 file there is the channel reference stuff you see in a channel editor, lamedb. Confusing.

So. I kind of understand the ASI output from commercial receivers. And ASI to HDMI converters. I guess that's how guys like us would watch channels from these receivers. Right? GigE and Ethernet? I'm grasping that the GigE output formats are selectable. A transport stream (.ts) being one. Perfect!
VLC opens .ts as do other media players.

Enosat has said that Enigma 2 receiver recorded .ts files don't "have enough information". But a TBS or similar dvb-s2 card can and do. All day long.
"For diagnostic purposes" Akin to Jack Daniels in a Georgia or Florida Baptist dry county "for medicinal purposes only", of course.
Would, if it were possible to, multicasting using one of our receivers allow direct use of one of the dvb players like DVB Dream and such?
I have tried using on of them (forget which one) to plug in my mio's IP and streaming port. Nada. Zip, zilch, zingo. Same as VLC.

Another thing. Is it Video for Linux? Linux version of Windows BDA.
Using one of the dvb cards under Linux. Do they output that format? And under Windows BDA?
Is there anything for Enigma 2 that sends a BDA out of the Ethernet port? Transcoder? Plugin?
Many consumer things like HD Homerun Silicon Dust boxes like BDA. Linux? Forget about it. Right?
So. Any solutions?

The TBS card recommended for doing the best under various Linux applications that is right down my alley is currently unobtanium. This guy:

Rob VK8FOES

Apologies. A "new" interest gone wild. Some time ago I was able to somehow muddle through dvbsnoop and use Wireshark and monitor human readable text using the mio. The NOAAPort transponder will not lock and will not scan in. Strange because I see some data transopnders that do scan in doing blindscans.
If I were able to manually create and force a channel and include it in my bouquet for 123W. One hurdle accomplished. But so far, clueless.
I know. I'm all over the place here. Uncharted territories I guess. Very willing to learn though. Gets you off of the TNAP discussion though.
 
Almost always, A commercial, rack type mount satellite receiver will be designed to do one single thing, and that is it. Setting one of these receivers up is usually more difficult when compared to tuning a professional satellite card or FTA receiver.It is that simple. However, in general, the overall performance on the commercial rack mount receiver may exceed most cards or fta receivers.

I think you will find Multicast IP range: 224.0.0.0 to 239.255.255.255
Multicast allows one transmitter to send to multiple receivers efficiently, which is perfect for satellite data distribution to multiple clients.

You don't need to compile anything. TNAP and maybe other images include udpxy as a pre-built package. Just run these commands on your osmio4k via SSH:
opkg update
opkg install udpxy
/etc/init.d/udpxy.sh start


Then in VLC on your PC, open network stream: http://osmio4k_ip:4022/udp/239.255.0.1:1234/
This converts multicast to HTTP. Hopefully VLC will play it perfectly.

The m3u8 file is basically the streaming address, which also contains:
This is Enigma2's internal channel identifier. It tells the receiver:
Which satellite
Which frequency
Which channel on that frequency
Which video/audio PIDs to extract
Enigma2 is designed to surf channels where the professional receiver is designed to sit on one transponder. There is a difference in the information that is needed for the commercial receiver as it does not care about satellite location for example.

To keep going with answers gets more complex. You might consider focusing on one topic at a time. Your original post contains:
Hardware & Equipment Topics:
1. Commercial rack mount receivers (GigE streaming capabilities)
2. Novra S300 receivers (features, password lockout concerns, pricing)
3. IDC Superflex rack mount receivers (comparison to S300, versatility)
4. TBS DVB-S2 cards (Linux compatibility, availability issues)
5. HD HomeRun Silicon Dust boxes (BDA compatibility)
6. ASI outputs and ASI-to-HDMI converters (commercial receiver outputs)
7. Osmio4k receiver capabilities (multicasting, streaming)

Protocol & Networking Topics:
8. Multicast protocol (IP addressing, 239.x.x.x ranges vs 10.x.x.x private IPs)
9. GigE/Ethernet streaming (transport stream formats, output options)
10. TCP/IP vs UDP multicast (differences, use cases)

Software & Compatibility Topics:
11. Linux compilation requirements (Git/Sourceforge source code, ./configure/make)
12. Windows .exe vs Linux packages (installation paradigms, Wine compatibility)
13. V4L (Video4Linux) vs BDA (Broadcast Driver Architecture) (Linux vs Windows DVB APIs)
14. DVB software compatibility (DVBDream, ProgDVB, etc. with Enigma2 receivers)
15. Enigma2 streaming methods (WebIF, m3u8 files, service references, HTTP streaming)

Satellite Data Reception Topics:
16. NOAAPort satellite data reception (123W/121W, transponder parameters, locking issues)
17. Transport stream completeness (Enigma2 recordings missing SI/PSI tables vs TBS card captures)

This is simply way too many topics to try to address in a single post or thread. My apologies.
 
Back
Top