Williewonka, to keep it very simple.
The network interface sends ethernet frames which are composed of a header, a payload and a CRC. At this stage it uses mac adresses to communicate.
A TCP/IP packet is a software created packet which will be the payload of a ethernet frame. TCP/IP is a little more complicated to explain but it uses a 3 way handshake to start a connection. Sequence numbers are used in those packets so that the a missing packet can be detected (if sequence number unexpectedly increases) and a resend can be asked with it's sequence number. For example if a package with sequence number 65 is received while there was no 64, a resend of 64 will be asked (it will actually go back to 64 which means that 65 will also be resend ... etc)
If you send a TCP/IP packet that packet will stay the same until it reaches it's goal (rare cases where it doesn't like a router using NAT), while every node will "repack" the TCP/IP packet into a new frame with the according mac addresses (a switch is not a node).
When a TCP/IP packet is lost it almost certainly happened "far away" (for example due to lack of bandwidth)
To get back on topic. I think the major problem with SPDIF is that each device generates it's own clock and older devices often generated a crappy clock.
Today's devices generate more consistant and accurate clocks which means less jitter problems.
The network interface sends ethernet frames which are composed of a header, a payload and a CRC. At this stage it uses mac adresses to communicate.
A TCP/IP packet is a software created packet which will be the payload of a ethernet frame. TCP/IP is a little more complicated to explain but it uses a 3 way handshake to start a connection. Sequence numbers are used in those packets so that the a missing packet can be detected (if sequence number unexpectedly increases) and a resend can be asked with it's sequence number. For example if a package with sequence number 65 is received while there was no 64, a resend of 64 will be asked (it will actually go back to 64 which means that 65 will also be resend ... etc)
If you send a TCP/IP packet that packet will stay the same until it reaches it's goal (rare cases where it doesn't like a router using NAT), while every node will "repack" the TCP/IP packet into a new frame with the according mac addresses (a switch is not a node).
When a TCP/IP packet is lost it almost certainly happened "far away" (for example due to lack of bandwidth)
To get back on topic. I think the major problem with SPDIF is that each device generates it's own clock and older devices often generated a crappy clock.
Today's devices generate more consistant and accurate clocks which means less jitter problems.