WiFi for pads is a secondary issue I'd like to accommodate. May I give you a case for some specific advice? I would like to have a mobile PA system that consists of some powered speakers (already have QSC K10s and don't care about Ethernet connection to the speakers), a single RM32AI, a CD18AI, and a Windows laptop to capture the audio. I wish Presonus were more clear about their product direction. This extra avb-compatible functionality in both hardware and firmware is probably why manufacturers wants to charge extra money for their efforts until the momentum is big enough to price their gear at a much lower price. As I also understand it, just because two devices speaks avb doesn't mean that they can speak with each other.Īs I understand it standardization efforts are also being made to enablesupport wifi carry low-latency audio streams that is aes67/dante compatible. Given that dante and aes67 requires no special hardware and has support for computer based daw/recording on most hardware for mac/pc I dont see how avb will be able to compete with and beat aes67/dante. Merging released a couple of weeks ago a free coreaudio driver for aes67 supporting upp to 64 channels and rumor has it that there will be a similar asio driver in a near future. Their virtual soundcard was lowered from $150 down to $30 making it almost a steal to buy now. You could probably say that audinate has given up on avb,for the time being.

Since then dante has exploded on the market also into the semi-pro stuff (and some MI-stuff as well) and audinate has commited to the open aes67 standard as well and have released firmware updates to their popular brooklyn cards to enable this. When presonus sprung(?) for avb dante was not as wildly accepted and mostly installed on high-end gear and comes with a heafty license fee as well.Īt the time audinate(dante) said that they would also jump on the avb train and enable their products to be compatible with avb.

Waves trackslive