Lots of signals, just one cable: Simplify AV installations and lower cost with Audio over IP (AoIP) methods such as Dante, AVB, and CobraNet. This course will serve as an introduction and comparison to three approaches to network-based audio signal distribution. Participants will learn fundamental networking concepts to help cut through marketing lingo and then move into basic system requirements, limitations, and applications of IP distribution so they can better assess suitability within the framework of a given project. Real-world scenarios and applications will be discussed, as well as resources for additional information and assistance in designing and implementing a network-based signal distribution system. Presented by Steve Alexander © Almo Professional AV

1. AoIP
An Introduction and
Comparison of
Dante, AVB/TSN, &
CobraNet
Methodologies

2. Overview
• Networking Basics
• Technical and Capabilities Overview
• AVB/TSN
• CobraNet
• Dante
• Which One and When?

3. • Introduction to AoIP
• Conversational foundation and frame of
reference when working with
• Customers
• Vendors / evaluating equipment
• System designer
• Building block for more further education
How will this help me?

4. Why audio
networking?

5. • Everything point-to-point or through matrix switch
• Individual terminations on every signal path
• Heavy multi-core snakes
• Reconfiguration and growth not very flexible
• Signal degradation with distance
• Minimal distribution-related latency
Old Way

6. • Minimal terminations
• One RJ45 for dozens or hundreds of signal paths
• Distance limited only by network
• Flexible growth & reconfiguration:
• End points at any network drop
• Soft routing
• Potential latency
Audio Networking

7. Networking
Basics:
The OSI Model

8. • Describe what happens in a network
• Data passes down from 7 through 1 & back up
The OSI Model
Host
7 Application What we interface with (i.e. email, etc.)
6 Presentation Conversion for Application (i.e. compression, encryption)
5 Session Establish Connections between hosts
4 Transport Reliability TCP / UDP, “Segments”
Media
3 Network Connects Subnets Routers: Packets, IP, “Packets”
2 Data Link Avoid Collisions Switches: Frames, MAC
1 Physical Moving Data Cables, Connectors, Hubs, “Bits”

9. Host
7 Application What we interface with (i.e. email, etc.)
6 Presentation Conversion for Application (i.e. compression, encryption)
5 Session Establish Connections between hosts
4 Transport Reliability TCP / UDP, “Segments”
Media
3 Network Connects Subnets Routers: Packets, IP, “Packets”
2 Data Link Avoid Collisions Switches: Frames, MAC
1 Physical Moving Data Cables, Connectors, Hubs, “Bits”
• Describe what happens in a network
• Data passes down from 7 through 1 & back up
The OSI Model

10. • Cables & connections
• Moving bits from place to place
• Hubs - all data to all ports, created collisions
Physical Layer
Host
7 Application What we interface with (i.e. email, etc.)
6 Presentation Conversion for Application (i.e. compression, encryption)
5 Session Establish Connections between hosts
4 Transport Reliability TCP / UDP, “Segments”
Media
3 Network Connects Subnets Routers: Packets, IP, “Packets”
2 Data Link Avoid Collisions Switches: Frames, MAC
1 Physical Moving Data Cables, Connectors, Hubs, “Bits”

11. • Collision avoidance
• Switches
• Media Access Control (MAC) Address
Layer 2: Data Link
Host
7 Application What we interface with (i.e. email, etc.)
6 Presentation Conversion for Application (i.e. compression, encryption)
5 Session Establish Connections between hosts
4 Transport Reliability TCP / UDP, “Segments”
Media
3 Network Connects Subnets Routers: Packets, IP, “Packets”
2 Data Link Avoid Collisions Switches: Frames, MAC
1 Physical Moving Data Cables, Connectors, Hubs, “Bits”

12. • VLAN: Group ports for
isolation
• Frame: Contains MAC address, payload data
Layer 2: Data Link
Host
7 Application What we interface with (i.e. email, etc.)
6 Presentation Conversion for Application (i.e. compression, encryption)
5 Session Establish Connections between hosts
4 Transport Reliability TCP / UDP, “Segments”
Media
3 Network Connects Subnets Routers: Packets, IP, “Packets”
2 Data Link Avoid Collisions Switches: Frames, MAC
1 Physical Moving Data Cables, Connectors, Hubs, “Bits”

13. • Divide network into smaller networks (subnets)
• Connect to larger network (i.e. the Internet)
• Separate data types for efficiency or security
Layer 3: Network Layer
Host
7 Application What we interface with (i.e. email, etc.)
6 Presentation Conversion for Application (i.e. compression, encryption)
5 Session Establish Connections between hosts
4 Transport Reliability TCP / UDP, “Segments”
Media
3 Network Connects Subnets Routers: Packets, IP, “Packets”
2 Data Link Avoid Collisions Switches: Frames, MAC
1 Physical Moving Data Cables, Connectors, Hubs, “Bits”

