10.4 .8 & Pro Tools 7 LE

I can see from other posters on here there are a lot of issues with the update 10.4.8
I am afraid i am also having issues with my Pro Tools 7 LE I'm not sure if it started when i installed the 10.4.8 update but now whenever i go to open Pro Tools it crashes
At the top of the problem report i get
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000006
I have been working with the Digidesign tech support to try & resolve this issue since thursday last week when the problem started since then i have removed everything from the usb ports Including removing the PCI card i use for 4 more usb ports Leaving me with the 3 usb ports i have on my G5 & all i had plugged into them was the Mbox my keyboard & my Ilok
I also removed my soundcard & also removed Logic Pro as according to Digidesign the latest update is supposed to have issues with Pro Tools
i then uninstalled Pro Tools then reinstalled it i got the same result
I repaired disc permissions after each stage i tried
Digidesign e mailed me this morning & told me that 10.4.8 was untested with Pro Tools & that this could be the issue & advised i reverted back to 10.4.7
How can i do this do i have to reinstall OS X from the beggining & update to 10.4.7 or is there a way of reverting back from my current OS X
Also is there a way i can reset my G5 would i have to perform a clean install & start all over again or is there a way of resetting & keeping all the items i have installed
Help Please
Powermac G5 2.5Ghz dual Mac OS X (10.4.8)

