Avid Pro Audio Community

Avid Pro Audio Community

How to Join & Post  •  Community Terms of Use  •  Help Us Help You

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

Go Back   Avid Pro Audio Community > Pro Tools Software > macOS
Register FAQ Today's Posts Search

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 12-29-2013, 07:45 AM
touch touch is offline
Member
 
Join Date: Dec 2003
Location: Bridgeport, CT, USA
Posts: 19
Default How do I launch co-install of PT10?

What am I missing?

I've installed and am successfully running PT 11.0.2 on my MacBook Pro 10.7.5 but I absolutely cannot find any information regarding how to launch PT 10.

I understand PT10 was included with my install of PT11, but searching on my computer yields no results for it. There's only one app icon and it's for PT11. It's also one of those tricky search terms which is tough to find info on through the googles.

Could I have missed a step with the install and only installed PT11? How would I then reinstall PT10? Going back to Avad.com/activation and entering my activation code says I can only download once.

**UPDATE** - Downloaded separate 10.3.8 installer and PT10 crashed on launch. So I moved plugins to the 'Unused' folder and 10 launched. Moved plugins back to the 'Used' folder, and it still works.

Last edited by touch; 01-03-2014 at 09:21 AM.
Reply With Quote
  #2  
Old 12-29-2013, 07:53 AM
Southsidemusic's Avatar
Southsidemusic Southsidemusic is offline
Moderator
 
Join Date: Dec 2011
Location: Stockholm - Sweden
Posts: 13,767
Default Re: How do I launch co-install of PT10?

Hi

PT10 is a separate installer and can be found under your Avid Account. Look under View My Products and there you can download PT10 and you also need to install a separate instrument and plugin file you also have in your account called 10.3 and is approx 2.6-2.7GB. Contains virtual instruments and AIR plugins.

Remember to install the latest version of PT = 10.3.8

Best Of Luck
Christopher
__________________
Best Regards
Christopher

#thestruggleisreal
—————————————
South Side Music Group
WEBHOME
—————————————
Reply With Quote
  #3  
Old 12-29-2013, 02:51 PM
touch touch is offline
Member
 
Join Date: Dec 2003
Location: Bridgeport, CT, USA
Posts: 19
Default Re: How do I launch co-install of PT10?