14. • {Packets [Frames (MAC address, Payload)]}
• Source IP Address, Destination Address,
DiffServ (Priority info), etc.
Layer 3 - Network Layer
Host
7 Application What we interface with (i.e. email, etc.)
6 Presentation Conversion for Application (i.e. compression, encryption)
5 Session Establish Connections between hosts
4 Transport Reliability TCP / UDP, “Segments”
Media
3 Network Connects Subnets Routers: Packets, IP, “Packets”
2 Data Link Avoid Collisions Switches: Frames, MAC
1 Physical Moving Data Cables, Connectors, Hubs, “Bits”

15. • Connection, data order, reliability, flow control,
multiplexing
• [Soft] Port Numbers: routing within a device
• Multiple IP protocols
• TCP – Transport Control Protocol
• UDP – User Datagram Protocol
Layer 4: Transport Layer
Host
7 Application What we interface with (i.e. email, etc.)
6 Presentation Conversion for Application (i.e. compression, encryption)
5 Session Establish Connections between hosts
4 Transport Reliability TCP / UDP, “Segments”
Media
3 Network Connects Subnets Routers: Packets, IP, “Packets”
2 Data Link Avoid Collisions Switches: Frames, MAC
1 Physical Moving Data Cables, Connectors, Hubs, “Bits”

16. • TCP – Transport Control Protocol
• UDP – User Datagram Protocol
Layer 4: Transport Layer - Protocols
Host
7 Application What we interface with (i.e. email, etc.)
6 Presentation Conversion for Application (i.e. compression, encryption)
5 Session Establish Connections between hosts
4 Transport Reliability TCP / UDP, “Segments”
Media
3 Network Connects Subnets Routers: Packets, IP, “Packets”
2 Data Link Avoid Collisions Switches: Frames, MAC
1 Physical Moving Data Cables, Connectors, Hubs, “Bits”

17. • Reliable: every packet acknowledged
• Useful when 100% accuracy is required
• Increases bandwidth consumption & latency
Layer 4: Transport Layer - TCP
Host
7 Application What we interface with (i.e. email, etc.)
6 Presentation Conversion for Application (i.e. compression, encryption)
5 Session Establish Connections between hosts
4 Transport Reliability TCP / UDP, “Segments”
Media
3 Network Connects Subnets Routers: Packets, IP, “Packets”
2 Data Link Avoid Collisions Switches: Frames, MAC
1 Physical Moving Data Cables, Connectors, Hubs, “Bits”

18. • No confirmation delivery – less header info
• When urgency is critical (i.e. Real-time audio)
• Disadvantage on unreliable network
Layer 4: Transport Layer - UDP
Host
7 Application What we interface with (i.e. email, etc.)
6 Presentation Conversion for Application (i.e. compression, encryption)
5 Session Establish Connections between hosts
4 Transport Reliability TCP / UDP, “Segments”
Media
3 Network Connects Subnets Routers: Packets, IP, “Packets”
2 Data Link Avoid Collisions Switches: Frames, MAC
1 Physical Moving Data Cables, Connectors, Hubs, “Bits”

19. Layer 4: TCP vs. UDP Headers
Host
7 Application What we interface with (i.e. email, etc.)
6 Presentation Conversion for Application (i.e. compression, encryption)
5 Session Establish Connections between hosts
4 Transport Reliability TCP / UDP, “Segments”
Media
3 Network Connects Subnets Routers: Packets, IP, “Packets”
2 Data Link Avoid Collisions Switches: Frames, MAC
1 Physical Moving Data Cables, Connectors, Hubs, “Bits”

20. Layer 4: TCP vs. UDP Headers
Host
7 Application What we interface with (i.e. email, etc.)
6 Presentation Conversion for Application (i.e. compression, encryption)
5 Session Establish Connections between hosts
4 Transport Reliability TCP / UDP, “Segments”
Media
3 Network Connects Subnets Routers: Packets, IP, “Packets”
2 Data Link Avoid Collisions Switches: Frames, MAC
1 Physical Moving Data Cables, Connectors, Hubs, “Bits”

21. • Mostly software & application related
Layers 5 - 7
Host
7 Application What we interface with (i.e. email, etc.)
6 Presentation Conversion for Application (i.e. compression, encryption)
5 Session Establish Connections between hosts
4 Transport Reliability TCP / UDP, “Segments”
Media
3 Network Connects Subnets Routers: Packets, IP, “Packets”
2 Data Link Avoid Collisions Switches: Frames, MAC
1 Physical Moving Data Cables, Connectors, Hubs, “Bits”

