Pro Tools Error 9073 Conundrum

Hi Everybody!
Two weeks ago I got this error during a Pro Tools session out of nowhere:
DAE can't get audio from the drive 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)
I clicked OK and Pro Tools freezed, forcing me to reboot my computer manually. After experiencing the same problem several times my external hard drive (a G-Tech, from which I had been working off of) stopped mounting all together (file structure glitch-related i think)
It would mount once a day and finally yesterday I was able to successfully reformat (erase) the entire G-Tech drive getting it to mount normally once again. I then copied back all my sessions from my backup drive...
HOWEVER, upon opening a different session I got the SAME ERROR 9073 after a minute of playback. Froze and I had to reboot. Happened a few more times and now my G-Tech external hard drive once again refuses to mount at all!
Since this all began, I have verified/repaired the disk and disk permissions of my system drive and have successfully used my backup drive to finish a session. So it appears the problem is related to the G-Tech drive. I was told its probably file structure related but it still happens after I reformatted. Also, G-Tech told me they usually don't have problems with the controllers in their drives so removing the drive out of its enclosure probably wouldn't help.
I'm stumped. I noticed everyone seems to have different experiences with the error 9073. Any ideas come to mind? Your help would be highly appreciated--Thank you for your time.
These are my System Details:
Apple MacBook Pro
Mac OSX 10.4.11
Mbox 2 mini
Pro Tools LE 7.3.1
G-Tech G-Drive FireWire800

Same thing here
insalling Pro Tools 8 on Mini Mac w/ 10.6.8
NO SUCCESS