Easiest is to boot with your install disk and do an Archive & Install installation (see http://docs.info.apple.com/article.html?artnum=107120 for details), saving user and network settings. Then, run the 10.4.7 COMBO update. Alternatively, use applications that have been updated for 10.4.8. I don't know Pro Tools, but this is pertinent: 10.4.8 was untested with Pro Tools.

Similar Messages

Recording Voice-Over via Final Cut Pro and Recording Via Pro Tools?

Hey all,
I'm recording some voice-over for a documentary shot on DV.
Here's my question: all other factors being the same, is there any disadvantage in terms of audio quality of recording into Final Cut (through an m-box2) using the voice-over tool, or recording into M-Powered Pro Tools using the mbox 2 (and then bringing the file to Final Cut)?
Pro Tools obviously allows for a far more sophisticated treatment of the sound after it has been imputed - but in terms of using it for capture?
I know that Pro tools allows 24bit recording, but I'd probably record at 16bit anyway so as to match the sample rate of the rest of my audio in the project.
I'd be using the same mic-xlr-mbox2 set-up and the same computer, does anyone have any views on the difference in the quality of the recorded audio?
Thanks
Richard O'Sullivan
San Francisco

actually an in point by itself won't help you
a valid recording range needs both In and Out point, or simply a clip in the timeline which by its presence denotes the recording range
the recording range must be less than 5 minutes
in a blank timeline some like to throw a slug in there to mark the recording range, i find it easiest to just enter a duration in the canvas (i type 4.. in the duration field at top left of the canvas and it automatically marks a 4 minute range)

Problems with Mac OSX 10.5.2 and installing my pro tools le 7.1.1

Problems with Mac OSX 10.5.2 and installing my pro tools le 7.1.1.
My garage band & reason software don´t open anymore giving me a error messasge regarding the midi drivers in the operating system.
Please help!!!
Thanks,
Paolo

Somewhere at either Macworld or here I learned that DVDSP 2, DVDSP 3 and now DVDSP 4 "internally" are major re-writes.
Support for HD among a few other items along with QT 7 which comes with Tiger means sincerely that one set of applications/OS is not going to be stable.
Personally I think of all the issues possible its DVDSP vs QT.
Unless you move to DVDSP v4 the alternative is to wipe the disk and go back to Jaguar (10.2) or perhaps Panther but avoid upgrading QT beyond 6. I advocate wiping the disk because I'n not sure an archive and install to down shift to an earlier version of the OS is possible. If it is I'd still worry about mis-matched files in all sorts of locations.

Pro Tools -9073 error, when I want to listen the track I import appears the error!!! Help!!!

I recently chance my iMac Hard Disc, cause it crashes...!
Whe I initialize Pro Tools everything is working cool...But When I try to listen my sessions.. I can listen like 5 -10 seconds and then stops and appears me this:
DAE can't get audio from the drivers fast enough. Your drive may be too slow or fragmented, or a firewire drive could be having trouble due to the extra firewire bandwidth or CPU load. (-9073)
Anyone can help me??? Cause my Hard disk its new, 85% empty, full RAM memory, and before the HD crashes, I recorded a lot with many pluggins in the mixes. Now I dont put pluaggins and ver worst.
Thanks!!

Note that updates on the Open Source / Partner update center are not officially supported or endorsed by Oracle. If you encounter issues with them, you should uninstall them.
From service update 2 onwards, this update center is disabled by default in the "automatic check for updates" balloon that appears on startup.
Thanks,
Brian

Having a problem with Pro Tools and Quiktime may be the cause. Need advice.

I recently installed Pro Tools recording software on my Mac and everytime I try and open the program I get a kernel panic "restart" screen. I have been told that it may have something to with my Quiktime version.
I am running
OSX version 10.4.7
Pro Tools version 7.1
and Quiktime version 7.0.4
Could this be my problem? thanks

A fax file is simply a TIFF file. If you converted it to a PDF (you did not give any info on your workflow), then you have a graphic. The conversion to Excel will also be a bunch of graphics I guess. You would need to run OCR first. Even then you may not get the column information and may have to copy column by column using alt key when selecting the text. That allows you go copy a column.

Logic 7.1.0 Won't open after installing Pro Tools 6.9.2

i just installed Pro Tools 6.9.2 and now Logic won't open at all. i get an 'send error report" window. I'm using a G5 dual 2.0, OS10.4.2, 002r, Logic 7.1.0 and Pro Tools 6.9.2. Is the Pro tools version i'm using not compatible with Logic. i can't even get into logic to change settings.
I was warned about digi hardware but i went with it anyway. Please help. Thank you.

here is the crash log
OS Version: 10.4.2 (Build 8C46)
Report Version: 3
Command: Logic Pro
Path: /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
Parent: WindowServer [67]
Version: 7.1.0 (7.1.0(877))
Build Version: 1A73
Project Name: LogicPro710_ApplicationData
Source Version: 900001
PID: 1731
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000020
Thread 0 Crashed:
0 <<00000000>> 0xfffeff18 objcmsgSendrtp + 24
1 com.apple.AppKit 0x937794a0 -[NSProgressIndicator dealloc] + 332
2 com.apple.AppKit 0x9360eacc -[NSView release] + 200
3 com.apple.Foundation 0x92859708 NSPopAutoreleasePool + 536
4 com.apple.logic.pro 0x004e3614 0x1000 + 5121556
5 com.apple.logic.pro 0x002327cc 0x1000 + 2299852
6 com.apple.logic.pro 0x00121114 0x1000 + 1179924
7 com.apple.logic.pro 0x002ed798 0x1000 + 3065752
8 com.apple.AE 0x91450a40 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 208
9 com.apple.AE 0x914508dc dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 44
10 com.apple.AE 0x91450734 aeProcessAppleEvent + 284
11 com.apple.HIToolbox 0x93126324 AEProcessAppleEvent + 60
12 com.apple.HIToolbox 0x9316a184 ProcessHighLevelEvent + 140
13 com.apple.HIToolbox 0x9316a0dc StandardApplicationEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 328
14 com.apple.HIToolbox 0x931229f4 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 692
15 com.apple.HIToolbox 0x9312214c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372
16 com.apple.HIToolbox 0x93121fc8 SendEventToEventTargetWithOptions + 40
17 com.apple.HIToolbox 0x9312930c ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 704
18 com.apple.HIToolbox 0x93122c44 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1284
19 com.apple.HIToolbox 0x9312214c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 372
20 com.apple.HIToolbox 0x93128ed0 SendEventToEventTarget + 40
21 com.apple.HIToolbox 0x93169e00 ToolboxEventDispatcher + 92
22 com.apple.HIToolbox 0x93169d8c HLTBEventDispatcher + 16
23 com.apple.HIToolbox 0x93168340 RunApplicationEventLoop + 148
24 com.apple.logic.pro 0x002f46b4 0x1000 + 3094196
25 com.apple.logic.pro 0x00121dd4 0x1000 + 1183188
26 com.apple.logic.pro 0x00005a08 0x1000 + 18952
27 com.apple.logic.pro 0x00005838 0x1000 + 18488
Thread 1:
0 libSystem.B.dylib 0x9000a778 machmsgtrap + 8
1 libSystem.B.dylib 0x9000a6bc mach_msg + 60
2 com.apple.CoreFoundation 0x9074b3d8 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x9074acdc CFRunLoopRunSpecific + 268
4 com.apple.CoreFoundation 0x9075a13c CFRunLoopRun + 52
5 com.apple.logic.pro 0x0038d2f8 0x1000 + 3719928
6 libSystem.B.dylib 0x9002c3d4 pthreadbody + 96
Thread 0 crashed with PPC Thread State 64:
srr0: 0x00000000fffeff18 srr1: 0x100000000200f930 vrsave: 0x0000000000000000
cr: 0x44022242 xer: 0x0000000020000000 lr: 0x00000000937794a0 ctr: 0x000000009287e4ec
r0: 0x0000000093779478 r1: 0x00000000bfffeaa0 r2: 0x0000000001b75d60 r3: 0x0000000001b75d60
r4: 0x0000000090a16918 r5: 0x0000000000000000 r6: 0x0000000001b95d95 r7: 0x00000000000095a5
r8: 0x0000000000000001 r9: 0x00000000a072970c r10: 0x00000000000012bb r11: 0x000000006f5f6918
r12: 0x0000000000000000 r13: 0x0000000000000002 r14: 0x0000000000000000 r15: 0x00000000a3122758
r16: 0x0000000001b3ad20 r17: 0x00000000bffff6f0 r18: 0x0000000065707063 r19: 0x0000000000000001
r20: 0x0000000001b3b120 r21: 0x00000000bffff4e0 r22: 0x00000000bffff550 r23: 0x0000000000000000
r24: 0x00000000bffff540 r25: 0x0000000001b50f74 r26: 0x0000000061657674 r27: 0x0000000000000001
r28: 0x0000000000000001 r29: 0x00000000a362f68c r30: 0x0000000001b95b10 r31: 0x0000000093779354
Binary Images Description:
0x1000 - 0xb8dfff com.apple.logic.pro 7.1.0 (7.1.0(877)) /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
0x1fe5000 - 0x1ff2fff com.apple.iokit.IOUSBLib 2.2.0 /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle/Co ntents/MacOS/IOUSBLib
0x695b000 - 0x696cfff com.apple.iokit.IOHIDLib 1.4.0 /System/Library/Extensions/IOHIDFamily.kext/Contents/PlugIns/IOHIDLib.plugin/Co ntents/MacOS/IOHIDLib
0x10000000 - 0x100d2fff com.apple.AECore 1.1.1 /Applications/Logic Pro.app/Contents/Frameworks/AECore.framework/Versions/A/AECore
0x11000000 - 0x1105cfff com.apple.LoopCore 1.1.1 /Applications/Logic Pro.app/Contents/Frameworks/LoopCore.framework/Versions/A/LoopCore
0x12000000 - 0x1201bfff com.apple.DfSearchEngineWrapper 1.1.1 /Applications/Logic Pro.app/Contents/Frameworks/DfSearchEngineWrapper.framework/Versions/A/DfSearch EngineWrapper
0x20000000 - 0x20056fff com.apple.LogicLoopBrowser 1.0 (1.6) /Applications/Logic Pro.app/Contents/Frameworks/LogicLoopBrowser.framework/Versions/A/LogicLoopBrow ser
0x8fcda000 - 0x8fdb2fff com.apple.prokit 3.1 (589) /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit
0x8fe00000 - 0x8fe51fff dyld 43.1 /usr/lib/dyld
0x90000000 - 0x901a6fff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x901fe000 - 0x90202fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
0x90204000 - 0x90257fff com.apple.CoreText 1.0.0 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
0x90284000 - 0x90335fff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
0x90364000 - 0x9069dfff com.apple.CoreGraphics 1.256.14 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x90728000 - 0x90801fff com.apple.CoreFoundation 6.4.2 (368.11) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x9084a000 - 0x9084afff com.apple.CoreServices 10.4 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x9084c000 - 0x9094efff libicucore.A.dylib /usr/lib/libicucore.A.dylib
0x909a8000 - 0x90a2cfff libobjc.A.dylib /usr/lib/libobjc.A.dylib
0x90a56000 - 0x90acafff com.apple.framework.IOKit 1.4 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90ae4000 - 0x90af6fff libauto.dylib /usr/lib/libauto.dylib
0x90afd000 - 0x90dc2fff com.apple.CoreServices.CarbonCore 10.4.1 (611.1) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x90e25000 - 0x90ea5fff com.apple.CoreServices.OSServices 4.0 (4.0.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x90eef000 - 0x90f2ffff com.apple.CFNetwork 10.4.2 (80) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x90f44000 - 0x90f5cfff com.apple.WebServices 1.1.2 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServ icesCore.framework/Versions/A/WebServicesCore
0x90f6c000 - 0x90feafff com.apple.SearchKit 1.0.3 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x9102f000 - 0x91056fff com.apple.Metadata 1.1 (121.6) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x91066000 - 0x91073fff libz.1.dylib /usr/lib/libz.1.dylib
0x91076000 - 0x91238fff com.apple.security 4.0.1 (223) /System/Library/Frameworks/Security.framework/Versions/A/Security
0x9133a000 - 0x91343fff com.apple.DiskArbitration 2.1 /System/Library/PrivateFrameworks/DiskArbitration.framework/Versions/A/DiskArbi tration
0x9134a000 - 0x91371fff com.apple.SystemConfiguration 1.8.0 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x91384000 - 0x9138cfff libbsm.dylib /usr/lib/libbsm.dylib
0x91390000 - 0x9140efff com.apple.audio.CoreAudio 3.0.1 /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x9144c000 - 0x9144cfff com.apple.ApplicationServices 10.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x9144e000 - 0x91486fff com.apple.AE 1.5 (297) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ AE.framework/Versions/A/AE
0x914a1000 - 0x9156cfff com.apple.ColorSync 4.4 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
0x915c1000 - 0x91654fff com.apple.print.framework.PrintCore 4.0 (172.1) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
0x9169a000 - 0x91757fff com.apple.QD 3.8.6 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
0x91795000 - 0x917f3fff com.apple.HIServices 1.5.0 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
0x91821000 - 0x91844fff com.apple.LangAnalysis 1.6 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
0x91858000 - 0x9187dfff com.apple.FindByContent 1.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ FindByContent.framework/Versions/A/FindByContent
0x91890000 - 0x918d1fff com.apple.LaunchServices 10.4.3 (157) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices
0x918ec000 - 0x91900fff com.apple.speech.synthesis.framework 3.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x9190e000 - 0x91944fff com.apple.ImageIO.framework 1.0.2 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
0x91958000 - 0x91a1afff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib
0x91a66000 - 0x91a7bfff libcups.2.dylib /usr/lib/libcups.2.dylib
0x91a80000 - 0x91a9cfff libJPEG.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x91aa1000 - 0x91b10fff libJP2.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x91b27000 - 0x91b2bfff libGIF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x91b2d000 - 0x91b45fff libRaw.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRaw.dylib
0x91b48000 - 0x91b8bfff libTIFF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x91b92000 - 0x91babfff libPng.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
0x91bb0000 - 0x91bb3fff libRadiance.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x91bb5000 - 0x91bb5fff com.apple.Accelerate 1.1.1 (Accelerate 1.1.1) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x91bb7000 - 0x91ca1fff com.apple.vImage 2.0 /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
0x91d34000 - 0x91d54fff libmx.A.dylib /usr/lib/libmx.A.dylib
0x91d5a000 - 0x91dbffff libvMisc.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x91dc9000 - 0x91e5bfff libvDSP.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
0x91e75000 - 0x92405fff libBLAS.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
0x9244d000 - 0x9275dfff libLAPACK.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x9278a000 - 0x92815fff com.apple.DesktopServices 1.3 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x92857000 - 0x92a80fff com.apple.Foundation 6.4.1 (567.12) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x92b9e000 - 0x92c7cfff libxml2.2.dylib /usr/lib/libxml2.2.dylib
0x92c9c000 - 0x92d8afff libiconv.2.dylib /usr/lib/libiconv.2.dylib
0x92d9c000 - 0x92dbafff libGL.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x92dc5000 - 0x92e1ffff libGLU.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x92e3d000 - 0x92e3dfff com.apple.Carbon 10.4 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x92e3f000 - 0x92e53fff com.apple.ImageCapture 3.0 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
0x92e6b000 - 0x92e7bfff com.apple.speech.recognition.framework 3.4 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x92e87000 - 0x92e9cfff com.apple.securityhi 2.0 (203) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
0x92eae000 - 0x92f35fff com.apple.ink.framework 101.2 (69) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
0x92f49000 - 0x92f54fff com.apple.help 1.0.3 (32) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
0x92f5e000 - 0x92f8bfff com.apple.openscripting 1.2.2 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
0x92fa5000 - 0x92fb5fff com.apple.print.framework.Print 4.0 (187) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
0x92fc1000 - 0x93027fff com.apple.htmlrendering 1.1.2 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
0x93058000 - 0x930aafff com.apple.NavigationServices 3.4.1 (3.4) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
0x930d6000 - 0x930f3fff com.apple.audio.SoundManager 3.9 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
0x93105000 - 0x93112fff com.apple.CommonPanels 1.2.2 (73) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
0x9311b000 - 0x9342bfff com.apple.HIToolbox 1.4.2 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x93576000 - 0x93582fff com.apple.opengl 1.4.0 /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x93587000 - 0x935a9fff com.apple.DirectoryService.Framework 2.0 /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
0x935f4000 - 0x935f4fff com.apple.Cocoa 6.4 (???) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x935f6000 - 0x93c27fff com.apple.AppKit 6.4.1 (824.1) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x93fb3000 - 0x9401dfff com.apple.CoreData 1.0 (46) /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x94055000 - 0x9411ffff com.apple.audio.toolbox.AudioToolbox 1.4.1 /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x94173000 - 0x94173fff com.apple.audio.units.AudioUnit 1.4 /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x94175000 - 0x942d4fff com.apple.QuartzCore 1.4.1 /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x9431c000 - 0x94359fff libsqlite3.0.dylib /usr/lib/libsqlite3.0.dylib
0x94361000 - 0x943acfff libGLImage.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
0x943eb000 - 0x9442efff com.apple.bom 8.0 (85) /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
0x94563000 - 0x9456ffff libCSync.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x945b4000 - 0x945c8fff libRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x945ce000 - 0x94838fff com.apple.QuickTime 7.0.3 /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
0x94a0f000 - 0x94b3cfff com.apple.AddressBook.framework 4.0.2 (475) /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
0x94bcd000 - 0x94bdcfff com.apple.DSObjCWrappers.Framework 1.1 /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWra ppers
0x94be4000 - 0x94c0bfff com.apple.LDAPFramework 1.4 (68) /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
0x94c11000 - 0x94c21fff libsasl2.2.dylib /usr/lib/libsasl2.2.dylib
0x94c25000 - 0x94c53fff libssl.0.9.7.dylib /usr/lib/libssl.0.9.7.dylib
0x94c63000 - 0x94c80fff libresolv.9.dylib /usr/lib/libresolv.9.dylib
0x95078000 - 0x95078fff com.apple.DiscRecording 3.0 (???) /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
0x9507a000 - 0x950fafff com.apple.DiscRecordingEngine 3.0 /System/Library/Frameworks/DiscRecording.framework/Versions/A/Frameworks/DiscRe cordingEngine.framework/Versions/A/DiscRecordingEngine
0x95126000 - 0x9516bfff com.apple.DiscRecordingContent 3.0 /System/Library/Frameworks/DiscRecording.framework/Versions/A/Frameworks/DiscRe cordingContent.framework/Versions/A/DiscRecordingContent
0x95c47000 - 0x95c49fff com.apple.ExceptionHandling 1.2 (???) /System/Library/Frameworks/ExceptionHandling.framework/Versions/A/ExceptionHand ling
0x9672c000 - 0x9676bfff com.apple.audio.midi.CoreMIDI 1.5 (41) /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
0x96b53000 - 0x96b72fff com.apple.vecLib 3.1.1 (vecLib 3.1.1) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
Model: PowerMac7,3, BootROM 5.1.8f7, 2 processors, PowerPC G5 (2.2), 2 GHz, 512 MB
Graphics: GeForce FX 5200, GeForce FX 5200, AGP, 64 MB
Memory Module: DIMM0/J11, 256 MB, DDR SDRAM, PC3200U-30330
Memory Module: DIMM1/J12, 256 MB, DDR SDRAM, PC3200U-30330
Modem: Jump, , V.92, Version 1.0,
Network Service: Built-in Ethernet, Ethernet, en0
Serial ATA Device: ST3160023AS, 149.05 GB
Serial ATA Device: WDC WD2000JD-22HBC0, 186.31 GB
Parallel ATA Device: SONY DVD RW DW-U21A, 249.55 MB
USB Device: XSKey, Emagic GmbH, Up to 1.5 Mb/sec, 500 mA
USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
USB Device: USB/PS2 Wheel Mouse, Kensington, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA
FireWire Device: Digi 002Rack, Digidesign, Up to 400 Mb/sec

Trying to run Tiger on an external drive for Pro Tools LE on a new iMac...

okay, i am buying an mbox2 that runs pro tools LE (which, as we all know, is not yet supported by leopard), and i am also buying an iMac 20-inch 2.0GHz Intel Core 2 Duo, ATI Radeon HD 2400 XT with 128MB memory (with leopard pre-installed). i've read in some forums that people have been formatting an external firewire 800 drive an installing tiger on it so as to use it as the startup disc when running pro tools LE. i basically have two questions regarding this:
1) does anyone think this would not work? why? and
2) will i be able to install tiger on the external drive using my macbook pro osx install disc that came with my laptop? (it's a tiger 10.4.8 install disc, but it does say "macbook pro" on it, so i'm wondering if apple doesn't allow you to install these on anything other than the laptops). my laptop is a macbook pro 2.16 GHz intel core duo.
thanks in advance for your help. please let me know if there's any other information i need to provide.
-mike

I run my Pro tools from an external drive on my iMac and have no problems. Digidesign say this:
+To use Pro Tools LE 7.x currently, you will need to boot from a Mac OS X 10.4 (Tiger) startup system.+
+If you choose to upgrade to Mac OS X 10.5 (Leopard), you will need to install Leopard on a separate hard drive or drive partition.+
+If you purchase a new Mac with Mac OS X 10.5 preinstalled, you will need to install Mac OS X 10.4 (Tiger) on a separate hard drive or drive partition.+
+If you are purchasing a new Mac with Mac OS X 10.5 preinstalled, check with Apple to see if your computer is able to boot from Mac OS X 10.4.+
You may well have problems using your MBP disks however. I would suggest buying a copy of Tiger.

Beige G3 with Pro Tools Freezes Every Time I Use PT (why I have the G3)

Please, if anyone can help....
I GOT my beige G3 running which had died and refused to reboot when last I had tried running Pro Tools. I GOT Pro Tools 6.1 reinstalled and running... and then when I was back in Pro Tools again on my newly-running system, I tried to "Save Session Copy" (including saving audio files), it froze. It seems whenever I ask Pro Tools (specifically, haven't had this problem with ANY other memory-intensive program) to do something even mildly memory-intensive, it freezes. Not just the program freezes, the whole computer does. And once again, the computer then refused to reboot. I tried running First Aid and Repair Permissions and so forth booting from the OS X.2 CD. No dice. I erased the 7.8 gig section (the bootable section) of the hard drive. Tried to re-install the OS. It freezes mid-install every time now. Didn't used to freeze (though always bogged down a bit from time to time). Then I tried erasing the WHOLE 120 gig disk (while weeping bitterly) and re-partitioning the 3 sections (as a Mac-person-who-knows-more-than-me instructed me to do- - was the only thing that worked- - the first section being 7.8 gigs) and reinstalling the OS. Still freezes when I try to install. I have to move the mouse around frantically just to keep the computer from freezing while erasing the drive (this actually works- - moving the mouse around).
I tried putting the 3 sticks of ram in different order- - they worked fine before- -the 3 sticks of RAM collectively add up to 600-something- 1 stick of 128 and 2 of 256 or whatever that amount is- - the 2 were originally bought for a "stripped" blue and white I had bought, but the blue and white makes heinous buzz-beeping sounds when I tried to run it most recently, though it worked for a while before. Also, the beige worked fine before with these same sticks of RAM installed, but this seemed maybe memory-related so I thought I'd experiment...?
Anyway, I have A LOT of extras plugged into this thing. The one that acts the most buggy is the TDK DVD-R drive I installed a couple years ago. The model is "Indi" something or other as I recall. It has always consistently done this weird thing where, after booting the computer, if you eject one disk (it will only eject if you drag to the trash) and insert a second disk (since booting), it will not allow you to eject the 2nd disk until you reboot again. If you drag that 2nd disk to the trash, the CD icon disappears from the desktop as though it's been ejected, but the drive does not physically eject. I just put up with it, because I could deal and there had been so many other issues, and everything was working, this seemed like a non-issue by comparison.
I am also running a PC monitor via a small adapter (not a card). I have a USB PCI card going (which the mouse is plugged into)- never had a problem, but now sometimes the mouse freezes on startup too and won't move and I have to force-power-down with that button on the front as if it didn't boot properly. I have an Audio Media III PCI card in there (for Pro Tools). I have the monitor card in there, but don't need it for this machine. Was trying to test if it worked-- last I tested, it didn't-- I should obviously just pull it out.
Anyway, I'm having a ** of a time getting the OS back on there, and even if I do, once I put Pro Tools back on (the point of doing all of this and using the machine at all), it will likely freeze again and I'll be right back where I am right now. If I can even get there in the first place.
Please please please help...
Blue and White G3 Mac OS X (10.2.x)

Conventional wisdom for installing 10.2 Jaguar is to strip the machine back to the minimum Apple might have shipped in it, Install the OS, then add your extras back in.
Memory seems to be a big issue -- I suggest you use the free DIMM First Aid under Mac OS 9 to scan your DIMMs and be sure they are OK for your Mac, and not too slow:
http://www.mactcp.org.nz/dimmfirstaid.html
I have found 10.3 Panther much simpler and more pleasant to install (even if you had to use XPostFacto 3.1 to do it) than 10.2 Jaguar ever was.

Final Cut, Quicktime, and Pro Tools conflicts

Hi there,
I'm working on a "situation" I recently encountered, and wonder if anybody else has had this problem.
I'm trying to upgrade Pro Tools LE to version 6.9.2 with the install discs that were sent to me from Digidesign, and it's wreaking havoc with Final Cut Pro and Quicktime.
Initially when I installed the upgrade, I was running OSX 10.4.2, FCP 5.0.3 and QT 7.0.2. The Pro Tools upgrade worked fine, as did FCP when I launched it, but Quicktime wouldn't launch- spinning beachball forevermore.
So after doing all the basics- trashing pref's and render files, repairing permissions, etc.- and finding QT still wouldn't work, I tried upgrading to QT 7.0.3.
Once I did that, QT still wouldn't work, and Final Cut Pro would no longer launch. It just hung on the application startup screen, at no particular point each time.
I then upgraded to FCP 5.0.4, and as well OS 10.4.3. No luck. I installed the Pro Application Support updates 2005-02 1.0, and 3.1, and still no luck.
Since there is not yet a downgrade from QT 7.0.3 to 7.0.2, I ran the 7.0.2 to 7.0.1 installer, and downgraded to QT 7.0.1. QT still wouldn't launch, and FCP still hung on launch but this time it hung at the point where it was loading audio filters.
I tried removing the audio filters from their folders to see if it would launch then, but that didn't work. At this point, the only thing I could think to do was to uninstall Pro Tools altogether (safe uninstall, not clean uninstall) and this is what finally brought Quicktime and Final Cut back to life. Great, because I use FCP and QT everday, but I no longer have the use of Pro Tools.
Throughout this process I made sure to diligenty repair permissions, trash prefs, and restart whenever I made a change.
So I'm not sure at this point how to get Pro Tools LE 6.9.2, Final Cut Pro 5.0.4, and Quicktime (any version above 7.0) to work harmoniously, and I'm unable to spare any more troubleshooting time for a week or so because there are of course, projects due.
Has anybody else encountered these oddities?
Thanks a lot,
Joni

Hi, Joni C
I'm Bump,
I'm having the same trouble, I have FCP I'm running it on a G5 power Mac dual 2.5 ghz with 2.5 gb of memory, my os is 10.4.4. I also have Quicktime pro 7.0.3 and I have Pro Tools LE 7.0, every time I try to use FCP it starts and about five sec. later it shuts back down. I also have a Universal Audio UAD pci card that runs audio plugins and I also have fxpansion program it converts my vst & Au plugins to rtas for pro tools le. IBefore I installed FCP I wiped my hard drive and re installed a fresh version of tiger 10.4 and then I installed FCP studio, then Pro Tools, then all plugin and kept checking to make sure every thing was working correctly and then the U audio stuff with the Vst to rtas wrapper and it all was working fine. I even did the full final cut tutorial still worked fine. Yesterday out of no where final cut just stop working and still all the other programs work fine like dvd studios, soundtrack, motion, pro tools. If you can shead any light on this I would be very greatful
Bump

OSX 10.8.5 + Pro Tools 10: Very strange issues - Firewire audio interface

I'm facing weird issues on my new system.
When I received my new iMac, I firstly used Migration Assistant. It didn't work well so I did a clean install. I installed the Digi003 drivers first, then PT, then all the plugins. Everything is up to date. Interface and computer are connected with a Firewire 400/800 cable and a brand new Thunderbolt/Firewire adapter. The computer is used for music production only and the hard drive is almost empty (not much data).
I know the Digi003 works fine as I used it with my former iMac which was a Core2Duo 3gHz with 4Go RAM running OSX 10.6.8 and PT 10.0.0. I used to set the buffer size on 128 to record audio. It worked well.
THE PROBLEMS ARE:
1- DigiAudioCore does not auto-launch anymore. If want to play a song with VLC, I have to manually launch DigiAudioCore.
2- PT stops (-6086) if I record with the buffer size set on 128. Buffer size on 256 is the minimum and PT still bugs sometimes even if there is only one track and no plugins in a 44.1kHz / 24bits session.
3- CPU spikes too if I have just a couple of plugins engaged.
4- I did some tests with an RME Fireface 800 and a Motu 828 MKII and I got the same issues (-6101). I still have to do a test with an USB interface.
5- Sometimes the iMac bugs when I open the System Prefs but it works normally after a few seconds.
I don't know what are the causes but it seems that there is a bandwidth problem caused by Thunderbolt/Firewire connection. I tried a brand new FW800 cable between the Fireface 800 and the computer but I got the same issues. Maybe the hard drive???
So now I really need some help to solve once for all these problems. I hope I don't have a do a clean install again!!!
Thanks in advance.
COMPUTER SPECS
iMac 27" bought october 2013
Processor: i7 3.5gHz (Turbo boost 3.9gHz)
Memory: 32Go RAM DDR3
Hard drive: Fusion Drive 1To
OSX: Mountain Lion 10.8.5
INTERFACE & DAW
Digi003 Rack+ (drivers up to date)
Pro Tools 10.3.7

Back up all data immediately as your boot drive may be failing.
This diagnostic procedure will query the system log for messages that may indicate a hardware fault. It changes nothing, and therefore will not, in itself, solve your problem.
If you have more than one user account, these instructions must be carried out as an administrator. I've tested them only with the Safari web browser. If you use another browser, they may not work as described.
Triple-click anywhere in the line below on this page to select it:
syslog -k Sender kernel -k Message CReq 'Channel t|GPU D|I/O|n Cause: -' | tail | open -ef
Copy the selected text to the Clipboard (command-C).
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V).
The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
A TextEdit window will open with the output of the command. Normally the command will produce no output, and the window will be empty. If the TextEdit window (not the Terminal window) has anything in it, post it — the text, please, not a screenshot. The title of the TextEdit window doesn't matter, and you don't need to post that.

How do I export detached audio files as separate files, for Pro Tools processing?

My project is a live band performance. I have every song as a separate Event with associated audio. I have detachd all the audio from all the video Events. I now want to Export the audio files to Pro Tools for editing, then Import the edited audio back into FCP X and snap the edited audio to the associated video Events.
My problem is this: FCP X keeps exporting the audio as a single large WAV file, rather than as separate WAV files. In fact, the video events are separate, and so the audio associated with the video Events are separate.
I first renamed the Role of every audio file as "Music", then did a Share --> Export Media of all "Music" audio Roles. After exporting, I found it was one large WAV file, rather than separate files of different sizes.
As a 2nd try, I created Sub-Roles for each audio clip, and named each one with a distinct Sub-Role name. I then Exported all these Sub-Roles (yes, tedious). The result was that every exported WAV file was the same size, the same as the file size in my first try. The only audio that could be heard in each file was the audio in that particular song, but FCP X still created the very large file with silence in all the rest of the file. Since the file lengths don't match the original audio fil lengths, there will be a problem when I Import the edited files back into FCP X and want to Snap them into place.
Question:
How can I export the individual detached audio clips as separate files, the length of each file equaling the length of the original audio file in FCP X?
Do I need to separate the detached audio into separate Layers visually in the Project Timeline, so they are not touching? Or does this matter?
Help!!

Michael Holmes1 wrote:
I have to record all the color changes I make in one Project, so I can repeat them in the other 17 projects, etc.
No.
You need to explore Compound Clips. This workflow may or may not be of help.
Select an Event with clips in it and press Option+G to make a (blank) compound clip.
Select the Event Browser, create a new Event and call it 'Effects'.
Drag the Compound Clip into this Event.
Right-click the clip and select 'Open in Timeline'.
Select the timeline and press Option+W. This will add a Gap Clip to the timeline.
Select the gap clip and press Ctrl+D then type in the duration you want the clip to be.
Now open a project and select and copy one of the clips with effects etc.
Open the Compound Clip in the Timeline again, select the gap clip and press Option+Cmd+V to paste the effects into your Compound Clip.
This clip is now saved in your Browser and will remain there for you to copy and then paste the effects into any clip in any project.
It's a bit clunky, but it works - and once you learn about Compound Clips, you can work wonders with them. As an example, if you want to add more effects without overwriting the effects in the Compound Clip, simply make the Compound Clip into a Compound Clip (again) and add the effects. They will be added to the original effects.
Andy.

G5 Quad Pro Tools HD 7 System Crashes on Launch of Logic Pro 7. WHY?

Updated to Logic Pro 7.1.1
Program gets to Launching DAE on the startup screen and then unexpectedly quits.
G5 Quad Mac OS X (10.4.8) Pro Tools installed
G5 Quad Mac OS X (10.4.8) Pro Tools installed

Hi,
you have to install at least Logic Pro 7.2 to be compatible with ProTools 7 at all, this version is not backwards compatible with ProTools 6.
http://docs.info.apple.com/article.html?artnum=302969
Logic Pro 7.1.1 is compatible with ProTools 6, but not 7.
http://docs.info.apple.com/article.html?artnum=302757
You will find this kind of information here:
http://www.apple.com/support/logic/
Best,
21th

Why can't I get Pro Tools LE to create a session on my new iMac?

Summary
I can't get Pro Tools LE to open a session on my brand new iMac.
Detail
Pro Tools launches but when I go to create a session it seizes up, the beach ball spins and I have to Force Quit and send yet another note to the Apple teacher. It does this without fail. I've tried to rectify this by saving to different locations and different external hard drives. The problem remains the same.
I've tried uninstalling/reinstalling, stripping the computer of anything that says "digidesign," etc... it doesn't work.
I am using the same Pro Tools with the same OS and the same Digidesign hardware on a MacBook Pro without a problem. Go figure.
_*The Kit*_
_The Troubled Computer_
iMac
Version: OS X 10.6.1 Snow Leopard
Processor: 2.66 GHz Intel Core 2 Duo
Memory: 4 GB 1067 MHz DDR3
Startup Disk: Macintosh HD
_The Untroubled Computer_
MacBook Pro
Version: OS X 10.6.1 Snow Leopard
Processor: 2.4 GHz Intel Core 2 Duo
Memory: 2GB 667 MHz DDR2 SDRAM
(the previous model - all aluminium)
_The Digidesign Interface_
MBox2 / USB connection
_The External Hard Drives_
iMac: Maxtor One Touch 4 Plus 600GB / FW800 > FW400 with a converter
MacBook Pro: Maxtor One Touch 4 Plus 750GB / FW400 > FW400
_The Pro Tools LE Software_
Pro Tools LE 8.0.3
I know what you're thinking... Snow Leopard is the problem. Right?
But the MacBook Pro has proven that theory wrong. The marriage between SL and LE8 on that notebook works fine.
As for LE on the iMac... At first it was 8.0.1 but now it is 8.0.3.
I upgraded to the supposedly Snow Leopard compatible Pro Tools LE 8.0.3 (pre-release) thinking that just maybe SL and LE8 weren't having as much fun together in the iMac bed as they were in the MacBook Pro. The result was identical -- stuck in Nowheresville.
I've been to the Digidesign discussion boards and the best I've been told so far is that my 3 day old iMac is a dud. On the other hand, away from Digidesign intoxication, some of the pros in the biz around town have said it's probably Pro Tools. Pro Tools they say is, at best, troublesome.
I'm planning on bailing out of Pro Tools altogether eventually and moving to an Apogee Duet with Nuendo 4 as I'm annoyed that I spend more time as an amateur paint-by-numbers technician than actually doing the job I'm paid to do. I'm also unhappy with expensive upgrades, lost paid for plugins due to upgrades and being railroaded into buying Avid gear only as demanded by the software.
But, in the meantime... I'm stuck with it. My own suspicions are that the cause of my troubles is the external hard drive and the FW400>FW800 conversion configuration but I'm not about to blow a few hundred bucks for a new hard drive based on a hunch that may not work. Your thoughts?
Any suggestions other than anything that involves screwdrivers and a cavalier mindset with the just out of the box hardware by a complete novice such as I are most welcome.
Thanks.

Hi
I have the same problem.
First I tried PT8LE 8.0 - didn't even start, afterwards i tried 8.0.3pr (1.25GB) - the same result. Now I downloaded the 8.0.3 normal (1.6GB) and it starts, but after I get to open/create new session dialogue box it just gives me the beach ball of death...
When I force quit PT it won't even start again and gets stuck at loading plugins (and there are just the bundeled one, no third party - it's a clean install of the whole machine).
I too have a week old 27" imac i5 with 10.6.2. On my old 24" with 10.6.1 it's runnig smoothly.
My external drives were off during this so I guess it's not a thing of the FireWire ports.
So I guess it's nothing positive or helpful, but You're not alone with this