22. • Just a tool to visualize & describe the process
• Data moves down through layers on the way out
& back up on the way in
OSI Model Recap
Host
7 Application What we interface with (i.e. email, etc.)
6 Presentation Conversion for Application (i.e. compression, encryption)
5 Session Establish Connections between hosts
4 Transport Reliability TCP / UDP, “Segments”
Media
3 Network Connects Subnets Routers: Packets, IP, “Packets”
2 Data Link Avoid Collisions Switches: Frames, MAC
1 Physical Moving Data Cables, Connectors, Hubs, “Bits”

23. Common
Timing, Priority
& Sync
Standards

24. • Differentiated Services / Quality of Service
• Priority by data type (clock sync and audio
packets over email)
• Prioritized by tags in IP header (Layer 3)
• Priority number assigned by manage switch to
each packet
Priority: “DiffServ” / “QoS”

25. • Real-time Transport Protocol (RTP) for UDP
• Keeps data in the right order
• Time stamp on UDP header
• Works with RTCP (Real Time Control Protocol) for
QoS and sync
• Variation: RTSP (Real Time Streaming Protocol)
for TCP
Timing: “RTP” & “RTSP”

26. • Precision Timing Protocol (PTP)
• Layer 2 - Switches provide hardware-based
time stamping
• Sub-microsecond accuracy to synchronize
subnets
Sync: “PTP”

27. • High Adoption & Growing
• Plug & Play
• Common Dante Controller
with Name-based routing
• Existing networks
• Network Setup for QoS
• 0.25 - 5ms Latency
•192 K / 32 bit
• Adoption in flux
• Plug & Play implementations
• Control & configuration varies
by manufacturer
• Requires certified switch
• Easy network setup
• Excellent sync & 2ms latency
• 192K / 32 bit floating point
• Tried and true
• Adoption Waning
• Dedicated
network suggested
• One sample rate
per system
• 8 Channel
Bundles
If need to run on existing
network or audio only
If able to upgrade to AVB/ TSN
certified switches & need video
If CobraNet is
already in place

28. AVB / TSN:
“It’s not a
protocol it’s a
standard”

29. • Standards:
• Agreed upon underlying technologies that allow things to
work
• i.e. Ethernet
• Protocols:
• A methodology
May utilize standards to accomplish a function
• Requires standards to function with other technologies
• i.e. Email
Standards vs. Protocols (Unofficial)

30. • 2012+
• Proponent: AVnu Alliance…
• Interoperable
• precise timing
• low latency requirements
• open standards
• Founders: Cisco, Harman, Intel, & others. Now 50+ members
• Collection of IEEE Layer 2 standards
Audio Video Bridging /
Time Sensitive Networking

31. • IEEE looked at the various standards to make sure
audio and video can go across a network and pulled
them together into one standard
• Does not require a dedicated network
• AVB by definition is part of the network
• Media prioritized over other traffic as part of this definition
− Audio will not suffer from other traffic
− Non-media will not get the same priority
• Requires AVB certified switch(es)
• Will not pass on non-certified switches
AVB / TSN – The Standard

32. • Stream reservations for AV held by the switch
• Switch reserves up to 75% of bandwidth for
media
• Queue in the switch to hold non-AVB signals
and prioritize AVB over DiffServ
• Guaranteed synch (<0.5ms, 1 Gigabit)
• Simplification: Enable AVB switch command
AVB - Stream Reservations

33. • Can run other data on same network.
• Can control amount of the bandwidth allocated
to AVB
• Don’t need to set up QoS on the switch
• Saves time
• “Enable AVB”.
• No VLANs to setup
AVB – Setup & Media Compatibility

34. • Up to 192K / 32 bit floating point
• Multiple simultaneous sample rates
• Channels: Reports vary by manufacturer
• 400-512+
• Different devices support different channel counts
• Latency 2ms up to 7 hops – some run less
• “Perfect Audio & Video Sync”
• Supports video, control, and any other payload data
across the same network and within AVB/TSN
AVB Audio Capabilities

35. CobraNet
“Tried & True”

36. • 1996 by Peak Audio
• 1997 Super Bowl Halftime Show & Disney’s Animal
Kingdom
• Now owned by Cirrus Logic
• Combination of software, hardware & network
protocol
• Layer 2 protocol compatible with standard network
infrastructure
CobraNet Background

37. • Up to 64 channels in and 64 channels out
• Up to 96kHz / 24 Bit
• Must match across system
• Audio grouped in 8 channel bundles
• Less at 24 bit
• Channel count expandable by VLAN
CobraNet Audio

38. • Fixed, applies to the entire system
• User definable: 1.33mS, 2.66mS, or 5.33mS
• Lower latency yields lower channel counts
• + AD/DA & DSP latency ≈ 10ms
CobraNet Latency

