Vienna Symphonic Library Forum
Forum Statistics

192,128 users have contributed to 42,832 threads and 257,544 posts.

In the past 24 hours, we have 13 new thread(s), 42 new post(s) and 193 new user(s).

  • Thanks, I'll try that.

  • Hello,

    I had the same problem, but with VEP5 (last version). I followed Paul's offline suggestion. I desinstalled VIP and VEP and I installed them again. The strange message disappeared.

    Hope this will help.

    C.B.


  • Happy user here, with same minor problem here on two Mac Pro's.

    No major headache, just a tad irritating when setting startupscripts for slaves.

    Tried clean uninstall and reinstall, same issue on two CPU's.

    Latest greatest MacOSX 10.9.1 and VEP 5.3.13045

    Grateful for any help


  • Just a bump if somebody has a sec? Is there a fix of sorts?


  • Bump,

    Still having this issue all the time after trying everything suggested in this thread and  reinstalls.

    Not a biggie but a minor irritation when starting up every morning.

    Would really appreciate a fix...

    thanx!


  • Hi, 

    Does that also happen with the latest version?

    This happens quite rarely, and Marnix already explained the background a bit... 

    Anyone else having the same issue here?

    Best, 

    Paul


    Paul Kopf Product Manager VSL
  • Thanx for reply.

    Yes, has happened with every new version on my two Mac Pros.


  • Hi houser,

    We believe you have some software installed which changes the system limits settings on boot.

    Unfortunately we don´t have any other pointers... any "exotic" software installed on your computer?

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • No esoteric stuff installed, no. AFAIK.

    Plain vanilla OSX 10.9xx and latest greatest VE Pro.

    Odd that it is only me, if that is the case...

    Ah well.

    I am serious about maintaining  my workstations and see no other problems.

    Just inconvenient...if you have any hint I would appreciate it!

    thanx again


  • Try reinstalling VE Pro. That dialog will only pop up when a change that the installer is supposed to make was somehow reverted.


  • I have done that a few times, and did it again now.

    Used the uninstaller to uninstall VEP5.

    Installed VEP 5.3.13151

    Restarted Mac Pro.

    Launched VEP 5

    Same dialog pops up

    Any helpful hints are appreciated...


  • Just a bump as I am getting tired of this one. Any chance of a way to fix this?


  • Hi,

    Just in case: I uninstalled both VIP and VEP (v.5).

    C.B.


  • Thanx C.B.

    I have uninstalled an reinstalled every single version since 4 just to be sure but the message still lingers.

    Just a tad irritating. Would be great to get rid of it.

    thanx again


  • Got tired of this one and decided to hunt it down. Found it...

    It was a conflict with Mac OSX server that was backing up via Time Machine.

    Would be great if VEP could be compatible with OSX server app running without asking for the OSA script password.

    thanx!

    j

    Getting some text from the console syslog that probably does not help, but here it is:

    Aug 20 17:27:20 servername_fudged servermgrd[341]: nsc_smb XPC: handle_event error : < Connection invalid >

    Aug 20 17:27:52 servername_fudged Vienna Ensemble Pro[1816]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.

    Aug 20 17:27:52 servername_fudged Vienna Ensemble Pro[1816]: CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.

    Aug 20 17:27:56 servername_fudged Vienna Ensemble Pro[1816]: CoreText performance note: Client called CTFontCreateWithName() using name "Trebuchet MS" and got font with PostScript name "TrebuchetMS". For best performance, only use PostScript names when calling this API.

    Aug 20 17:27:56 servername_fudged Vienna Ensemble Pro[1816]: CoreText performance note: Client called CTFontCreateWithName() using name "Arial" and got font with PostScript name "ArialMT". For best performance, only use PostScript names when calling this API.

    Aug 20 17:27:57 servername_fudged Vienna Ensemble Pro[1816]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.