Vienna Symphonic Library Forum
Forum Statistics

196,640 users have contributed to 43,021 threads and 258,416 posts.

In the past 24 hours, we have 0 new thread(s), 0 new post(s) and 92 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Updated VEPro 5 no longer connects to Mac slave
  • R
    R

    Any ideas on this?

    Again, my PC slave has no problem connecting to old Logic sessions via the newly updated VEPro 5.  Master Mac computer and PC slave work as expected.

    And the connections are available on the network, properly named etc.  I can connect to them manually on the Mac slave.  And once done and resaved, all works as expected.  But it never works on a recalled project since the new update (5.3.13240)
  • PaulP
    VSL Team
    PaulP

    Hi rcstudio,

    Are you working with static IP addresses? That should keep the system steady - VE PRO connects based on the instance name and the IP address.

    Best,

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • R
    R

    Thanks for the reply, Paul

    The IP address of my Mac Slave is 192.168.1.18 and that has never changed.  I am using DHCP  Let me know if there are settings you want me to check.

    However, I don't see how this can be it, when I have been working over 18 months on this same setup (Master Mac Pro, Mac Slave, PC Slave) with no Logic/VE Pro 5 recall problems.  This through many VE Pro updates, OS updates, Logic updates (even going from Logic 9 to 10) etc etc.  It has always just worked ;-)

    Not until I updated to your new version this past Monday morning (Tennessee US) did these problems begin to occur.  
  • R
    R

    Any further ideas on why this is continuing to happen, and only on the one Mac Slave?

    Again, all the names of instances are the same, unchanged.  All the instances are available on the network.  The computers communicate with each other.  But Logic projects will no longer automatically connect to the instances in the Metaframe.  Manual reconnection works fine.

    What would have affected the Mac and not the PC (slave)?  And why now, and never in the last 18+ months?

    I'd love to figure this out, so that it does not ever happen again.

    Also, in the original set up of my system (over 18 months ago) I used all the instructions here and in the VE Pro Manual, plus the excellent tutorials by Tobias Escher. All has been fine until the June 2 update.

    Thanks 
  • PaulP
    VSL Team
    PaulP

    Hi, 

    Just to be on the sure: Please re-save the project with manually connected instances, then see if that project loads properly. If this is the case, then most likely the IP address of your server has changed (even though you say it has not changed).

    Best, 

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • R
    R

    As I said a couple of times earlier in this thread, Manual reconnect works and when saved and recalled, the connections stay.

    1.)  When you say "the IP address of your server has changed" you mean, JUST the IP address of the Mac slave, as all the VE Pro connections on my Master computer and PC slave work correctly.

    2.)  Not trying to be a smart A here, this is a real question:  What would cause the IP address to change at this point on the one Mac Slave computer and make all this not work, when it's been working steadily for over a year and a half through many film projects, VE PRO updates, OS updates, hard drive changes etc?  What makes an IP address change, if nothing is added or taken away from the private LAN that the 3 computers are on?  Plus, the Master and PC Slave have never changed.  I know it's not your job to teach me everything about computer networking, so thanks for your patience.  Just trying to learn.

    3.)  IS there a way to know what IP address the 7 VE Pro Instances assigned to the Mac Slave in my Logic X projects are actually looking for?  The IP address stored with the Project?  Because it would be way easier to just change it to what they want, rather than reconnecting all seven of the instances assigned to the Mac Slave.

    4.)  Finally, to avoid this in the future, are you saying that I should go to the Network Prefs pane on the Mac and change (on the first page there) from "using DHCP" on "Configure IPv4" to "using DHCP with manual address" or just "Manually"?  Or do I need to go to the Advanced page and change things there as well.  

    And I suppose I should to equivalent changes to my Master and the PC slave?  Does the original manual recommend fixed IP addresses?  I feel silly for missing that in both the VE Pro manual and Tobias Escher's tutorials!

    Thanks
  • R
    R

    Was that too many questions?
  • civilization 3C
    civilization 3C
    last edited
    last edited

    @rtcstudio said:

    Network Prefs pane on the Mac and change (on the first page there) from "using DHCP" on "Configure IPv4" to "using DHCP with manual address" or just "Manually"?

    And I suppose I should to equivalent changes to my Master and the PC slave?  Does the original manual recommend fixed IP addresses?  I feel silly for missing that in both the VE Pro manual and Tobias Escher's tutorials!

    Configure manually, ie., type in an address. This is THE address, it is 'fixed'. I never got this from the manual. It ought to be there.
    Every connection should be fixed. You've been insanely lucky if your performance hasn't been terrible with a dynamic IP.
  • R
    R

    Okay, pretty straightforward for the slaves, I assign a fixed IP address using the one that the plugins are currently connected to.

    The server on the Master computer is different - the IP address of the master computer is 

    192.168.1.24

    But the plugins using this VEPro on the Master computer are connected to Local Host at

    127.0.0.1

    I assume I still use the 192.168.1.24 as the fixed IP address - will it automatically assign the same Local Host address?  Or do I need to type this in somewhere else to ensure future connectivity? 

    Thanks

    Yes, insanely lucky for over 18 months.... 
  • R
    R

    Nevermind, found it on the Web.  

    For others who didn't know, 127.0.0.1 is a special "loop back address" for a computer to access it's internal TCP/IP network resources.