Similar Messages

  • 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

  • OS9 Quicktime update 4.1.2 error-- Pro Tools 5.1.1

    I have a Pro Tools optimized OS9 G4 graphite (?) mac
    When I try to open Pro Tools LE, I get an error message:  
    can not be opened because "Soundlib--SoundConverterFillBuffer" could not be found.
    After googling this error message, on an Avid Forum, I found that it refers to a Quicktime 4.1.2 update that must be made before Pro Tools LE 5.1.1 can run on OS9:
    http://duc.avid.com/showthread.php?t=23094
    Ok, so, I downloaded the Quicktime update onto my MacBook laptop USB-stick, then tried to install on my OS9 G4-- but to no avail-- when trying to install, I get the following error message:
    "Quicktime Installer" could not be opened because an error type -39 occurred.
    I'm not finding anything useful on Google in regard to this "error type -39"
    I'd be eternally grateful if anyone here has any ideas on what I might try to remedy the above problems.
    A "friend" gave me this G4 to use for a inexpensive recording device-- he told me "it worked." Maybe he was wrong, or didnt wanna admit that it had this problem (?) Or maybe its something simple that anyone familiar with OS9 would know about-- I've never worked much on one of these os9 macs...

    That error is often caused by Stuffit Expander intruding where it should not, particularly when the download is in a .smi (self-mounting image) format, a format generated by Apple's Disk Copy. Stuffit Expander has ShrinkWrap technology built-in, which allows it to mount some kinds of disk images - but not .smi ones. Yet ShrinkWrap tries to - hence the error message.
    The solution - double-click Stuffit Expander, and open its Preferences (under the File menu). Select "Disk Images" from the list on the left, then turn off (uncheck) "Mount Disk Images". Quit Stuffit Expander.

  • Pro Tools CPU Error Message

    I'm running Pro Tools on a store-bought iMac G5 with a CPU speed of 1.8GHz and I am getting an error message that is stopping me from recording multiple tracks. Or, at times, after I've recorded a number of tracks, I've been rudely halted by the CPU Error message at a time when I am trying to burn a CD on iTunes. Anybody have any ideas how to get my CPU to devote all its power to Pro Tools or how else I can get by this nasty problem?

    Best thing to do is to go to duc.digidesign.com and describe (in detail) exactly what you're using (ProTools hardware, software, OS version) and exactly what the error messages are.

  • Error Code -2807 and pro tools LE

    I recently tried to upgrade From Pro tools Le 6.8.1 On an MBox 2 to Pro Tools 7 LE, so i downloaded and installed what it thought was the correct upgrade, but was infact for Pro tools M-Powered systems. After realising it was the wrong update i trashed all the files and re-installed Pro Tools LE 6.8.1.
    When i Tried to start it again it gives this message.
    The application "Pro Tools" could not be launched because of a shared library error: "4<Pro Tools PPC dbg><Pro Tools PPC dbg><DAE><FreeFic>"
    Ive tried deleteing every other file from The M-powered install but nothing has worked. I have used disk utility to repair the disk and repair the permissions, but no luck.
    In the console it gives this message
    /Applications/Digidesign/Pro Tools/Pro Tools LE 6.8.1[560] Launch failed with error code -2807 (cfragUnresolvedErr) for application -psn011403265
    Jan 5 18:28:29 joshua-grahams-ibook-g4 /Applications/Digidesign/Pro Tools/Pro Tools LE 6.8.1: launch failed with error code -2807 (cfragUnresolvedErr) for application -psn011403265\n
    Can anyone help me with this?

    thinking about maybe switching to a mini later this year depending on what the new ones offer when they're announced.....
    If that's what you are planning, wait till they are announced to be in the channel to find out what the mileage is like. You never know what new compatibility issues might arise. Remember with each new release, no Mac can run an older Mac operating system than shipped with it. So any experience we give here today may be vastly different from what you might run into in the future.
    Then if people's mileage is not what you want, and it is better on the old, get a refurbished model*:
    http://www.macmaps.com/usedrefurbished.html
    Note, most Mac Mini users are not running Pro Tools. If you want Pro Tools experience of today, it is better to ask in the Mac Mini forum. If you like, I can ask a moderator to move this thread.

  • 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

  • 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.

  • Windows Update Loop - Win 7 Pro - x64 :: Error 80071A91

    Hi, I've been referred to this forum by the Microsoft community from this post: answers.microsoft.com  /en-us/windows/forum/windows_7-system/windows-update-loop-win-7-pro-x64-error-80071a91/b17c5bc5-7977-4f8b-9b45-ecb265886381 (same as below)
    Any assistance is appreciated. dave_ned at hotmail.com.
    Hi,
    "There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again"
    I've got the error (80071A91) that others have experiences while trying windows update and for the life of me I cannot get the updates to install.
    Looking for the past 4 hours via Google, trying different recommended things and still no luck
    http://answers.microsoft.com/en-us/windows/forum/windows_vista-windows_update/unable-to-install-updates-getting-error-code/27a21977-f964-4376-bfab-2f29ea127c6a
    # SFC /scannow causes the "repair status message" and asks for reboot.
    I've downloaded fix-it, tried booting into a system repair/restore disk using command line to run
    #sfc /scannow /offline....
    using the dispart to LIST VOLUMES  (based on this http://mikemstech.blogspot.com.au/2011/12/how-to-perform-offline-system-integrity.html )
    I've tried #fsutils resourse set autorevert=true (or something, can't find the exact post as I've rebooted so many times)
    I've tried dismc.exe (or similar without success)
    Basically I'm stuck with these updates (~10 of them) always sitting there downloading, installing every time I shut down the PC.
    Running a system repair disk created in windows still does not allow #sfc /scannow....
    My Last system restore was 04/08/14 and I cannot even restore the system to this point as the restore fails and asks to remove itself once I restart the system.
    Details:
    OEM version of windows purchased legally and genuine microsoft logo in system dashboard.
    Intel Core I5 -3330
    16GB RAM
    Windows 7 Pro - 64bit OS
    Service pack 1
    **NOTE** I have the C drive hooked up in RAID 0. Two(2) * 60GB SSD disks in RAID 0 used as C: via BIOS RAID
    Secondary storage disk a D:
    Been working and updating fine for the past 5-6 months.
    I have the Optical drive setup as O: and a Daemon tools virtual drive as drive E:
    While running DISKPART and using LIST VOLUME I see this:
    currently the system seems to have lost all update history
    Any information or help on this is appreciated. I don't want to reformat and reinstall, I don't really want to 'repair' and wipe my current software installation so I'm hoping there is a way.
    Anyway I can get the 'pending state' removed.?
    Thanks in advance
    David

    Hi, I've rebooted into Repair mode (Console), (because repair said windows is installed on E:) run dism.exe /image:E:\ /cleanup-image /revertpendingactions
    This gave a message about small scratch space but did say something out a fix. Upon reboot into safemode with console I received the same message 
    "C:\Windows\system32>sfc /scannow
    Beginning system scan.  This process will take some time.
    There is a system repair pending which requires reboot to complete.  Restart Windows and run sfc again."
    I then rebooted and tried SCF again, no luck... Same message, same updates still sitting there.
    Partition info: (as mentioned earlier C is in RAID 0 with 2 SSD disks)
    DISKPART> list volume
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      Volume 0     O                       DVD-ROM         0 B  No Media
      Volume 1     E                       DVD-ROM         0 B  No Media
      Volume 2         System Rese  NTFS   Partition    100 MB  Healthy    System
      Volume 3     C                NTFS   Partition    111 GB  Healthy    Boot
      Volume 4     D   GB320        NTFS   Partition    298 GB  Healthy

  • 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

  • HELP!! Since upgrading to Mac OS x 10.3.2 my Pro Tools sessions won't open!

    Can anyone please help me. I was running Mac OS 9 and Pro Tools 5.1 on my Mac G4. I needed to upgrade to add a new piece of equipment. So I was told to update to Mac OSx 10.3.2 and Pro Tools 6.0. Since doing so, when I try to open my Pro Tools, it opens, but when I try to open a new session, I keep getting a small screen that says I must restart my computer. AFter restarting and repeating the above, I get the same message over and over. I tried updating to Mac OSx 10.3.8 and the problem is still occuring. Can anyone out there give me some advice on what to do next??? Thank you!!!

    Hi Susan,
    I dont know what the specific issue is but will try to be helpful anyway.
    If this were my problem the first thing I would assess (preferably from Digidesign) is - is PT 6.x known to be compatible with Mac OSX 10.3.x ?
    Once this hurdle has been cleared, and assuming that the compatibility is there,
    then I would want to know if your install/upgrade to 10.3.8 is 'clear'. Meaning, you've run Disk Utility *from the Panther Retail install disk* and DU is showing no errors, either with Permissions or with "Repair Disk". The logic being an app cant be expected to work right on top of an OS that isnt even healthy.
    Next, you say PT launches. You seem to imply that either:
    a. File/Open/sessionX
    or
    b. 2x clicking a session
    causes some kind of window to appear. Is that a PT related window or OSX type window ?
    Does the window occur with either a. or b. above or with only one method or what ?
    Can you do a "File / New ..." and not see the window appear ?
    Best,
    Chris

  • 10.4.11 Pro Tools Compatability

    As i was installing 10.4.11 through software update an error occoured in the update. I then had to do an archive install. Once installed i ran the 10.4.11 combo update. Everything is working fine except Pro Tools. Everytime i try to launch the application i get the "black screen of death". I have tried uninstalling and re installing pro tools with no luck. I have also verified my HD, along with running the pre binding script application. Do i have to go back to 10.4.9? to reinstall pro tools, and if so is the only way of doing this by archive and installing off my original install disc? I am desperate as this is my lively hood and projects are due!

    Hi Thomas,
    I'm not a pro tools user but I have been perusing the digidesign site and was wondering if you had tried downloading and running the OS X Prebinding script? According to digidesign:
    "Although Mac OS X 10.4.10 and 10.4.11 have not been tested or qualified by Digidesign, the only known issue at this time has to do with Pro Tools failure to launch in some cases due to improper prebinding. In many cases, downloading and running the Mac OS X Prebinding Script from PACE may resolve the issues described above"
    Check out this link, it might be of help: http://www.digidesign.com/index.cfm?navid=54&langid=100&categoryid=35&itemid=229 04
    Best of luck, Jake

  • Having trouble with DV NTSC export file for Pro Tools.

    Pro Tools only takes NTSC format video. For some reason every single DV NTSC file that has been exported freezes in a certain spot and in other portions tends to flicker. I'm not so sure as to why that is. I tried exporting it through the QuickTime Movie option which always works, but gives me the previously stated problems. I tried exporting it through the QuickTime Conversion many times as well; the problem with doing it with this manner is that the video is just white, although the sound still works. I've rendered everything many times. At this point I was thinking about reimporting the raw footage from the P2 cards.
    Has anyone encountered this problem? Or have any suggestions? At this point I'm not sure what's wrong.

    have added this code to over come runtime error
    <script type="text/javascript" src="linediv.js"></script>

  • Pro Tools and Leopard

    Just wanted to know if anyone had heard any information about Digidesign patching up Pro Tools to work with Leopard.
    I really hope they do it soon...

    I just got this info from Digidesign on LE and Leopard.
    Hello Everyone,
    I'm Dave Lebolt, general manager of Digidesign. I wanted to take a moment to talk to you about what is happening with Mac OS X Leopard and support in Pro Tools. Some of you have commented that getting Leopard qualified far earlier than now would seem like a "no-brainer," or that Digidesign is often far too late in coming on line in support of newer OS versions. Some have hypothesized that we will charge for an upgrade just to offer you Leopard support. Some people have even said that it's possible that Apple may be causing problems for Pro Tools on purpose. And some folks have said all of these things at once!
    The first thing I want to say to all of you is: I'm sorry. I'm sorry that getting here is taking so long and that we have not been able to communicate more about it, and also because we really do care about your experience as customers... People working here are passionate about Pro Tools, a lot of us here want to use our product with Leopard too, and most of all we care because we genuinely want to do anything we can to help you be creative and successful in what you do. So I'm sorry if we're letting you down by not getting things released sooner.
    Lack of Leopard support across our product line affects many of you (and affects our business), so I wanted to give you some insight into what's been happening and where we are in the process. Some quick answers to the above statements:
    * We have an excellent working relationship with Apple. I have regular communications with senior folks there, as do many others in our organization with their peers (especially engineering and test). The people I talk to at Apple want Pro Tools to be compatible as much as we do; they know that a lot of you are our mutual customers. Ultimately, Apple considers Digidesign to be an important developer on the platform.
    * Rest assured, we will not charge Pro Tools 7.4 owners for an update to support OS X Leopard. In fact, it is not our policy (nor has it ever been) to charge for a "dot release" where the only change is support for a new OS version.
    * We'd love to have the new Leopard compatible version out to all of you, and it's very painful not to have it for everyone right now. We start work on the qualification (and development process as required) early in the cycle. We begin work on the "seed" versions of the operating system as soon as they are available and sometimes things are changing even as the initial OS release goes to market. If anything changes after that (i.e., a dot release), we sometimes have to start over in addressing any problems that may be newly introduced and go through entirely new rounds of testing to ensure quality.
    What's The Current Status?
    We have been working hard on supporting OS X Leopard since its introduction to developers at WWDC in 2006 for many months (including some period of time prior to Leopard's release). As is often the case with entirely new major OS versions, there were some quick "dot" releases after introduction. Many of the problems that Apple addressed in these dot releases were critical to improve OS X Leopard operations (you can read about some of them on the support section of Apple's website). These improvements and fixes were very valuable to a broad base of Mac users. Unfortunately, the currently shipping OS X Leopard release, 10.5.2, contains some changes that actually caused problems with Pro Tools (and some other apps as well). In our case, the problems included audio interfaces not being recognized by the computer, track counts dropping to near zero, and errors coming up during normal operation. Some of you who may have experimented with Pro Tools and OS X Leopard 10.5.2 may have encountered some of these problems.
    We have worked closely with Apple's engineering group, who have been working very hard in cooperation with us to get the problems ironed out. The good news is that we're getting close to the home stretch, but we have to do a lot of testing of the fixes that have been implemented in order to be sure that we're in good shape. We need to make sure that our product works well and you're not just getting something that's marginal, and it takes time to exercise all of the newly changed code.
    What Works on Leopard? Anything At All?
    Currently, only Pro Tools|HD systems running Pro Tools 7.4.1 software are officially qualified with OS X Leopard 10.5.1 running on the new generation Mac Pro 8 core desktop machines (with "Harpertown" processors). This means no support yet for Pro Tools LE and M-Powered, and it means that users of the new Mac Pros need to stick with OS X 10.5.1 for the time being.
    Why this Message?
    We have posted this information along the way (just a couple of weeks ago our head of customer service posted information to the DUC), but the amount of time that is passing combined with our concern within the company prompted me to want to reach out to all of you. We work cooperatively with Apple, and want to respect the process that we have in place for fixing problems; but I wanted to give you a bit more information about what's been happening and why we're not there yet...
    When Will It Ship?
    We hope to have the new release within between 1 and 2 months from now; some of that timetable is contingent on Apple. We'll keep you posted as we get closer. Normally, we don't want to give specific dates because that can cause problems in expectation and it's better not to have negative surprises, but I'd like to share this info with you in the spirit of keeping closer to you as our customers.
    I hope that my note gives you a better idea of what's been going on — thanks for listening.
    - Dave L.

  • Pro Tools Missing  audio file message syndrom exists on Logic

    I come from Pro tools and i am a bit traumatised by this fkn Pro Tools missing audio file message for those who know what i mean..
    Is it something possible and frequent in logic when we work on a daily basis ?

    No, you simply copy the entire project folder to a flash drive and bring it home. If you have included the audio files in the project folder, which logic does by default, logic will find them just fine at home. If it asks where they are, you just hit "search" and if they're there, If you've copied the song file to your drive without including the audio files ("pilot error") then  the program can't find them. Often, I get protools sessions from clients with missing files. Sometimes the entire audio files folder is missing, but more often the missing files are out-takes that are no longer part of the arrangement, and were still in the audio file list of the song, but were not included in the folder when the project was copied and brought to me. How or why, I cannot tell you.

  • Pro Tools 10 not working with 10.7.5 HELP!

    My reading suggests that Pro Tools 10 will work with 10.7.4 . My mid 2012 macbook pro came with 10.7.5 and it looks like trying to roll back to 10.7.4 will crate other issues with Safari, iphoto, etc. I tried to install the late 2012 10.7.5 update which fixes some programs not launching, but I get an error mesage saying that my harddrive does not meet the requirements. Huh? It's a 750 g standard isue partitioned to use boot camp as well.
    I'm desperate. I need my recording studio to work!! HELP!

    That is because your Mac came with a special build of Lion made just for the newest models, it contains the correct driver set for the newer hardware in the new models. You may have to do a complete reinstall over the top of your current install from the Online Internet Recovery system, IE Not the Recovery HD partition on the internal drive, to get the correct 10.7.5 build for your model.
    As to Pro Tools 10 working on Lion 10.7.5 you would need to contact Pro Tools and ask them.

Maybe you are looking for