I wonder if there's some confusion here about things.
sea_hawk_12 wrote: ↑
Tue Aug 07, 2018 7:29 pm
As of now, no, there is no encoding or compressing of the audio stream. I am receiving packets in SDP format. I will be sure to play with aplay. I guess the question I should be asking is: can the Raspberry Pi receive audio over Ethernet?
From what I remember SDP is just a protocol that describes a multimedia stream, it doesn't contain any media (video or audio) itself.
sea_hawk_12 wrote: ↑
Mon Aug 06, 2018 5:50 pm
I am working on a multicast client project, were the Raspberry Pi 3 Model B is the client and my Cisco switch is the server where there are multiple devices connected and subscribing to the multicast group. The Raspberry Pi is connected by Ethernet.
I’ve already written the C code on the Raspberry Pi allowing it to subscribe to the multicast audio stream via Ethernet.
The part I’m stuck on is once I am receiving multicast packets via the Ethernet port on the Raspberry Pi, how do I take these packets and output them using the onboard audio jack? Does the Pi have an audio CODEC I need to communicate with?
For media there's nothing different to using a multicast source to a unicast udp stream. Within an Layer2 Ethernet the only difference is that instead of sending to a unicast address the media source send to a multicast group. The clients will then subscribe to that same group and a suitably intellegent switch will control (via IGMP) what ports the data goes out of (if it doesn't do IGMP snooping the stream should just get sent out all ports)
In a layer 3 environment other stuff comes into play with protocols like PIM and extra devices such as RP and BSR, these are just to help support the multicast network, they don't provide any content themselves.
I'm a bit confused as to how you think the Cisco switch is the server ? It might help if you described a bit more of the setup - maybe with some diagram. If your able to share some of the (hopefully commented code) that may help others to help you.
Also as a starting point it's possible to use things like vlc and ffmpeg to act as both a multicast source and client. As a starting point it might make sense to get something working with those first then look at making your own client to receive and process the data using vlc and ffmpeg as the source.