mrwish7
commented
12 months ago I hadn't taken into account that ZeroMQ can achieve the same end goal pretty well (with eti2zmq), I have that working nicely now. Multicast forwarding could be useful for some use cases though I guess
Would it be possible to essentially do the reverse of edi2eti, i.e. encapsulate an ETI-NI stream as EDI and send to a UDP destination?
This would be handy for transporting the DAB data around a local network (or otherwise) to another machine - EDI works very well as a native input for the ODR-DabMod tool for example.
I find that with DAB signals already in EDI format on satellite, the modulation process works very smoothly. I have a PC with tuner card using tsduck with mpe filter, forwarding decapsulated DVB-IP MPE packets onto my local network - e.g. from 7°E 12567V 17017 I could forward 239.132.1.50:5004 (SWR BW S). Then on a Raspberry Pi 4 with a HackRF connected I can run ODR-DabMod with native EDI source (239.132.1.50:5004). This runs very stably - tested for hours at a time.
It would be useful to be able to use a similar mechanism for streams in ETI-NA or ETI V.11 (decoded with tsniv2ni). If we could encapsulate them into EDI and forward them onto the network interface. Command options would be local interface address, multicast address and port. As mentioned in title, I guess this could either be part of the ni2out application as a new option, or a specific eti2edi tool.