SemV crashes Pro Tools HD 10.3.3

[noeqplease]

Hi guys,

I was changing presets while playing back my session. And it totally crashed Pro Tools.

Any ideas as to what is happening?

Here's part of the error log:

Process:         Pro Tools [20058]
Path:            /Applications/Avid/Pro Tools/Pro Tools.app/Contents/MacOS/Pro Tools
Identifier:      com.digidesign.ProTools
Version:         10.3.3.111 (10.3.3f111)
Build Info:      Unknown-10330111~111
Code Type:       X86 (Native)
Parent Process:  launchd [128]

Date/Time:       2013-01-29 12:15:15.983 -0800
OS Version:      Mac OS X 10.6.8 (10K549)
Report Version:  6

Interval Since Last Report:          197323 sec
Crashes Since Last Report:           1
Per-App Interval Since Last Report:  32596 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:                      88C5C9ED-061B-41E3-BD3B-47C552B04703

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000002
Crashed Thread:  23


Thread 23 Crashed:
0                                 0x00000002 0 + 2
1   ...Arturia.Oberheim-SEM-V.Vst2   0x6657416f GetPluginFactory + 1696687
2   ...Arturia.Oberheim-SEM-V.Vst2   0x6656671a GetPluginFactory + 1640794
3   ...Arturia.Oberheim-SEM-V.Vst2   0x6656e8fa GetPluginFactory + 1674042
4   ...Arturia.Oberheim-SEM-V.Vst2   0x665947c6 GetPluginFactory + 1829382
5   ...Arturia.Oberheim-SEM-V.Vst2   0x6653628d GetPluginFactory + 1443021
6   ...Arturia.Oberheim-SEM-V.Vst2   0x66534b10 GetPluginFactory + 1437008
7   ...Arturia.Oberheim-SEM-V.Vst2   0x66534add GetPluginFactory + 1436957
8   ...Arturia.Oberheim-SEM-V.Vst2   0x663d429d VSTPluginMain + 31501
9   ...Arturia.Oberheim-SEM-V.Vst2   0x663c9ca5 0x663ae000 + 113829
10  ...Arturia.Oberheim-SEM-V.Vst2   0x663c6dd5 0x663ae000 + 101845
11  ...Arturia.Oberheim-SEM-V.RTAS   0x619bdf84 CloseMachOPlugIn + 43460
12  ...Arturia.Oberheim-SEM-V.RTAS   0x619baff9 CloseMachOPlugIn + 31289
13  com.digidesign.framework.DAE     0x2cf0bdd3 FWMidiCallback + 321587
14  com.digidesign.framework.DAE     0x2cf0c0ee FWMidiCallback + 322382
15  com.digidesign.framework.DAE     0x2cf0c3ec FWMidiCallback + 323148
16  com.digidesign.framework.DAE     0x2cf0c554 FWMidiCallback + 323508
17  com.digidesign.framework.DAE     0x2ce9f205 FicGetContiguousMemRequirements + 100245
18  com.digidesign.framework.DAE     0x2ce9196a FicGetContiguousMemRequirements + 44794
19  com.digidesign.framework.DAE     0x2ce919cc FicGetContiguousMemRequirements + 44892
20  com.digidesign.framework.DAE     0x2ceebdf0 FWMidiCallback + 190544
21  com.digidesign.framework.DAE     0x2ceee91b FWMidiCallback + 201595
22  com.digidesign.framework.DAE     0x2cef0d65 FWMidiCallback + 210885
23  com.digidesign.framework.DAE     0x2ceea433 FWMidiCallback + 183955
24  com.digidesign.framework.DSI     0x009184a7 ResetDSP + 2503
25  ...n.framework.PlatformSupport   0x008c3d24 PSCPUTime_GetAbsoluteTicks(unsigned long long&) + 2638
26  ...n.framework.PlatformSupport   0x008c47e8 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 2451
27  ...n.framework.PlatformSupport   0x008c62a3 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9294
28  libSystem.B.dylib                0x97928259 _pthread_start + 345
29  libSystem.B.dylib                0x979280de thread_start + 34

[Adrien]

Hi

that is strange, it is the first time we see this.
Can you reproduce it ?
If playing you protools project generates this error could you send it to us.

Also, Do you know if we can play this project with PT10 (not HD) ?

Did this happen to anyone else ?

Best

[johnallan]

Yes. I stopped using SEM because it was SO unstable. Haven't tried it in Pro Tools 10.3.3, but it was crashing 10.3.2 (Native).
Basically unusable, in spite for the fact that it makes some nice sound, for the few minutes it runs. It's just not worth risking a project using it.


Here is my Arturia forums thread: http://www.arturia.com/evolution/smf/index.php?topic=7640.0

[johnallan]

So, have you fixed this issue yet, so I can use SEM with Pro Tools?
As I've said, SEM crashes Pro Tools 10 Native - and apparently Pro Tools 10 HD (see above) also.
I haven't even see Arturia acknowledge that this serious problem exists.
It's pretty serious when SEM can't even be used in the leading industry DAW.
BTW: None of the other Arturia instruments crash Pro Tools ( I have Mini Mg, Prophet V, Arp 2600 ).

[Adrien]

Hi

We put a really big effort on PT AAX 2.0 recently and with AAX you will have very good stability from what we see currently.
PT 11 and PT HD 11 have been extensively tested, I think AVID will release an update of PT 10 so PT 10 can support the AAX v2 that is in PT11.
As everything yould be release really soon (AAX updater + PT11) I realy advise you to move to AAX rather than the old RTAS.

Best

[jackn2mpu]

Hi

We put a really big effort on PT AAX 2.0 recently and with AAX you will have very good stability from what we see currently.
PT 11 and PT HD 11 have been extensively tested, I think AVID will release an update of PT 10 so PT 10 can support the AAX v2 that is in PT11.
As everything yould be release really soon (AAX updater + PT11) I realy advise you to move to AAX rather than the old RTAS.

Best

If you're staying on PT 10 I'd not install the AAX updater as it's not supported. AAX in PT10 is only aax 32 bit. It's up to the developer which in this case is Arturia whether their plugins support AAX 32 and AAX 64 bit in the same plug. PT10.3.6 is the PT version you need to have if you are also running PT 11; it does nothing special to recognize AAX 64 bit plugins. Remember that PT10 is a 32 bit only application.

Arturia programmers and people would do well to contact Avid about this (or at least spend time over on the DUC) rather than just speculate and give out what could be wrong info.

[Adrien]

Hi

yes indeed we only support 64 bit AAX. And it will not work on any PT 10 version;

[noeqplease]

Hi,
Just an update:

I have bee using the Oberheim SEM V successfully now for a few days.

Plug In version: 1.1.7
Pro Tools HD 10.3.6
Session is 24bit/44100Hz
Mac OS 10.6.8
12GB RAM

Thanks!!!

[Adrien]

Ok,

Maybe something was wrong in the preferences, or some cached data.
I m happy that it works again.

Let me know if you have more trouble.

best