39. • Fixed, applies to the entire system
• User definable: 1.33mS, 2.66mS, or 5.33mS
• Lower latency yields lower channel counts
• + AD/DA & DSP Latency ≈ 10ms
CobraNet Latency

40. • Clock accuracy: 10µs for channels originating
on the same switch
• Longer for devices connected to different
switches
• “Conductor” [Master Clock]sends out “Beat
packet” for entire system
Clocking

41. • Dedicated network highly recommended
but not required
• VLAN’s an option to segment traffic
• Bandwidth use up to capacity of the switch
CobraNet Networking

42. • Many CobraNet (and Dante) devices offer
primary and secondary ports
• For redundancy, not to daisy chain off ports
• For automatic cutover in case of network failure
CobraNet Redundancy

43. Network Design Support:
http://www.cobranet.info/support/design
CobraCAD

44. Monitoring, Troubleshooting, Maintenance
Discovery Utility “Disco”

45. “The new kid,
that’s not so
new”

46. • 2003 Former team from Motorola started Audinate
• Over 350 manufactures
• 1000+ products
• Over 30 million Dante network channels
• Wide adoption & major events
• Pope Francis, Paul McCartney, Bruce Springsteen, Elton John,
Bob Dylan, Kenny Chesney, Foo Fighters, The Killers, etc.
Dante - Background

47. • Proprietary system of software & hardware
• Licensed technology for use on standard
networks
• Managed switch on converged network
• Standard switch on dedicated networks
Dante Networking

48. • OSI Layer 3
• DHCP to automatically assign IP addresses
• Plug & Play device discovery
• UDP / IP for speed
• DiffServ QoS
• Priority by data type
• Priority number assigned to each packet at managed
switch
Dante Networking (cont.)

49. • Supported channel count: 1024 (512/512)
• Can route individually (No Bundles)
• 192K / 32Bit
• Supports multiple simultaneous sample rates
• Must match between “subscriptions”
• Subscriptions are signal routings from outputs of one
device to inputs on another
• Label-based routing
Dante – Basic Audio

50. Consistent system
management
interface:
• Routing
• Network status
• Device info
Dante Controller:

51. Dante Controller – Network Status

52. Dante Controller – Device Info

53. • Latency: <0.15ms – 5ms
• User adjustable & constant
• Set in Dante Controller at receiver
• Based on network size
• Negotiation between receiver & transmitter to
ensure high enough
Dante – Latency

54. • Latency: <0.15ms – 5ms
• User adjustable & constant
• Set in Dante Controller at receiver
• Based on network size
• Negotiation between receiver & transmitter to
ensure high enough
Dante – Latency

55. • Dante Virtual Soundcard
• Provides routing from individual channels within internal
applications
• ProTools, Cubase, etc.
• Dante Via
• Allows a standard Apple Mac or Windows PC to function
as a Dante device
• No Dante enabled hardware required
• Dante Domain Manager
Other Dante Software

56. • Some Dante (and many CobraNet) devices offer
primary and secondary ports
• For redundancy, not to daisy chain off ports
• For automatic cutover in case of network failure
Dante Network Redundancy

57. • AES67 – A standard for standards…
• Get DiffServ standards to function together
• May lose advanced functionality
• ST-2110
• HQ Net – HARMAN Pro – Control Only
• EtherSound
• QLAN / QSYS – QSC Only
• ANET – AVIOM
• ROCKETNET
• RAVENNA
• H.264
AES67, ST-2110 & Other Players

58. • Dante / Audinate uses DiffServ
• Audinate is a member of AVnu Alliance (AVB)
• Will also make available compatibility to AVB
• AES67 – Unifies DiffServ family of protocols
according to commonalities
• Compatible with AES67 & AVB
• Bridging between protocols can exist within a
device
Dante with AVB & AES67

59. • High Adoption & Growing
• Plug & Play
• Common Dante Controller
with Name-based routing
• Existing networks
• Network Setup for QoS
• 0.25 - 5ms Latency
•192 K / 32 bit
• Adoption in flux
• Plug & Play implementations
• Control & configuration varies
by manufacturer
• Requires certified switch
• Easy network setup
• Excellent sync & 2ms latency
• 192K / 32 bit floating point
• Tried and true
• Adoption Waning
• Dedicated
network suggested
• One sample rate
per system
• 8 Channel
Bundles
If need to run on existing
network or audio only
If able to upgrade to AVB/ TSN
certified switches & need video
If CobraNet is
already in place

60. • The protocols themselves don’t matter as much
as what they allow you to do with the equipment
connected to them
• While Dante, AVB, and CobraNet all have
strength and limitations, they are each flexible
enough to meet most audio demands
• Consider starting with the rest of the system and
then working towards the network methodology
Conclusion: It’s not about the network…

61. Questions?
Rob Ziv
rziv@almo.com