Avid Pro Audio Community

Avid Pro Audio Community

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

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

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

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 06-12-2016, 09:16 AM
michaelray1284 michaelray1284 is offline
Member
 
Join Date: Mar 2015
Location: Greenville, NC
Posts: 9
Default Pro Tools First with Focusrite: How is this a "Pro" DAW

I wanted to give Pro Tools a shot but....

I spent 3-4 hours yesterday trying to get my Focusrite Scarlett to work with Pro Tools First. Every other DAW i have used which included my main one, Reaper, has never given me issues. Its been plug and play with Studio One, Reaper and Cubase but for some technical reason "Pro" Tools seems to be the only DAW that cant work i/O properly.

Ive searched the tread and forums for solutions but its evident that Avid clearly want you to invest into their major supporters. Ive heard things as far as its Focusrite and driver issues. Ive used Asio4All for these DAWs and come across no issues.

Im an IT and I've never seen such excuses from Avid. If Presonus, Reaper and Cubase can do it trouble free then so should AVID, the "industry" standard.

I really like the work flow and stock content that Pro Tools comes with and most my friends use it. I cant justify myself to upgrade all my Focusrite Scarlet interfaces just so i can have Pro Tools.
Reply With Quote
  #2  
Old 06-12-2016, 03:51 PM
guitardom guitardom is offline
Member
 
Join Date: May 2004
Location: New Mexico
Posts: 6,809
Default Re: Pro Tools First with Focusrite: How is this a "Pro" DAW

The problem is that so many other developers create Asio drivers that work with Pro Tools perfectly. For some reason Focusrite among a couple others (Behringer comes to mind) are having a TERRIBLE time getting drivers to work.

Blaming Avid and not the developer of the hardware drivers is obviously only half the problem when you have someone like RME and many others that build perfect working USB drivers for PT. Its also odd that Focusrite's Firewire drivers work great on Windows.
__________________

pro-tools-pc.com


TRASHER Pro Tools Utility(updated 4-11-2024)

HD Native, Avid 16x16, Eleven Rack, Focusrite Clarett 8preX, UA Quad Apollo TB.

Intel I7 9900k
Win 10
Reply With Quote
  #3  
Old 06-12-2016, 04:02 PM
Darryl Ramm Darryl Ramm is offline
Member
 
Join Date: Nov 2010
Location: USA
Posts: 19,657
Default Re: Pro Tools First with Focusrite: How is this a "Pro" DAW

Quote:
Originally Posted by michaelray1284 View Post
I wanted to give Pro Tools a shot but....

I spent 3-4 hours yesterday trying to get my Focusrite Scarlett to work with Pro Tools First. Every other DAW i have used which included my main one, Reaper, has never given me issues. Its been plug and play with Studio One, Reaper and Cubase but for some technical reason "Pro" Tools seems to be the only DAW that cant work i/O properly.

Ive searched the tread and forums for solutions but its evident that Avid clearly want you to invest into their major supporters. Ive heard things as far as its Focusrite and driver issues. Ive used Asio4All for these DAWs and come across no issues.

Im an IT and I've never seen such excuses from Avid. If Presonus, Reaper and Cubase can do it trouble free then so should AVID, the "industry" standard.

I really like the work flow and stock content that Pro Tools comes with and most my friends use it. I cant justify myself to upgrade all my Focusrite Scarlet interfaces just so i can have Pro Tools.
Pro Tools First is not ever going to be considered to be a "pro" DAW. That should be obvious from the feature stripping/limitations in it's use. C'mon can't open existing sessions, can't reuse plugins you already own, can't save sessions locally, no clip gain, awkwardly dumbed down UI, and on and on. Its' a horribly mis-marketed joke.

And ASIO4ALL is also a joke. Unless you had to to work around some problem why would you use an ASIO4ALL interface driver for an interfaces that have native ASIO drivers. And the corollary is don't buy any interfaces that don't have good native ASIO drivers. Wrapping WDM drivers with ASIO4ALL is a band-aid at best. And that is not just a Pro Tools limitation.

If you want help here from other Pro Tools users you are posting to the wrong forums session and not providing *any* useful/expected details of your problem or system setup. Start at the "help use help you" link up the top of every DUC web page and post to the Pro Tools First forum section. Complaining to most Pro Tool users about First will likely not get you anywhere. Few if any folks here are going to be using it.
Reply With Quote
Reply


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

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

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
"Pro Tools quit unexpectedly" when opening (holding "n" no longer fixes it)[RESOLVED] andrew24c macOS 4 07-23-2014 07:21 PM
Does "Westmere" qualification apply to "Bloomfield" and "Gulftown" also? bashville Pro Tools 10 5 03-23-2013 03:04 PM
"Pro Tools not responding" error and a very "laggy" session! Help! drumbumd Pro Tools M-Powered (Win) 0 02-10-2012 05:37 PM
Pro Tools 9 "Pausing" when I press "Play" with Focusrite Scarlett interface eanderso22304 macOS 3 11-23-2011 06:45 AM
Pro tools 9 crashes at startup "Bus error" in thread "MainThread", at address 0x0 danball macOS 2 09-26-2011 04:49 PM


All times are GMT -7. The time now is 04:44 AM.


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