Vienna Symphonic Library Forum
Forum Statistics

181,978 users have contributed to 42,198 threads and 254,643 posts.

In the past 24 hours, we have 4 new thread(s), 8 new post(s) and 45 new user(s).

  • VePro Aborts Shutdown on remote Macs

    When I shotdown my mac, VePro aborts the shutdown. I then must shutdown again. This is not logical and not a very Mac friendly behaviour. On a normal shutdown, unsaved documents in open applications will correctly prompt the user to save, thereby aborting shutdown. The user then saves, and shuts down again.

    VePro, even though it has no open "documents", aborts shutdown in a similar manner. But there is nothing to save. Oddly, it also quits itself - making the whole thing pointless. The quitting part also seems to confuse Remote Desktop. And yes, I have quit my Sequencer, releasing VePro, before attempting shutdown.

    Could VePro PLEASE by updated to behave properly? Can it please only abort a shutdown if there is an unsaved instance STILL ACTIVE.

    When running VePro on remote macs, one of the beauties of this is the ability to run servers without extra screens and keyboards. At the end of my day, I send a remote command to all my servers to shutdown. This is a long time ingrained habit. I then discover that the machines are not shutdown, AND I have lost communication with Apple's remote Desktop because Remote Desktop believes shutdown has proceeded.

    To get round this, I must REMEMBER to actually go into each server, quite the various VePro instances, and then shut down.

    I've got caught out by this too many times now, hence my (2nd) post on this subject.

    On the subject of Remote Desktop, it would be nice if VePro was "signed" or whatever, so that I also don't need to prompt Apple's firewall to accept VePro. This occurs on almost every startup.

    Thanks

    Ben


  • last edited
    last edited

    Hi Ben,

    @Another User said:

    On the subject of Remote Desktop, it would be nice if VePro was "signed" or whatever, so that I also don't need to prompt Apple's firewall to accept VePro. This occurs on almost every startup.

    We will look into it.

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • Thanks that's great.

    Ben


  • Update for VSL team -

    Not to stop you investigating, but the Firewall "nag" from OSX does seem a lot less frequent now. It would be nice to know what is going on there, but the problem does seem much less. It may be since I manually added VEPro to the Firewall filter?

    Regarding the shutdown issue - that's still very much alive and I appreciate that you aim to resolve this.

    Ben


  • Hi Guys,

    The shutdown "irritation" I mentioned before is still happening. Does the new PB address this?

    Thanks