Replies created

 

Viewing 11 replies - 1 through 11 (of 11 total)
  • Mark Browne
    Participant

    I am having the same issue on Mac OS 10.9.5 w/ SD3 3.1.4 hosted in Vienna Ensemble Pro 6. My user presets will not load unless, I carefully follow the “click and release” with my mouse, as detailed above. Toontrack- I hope this can be fixed!


    Reply To: Can't load kit presets properly in SD3 core library after installing 3.1.3 version: 3.1.4
    Operating system: OS X Mavericks (10.9)
    Mark Browne
    Participant

    Scott- Thank you for your reply.
    I stand corrected! Pro Tools 10 is 32bit.
    SD3 is loaded into VEPro6 in network w/ Pro Tools on my Mac Pro.
    Is it impossible to drag a MIDI file from SD3 (hosted in VEPro6) directly into a Pro Tools 10 MIDI track?
    (I thought I had beed able to do this before my latest SD3 update.)
    -Mark

    Mark Browne
    Participant

    I’ve contacted Paul and Marnix at VSL. There will not be an update from VSL that will run on Mac OS 10.9 to address this issue. Mac 10.9 is no longer supported for Vienna Ensemble Pro 6.
    I’ve also discovered in my own testing and workflows on our systems that, the crashes only occur on SD3 and SD2 drum kits whose layer limits have been altered from their original preset values.
    -Mark

    Mark Browne
    Participant

    Olof- Thank you SO much for you diligence! I hope it’s an easy solution.

    Mark Browne
    Participant

    Oops, my session didn’t upload on my previous message. Here it is, again…

    Mark Browne
    Participant

    Hello Olof,
    Here is a small (no audio files) Pro Tools HD 10.3.10 session with a VEP6 64bit server instance with SD3 and a Progressive Foundry Library kit.
    This is a typical session setup that’ll crash VEP6 on closing the Pro Tools session. No other virtual instruments (individual or in combination) will cause a similar crash.
    These crashes only occur with SD3 in VEP6 64bit server within Pro Tools HD 10.3.10 session (Mac OS 10.9.5).
    If you see anything that may be helpful in finding a solution please let me know. Again, thank you for taking the time to help me with this issue.
    -Mark Browne

    Mark Browne
    Participant

    Hello Olof,
    Thank you again for taking the time to help me diagnose this issue. You have re-produced my VEPro6 set up correctly. I do not “preserve” my VEPro6 sessions since each session I create in Pro Tools is so drastically different. Anyway, I will send you a sample Pro Tools 10 session from my system to see how it will work in your system, asap. (I’m currently in Toronto for a recording session for a couple of days)
    I’m starting to feel that since no one can reproduce my crashes on similar systems, I may have a issue with my set up. I’ve consistently see that my larger RAM allocated SD3 sessions are the culprit in my crashes. I just don’t know where to look for a solution in my system. Until now it’s been really solid (knock wood).
    -Mark Browne

    Mark Browne
    Participant

    Here’s the sequence that causes the crash…
    -close Pro Tools session (this unloads all VI’s hosted in VEPro 6)
    -VEP6 crash occurs immediately after the session is closed.
    -only occurs after a session with SD3.0.2 loaded in VEPro 6
    -SD2 or EZDrummer does not cause this crash.

    Originally, I thought it was an issue with VEPro but, after contacting Vienna Instruments Tech Support and submitting crash reports, they said they couldn’t re-create the crash
    and it was most likely a SD3 issue. They recommended that I contact Toontrack.

    Update: I opened an SD3 kit last night and I did not change the mixer outputs or sample layer limits. VEPro 6 did not crash after this SD3 configuration.
    Observation: My VEPro 6 crashes seem to occur on SD3 kits that are NOT configured to have higher layer limits.

    Thank you for your time and help with this matter.
    -Mark Browne

    Mark Browne
    Participant

    I’m re-sending the Apple crash report here…
    Let me know if there’s a way to generate a more detailed crash report to diagnose this issue.
    Thank you,
    MB

    Mark Browne
    Participant

    Thank you for your reply. I had included my “Apple” crash report in my previous message as a .pdf attachment. Did you receive it? (I will send it again, if necessary)
    I have been using VEPro 6.0.16068 as a server in Pro Tools HD 10.3.10. My kits in SD3 are typically 4-5GB (bleed channels are all on and sensitivity layers are at the high setting, similar to SD2. My buffer setting in VEPro6 is “one buffer” My playback buffer in PT is 512MB. If I run SD2 in the same VEPro 6 configuration, I never experience these crashes. SD3 is the only VI that causes this VEPro 6 crash after closing my sessions. Nothing is running in the background and my internet access is disabled. I have not had any othe occurrences of unusual behavior, until now. Let me know if I can provide you with any more info. Again, thank you for your help with this!
    -Mark Browne

    Mark Browne
    Participant

    Thank you for your reply!
    • I only have the Apple crash log (please see attached .pdf ). Is there a way to generate a more useful crash log for diagnosing this issue?

    • VEPro 6 is running on the same Mac Pro as Pro Tools HD 10.3.10. Only one instance of SD3 is instantiated within VEPro6. (No other VI’s are running in VEPro6 or PT).

    Again, thank you for any help, in advance!
    -Mark Browne

Viewing 11 replies - 1 through 11 (of 11 total)

No products in the cart.

×