As mentioned in a previous posting, I still haven’t yet moved completely away from Pro Tools 8, in favor of PT 10. Thus, as I keep exploring version 8, I keep finding its massive, incredible deficiencies. It’s to the point that it’s absolutely ridiculous (do you see the root word “ridicule” in there, Avid?). I decided, since I keep having fatal error messages pop up that require me to restart the computer to get the software to run again, maybe I should start a log of all the error messages that come up, keeping me from getting anything done. This is a work in progress unless, miraculously, all the errors listed below end up being all the error messages I end up coming across.
1) Assertion in”../Mdie_TrackPlayer.cpp”, line 469
2) Could not complete the Close Session command because Access violation occured, unable to read location: 0xBAFBF800 at address: 0x7C91OA19 in module: ntdll.dll. (one similar: Could not complete the Close Session command because Access violation occurred, unable to read location: 0x00000038 at address: 0x042E01D4 in module: ProTools.dll)
3) Access violation occurred, unable to read location: 0x00000000 at address: 0x048B8D90 in module: ProTools.dll (also, similarly: Access violation occurred, unable to read location: 0x00000002C at address: 0x049D6B69 in module: ProTools.dll)
4) This one is a frequent annoyance: “One or more ReWire applications did not terminate. You need to manually quit those applications before quitting Pro Tools”
5) Could not complete the Exit command because Access violation occurred, unable to read location: 0x00000010 at address: 0x049F6FCB in module: ProTools.dll.
6) DAE error -7453 was encountered.
7) Access violation occurred, unable to read location: 0x00000008 at address: 0x009322D1 in module: DFW.dll
8) Pro Tools was unable to Auto Backup your session. If your session is on a read-only drive, you must disable “AutoSave” by unchecking “Enable Session File Auto Backup” (located in the Operations tab of the Pro Tools Preferences dialog) to avoid this error. (Error was: Access violation occurred, unable to read location: 0x00000014 at address: 0x049E87DB in module: ProTools.dll)
9) Access violation occurred, unable to write location: 0x28A2E000 at address: 0x781472F9 in module: MSVCR80.dll
The fine print: *Avid’s lawyers would like you to know there is no implied or explicitly expressed claim that the use of “pro” in “Pro Tools” is a shortened version of the word “professional.” “Pro” may be referring to “protein,” “proletariat,” “project,” “proxy,” quite possibly “prohibitive,” and, less likely, “protest.” Given the nature of such vague abbreviations, “Pro Tools,” it’s subsidiaries and parent company will accept no claims that its products are not professional enough as, again, no such claims of the software being “professional” exist.**
**Dear Avid’s lawyers: this is a parody of what you might likely say. If you are reading this and take offense, get a life.
If you’re looking to pass some time, check out the music I’ve been able to record on not Pro Tools, but GarageBand instead, here: https://www.kilmermedia.net/music
Comments