Thanks Christopher. I found it and installed PT10, but it crashes on launch. This is the error report:
Quote:
Process: Pro Tools [426]
Path: /Applications/Avid/*/Pro Tools.app/Contents/MacOS/Pro Tools
Identifier: com.digidesign.ProTools
Version: 10.3.8.378 (10.3.8f378)
Build Info: Unknown-10380378~378
Code Type: X86 (Native)
Parent Process: launchd [130]

Date/Time: 2013-12-29 17:51:00.430 -0500
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9

Interval Since Last Report: 2090121 sec
Crashes Since Last Report: 6
Per-App Interval Since Last Report: 143 sec
Per-App Crashes Since Last Report: 5
Anonymous UUID: 2D9B3F70-ECA1-4CE9-AF15-691A02BB0B7D

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

VM Regions Near 0:
--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Applications/Avid/*/Pro Tools.app/Contents/MacOS/Pro Tools
__TEXT 0000000000001000-0000000000143000 [ 1288K] r-x/rwx SM=COW /Applications/Avid/*/Pro Tools.app/Contents/MacOS/Pro Tools

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

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 ??? 0000000000 0 + 0
1 [Bundle] 0x2a964680 MDKPBAP4SRKFK + 157056
2 [Bundle] 0x2a964768 MDKPBAP4SRKFK + 157288
3 [Bundle] 0x2a97b86c MDKPBAP4SRKFK + 251756
4 [Bundle] 0x2a924aab O4LUGKLJA9ULU + 318063
5 [Bundle] 0x2a924b58 O4LUGKLJA9ULU + 318236
6 [Bundle] 0x2a9252f1 O4LUGKLJA9ULU + 320181
7 [Bundle] 0x2a925831 O4LUGKLJA9ULU + 321525
8 [Bundle] 0x2a9209fb O4LUGKLJA9ULU + 301503
9 [Bundle] 0x2a8feb06 O4LUGKLJA9ULU + 162506
10 [Bundle] 0x2a8feedb O4LUGKLJA9ULU + 163487
11 [Bundle] 0x2a8efdc7 O4LUGKLJA9ULU + 101771
12 [Bundle] 0x2a8f0cc0 O4LUGKLJA9ULU + 105604
13 [Bundle] 0x2a8ed90e O4LUGKLJA9ULU + 92370
14 [Bundle] 0x2a8f28f5 O4LUGKLJA9ULU + 112825
15 [Bundle] 0x2a8fe347 O4LUGKLJA9ULU + 160523
16 [Bundle] 0x2a8d7d42 O4LUGKLJA9ULU + 3334
17 [Bundle] 0x2a8d80bd O4LUGKLJA9ULU + 4225
18 [Bundle] 0x2a952f25 MDKPBAP4SRKFK + 85541
19 [Bundle] 0x2a95306a MDKPBAP4SRKFK + 85866
20 [Bundle] 0x2a98ba3d IL_SC_D_PPC + 343
21 [Unknown Bundle] 0x189a1cf3 EntryPoint + 103553
22 [Unknown Bundle] 0x189890b7 EntryPoint + 2117
23 [Unknown Bundle] 0x18988910 EntryPoint + 158
24 ??? 0x2c135dea g_dwILiLokTokens + 3450
25 dyld 0x8fe53203 ImageLoaderMachO::doModInitFunctions(ImageLoader:: LinkContext const&) + 251
26 dyld 0x8fe52d68 ImageLoaderMachO::doInitialization(ImageLoader::Li nkContext const&) + 64
27 dyld 0x8fe502c8 ImageLoader::recursiveInitialization(ImageLoader:: LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 256
28 dyld 0x8fe51268 ImageLoader::runInitializers(ImageLoader::LinkCont ext const&, ImageLoader::InitializerTimingList&) + 62
29 dyld 0x8fe4531d dyld::runInitializers(ImageLoader*) + 91
30 dyld 0x8fe4c17b dlopen + 585
31 libdyld.dylib 0x95f6ba95 dlopen + 70
32 com.apple.CoreFoundation 0x95b2b3ce _CFBundleDlfcnLoadBundle + 206
33 com.apple.CoreFoundation 0x95b26a8e _CFBundleLoadExecutableAndReturnError + 1470
34 com.apple.CoreFoundation 0x95b52b91 CFBundleLoadExecutable + 33
35 com.digidesign.framework.CoreFoundation 0x001b72de Sys_DLLMacOS::LoadBundle(Sys_FileLoc const&) + 126
36 com.digidesign.framework.CoreFoundation 0x001b782f Sys_DLLMacOS::Load(Sys_FileLoc const&, long) + 127
37 com.digidesign.framework.DAE 0x0c04b8cd FicGetApplicationInterface + 50461
38 com.digidesign.framework.DAE 0x0c04cb40 FicGetApplicationInterface + 55184
39 com.digidesign.framework.DAE 0x0c09fb4d FicGetContiguousMemRequirements + 194701
40 com.digidesign.framework.DAE 0x0c0a05b1 FicGetContiguousMemRequirements + 197361
41 com.digidesign.framework.DAE 0x0c07395a FicGetContiguousMemRequirements + 13978
42 com.digidesign.framework.DAE 0x0c0274a5 FicMain + 69
43 com.digidesign.framework.DAE 0x0c026860 InitFic + 160
44 com.digidesign.framework.ProTools 0x09bb1d26 MFortressHWBPEntryPoint_exit_mfort6317_ + 9006972
45 com.digidesign.framework.ProTools 0x09bb2f22 MFortressHWBPEntryPoint_exit_mfort6317_ + 9011576
46 com.digidesign.framework.ProTools 0x0ab1ea8b MFortressHWBPEntryPoint_exit_mfort6317_ + 25181409
47 com.digidesign.framework.DFW 0x0059a78b TCommandHandler::PerformCommand(TCommand*) + 187
48 com.digidesign.framework.DFW 0x0059b0df TCommand::Process() + 31
49 com.digidesign.framework.DFW 0x00590b8a TApplication::ProcessEvent(TEvent*) + 26
50 com.digidesign.framework.DFW 0x005914a0 TApplication::WakeUp() + 64
51 com.digidesign.framework.DFW 0x006f751b TApplication::CreateNewOSApplication(void*, void*, void*) + 667
52 com.apple.HIToolbox 0x9aca9c0c _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
53 com.apple.HIToolbox 0x9ab25313 _ZL23DispatchEventToHandlersP14EventTargetRecP14Op aqueEventRefP14HandlerCallRec + 1602
54 com.apple.HIToolbox 0x9ab24790 _ZL30SendEventToEventTargetInternalP14OpaqueEventR efP20OpaqueEventTargetRefP14HandlerCallRec + 482
55 com.apple.HIToolbox 0x9ab245a8 SendEventToEventTargetWithOptions + 75
56 com.apple.HIToolbox 0x9ab3a1c6 _ZL29ToolboxEventDispatcherHandlerP25OpaqueEventHa ndlerCallRefP14OpaqueEventRefPv + 3152
57 com.apple.HIToolbox 0x9ab257ce _ZL23DispatchEventToHandlersP14EventTargetRecP14Op aqueEventRefP14HandlerCallRec + 2813
58 com.apple.HIToolbox 0x9ab24790 _ZL30SendEventToEventTargetInternalP14OpaqueEventR efP20OpaqueEventTargetRefP14HandlerCallRec + 482
59 com.apple.HIToolbox 0x9ab39571 SendEventToEventTarget + 76
60 com.apple.HIToolbox 0x9aca9a58 ToolboxEventDispatcher + 82
61 com.apple.HIToolbox 0x9aca9b87 RunApplicationEventLoop + 236
62 com.digidesign.framework.DFW 0x00700a5b DFW_EventLoop::RunApplicationEventLoop() + 11
63 com.digidesign.framework.DFW 0x00590c5d TApplication::Run() + 45
64 com.digidesign.framework.ProTools 0x0ad641b1 MFortressHWBPEntryPoint_exit_mfort6317_ + 27563015
65 com.digidesign.framework.ProTools 0x0ad656d4 LaunchProTools + 1412
66 com.digidesign.ProTools 0x0000f277 0x1000 + 57975
67 com.digidesign.ProTools 0x0001037a 0x1000 + 62330
68 com.digidesign.ProTools 0x0000effd 0x1000 + 57341

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x91e1390a kevent + 10
1 libdispatch.dylib 0x99299e04 _dispatch_mgr_invoke + 969
2 libdispatch.dylib 0x99298853 _dispatch_mgr_thread + 53

Thread 2:
0 libsystem_kernel.dylib 0x91e10c5e 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 0x92237ed9 _pthread_start + 335
6 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 3:
0 libsystem_kernel.dylib 0x91e10c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91e101f6 mach_msg + 70
2 com.apple.CoreFoundation 0x95aee9da __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x95af7b04 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x95af71dc CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x95b07f01 CFRunLoopRun + 129
6 com.digidesign.framework.ProTools 0x0ad61a97 MFortressHWBPEntryPoint_exit_mfort6317_ + 27553005
7 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 4:
0 libsystem_kernel.dylib 0x91e10c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91e101f6 mach_msg + 70
2 com.digidesign.framework.CoreFoundation 0x0024f372 Sys_MachExceptionHandler::Init(bool, int) + 706
3 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
4 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 5:
0 libsystem_kernel.dylib 0x91e10c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91e101f6 mach_msg + 70
2 com.apple.CoreFoundation 0x95aee9da __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x95af7b04 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x95af71dc CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x95b07f01 CFRunLoopRun + 129
6 com.digidesign.framework.DAE 0x0c026da7 FicIsAlive + 983
7 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 6:
0 libsystem_kernel.dylib 0x91e122de __ioctl + 10
1 com.digidesign.framework.PlatformSupport 0x008c6e71 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 8220
2 com.digidesign.framework.PlatformSupport 0x008d152e PSThreadTable_AddTable(SPSThreadPriorityEntry const*, unsigned long) + 492
3 com.digidesign.framework.CoreFoundation 0x00249846 Sys_BlockingTimer:estroy(Sys_BlockingTimer*&) + 886
4 com.digidesign.framework.CoreFoundation 0x0022d280 Sys_RawThreadTimerTask::Exec() + 64
5 com.digidesign.framework.CoreFoundation 0x0022d094 Sys_RawThreadTask::Run() + 36
6 com.digidesign.framework.CoreFoundation 0x00249c34 Sys_RawThread::ThreadIDsAreEqual(void*, void*) + 68
7 com.digidesign.framework.PlatformSupport 0x008c72a3 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9294
8 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
9 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 7:
0 libsystem_kernel.dylib 0x91e122de __ioctl + 10
1 com.digidesign.framework.PlatformSupport 0x008c6e71 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 8220
2 com.digidesign.framework.PlatformSupport 0x008d152e PSThreadTable_AddTable(SPSThreadPriorityEntry const*, unsigned long) + 492
3 com.digidesign.framework.CoreFoundation 0x00249846 Sys_BlockingTimer:estroy(Sys_BlockingTimer*&) + 886
4 com.digidesign.framework.CoreFoundation 0x0022d280 Sys_RawThreadTimerTask::Exec() + 64
5 com.digidesign.framework.CoreFoundation 0x0022d094 Sys_RawThreadTask::Run() + 36
6 com.digidesign.framework.CoreFoundation 0x00249c34 Sys_RawThread::ThreadIDsAreEqual(void*, void*) + 68
7 com.digidesign.framework.PlatformSupport 0x008c72a3 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9294
8 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
9 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 8:
0 libsystem_kernel.dylib 0x91e122de __ioctl + 10
1 com.digidesign.framework.PlatformSupport 0x008c6e71 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 8220
2 com.digidesign.framework.PlatformSupport 0x008d152e PSThreadTable_AddTable(SPSThreadPriorityEntry const*, unsigned long) + 492
3 com.digidesign.framework.DAE 0x0c094e00 FicGetContiguousMemRequirements + 150336
4 com.digidesign.framework.CoreFoundation 0x0022d094 Sys_RawThreadTask::Run() + 36
5 com.digidesign.framework.CoreFoundation 0x00249c34 Sys_RawThread::ThreadIDsAreEqual(void*, void*) + 68
6 com.digidesign.framework.PlatformSupport 0x008c72a3 PSHardware_MatchDeviceInfo(TPSPCIDeviceInfo const*, TPSPCIDeviceInfo const*) + 9294
7 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 9:
0 libsystem_kernel.dylib 0x91e10c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91e101f6 mach_msg + 70
2 ??? 0x1041d907 g_dwILResult + 796919
3 ??? 0x1041d841 g_dwILResult + 796721
4 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 10:
0 libsystem_kernel.dylib 0x91e10c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91e101f6 mach_msg + 70
2 ??? 0x1149c907 g_dwILResult + 764151
3 ??? 0x1149c841 g_dwILResult + 763953
4 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 11:
0 libsystem_kernel.dylib 0x91e10c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91e101f6 mach_msg + 70
2 ??? 0x128f4907 g_dwILResult + 923895
3 ??? 0x128f4841 g_dwILResult + 923697
4 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 12:
0 libsystem_kernel.dylib 0x91e10c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91e101f6 mach_msg + 70
2 ??? 0x1394f907 g_dwILResult + 772343
3 ??? 0x1394f841 g_dwILResult + 772145
4 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 13:
0 libsystem_kernel.dylib 0x91e10c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91e101f6 mach_msg + 70
2 ??? 0x149bb907 g_dwILResult + 723191
3 ??? 0x149bb841 g_dwILResult + 722993
4 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 14:
0 libsystem_kernel.dylib 0x91e10c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91e101f6 mach_msg + 70
2 libcrypto.0.9.7.dylib 0x15da8907 DES_SPtrans + 1159
3 libcrypto.0.9.7.dylib 0x15da8841 DES_SPtrans + 961
4 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 15:
0 libsystem_kernel.dylib 0x91e10c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91e101f6 mach_msg + 70
2 ??? 0x1721a907 0 + 388081927
3 ??? 0x1721a841 0 + 388081729
4 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 16:
0 libsystem_kernel.dylib 0x91e10c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91e101f6 mach_msg + 70
2 [Unknown Bundle] 0x189ac907 EntryPoint + 147605
3 [Unknown Bundle] 0x189ac841 EntryPoint + 147407
4 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 17:
0 libsystem_kernel.dylib 0x91e10c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91e101f6 mach_msg + 70
2 ??? 0x1a028907 0 + 436373767
3 ??? 0x1a028841 0 + 436373569
4 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 18:
0 libsystem_kernel.dylib 0x91e10c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91e101f6 mach_msg + 70
2 ??? 0x1b420907 0 + 457312519
3 ??? 0x1b420841 0 + 457312321
4 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 19:
0 libsystem_kernel.dylib 0x91e10c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91e101f6 mach_msg + 70
2 ??? 0x1c17f907 0 + 471333127
3 ??? 0x1c17f841 0 + 471332929
4 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9223b6de thread_start + 34

Thread 20:
0 libsystem_kernel.dylib 0x91e10c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x91e101f6 mach_msg + 70
2 ??? 0x1d1e4907 0 + 488524039
3 ??? 0x1d1e4841 0 + 488523841
4 libsystem_c.dylib 0x92237ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9223b6de thread_start + 34
Reply With Quote
  #4  
Old 12-29-2013, 05:09 PM
Southsidemusic's Avatar
Southsidemusic Southsidemusic is offline
Moderator
 
Join Date: Dec 2011
Location: Stockholm - Sweden
Posts: 13,767
Default Re: How do I launch co-install of PT10?

Hi

I am on it, asking a few guys here who knows more about crash reports for MAC so hang in there and we will get back to you

Christopher
__________________
Best Regards
Christopher

#thestruggleisreal
—————————————
South Side Music Group
WEBHOME
—————————————
Reply With Quote
  #5  
Old 01-03-2014, 06:13 AM
touch touch is offline
Member
 
Join Date: Dec 2003
Location: Bridgeport, CT, USA
Posts: 19
Default Re: How do I launch co-install of PT10?

PT10.3.8 is still crashing on launch. "Pro Tools quit unexpectedly"

Do I need to uninstall PT11 before installing 10? What I'm reading leads me to believe this is not necessary.
Reply With Quote
  #6  
Old 01-03-2014, 08:22 AM
touch touch is offline
Member
 
Join Date: Dec 2003
Location: Bridgeport, CT, USA
Posts: 19
Default Re: How do I launch co-install of PT10?

I finally got it to launch. I moved all the plug-in's into the 'Unused' folder, and it started working. Then I started adding them back into the 'Used' folder. When I got to the end and they were all back in there it still works. Go figure...
Reply With Quote
  #7  
Old 05-24-2014, 07:59 AM
PrrLl PrrLl is offline
Member
 
Join Date: Feb 2011
Location: Denmark
Posts: 1
Default Re: How do I launch co-install of PT10?

Quote:
Originally Posted by touch View Post
**UPDATE** - Downloaded separate 10.3.8 installer and PT10 crashed on launch. So I moved plugins to the 'Unused' folder and 10 launched. Moved plugins back to the 'Used' folder, and it still works.
Thanks! This helped me, too. PT 10.3.7 & 10.3.9 was "quitting unexpectedly" even before startup, and this bandying with the plugins (taking them out, then putting them back to the Plug-Ins folder) seems solving the problem.

Cheers!
Reply With Quote
  #8  
Old 05-24-2014, 09:46 AM
soundboy35 soundboy35 is offline
Member
 
Join Date: Mar 2001
Location: Depends
Posts: 1,306
Default Re: How do I launch co-install of PT10?

You should check the docs, looks like Lion is not supported for PT11 or the co-install
http://avid.force.com/pkb/articles/e...m-Requirements
__________________
MacBook Pro 15in, 2.3gHz,i7
PT 2021.x
PT12.8.x
Reply With Quote
  #9  
Old 05-24-2014, 10:02 AM
Bruce Paine Bruce Paine is offline
Admin Emeritus
 
Join Date: Apr 1998
Location: Carmel, CA
Posts: 2,864
Default Re: How do I launch co-install of PT10?

Quote:
Originally Posted by PrrLl View Post
Thanks! This helped me, too. PT 10.3.7 & 10.3.9 was "quitting unexpectedly" even before startup, and this bandying with the plugins (taking them out, then putting them back to the Plug-Ins folder) seems solving the problem.

Cheers!
The first thing that comes to mind for me is that the 4GB RAM limit in the 32-bit Pro Tools 10 application can cause Pro Tools to run out of memory when 1st loading a lot of plug-ins. The solution you mentioned would work, and what I have had work in the past is relaunching until the plug-ins database has been completed.
__________________
Bruce Paine
System Details
Reply With Quote
  #10  
Old 05-24-2014, 12:52 PM
nigelpry's Avatar
nigelpry nigelpry is offline
Member
 
Join Date: Dec 2008
Location: Home
Posts: 2,166
Default Re: How do I launch co-install of PT10?

Bruce, I've had exactly the same. Just persevering and relaunching PT10 after it fails is the solution.

When you watch the progress of plugins being scanned, as shown on the splash screen, it gets further each time. Eventually, in my case after 4 relaunches, it gets all the way through the scan. After that, no problems launching subsequently. I've had that with every iteration of PT10 for a while, just got used to it whenever a new version of PT10.x cones out.
__________________
Mac Pro 2009 with 2010 firmware, 12-Core 3.46ghz, 64gb RAM & working Thunderbolt, OS 10.14.6 and Windows 10
iMac 2012 27", 3.4ghz i7, 32gb RAM OS 10.14.6
Digi 003 Console for control surface only, Focusrite OctopreLE and MOTU Traveler for extra analog-ADAT conversion, UAD Apollo Quad Silver with Thunderbolt card, Apollo x4 and pci-e Octo, Adam A77X monitors.
Pro Tools 2022.4, Media Composer 8.9, Sibelius 8.7, Cubase Pro 11, Wavelab Pro 11, Logic Pro X 10.5.1, Mainstage 3.
Various apps, soft synths, FX plugins.
Plenty of hardware synths, rack gear, microphones etc.
And then there's the studio ;-)
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
PT10.3.8/PT11.1.1 launch issues... cwhite771 macOS 16 06-27-2014 06:30 AM
Co-Install PT11/10.3.8 - Can't launch PT10 - Help kentuckyben macOS 2 01-07-2014 02:18 PM
my new pt10 wont launch... evoyzey Pro Tools 10 15 12-27-2012 12:22 PM
PT10 upgrade won't launch in HD seafra macOS 3 11-09-2012 07:06 PM
West Aussie PT10 launch Draulym Pro Tools 10 3 11-14-2011 10:29 PM


All times are GMT -7. The time now is 01:40 AM.


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com