Avid Pro Audio Community

Avid Pro Audio Community (https://duc.avid.com/index.php)
-   Pro Tools 11 (https://duc.avid.com/forumdisplay.php?f=115)
-   -   Protools could be called "CrashTools" (https://duc.avid.com/showthread.php?t=408677)

Kinh 02-24-2020 10:24 PM

Protools could be called "CrashTools"
 
Every time I close a session ...CRASH!. Every time I sneeze...CRASH!
Any excuse...CRASH!
Even holding shift to disable all plugins and close ...CRASH!
Clearly it's pointless blaming it 3rd party plugins. Let's face it Protools is just sh#t!
Poor quality product with 0 support.
And before any of you say "how dare you!", "it doesn't happen to me so...you must be WRONG", google "protools + crash" and watch the internet light up like a Xmas tree.

No other daw crashes more. Avid wins the most unreliable product award hands down, that includes vacuum cleaners, electric toothbrushes, blenders, mobile phones, internet services...everything!

Wizzoboy 02-25-2020 03:45 AM

Re: Protools could be called "CrashTools"
 
The one thing that shouldn't happen is crashing when you do simple tasks such as closing a session. Trouble is there are many causes of crashes and finding the cause is not always easy.
There are plug-ins that will cause crashes, out of date drivers will, an inadequate graphics card, etc.
Now, I have been running 64 bit PT since version 11.0 on the same computer that now runs 2018.3. I have never experienced a crash in any of the versions I have used. Maybe it's because I use a workstation (which by the way is 12 years old) or keep everything up to date. I'm not alone as many people have stable systems.
There are, unfortunately, so many variables when using Windows that problems and conflicts can be hard to track down. The fact that you get a crash with simple tasks such as closing PT points to a problem elsewhere in your system.

TOM@METRO 02-25-2020 08:30 AM

Re: Protools could be called "CrashTools"
 
Are you still running the system described in your signature?

AE 02-25-2020 10:34 AM

Re: Protools could be called "CrashTools"
 
some versions of pro tools have been more stable than others, but none have ever performed remotely as you've described. your problem is almost certainly software incompatibility or file corruption. these issues can occur with any app, and generally lead to intense frustration... but it's absolutely fixable.

JFreak 02-25-2020 10:47 AM

Re: Protools could be called "CrashTools"
 
64bit Windows 7 and PT11? Not supported. Compatibility info here

TOM@METRO 02-25-2020 12:54 PM

Re: Protools could be called "CrashTools"
 
Your best bet would be to update to the latest version of both Windows and Pro Tools.

Another thing you might consider is that your Mbox 3 Pro is very close to EOL. Although this should not be part of your current issue as long as drivers are current.

Wizzoboy 02-25-2020 02:28 PM

Re: Protools could be called "CrashTools"
 
1 Attachment(s)
As PT 11 is a 64bit app it does run under 64bit Win 7, which is why I bought a 64bit computer and installed 64bit Win 7 in the first place.
This is from Avid.

Wizzoboy 02-25-2020 02:34 PM

Re: Protools could be called "CrashTools"
 
Tom, if your question is directed at me the answer is yes.

JFreak 02-25-2020 03:48 PM

Re: Protools could be called "CrashTools"
 
Running on 64bit and supported on 64bit are apparently two different things as you have found out. You need PT12 to be supported. Check the link I posted a while ago. Though that page also has contradicting info as it says PT11 requires W7SP1 but also says PT11 and higher require 64bit OS. Go figure. Best to contact Avid Support

EDIT: on third look I would understand that only 64bit W8 is supported but if you are on W7 it needs to be 32bit for PT11 and 64bit for PT12

Kinh 02-25-2020 06:17 PM

Re: Protools could be called "CrashTools"
 
To put your concerns about OS/system compatibility to rest, PT11 wasn't doing this on the same system I have now ..win7 64bit. It was only recently it started crashing when I close. It happened after I opened a few old sessions from the past which had different I/O, sample rate settings. Now it crashes every time I close a session after I've bounced down a file and 50% of the time after I close any session without bouncing whilst holding down shift (disarm plugins).

I've got 9 tracks I have to master in a row right now = 9 crashes, 9 reboot computer, 9 relaunch PTs = 45mins wasted + frustration and anger caused.

There is no way I'm upgrading windows to 10 or PTs to 12 just to end up with the same problems again. I work mostly in Ableton anyway. Id much rather switch my mixing daw to one that works even if it means spending twice as much.


All times are GMT -7. The time now is 10:37 AM.

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