Vienna Symphonic Library Forum
Forum Statistics

196,946 users have contributed to 43,043 threads and 258,499 posts.

In the past 24 hours, we have 2 new thread(s), 15 new post(s) and 54 new user(s).

  • [SOLVED] Build 6776 causes problems with PTHD 8.0.1cs2

    Let me say up front that I don't have any crash logs so I can't contribute on a more proactive basis. Sorry about that but I was more concerned with getting back up and running.

    I noticed a new release of VEPro so I went ahead and installed on Master and Slave.

    Straight away I had problems with the eLicenser Control Center. It would not recognise ANY of my licenses. So I had to deinstall and download the latest version. Ok that fixed that (but why did it not work in the first place?)

    I am using PTHD 8.0.1cs2 on the Master and installed build 6776. What was a stable system started crashing straight away if I moved midi notes in PT...........of course with Kontakt 4(latest version). It's always Kontakt............but it had been behaving itself with build 6150.

    This kept happening after multiple starts and trashing of PT relevant files.

    I deinstalled VEPro and whent back to a fresh install of 6150.

    Now I am working again.

    That's 4 hours of my life I'd like back!

    Anyway just a heads up to other PT users. Please let me know your experiences with the latest build in combination with PT8.

    So if I feel brave again one day I will try the latest version and send you some crash logs but I have some deadlines right now.


  • Dear Philco,

    we are sorry to hear about this problem. Please send your setup details and the crashlog files to our The information in the crashlog will help us to narrow down the problem.

    On Mac you´ll find the crashlogs here:

    "Mac HD"/Users/"Username"/Library/Logs/....

    or

    "Mac HD"/Library/Logs/....

    Please look into the folder called "Crashreporter" too and send us the latest crashreports from there.

    Best regards,

    Maya


  • Thanks Maya. I will have to find some free time to reinstall the latest version and make the crash happen and then I will send the log.

    I worked all day today on 6150 and had no crashes.

    No one else is complaining so at this point it must be system specific.


  • Oh I just re read your post and found all the crash logs. Thanks for that. I have sent them.


  • Just to update anyone who is interested. It appears as though it was the Motu BPM plug causing all the crashes. (the crash logs have been examined).

    Nice to know that VEPro is not the culprit.

    Time to give that plug a rest (damn I just spent good money on the 1.5 upgrade!!)


  • Okay. Thx for reporting!

    /Regards,

    Maya