Hi everyone. This seems to be the place to mention some thoughts on this. I am a current mix system owner and I have contacted Presonus as well as several prominent AVB component manufacturers about how this problem could be solved.
Of course the PreSonus answer is always the same given one, actually copy paste : (
I realize PreSonus has made several statements on this and basically it looks like there will never be support between the two eco-systems. However I would like to add some information for consideration:
I have spent time researching 1722 and 1722.1 inter-oprability or conversion. I then contacted a number of AVB developers about this subject. (One of them even knows someone at PreSonus and called them regarding it) Three of the companies: AudioScience, Attero Tech, and XMOS.
Each one told me basically the same thing: I would have get PreSonus on-board to share code and issues to make any progress. BUT each one of them indicated that they felt it was purely a software/mapping issue. But of course no one will ever know or get a chance to do anything unless PreSonus releases the code and makes it open to us.
This led me to the next question which involves the SW5e switch which I purchased. How is it possible for this device to work in BOTH eco systems but yet neither one can communicate with one another while connected to it!? AudioScience makes a Custom Hono AVB device AND Hono AVB controller software which DO exactly that between 1722 and 1722.1 devices (including clock support) Unfortunately the AVB software does not see the my RM32ai or RM16ai, but it does see my AVB enabled Mac. (The device is made to work with thier own components at the moment and only 1722.1 AVB 3rd party devices)
One explanation from PreSonus is the developer closed its doors and did not complete the coding. Even if this is the case, why not develop a new card? If you are worried that everyone owner will want one for free, then stipulate that there is a cost, set that cost at the level at which is sensible but pays for the production and development.
I truly believe that PreSonus has everything to gain by trying to solve this problem of the "two eco-systems cannot work together". It doesnt need to be FULL support, but at least some usabillity between the two systems. In this way people can upgrade piece by piece, adding mixers when they actually want or need the lastest greatest features. As it is now they are forcing people to choose between them, and even worse forcing current loyal customers to basically abandon the old for the new which leaves a bit of a sour feeling. Not to mention the "future" promises that still havent happened.
If resources are the main issue, I am willing to spearhead a kick-starter style campaign to help solve the problem. Maybe its basically a new RM/AI thunderbolt or USB card, maybe its a converter box, maybe its actually retrofitting with a new board if necessary -- Some of us will pay to keep our systems out of legacy.
I think there are viable solutions which could be:
1. Open source code release for 3rd party development
2. Funding for a new card by a kick-starter campaign
3. Manufacture of new card (the networking is in the card as evidence by the fact there is a Dante card)
4. Turn the series into the "Presonus Dante" solution exclusively and actually build up on that with new products (this would mean simply dropping the old AVB and letting the series be only Dante -- with some functionalities reworked)
5. A simple rebate exchange AVB for Dante card program (with some cost incurred by customers and some by PreSonus)
Thats my 2 cents... would love to hear what others think....
I will keep my system in the end but it is shame to see such a versatile system that currently has features unavailable in the series III go to waste. I am currently beta testing the new firmware and still have some hopes to see what will happen, but I am not holding my breath.