Two questions: pro tools HD compatbility. iMac vs MBP.

I'll first start off with the question regarding Pro Tools HD compatibility. When it says "compatible", what is this meaning exactly? I'm transferring to Belmont University for Music Business/Production next semester and have contacted the studio manager and he said they mainly use Pro Tools HD in the campus studios. I already have Pro Tools LE 7 with an Mbox, so I'll be able to take projects from the studio on a firewire drive into Pro Tools LE for editing.
But I'm curious if "compatible" means that I'll be able to open my projects recorded in a Pro Tools studio in Logic Pro later on or if it means that I could use Logic Pro with the Pro Tools HD interface in the studio and record directly into Logic Pro? The studio manager told me that all the studios are equipped with Powermac G5s and everything I need will be there, but I want the ability to take my stuff away on a FW drive (oh, another question...any recommendations on firewire drives?) and work independently on my own system. Which leads to my next question....
In my email to him, I also asked about the importance of owning a laptop over a desktop and he said it wasn't imperative to have a laptop since the studios were equipped with Powermacs. I know if money wasn't an issue the Powermac is the best choice for audio production, but I am a student, and I cannot afford to buy a Powermac with sufficient RAM plus a display.......I was highly considering a Macbook Pro, but after realizing that I would be carrying my hard drive around more than my computer, it has me wondering about an iMac. I know the 2 gb RAM limit is a downfall for this system, but I would have that limit in the MBP also, so that doesn't affect anything between comparing the two. I have configured both systems with the education discount and Applecare:
15" MacBook Pro: $2,898.00
-2.16GHz Intel Core Duo
-2GB 667 DDR2 - 2x1GB SO-DIMMs
-100GB Serial ATA drive @ 7200 rpm
-MacBook Pro 15-inch Widescreen Display
-SuperDrive (DVD±RW/CD-RW)
-AirPort Extreme Card & Bluetooth
-Backlit Keyboard/Mac OS - U.S. English
-AppleCare Protection Plan for MacBook Pro/PowerBook (w/or w/o Display) - Auto-enroll
-15.4-inch TFT Display
20" 2.0 GHz iMac: $2,056.00
-2GB 667 DDR2 SDRAM - 2x1GB
-250GB Serial ATA drive
-ATI Radeon X1600/256MB VRAM
-SuperDrive 8x (DVD+R DL/DVD+RW/CD-RW)
-Keyboard & Mighty Mouse + Mac OS X - U.S. English
-Accessory kit
-AppleCare Protection Plan for iMac - Auto-enroll
-20-inch widescreen LCD
-2GHz Intel Core Duo
-AirPort Extreme
-Bluetooth 2.0 + EDR
So, with portability no longer being a great concern, for system performance, which would be the best system? I will be using Pro Tools LE 7 for editing/mixing and Logic Pro for MIDI/creating music with virtual instruments. Any advice you have would be greatly appreciated.
Thanks,
Scott
12 Powerbook w/Superdrive; 512mb; 80gb; Airport Mac OS X (10.4.7)

