One of the most complicated, and frankly frustrating, things to wrap your head around when you are first working with Wheatnet IP is the concept of Sources and Destinations. At first, your tendency is to think that all sources must just be inputs and all destinations must be outputs, but you would be wrong to do that. The truth is that Source and Destination as identifiers are equally as subjective as inputs and outputs; they all beg the question ‘to what?’
When we set out to create a near latency free routing system for thousands of audio signals over a complicated IP network, the daisy chained template of ‘input connects to output’ didn’t fit the mold for multicast IP. How would one manage this complicated web of audio in such a linear fashion? Enter the crosspoint grid. Think of your Wheatnet-IP as ‘the cloud’. You can upload and download things to and from the cloud from innumerable devices from nearly anywhere in the world.
Your Wheatnet works in exactly this same way! A Source is basically an upload to your Wheatnet-IP cloud and a destination is a download from your Wheatnet-IP cloud. In your crosspoint grid, the cloud is the space where you make the crosspoints, and along one side of it you have all of the available things that can feed your cloud. This could be physical inputs on a blade, or it could be output busses of a surface, or even processed audio leaving your MP-532. Conversely, the other side is all the things that can take a feed from the cloud. This could be a physical output on a blade, or it could be an input fader on your surface, or an input to a utility mixer that lives on a blade.
Once you wrap your head around the concept that inputs and outputs are subjective and that the Wheatnet-IP is a network of audio signals that are available to give and take, you will find that the old analog concept of audio routing to be completely obsolete, and the modern way of audio routing in a digital audio over IP realm will completely open your mind to a different world of audio routing possibilities.
