@yt020490_13791 said:
When I was first setting up VEP I did some tests as to how it recognises the slave and found that it is exclusively by IP. So I have set up all our VEP machines with static IPs.
This has allowed me to create 2 matching systems where, relative to the master machine, the slave in both systems is 192.168.2.2; this means that cues saved on one of the 2 systems, will load, and automatically pair to the appropriate slave instances on the other system.
That is a great suggestion. This was, if I take my protools session to another studio, as long as all IP addresses match, the files will have a chance of opening if all IP addresses match.
I think the VE Pro docs should have 1 paragraph that suggests all machines in a VEPro network use static IP. Even 1 sentence with a suggestion to search this forum would be helpful.
It is NOT VEPro's job to educate the user on networking principles, but it is the role of VEPro documentation to explain that this is an IP based system and if the IP address of the machines change, so will the ability to restore. Even though I consider myself a smart guy when it comes to networking, I failed to understand that it's looking for a static IP -- if the docs had stated, "for best results, set all machines in your network to static IP". Done. This will greatly enhance the user experience.