Topic: SD3 Crashes Vienna Ensemble 6.16068 (Mac)

Viewing 15 replies - 1 through 15 (of 17 total)

Replied November 2, 2017 at 11:13 #1999983

Olof Hermansson
Moderator

Hi, do you have any crash logs you could upload? In what way have you connected VEP, PT and SD3? One or more instances of SD3 – in PT, VEP or both?

Olof Hermansson - Toontrack
Coder

Replied November 2, 2017 at 23:00 #1999992

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

Replied November 3, 2017 at 08:21 #1999994

John
Moderator

Hi,

you forgot to attach the log. You can attach the ‘.crash’ file in a ZIP.

BR,
John

John Rammelt - Toontrack
Technical Advisor

Replied November 3, 2017 at 13:06 #2000007

Olof Hermansson
Moderator

Are you using VEPro Server or the non-server VEPro application? Do you have an instance of the VEPro plug-in in Pro Tools, connected to the VEPro server?

I’ve been trying to reproduce this but haven’t found any problems.

Olof Hermansson - Toontrack
Coder

Replied November 4, 2017 at 04:57 #2000024

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

Replied November 4, 2017 at 10:12 #2000026

Olof Hermansson
Moderator

There was no attachment in your previous message so please send the crash report again.

Olof Hermansson - Toontrack
Coder

Replied November 4, 2017 at 18:51 #2000047

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

Replied November 6, 2017 at 09:51 #2000080

Olof Hermansson
Moderator

Hm, this crash report shows that there is no SD3 loaded in VEPro. There is no sign of any Toontrack product in it. You are quitting Pro Tools (and not VEPro) and at that time, VEPro crashes? Is it expected that VEPro unloads SD3 when you quit Pro Tools?

Olof Hermansson - Toontrack
Coder

Replied November 6, 2017 at 19:13 #2000099

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

Replied November 7, 2017 at 10:11 #2000105

Olof Hermansson
Moderator

I think the best would be if you could upload a small PT project that causes this crash.

I have now figured out how to make SD3 close in VEP when the PT session is closed – by connecting to a new ‘unpreserved’ instance, though I’m not sure if that is how you do it. Still I can’t make it crash.

Olof Hermansson - Toontrack
Coder

Replied November 8, 2017 at 08:37 #2000131

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

Replied November 13, 2017 at 21:25 #2000297

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

Replied November 13, 2017 at 21:27 #2000298

Mark Browne
Participant

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

Replied November 14, 2017 at 13:01 #2000313

Olof Hermansson
Moderator

Hi and thanks for the file. I was able to reproduce the crash after several attempts of opening and closing the session. However, if I exchange SD3 for SD2 in the session (and restart VEP), I can get it to crash in the same way and it never crashes in our code. I am contacting Vienna Instruments about this.

Olof Hermansson - Toontrack
Coder

Replied November 15, 2017 at 05:45 #2000329

Mark Browne
Participant

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

Replies

Viewing 15 replies - 1 through 15 (of 17 total)

SD3 Crashes Vienna Ensemble 6.16068 (Mac)

Superior Drummer 3 Help

Viewing 15 replies - 1 through 15 (of 17 total)