Hey Scott.
Check out the "Benchmark Song 2" thread on this forum. That will show some performance test on different computers.
About the choice of computer, well, all I can say is get the best of what you can afford. Logic runs nicely on both those machines by all reports. I would also like to say that the Mac Pros (new Powermacs) should be out before the end of the year and will smoke both of these computers. And the price should be comparable to the MacBook Pro.
X

From iMac to Mac Pro for the good of my Pro Tools 10...

hey guys,
here's the deal : it seems I'm at a turning point with my iMac (27", 3.1 Ghz i5, 4GB memory, 1TB hard drive, lion, PT10) and I'm thinking of buying a mac pro. Problem is, I'm not sure which model is best for my needs. I do postproduction work for television and I often have to work with pretty heavy projects.
My pro tools 10 keeps giving me the same 2 errors --
1- DAE can't get audio from the drive(s) fast enough. Your drive may be too slow, or fragmented, or a firewire drive could be having trouble due to the extra firewire bandwidth or cpu load. (-9073)
2- A CPU overload error occurred. If this happens often, try increasing the "H/W Buffer Size" in the Playback Engine Dialog, or removing some plug-ins. (-6101)
I might add, my Playback Engine's maxed out and I'm barely running any plugins (some 5 or 6 EQ3s, maybe 1 or 2 L2 and a Dorrough).
I have a MOTU Audio Express which is plugged in firewire and I'm running an external drive with my SFX on it, which is also plugged in firewire. The iMac having only one firewire plug (downsizing from the earlier iMac, for some obscure reason), I have a firewire hub.
I get the first error whenever I get too deep into a project and I start having a lot of SFX and I'm looking to add more and I get the second error whenever I try to run Dolby Media Meter.
I'm pretty aware I'm overrunning my iMac, so I'm willing to pay big bucks to get a computer that's best fitted to my needs and which I'll be able to upgrade every once in a while. Now, I'm just wondering what I actually need in a computer.
It's either the 3.2 GHz quad-core intel xeon, 6GB memory, 1TB HD or the two 2.4GHz 6-core intel zeon, 12GB memory, 1TB HD. I gotta say the second one seems kind of a lot... but I don't want to spend so much money and get a tiny upgrade from where I'm at right now.
So please! All of you mac wizards and other knowledgeable folks, HELP!

An i7 3.9GHz would do if you had 32GB RAM, an SSD boot drive, and 2TB hdd.
The sweet spot today on Mac Pro is $1800 4-core special and DIY to W3690 or W3680 6-core 3.33 or higher with 32-48GB RAM. And lots of SSDs and disk drives.
http://store.apple.com/us/browse/home/specialdeals/mac/mac_pro
Refurbished 27-inch iMac 3.4GHz quad-core Intel Core i7
http://store.apple.com/us/browse/home/specialdeals/mac/imac/27
The Mac Pro line is at a - not ready to ship the new 2013 6,1 model / not ready with 10.9 that it will need / and current configuration is really 2010 3 yrs old (but also how well they hold up and mature).
You do not want to give up GHz for more cores. MHz still rules. Only reason would be if you planned to replace the processors for the fastest expensive (use to be, though changing) 4 or 6-core 3.4GHz for total of 8 or 12-cores, but never the 2.4GHz, no way.
The 2009 4,1 used is cheaper and can be found for $1000 and upgraded to 6-core and everything else (dual core upgrades are harder and not good to plan for.
And http://www.barefeats.com has done some tests on iMac and Mac Pro.
Graphics on Mac Pro, RAM and PCIe and SSD, hdd are easy upgrades.
This site has some great tips
http://www.macperformanceguide.com

How do I get Pro Tools MP9 to work with Mt. Lion 10.8.2?

I have Pro Tools MP9 installed on my IMac 27" and just today I upgraded my system software from 10.6.8 to Mountain Lion 10.8.2. Now my Pro Tools has all kinds of problems. The system software doesn't recognize the M-Powered USB audio interface or any other hardware hooked up to my Pro Tools! Safari runs real slow and had I had any idea this was going to happen, I'd have not upgraded anything as everything was working so well before. Anyone else out there have this same problem or is there anyone that can help me solve this dilema?

You might get more relevant help by contacting Pro Tools tech support. It may be as simple as an update to bring compatibility for the latest version of OS X, or some other procedure, but they would have the best info on this.

10.4 .8 & Pro Tools 7 LE

Similar Messages

Maybe you are looking for