Login / Register
 
PT 10.3.3 crash AFTER I quit Pro tools!
New Reply
Subscribe
Juhannike
Thread Starter
#1
21st February 2013
Old 21st February 2013
  #1
http://jarpehag.com/
 
Joined: Apr 2011
Posts: 35

Thread Starter
Juhannike is offline
PT 10.3.3 crash AFTER I quit Pro tools!

Almost every time I work with VI's in Pro tools HDX 10.3.3.. and close the program, I get this message that Pro Tools crashed unexpectedly.
Can any of you guys figure this report out? Is there any obvious reason why it crashes AFTER I quit protools? :confused:



I can not post the entire crash report :/ .. but here is the first part, and the last part of it:


Process: Pro Tools [3529]
Path: /Applications/Avid/*/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 [131]

Date/Time: 2013-02-21 13:34:42.472 +0100
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9

Interval Since Last Report: 292007 sec
Crashes Since Last Report: 11
Per-App Interval Since Last Report: 37267 sec
Per-App Crashes Since Last Report: 11
Anonymous UUID: 557651AC-B58F-438F-B5D7-83730E193AFD

Crashed Thread: 40

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000002345f529

VM Regions Near 0x2345f529:
MALLOC_LARGE 0000000021e33000-0000000021e70000 [ 244K] rw-/rwx SM=PRV
-->
MALLOC_LARGE 0000000023a64000-0000000023a91000 [ 180K] rw-/rwx SM=PRV

Application Specific Information:
objc[3529]: garbage collection is OFF

Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x9c32ec5e semaphore_wait_trap + 10
1 com.digidesign.framework.PlatformSupport 0x008c4f2c PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 12503
2 com.digidesign.framework.DSI 0x0098b636 DsiCardHealth_GetStatus() + 198
3 com.digidesign.framework.DSI 0x009100fe UnInitSADriver + 62
4 com.digidesign.ProTools 0x000103b4 0x1000 + 62388
5 com.digidesign.ProTools 0x0000effd 0x1000 + 57341

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x9c33190a kevent + 10
1 libdispatch.dylib 0x93f8be04 _dispatch_mgr_invoke + 969
2 libdispatch.dylib 0x93f8a853 _dispatch_mgr_thread + 53

Thread 2:
0 libsystem_kernel.dylib 0x9c32ec5e semaphore_wait_trap + 10
1 com.digidesign.framework.digitrace 0x0151398a digitrace_initialize + 10122
2 com.digidesign.framework.digitrace 0x015180df DigiTraceIsActiveFunc + 1263
3 com.digidesign.framework.digitrace 0x01518265 DigiTraceIsActiveFunc + 1653
4 com.digidesign.framework.digitrace 0x015183c1 DigiTraceIsActiveFunc + 2001
5 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
6 libsystem_c.dylib 0x92c4c6de thread_start + 34

Thread 3:
0 libsystem_kernel.dylib 0x9c32ec22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9c32e1f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9974a9da __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x99753b04 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x997531dc CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x99763f01 CFRunLoopRun + 129
6 com.digidesign.framework.ProTools 0x0bf6d327 MFortressHWBPEntryPoint_exit_mfort6317_ + 27326733
7 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
8 libsystem_c.dylib 0x92c4c6de thread_start + 34

Thread 4:
0 libsystem_kernel.dylib 0x9c32ec22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9c32e1f6 mach_msg + 70
2 com.digidesign.framework.CoreFoundation 0x0024ead2 Sys_MachExceptionHandler::Init(bool, int) + 706
3 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
4 libsystem_c.dylib 0x92c4c6de thread_start + 34

Thread 5:
0 libsystem_kernel.dylib 0x9c32ec5e semaphore_wait_trap + 10
1 com.digidesign.framework.PlatformSupport 0x008c4fd7 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 12674
2 com.digidesign.framework.DSI 0x0096166a DsiTIDSP_GetNumberOfTIDSPs() + 5626
3 com.digidesign.framework.PlatformSupport 0x008c42a3 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9294
4 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
5 libsystem_c.dylib 0x92c4c6de thread_start + 34

Thread 6:
0 libsystem_kernel.dylib 0x9c32ec76 semaphore_timedwait_trap + 10
1 com.digidesign.framework.DSI 0x009610bc DsiTIDSP_GetNumberOfTIDSPs() + 4172
2 com.digidesign.framework.PlatformSupport 0x008c42a3 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9294
3 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
4 libsystem_c.dylib 0x92c4c6de thread_start + 34

Thread 7:
0 libsystem_kernel.dylib 0x9c32ec76 semaphore_timedwait_trap + 10
1 com.digidesign.framework.DSI 0x0098b2d2 DsiTopology_GetLocationClusterId(EDhmRouterDepotType, unsigned long, unsigned long&) + 5442
2 com.digidesign.framework.PlatformSupport 0x008c42a3 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9294
3 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
4 libsystem_c.dylib 0x92c4c6de thread_start + 34

Thread 8:
0 libsystem_kernel.dylib 0x9c32ec76 semaphore_timedwait_trap + 10
1 com.avid.framework.TIShellMgr 0x0d83a10a CTIShellMgr_Chip::DeleteClump(Sys_FileLoc const&, std::string const&) + 70906
2 com.digidesign.framework.PlatformSupport 0x008c42b8 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9315
3 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
4 libsystem_c.dylib 0x92c4c6de thread_start + 34

Thread 9:
0 libsystem_kernel.dylib 0x9c3302de __ioctl + 10

Thread 11:
0 libsystem_kernel.dylib 0x9c3302de __ioctl + 10
1 com.digidesign.framework.PlatformSupport 0x008c3e71 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 8220
2 com.digidesign.framework.DAE 0x0d22fa35 FWMidiCallback + 504981
3 com.digidesign.framework.DAE 0x0d1dc3c3 FWMidiCallback + 163363
4 com.digidesign.framework.DAE 0x0d22f9d2 FWMidiCallback + 504882
5 com.digidesign.framework.PlatformSupport 0x008c42b8 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9315
6 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
7 libsystem_c.dylib 0x92c4c6de thread_start + 34

Thread 12:
0 libsystem_kernel.dylib 0x9c3302de __ioctl + 10
1 com.digidesign.framework.PlatformSupport 0x008c3e71 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 8220
2 com.digidesign.framework.DAE 0x0d22fa35 FWMidiCallback + 504981
3 com.digidesign.framework.DAE 0x0d1dc193 FWMidiCallback + 162803
4 com.digidesign.framework.DAE 0x0d22f9d2 FWMidiCallback + 504882
5 com.digidesign.framework.PlatformSupport 0x008c42b8 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9315
6 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
7 libsystem_c.dylib 0x92c4c6de thread_start + 34

Thread 13:
0 libsystem_kernel.dylib 0x9c32ec22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9c32e1f6 mach_msg + 70
2 libsystem_kernel.dylib 0x9c32eb9e mach_msg_receive + 63
3 com.digidesign.framework.PlatformSupport 0x008c272a PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 2261
4 com.digidesign.framework.PlatformSupport 0x008c42a3 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9294
5 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
6 libsystem_c.dylib 0x92c4c6de thread_start + 34


6 com.digidesign.framework.CoreFoundation 0x00249394 Sys_RawThread::ThreadIDsAreEqual(void*, void*) + 68
7 com.digidesign.framework.PlatformSupport 0x008c42a3 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9294
8 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
9 libsystem_c.dylib 0x92c4c6de thread_start + 34

Thread 18:
0 libsystem_kernel.dylib 0x9c3302de __ioctl + 10
1 com.digidesign.framework.PlatformSupport 0x008c3e71 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 8220
2 com.digidesign.framework.PlatformSupport 0x008ce52e PSThreadTable_AddTable(SPSThreadPriorityEntry const*, unsigned long) + 492
3 com.digidesign.framework.ProTools 0x0c353615 TTimelineSelectionLayer_ForwardDeclarationHack::RemoveReference(TTimelineSelectionLayer*) + 3372389
4 com.digidesign.framework.ProTools 0x0c353648 TTimelineSelectionLayer_ForwardDeclarationHack::RemoveReference(TTimelineSelectionLayer*) + 3372440
5 com.digidesign.framework.CoreFoundation 0x0022c7f4 Sys_RawThreadTask::Run() + 36
6 com.digidesign.framework.CoreFoundation 0x00249394 Sys_RawThread::ThreadIDsAreEqual(void*, void*) + 68
7 com.digidesign.framework.PlatformSupport 0x008c42a3 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9294
8 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
9 libsystem_c.dylib 0x92c4c6de thread_start + 34

Thread 19:
0 libsystem_kernel.dylib 0x9c3302de __ioctl + 10
1 com.digidesign.framework.PlatformSupport 0x008c3e71 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 8220
2 com.digidesign.framework.PlatformSupport 0x008ce52e PSThreadTable_AddTable(SPSThreadPriorityEntry const*, unsigned long) + 492
3 com.digidesign.framework.CoreFoundation 0x00248fde Sys_BlockingTimer::Destroy(Sys_BlockingTimer*&) + 942
4 com.digidesign.framework.ProTools 0x0c37350d TTimelineSelectionLayer_ForwardDeclarationHack::RemoveReference(TTimelineSelectionLayer*) + 3503197
5 com.digidesign.framework.CoreFoundation 0x0022c7f4 Sys_RawThreadTask::Run() + 36
6 com.digidesign.framework.CoreFoundation 0x00249394 Sys_RawThread::ThreadIDsAreEqual(void*, void*) + 68
7 com.digidesign.framework.PlatformSupport 0x008c42a3 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9294
8 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
9 libsystem_c.dylib 0x92c4c6de thread_start + 34

Thread 20:
0 libsystem_kernel.dylib 0x9c3302de __ioctl + 10
1 com.digidesign.framework.PlatformSupport 0x008c3e71 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 8220
2 com.digidesign.framework.PlatformSupport 0x008ce52e PSThreadTable_AddTable(SPSThreadPriorityEntry const*, unsigned long) + 492
3 com.digidesign.framework.ProTools 0x0c353615 TTimelineSelectionLayer_ForwardDeclarationHack::RemoveReference(TTimelineSelectionLayer*) + 3372389
4 com.digidesign.framework.ProTools 0x0c353a68 TTimelineSelectionLayer_ForwardDeclarationHack::RemoveReference(TTimelineSelectionLayer*) + 3373496
5 com.digidesign.framework.CoreFoundation 0x0022c7f4 Sys_RawThreadTask::Run() + 36
6 com.digidesign.framework.CoreFoundation 0x00249394 Sys_RawThread::ThreadIDsAreEqual(void*, void*) + 68
7 com.digidesign.framework.PlatformSupport 0x008c42a3 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9294
8 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
9 libsystem_c.dylib 0x92c4c6de thread_start + 34

Thread 21:
0 libsystem_kernel.dylib 0x9c32ec22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9c32e1f6 mach_msg + 70
2 com.apple.audio.midi.CoreMIDI 0x004d8fcb XServerMachPort::ReceiveMessage(int&, void*, int&) + 101
3 com.apple.audio.midi.CoreMIDI 0x004fbf8b MIDIProcess::RunMIDIInThread() + 259
4 com.apple.audio.midi.CoreMIDI 0x004fc912 MIDIProcess::MIDIInPortThread::Run() + 24
5 com.apple.audio.midi.CoreMIDI 0x004da59f XThread::RunHelper(void*) + 17
6 com.apple.audio.midi.CoreMIDI 0x004d9f69 CAPThread::Entry(CAPThread*) + 123
7 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
8 libsystem_c.dylib 0x92c4c6de thread_start + 34

Thread 22:
0 libsystem_kernel.dylib 0x9c3302de __ioctl + 10
1 com.digidesign.framework.PlatformSupport 0x008c3e71 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 8220
2 com.digidesign.framework.DAE 0x0d22fa35 FWMidiCallback + 504981
3 com.digidesign.framework.DAE 0x0d20331b FWMidiCallback + 322939
4 com.digidesign.framework.DAE 0x0d22f9d2 FWMidiCallback + 504882
5 com.digidesign.framework.PlatformSupport 0x008c42b8 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9315
6 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
7 libsystem_c.dylib 0x92c4c6de thread_start + 34

Thread 23:
0 libsystem_kernel.dylib 0x9c3302de __ioctl + 10
1 com.digidesign.framework.PlatformSupport 0x008c3e71 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 8220
2 com.digidesign.framework.DAE 0x0d22fa35 FWMidiCallback + 504981
3 com.digidesign.framework.DAE 0x0d20331b FWMidiCallback + 322939
4 com.digidesign.framework.DAE 0x0d22f9d2 FWMidiCallback + 504882
5 com.digidesign.framework.PlatformSupport 0x008c42b8 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9315
6 libsystem_c.dylib 0x92c48ed9 _pthread_start + 335
7 libsystem_c.dylib 0x92c4c6de thread_start + 34



Thread 40 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x2345f29e ecx: 0xb2592ecc edx: 0xffffffff
edi: 0xb2592f44 esi: 0x18b5b780 ebp: 0xb2592f58 esp: 0xb2592f30
ss: 0x00000023 efl: 0x00010286 eip: 0x2345f529 cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000023 gs: 0x0000000f
cr2: 0x2345f529
Logical CPU: 6



External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 29
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 5858
thread_create: 0
thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=312.5M resident=222.2M(71%) swapped_out_or_unallocated=90.2M(29%)
Writable regions: Total=930.7M written=378.8M(41%) resident=702.9M(76%) swapped_out=0K(0%) unallocated=227.8M(24%)

REGION TYPE VIRTUAL
=========== =======
ATS (font support) 32.8M
CG backing stores 1476K
CG image 176K
CG raster data 192K
CG shared images 3568K
CoreAnimation 4K
CoreGraphics 8K
CoreImage 8K
CoreServices 1072K
IOKit 26.7M
IOKit (reserved) 4096K reserved VM address space (unallocated)
MALLOC 790.4M
MALLOC guard page 48K
MALLOC_LARGE (reserved) 20.0M reserved VM address space (unallocated)
Memory tag=240 4K
Memory tag=242 12K
Memory tag=249 264K
OpenCL 56K
OpenGL GLSL 896K
Stack 87.4M
VM_ALLOCATE 16.4M
__CI_BITMAP 80K
__DATA 21.6M
__DATA/__OBJC 148K
__IMAGE 528K
__IMPORT 104K
__LINKEDIT 57.3M
__OBJC 3100K
__OBJC/__DATA 80K
__PAGEZERO 4K
__PDSIG 324K
__TEXT 255.2M
__UNICODE 544K
mapped file 107.9M
shared memory 27.3M
shared pmap 5104K
=========== =======
TOTAL 1.4G
TOTAL, minus reserved VM space 1.4G

Model: MacPro5,1, BootROM MP51.007F.B03, 8 processors, Quad-Core Intel Xeon, 2.4 GHz, 20 GB, SMC 1.39f11
Graphics: ATI Radeon HD 5770, ATI Radeon HD 5770, PCIe, 1024 MB
Memory Module: DIMM 1, 4 GB, DDR3 ECC, 1066 MHz, 0x0702, 0x35313237325931303647000000004D544900
Memory Module: DIMM 2, 4 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x31384A53463531323732415A2D3147314131
Memory Module: DIMM 3, 1 GB, DDR3 ECC, 1066 MHz, 0x80AD, 0x484D54313132553754465238432D48392020
Memory Module: DIMM 4, 1 GB, DDR3 ECC, 1066 MHz, 0x80AD, 0x484D54313132553754465238432D48392020
Memory Module: DIMM 5, 4 GB, DDR3 ECC, 1066 MHz, 0x0702, 0x35313237325931303647000000004D544900
Memory Module: DIMM 6, 4 GB, DDR3 ECC, 1066 MHz, 0x80AD, 0x000000000000000000000000000000000000
Memory Module: DIMM 7, 1 GB, DDR3 ECC, 1066 MHz, 0x80AD, 0x484D54313132553754465238432D48392020
Memory Module: DIMM 8, 1 GB, DDR3 ECC, 1066 MHz, 0x80AD, 0x484D54313132553754465238432D48392020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.198.19.22)
Bluetooth: Version 4.0.8f17, 2 service, 11 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: ATI Radeon HD 5770, sppci_displaycontroller, Slot-1
PCI Card: pci11af,ef70, sppci_othermultimedia, Slot-2
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: WDC WD1001FALS-41Y6A0, 1 TB
Serial ATA Device: ST31000528AS, 1 TB
Serial ATA Device: ST31000528AS, 1 TB
USB Device: hub_device, 0x0409 (NEC Corporation), 0x0059, 0xfd100000 / 2
USB Device: USB Keystation 88es, 0x0763 (M-Audio), 0x0192, 0xfd140000 / 3
USB Device: iLok, 0x088e, 0x5036, 0xfd130000 / 4
USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0xfa200000 / 2
USB Device: Apple Keyboard, apple_vendor_id, 0x0221, 0xfa220000 / 3
USB Device: Razer Abyssus, 0x1532, 0x001c, 0x3d100000 / 2
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x5a100000 / 2
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0x5a110000 / 3
FireWire Device: built-in_hub, 800mbit_speed
#2
22nd February 2013
Old 22nd February 2013
  #2
Lives for gear
 
mirrorboy's Avatar
 
Joined: Mar 2011
Location: Orange County, CA
Posts: 1,287

mirrorboy is offline
I have no idea what any of that 'error code' means but here's a suggestion to help get you up & running and stop the VI-induced issues inherent in Pro Tools 10 & lower (all shades):

Download the latest 10.3.3 PT HD Installer.

Uninstall PT
Restart & Repair Permissions
Install PT
Restart & Repair Permissions
--
Buy Vienna Ensemble Pro 5
Install that
Restart & Repair Permissions
--

Now, load all your VIs in VEP 64 Bit Server (which basically is limited only by the amount of RAM in your machine). You could also launch VEP 32 bit server and host your 32 bit VIs there, simultaneously. VEP hosts AUs.

Hosting AVID / AIR / DIGI VIs (and only these ones) including the Click should work fine & without issue in Pro Tools. For whatever reason, they are unbelievably efficient.

Everything else (even FX plugs if you want) in VEP 64 bit or 32 bit Server

You only need one computer.

It's all extremely simple once you get going & you won't believe the efficiency, stability & workflow enhancements!! (;


Hope this helps!!

Good luck!!

Scott

P.S. Another helpful thing is to upgrade to the latest plugs and VIs that have AAX available.

P.P.S. The issue as a whole looks to me like typical Pro Tools / VIs / Ram stuff....but I could be way off!! (;
__________________
Play what serves the song, not yourself.
__________________
www.thrivingivory.com
www.facebook.com/thrivingivory
www.facebook.com/scottleejason
Juhannike
Thread Starter
#3
22nd February 2013
Old 22nd February 2013
  #3
http://jarpehag.com/
 
Joined: Apr 2011
Posts: 35

Thread Starter
Juhannike is offline
Thanks for the tip! Maybe I look in to VE pro.

Anyone else?

All the best!
Jonatan
#4
22nd February 2013
Old 22nd February 2013
  #4
Gear interested
 
Joined: Jun 2011
Location: Sydney NSW
Posts: 21

Trojan is offline
Quote:
Originally Posted by mirrorboy View Post
I have no idea what any of that 'error code' means but here's a suggestion to help get you up & running and stop the VI-induced issues inherent in Pro Tools 10 & lower (all shades):

Download the latest 10.3.3 PT HD Installer.

Uninstall PT
Restart & Repair Permissions
Install PT
Restart & Repair Permissions
--
Buy Vienna Ensemble Pro 5
Install that
Restart & Repair Permissions
--

Now, load all your VIs in VEP 64 Bit Server (which basically is limited only by the amount of RAM in your machine). You could also launch VEP 32 bit server and host your 32 bit VIs there, simultaneously. VEP hosts AUs.

Hosting AVID / AIR / DIGI VIs (and only these ones) including the Click should work fine & without issue in Pro Tools. For whatever reason, they are unbelievably efficient.

Everything else (even FX plugs if you want) in VEP 64 bit or 32 bit Server

You only need one computer.

It's all extremely simple once you get going & you won't believe the efficiency, stability & workflow enhancements!! (;


Hope this helps!!

Good luck!!(

Scott

P.S. Another helpful thing is to upgrade to the latest plugs and VIs that have AAX available.

P.P.S. The issue as a whole looks to me like typical Pro Tools / VIs / Ram stuff....but I could be way off!! (;
I think you're probably spot on Scott! I reached the same conclusion and its time to go VE Pro for me too. Is it worth checking out the demo?
'
Sent from my XT535
__________________
Gear Junkie
#5
22nd February 2013
Old 22nd February 2013
  #5
Lives for gear
 
mirrorboy's Avatar
 
Joined: Mar 2011
Location: Orange County, CA
Posts: 1,287

mirrorboy is offline
Quote:
Originally Posted by Trojan View Post
I think you're probably spot on Scott! I reached the same conclusion and its time to go VE Pro for me too. Is it worth checking out the demo?
'
Sent from my XT535
Right on!

And definitely! I didn't even know there was a demo!! haha


Scott
#6
22nd February 2013
Old 22nd February 2013
  #6
Lives for gear
 
Bishbashbosh's Avatar
 
Joined: Sep 2005
Location: London
Posts: 646

Bishbashbosh is offline
Good advice re VE Pro... It's an indispensable tool.
That said, it's always handy to pin down those errors...!
They can often be caused by too much RAM useage (often VI's don't release RAM once they are uninstalled)...
Sometimes the quit after PT quits is caused by an incompatible plugin... I had this repeatedly with EW Play.
VEPro gets round both those issues, by being 64 bit, and also using AU format....
Juhannike
Thread Starter
#7
23rd February 2013
Old 23rd February 2013
  #7
http://jarpehag.com/
 
Joined: Apr 2011
Posts: 35

Thread Starter
Juhannike is offline
Quote:
Originally Posted by Bishbashbosh View Post
Good advice re VE Pro... It's an indispensable tool.
That said, it's always handy to pin down those errors...!
They can often be caused by too much RAM useage (often VI's don't release RAM once they are uninstalled)...
Sometimes the quit after PT quits is caused by an incompatible plugin... I had this repeatedly with EW Play.
VEPro gets round both those issues, by being 64 bit, and also using AU format....
Yes. I think it's EW Play that causes the after I quit-crash. I do not think it happens when I just use NI Kontakt in a session.
#8
23rd February 2013
Old 23rd February 2013
  #8
Lives for gear
 
mirrorboy's Avatar
 
Joined: Mar 2011
Location: Orange County, CA
Posts: 1,287

mirrorboy is offline
Quote:
Originally Posted by Juhannike View Post
Yes. I think it's EW Play that causes the after I quit-crash. I do not think it happens when I just use NI Kontakt in a session.
Ahhh...ok.

One thing to note, if you do get VEP, EW recommends running PLAY before KONTAKT in VEP (as far as order goes).

Also, keeping Kontakt's memory server off (as its hosted in VEP) has worked well for me.


Cheers!

Scott
#9
23rd February 2013
Old 23rd February 2013
  #9
Lives for gear
 
Bishbashbosh's Avatar
 
Joined: Sep 2005
Location: London
Posts: 646

Bishbashbosh is offline
I eventually just gave up on Play... Way too buggy, and doesn't play nicely with others.
That may have been resolved now... But it was causing constant crashes with my otherwise very stable setup.
I'm just using Kontakt and Spectrasonics instruments now, and everything is absolutely rock solid.... By which I mean 12-18 hours a day every day for 18 months, no crashes.
I actually do use Kontakt memory server, but actually thinking about it, there's no need in 64 bit VE Pro is there..!?
Highly recommend VE Pro.
cut
#10
24th February 2013
Old 24th February 2013
  #10
cut
Gear maniac
 
cut's Avatar
 
Joined: Nov 2008
Location: S.W. Connecticut (N.Y.C Burbs)
Posts: 159

cut is offline
Quote:
Originally Posted by Bishbashbosh View Post
I eventually just gave up on Play... Way too buggy, and doesn't play nicely with others.
That may have been resolved now... But it was causing constant crashes with my otherwise very stable setup.
I'm just using Kontakt and Spectrasonics instruments now, and everything is absolutely rock solid.... By which I mean 12-18 hours a day every day for 18 months, no crashes.
I actually do use Kontakt memory server, but actually thinking about it, there's no need in 64 bit VE Pro is there..!?
Highly recommend VE Pro.
Play is the worst performing VI - Bar none.
Juhannike
Thread Starter
#11
24th February 2013
Old 24th February 2013
  #11
http://jarpehag.com/
 
Joined: Apr 2011
Posts: 35

Thread Starter
Juhannike is offline
Quote:
Originally Posted by cut View Post
Play is the worst performing VI - Bar none.
Yes. It's the WORST!
New Reply Submit Thread to Facebook Facebook  Submit Thread to Twitter Twitter  Submit Thread to LinkedIn LinkedIn  Submit Thread to Google+ Google+ 
 
Topic:
Thread Tools
Search this Thread
Search this Thread:

Advanced Search
Similar Threads
Thread
Thread Starter / Forum
Replies
hearmeshimmer / Music Computers
2
Damian Taylor / Music Computers
4

Forum Jump

SEO by vBSEO ©2011, Crawlability, Inc.