Driverless Ethernet Sound Card

Status
This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.
He says
Furthermore, the software interfaces to networking functions are essentially the same across all operating systems, unlike the interfaces to the audio subsystem. This makes it easy to write portable audio applications.
I'm not certain that is true, unless things have considerably changed since I was a systems programmer. Networking can be a nightmare!

The thing to remember is that TCP does not guarantee when packets will be delivered. UDP does not guarantee that they will be delivered (IIRC). The receiver will need a big FIFO buffer, so there will be a delay on starting up as the buffer half fills.
 
Well, the sockets interface is usually pretty samey across consumer operating systems, even Windows is not that different (Broken in some ways, but you can do most of the common things with only a few #ifdefs).

UDP is the way to go, over a deadicated link it is quite reliable these days, unlike back when hubs ruled.

The elephant in the room however is that you STILL need a driver (even if it could be a library in userspace), and it still needs to work to a defined API of some sort (Most likely it needs to appear as one or more soundcards to the system), which can be tricky (And is highly platform dependent) from userspace.

Regards, Dan.
 
Status
This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.