Case 1: Control Not Matched


If happens that all of your speakers and control are highlighted in orange, even if the total amount of speakers and their wiring order is correct, then you probably are using a control 8 in a different IP address than last time.

To let the software know this is your new control hub, all you have to do is drag the real hub into your software project window, overwriting the virtual one. When both control and speakers are green, you can proceed going online with the green button.




Case 2: More Speakers

When we have more speakers in reality than in our project, our matching window will show us (on the Detected items section) the extra speakers highlined in orange.
In this example we will consider one more VIO L208 frontfill speaker, routed on the channel 4.






To solve this, just drag the new VIO L208 in the correct position, which is slot 4 , in the fourth channel of the software window.
Now that everyting is green, we can go online.




Case 3: Less Speakers

What if we have less speakers in reality compared to our Aurora project?
This is by far the easiest match to solve, since all our detected items will match.
we can simply hit the green button and confim to go online.

we'll see the extra speaker greyed out in our Software Project workspace. it might be useful to keep it there, in case of a future gig where this guy will be included. This way we're not losing all settings such as filters and delay.
We could also delete if from the project if we're not planning to use it again.




Case 4: Different speaker model

What if we want to replace a certain speaker with another one, and also move all of the settings to the new one?
In the example below, we substituted 3x VIO L208 with 3x VIO L1610. In Software project workspace our previous VIO L208s are greyed out.
To keep their processing data while using VIO L1610 instead, hold CMD on mac ( or CTRL on windows) and click on the newly added frontfills in the detected items workspace (from the First on top to last one), then simply drag them from detected to software, in the correct position.




Case 5: Different channel wiring

Le'ts now see how to make Auroranet aware that we wired certain speakers in a different channel than the one originally stored in the project.
For example: let's analyse what happens if the VIO L208s frontfills that were supposed to be on channel 4 are actually on a different one, channel 7.





The 3x VIO L208 on the Software project area are greyed out, that's because they're still on the wrong channel. To fix this, simply select them all and move them on channel 7.




case 6: change wiring order

Sometimes it can be convenient to run both frontfills and subs on the same channel. Let's analyse this scenario:
On our project we have subwoofers on channel 3 and frontfills on channel 4, but in reality they both are daisy chained and wired to channel 3.
In the image below you can easily spot that the reality on the left differs quite a lot from the software project on the right:





To fix this, all we have to do is drag and drop the items on the software area to rearrange them exactly as they show in the detected area.
(use the routing IDs on the left as a reference to help you in this operation)
So, in this example, we start with the first VIO L208 routed on channel 4: we drag and drop it in the position 3 of channel 3, inbetween the two VIO S118.





Please note, you need to insert this item inbetween oters, and not replace items. is you do so, the removed item will go to the warehouse on the right.
Once done, repeat the procedure for each of the unmatched items.

Case 7: adding a controller

We decide to split our system in multiple RDNet control8 or control2, even if we designed the project with only one.
For example: we add a Control8 and we wire the ch.1 of our first Control8 to ch.1 of the newly added one.
This is what our matching work area will show us after discovery:





In the detected item section a new Control8 will show up in orange, while in the project area all the speakers routed to ch.1 are highlined in orange.
To fix this: click on the minus icon on the top right cornet of our Control8, once our Control8 will collapse, let's drag and drop the new Control8 to below the existing one in the software project area:





Once done, let's open our controllers again, with the "+" symbol on the right corner. Now we are ready to select all the ch.1 speakers and drag them on the new Control8 ch.1.




Case 8: Mixed scenario

These are the most comon cases you might face once it comes to match an existing project with the PA you have in the real world.
Some times you might have combinations of this, such as a control 8 with a different IP, one less Line array module on each side and, why not, also a different model of Frontfill to be replaced. to fix this, just use all the informations we just shared, one by one, in order to adapt your project to what you have in fron ton you on show date.

Send us the best pics of the event and do not forget to describe the event with as much informations as you can: venue, date, artist, system configuration - only VIO Series.
Attachment (max 15Mb)


I declare that I have read and accept the contest rules.
The contact form made available on the site has the sole purpose of allowing site visitors to contact if they so wish, the operator of the site, by sending an email through this form to the manager. This information concerns the personal data sent by visitors when completing the contact form. We inform you that the data which will give us either through the form will be turned into an email that will eventually be kept within the system receiving emails used by the owner of the site. These data are not recorded on other media or devices. For more informations read our privacy policy.
Send