<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Pro Sound Blog &#187; Why ProTools Sucks</title>
	<atom:link href="http://www.prosoundblog.com/category/protools/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.prosoundblog.com</link>
	<description>Rants of a professional drummer and recording engineer.</description>
	<lastBuildDate>Wed, 04 Jan 2012 09:17:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>10 reasons I&#8217;d pick Cubase over Protools</title>
		<link>http://www.prosoundblog.com/2010/09/02/10-reasons-id-pick-cubase-over-protools/</link>
		<comments>http://www.prosoundblog.com/2010/09/02/10-reasons-id-pick-cubase-over-protools/#comments</comments>
		<pubDate>Fri, 03 Sep 2010 06:40:04 +0000</pubDate>
		<dc:creator>mediaguru</dc:creator>
				<category><![CDATA[Why ProTools Sucks]]></category>
		<category><![CDATA[Cubase]]></category>

		<guid isPermaLink="false">http://www.prosoundblog.com/?p=521</guid>
		<description><![CDATA[1. Cubase (or Logic or any other system) costs about a billionth of protools.  But if you really want to be cool, you could pay lots more for a system which does lots less.  Your choice. 2. Cubase (and many other software based daw&#8217;s like Logic etc) has a billion more features. I&#8217;m not kidding. [...]]]></description>
			<content:encoded><![CDATA[<p>1. Cubase (or Logic or any other system) costs about a billionth of protools.  But if you really want to be cool, you could pay lots more for a system which does lots less.  Your choice.</p>
<p>2. Cubase (and many other software based daw&#8217;s like Logic etc) has a billion more features. I&#8217;m not kidding. A billion. Protools is so feature-less it is amazing people pay for it. For instance, if you want a good four band parametric on a channel in protools, you have to BUY one for hundreds of dollars, which will likely work on only one to four channels, if that. Cubase comes WITH a four band parametric for every channel, and could run hundreds of them at a time if you have enough computer processor power.  The same applies with other types of inserts on a channel, like compressors, gates etc.</p>
<p>3. Commercial plugins (effects, compressors etc), cost more for protools, because you&#8217;re so cool being a protools owner that you want to pay more for everything.  Case in point, a VST plugin reverb I bought for Cubase at $200 sold the Protools version for $500.</p>
<p>4. You are committed to Digidesign&#8217;s hardware, which can&#8217;t even record at 32 bit.  That blows.  But hey, if you own protools, you are cool.  It doesn&#8217;t matter if you have 10X the dynamic range on systems which cost thousands less.  You just want to be cool.</p>
<p>5. Cubase can use any of hundreds of hardware devices, and records at 32 bit.  Know how hard it is to clip a 32 bit system?  A hell of a lot harder than it is to clip a Protools system.</p>
<p>6. Protools tech support sucks worse that a $20 hooker.</p>
<p>7. Protools thinks it &#8220;owns&#8221; every hard drive you connect to your computer, and insists that it &#8220;mark its territory&#8221; by putting a bunch of files on them, even if you have no intention of using protools on that drive.  And it bugs the crap out of me when running protools that I have to use Protools to eject a damn drive, not the computer&#8217;s own operating system.  What&#8217;s next?  I have to use Protools to flush the toilet in the studio?</p>
<p>8. Midi on protools is so limited and crappy, that it may not even be better than the midi implementation of a Commodore 64 from 1983, while Cubase&#8217;s midi is outstanding.  Don&#8217;t believe me?  Well just find out what sort of HELL you&#8217;ll go through working with Midi and buy a PT system.  You&#8217;ll come crying back to me later.</p>
<p>9. Cubase can output sheet music from midi you play in. Protools couldn&#8217;t do that in a million years.</p>
<p>10. When you pay your billion dollars for protools, upgrading is SO fun!  Like when my buddy bought a $15,000 system, and then couldn&#8217;t update it when they came out with a new version two weeks later unless he forked out another $5,000! Yeah baby. Protools is SO cool!  My last Cubase update, from version 2 to version 4 (a large upgrade) cost me $249.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.prosoundblog.com/2010/09/02/10-reasons-id-pick-cubase-over-protools/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why ProTools Sucks #9: Delete key doesn&#8217;t delete markers</title>
		<link>http://www.prosoundblog.com/2009/02/10/why-protools-sucks-10-delete-key-doesnt-delete-markers/</link>
		<comments>http://www.prosoundblog.com/2009/02/10/why-protools-sucks-10-delete-key-doesnt-delete-markers/#comments</comments>
		<pubDate>Tue, 10 Feb 2009 17:19:38 +0000</pubDate>
		<dc:creator>mediaguru</dc:creator>
				<category><![CDATA[Rants]]></category>
		<category><![CDATA[Why ProTools Sucks]]></category>

		<guid isPermaLink="false">http://www.prosoundblog.com/?p=446</guid>
		<description><![CDATA[If you have markers you want to delete in a ProTools project, you can&#8217;t just select them and hit delete.  You have to use a pull down menu called &#8220;clear marker.&#8221; This really sucks.  Let&#8217;s say you need to delete 10, 100, 1000, or even 2800 markers from a project like I had to once.  [...]]]></description>
			<content:encoded><![CDATA[<p>If you have markers you want to delete in a ProTools project, you can&#8217;t just select them and hit delete.  You have to use a pull down menu called &#8220;clear marker.&#8221;</p>
<p>This really sucks.  Let&#8217;s say you need to delete 10, 100, 1000, or even 2800 markers from a project like I had to once.  That means individually selecting 2800 markers then pulling down a menu 2800 times?  No f&#8217;n way!  That is at least 5800 mouse clicks and a case of tedinitis waiting to happen.</p>
<p>To be clear, there is a &#8220;clear all markers&#8221; in ProTools.  But in this particular project I had over 3000 markers, 2800 of which needed to be deleted.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.prosoundblog.com/2009/02/10/why-protools-sucks-10-delete-key-doesnt-delete-markers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why ProTools Sucks #8: Can&#8217;t select multiple markers</title>
		<link>http://www.prosoundblog.com/2009/02/02/why-protools-sucks-8-cant-select-multiple-markers/</link>
		<comments>http://www.prosoundblog.com/2009/02/02/why-protools-sucks-8-cant-select-multiple-markers/#comments</comments>
		<pubDate>Mon, 02 Feb 2009 17:16:24 +0000</pubDate>
		<dc:creator>mediaguru</dc:creator>
				<category><![CDATA[Rants]]></category>
		<category><![CDATA[Why ProTools Sucks]]></category>

		<guid isPermaLink="false">http://www.prosoundblog.com/?p=444</guid>
		<description><![CDATA[I’m editing this book on CD. It’s a 350 page book where the author has read the entire thing. The author has a speech impediment and screws up constantly. So there are over 3000 markers in this ProTools project, each marker represents an edit or fix that needs to be done. I’ve got the book [...]]]></description>
			<content:encoded><![CDATA[<p>I’m editing this book on CD. It’s a 350 page book where the author has read the entire thing. The author has a speech impediment and screws up constantly. So there are over 3000 markers in this ProTools project, each marker represents an edit or fix that needs to be done.</p>
<p>I’ve got the book edited and now I need to get rid of most of the 3000 markers and put new ones in. So about 2800 of the markers need to be deleted. Should be easy, right? Just select a marker, hold down the shift key, then select the end of the group you want to delete….right? WRONG.  Click and hold your mouse, then drag across the markers then?  NO.  You can’t select multiple markers in ProTools. You can delete ALL the markers, but you can’t say select 30 of them and delete them, leaving the rest.</p>
<p>I have the choice of deleting all 3000 markers, and losing the 200 I want to keep. Or I can delete 2800 markers, one at a time. Oh you can’t just hit the delete key when you have a marker selected either. You have to select the marker, then use a pull down menu to select “clear marker.” This process would take me close to 10,000 mouse clicks on this project. Is digidesign willing to pay my doctor bill for ligament damage which I’ll incur from clicking my mouse so many times?</p>
<p>See Why ProTools Sucks #9&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.prosoundblog.com/2009/02/02/why-protools-sucks-8-cant-select-multiple-markers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why ProTools sucks #7: ProTools plug-ins cost more</title>
		<link>http://www.prosoundblog.com/2008/06/21/why-protools-sucks-6-protools-plug-ins-cost-more/</link>
		<comments>http://www.prosoundblog.com/2008/06/21/why-protools-sucks-6-protools-plug-ins-cost-more/#comments</comments>
		<pubDate>Sat, 21 Jun 2008 15:18:17 +0000</pubDate>
		<dc:creator>mediaguru</dc:creator>
				<category><![CDATA[Rants]]></category>
		<category><![CDATA[Why ProTools Sucks]]></category>

		<guid isPermaLink="false">http://www.prosoundblog.com/?p=393</guid>
		<description><![CDATA[Reason #7 ProTools sucks? Plug-ins cost more. Say you find a plug for VST or other systems which runs around $200. The same exact TDM plug for ProDrools would cost about $500.]]></description>
			<content:encoded><![CDATA[<p><strong>Reason #7 ProTools sucks?  Plug-ins cost more. </strong></p>
<p>Say you find a plug for VST or other systems which runs around $200.<br />
The same <em>exact</em> TDM plug for ProDrools would cost about $500.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.prosoundblog.com/2008/06/21/why-protools-sucks-6-protools-plug-ins-cost-more/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why ProTools sucks #6: Cost per bit</title>
		<link>http://www.prosoundblog.com/2008/05/30/why-protools-sucks-6-cost-per-bit/</link>
		<comments>http://www.prosoundblog.com/2008/05/30/why-protools-sucks-6-cost-per-bit/#comments</comments>
		<pubDate>Sat, 31 May 2008 04:42:31 +0000</pubDate>
		<dc:creator>mediaguru</dc:creator>
				<category><![CDATA[Rants]]></category>
		<category><![CDATA[Why ProTools Sucks]]></category>

		<guid isPermaLink="false">http://www.prosoundblog.com/?p=392</guid>
		<description><![CDATA[I just converted a session from ProTools to Cubase. I had to convert the files from 24-bit (ProTools) to 32-bit (Cubase). Seems odd I&#8217;d have to &#8220;upgrade&#8221; my audio files to go from an insanely expensive and industry standard system costing tens of thousands of bucks, in order to work with a program that retails [...]]]></description>
			<content:encoded><![CDATA[<p>I just converted a session from ProTools to Cubase.  I had to convert the files from 24-bit (ProTools) to 32-bit (Cubase).  Seems odd I&#8217;d have to &#8220;upgrade&#8221; my audio files to go from an insanely expensive and industry standard system costing tens of thousands of bucks, in order to work with a program that retails for $799.</p>
<p>Do you have any idea how much of a headroom difference there is between 24-bit and 32-bit recording?  It&#8217;s huge.</p>
<p>Steinberg&#8217;s Cubase and Nuendo can record 32-bit and they cost from $199-$2,000.<br />
ProTools maxes out at 24-bit and can cost tens of thousands of $$$.</p>
<p><strong>Reason #6 ProTools sucks?  The cost per bit!</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.prosoundblog.com/2008/05/30/why-protools-sucks-6-cost-per-bit/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why ProTools Sucks #5 &#8211; Tab button doesn&#8217;t work in OS file dialogs</title>
		<link>http://www.prosoundblog.com/2008/05/25/why-protools-sucks-5-tab-button-doesnt-work-in-os-file-dialogs/</link>
		<comments>http://www.prosoundblog.com/2008/05/25/why-protools-sucks-5-tab-button-doesnt-work-in-os-file-dialogs/#comments</comments>
		<pubDate>Sun, 25 May 2008 15:52:07 +0000</pubDate>
		<dc:creator>mediaguru</dc:creator>
				<category><![CDATA[Rants]]></category>
		<category><![CDATA[Why ProTools Sucks]]></category>
		<category><![CDATA[pro tools]]></category>

		<guid isPermaLink="false">http://www.prosoundblog.com/?p=391</guid>
		<description><![CDATA[In the Mac operating system, hitting the tab key while in an open or save dialog box tabs you through to the filename and highlights it. So say you want to save a new file, you hit save as and then a save dialog pops up. If you hit tab, the file name becomes active [...]]]></description>
			<content:encoded><![CDATA[<p>In the Mac operating system, hitting the tab key while in an open or save dialog box tabs you through to the filename and highlights it.  So say you want to save a new file, you hit save as and then a save dialog pops up.  If you hit tab, the file name becomes active and highlighted and you just start typing your filename.</p>
<p>This function is a time saver, especially if you deal with a lot of files.  In ProDrools, this doesn&#8217;t happen.  Tab does nothing.  But ProTools isn&#8217;t about saving time, it&#8217;s about taking MORE time, so your big expensive studio can bill your client more hours and make more money, thus helping you afford your overpriced recording system.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.prosoundblog.com/2008/05/25/why-protools-sucks-5-tab-button-doesnt-work-in-os-file-dialogs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why ProTools Sucks #4 &#8211; It thinks it owns every drive, and marks its territory like a cat pissing on your carpet</title>
		<link>http://www.prosoundblog.com/2008/05/25/why-protools-sucks-4-it-thinks-it-owns-every-drive-and-marks-its-territory-like-a-cat-pissing-on-your-carpet/</link>
		<comments>http://www.prosoundblog.com/2008/05/25/why-protools-sucks-4-it-thinks-it-owns-every-drive-and-marks-its-territory-like-a-cat-pissing-on-your-carpet/#comments</comments>
		<pubDate>Sun, 25 May 2008 15:45:38 +0000</pubDate>
		<dc:creator>mediaguru</dc:creator>
				<category><![CDATA[Rants]]></category>
		<category><![CDATA[Why ProTools Sucks]]></category>

		<guid isPermaLink="false">http://www.prosoundblog.com/?p=390</guid>
		<description><![CDATA[If you have ProTools running (I&#8217;m on the Mac OS by the way), hooking up any kind of drive results in a pain in the ass. Let&#8217;s say you&#8217;re working in a ProTools project and your daughter comes in and needs you to print something off of some flash drive or portable drive she brought [...]]]></description>
			<content:encoded><![CDATA[<p>If you have ProTools running (I&#8217;m on the Mac OS by the way), hooking up any kind of drive results in a pain in the ass.</p>
<p>Let&#8217;s say you&#8217;re working in a ProTools project and your daughter comes in and needs you to print something off of some flash drive or portable drive she brought in from a computer at school or something.  You leave the PT environment and print the document.  Then you try to eject the drive, but you can&#8217;t.  It&#8217;s in use by ProTools.  You then have to go into ProDrools, go to the &#8220;workspace&#8221; drop down menu, and then select about the 50th menu selection down called &#8220;unmount.&#8221;</p>
<p>Upon inspection of this drive you had to &#8220;unmount&#8221; there is a new folder on there called &#8220;Digidesign Databases.&#8221;  I didn&#8217;t f&#8217;ing ask ProDrools to put a damn thing on this drive.  I didn&#8217;t tell ProDrools that this drive was going to ever be used for any sort of project.</p>
<p>ProTools owns every drive you hook up to your system while it is running, whether you want it to or not.  And that is another reason ProTools sucks.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.prosoundblog.com/2008/05/25/why-protools-sucks-4-it-thinks-it-owns-every-drive-and-marks-its-territory-like-a-cat-pissing-on-your-carpet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Drummer needs a vacuum</title>
		<link>http://www.prosoundblog.com/2008/05/23/drummer-needs-a-vacuum/</link>
		<comments>http://www.prosoundblog.com/2008/05/23/drummer-needs-a-vacuum/#comments</comments>
		<pubDate>Sat, 24 May 2008 05:20:42 +0000</pubDate>
		<dc:creator>mediaguru</dc:creator>
				<category><![CDATA[Musicians]]></category>
		<category><![CDATA[Random]]></category>
		<category><![CDATA[Rants]]></category>
		<category><![CDATA[Recording]]></category>
		<category><![CDATA[Why ProTools Sucks]]></category>

		<guid isPermaLink="false">http://www.prosoundblog.com/?p=387</guid>
		<description><![CDATA[Tonight I just completed the setup for the big double album technical rock band 1.5 month project. Now I know it is likely that some of these band members I&#8217;m working with will be reading my journals here, so be warned not to take any of it too deeply. It&#8217;s all in fun&#8230; maybe. The [...]]]></description>
			<content:encoded><![CDATA[<p><a href='http://www.prosoundblog.com/wp-content/uploads/2008/05/drumvacuum.jpg'><img src="http://www.prosoundblog.com/wp-content/uploads/2008/05/drumvacuum.jpg" alt="" title="drumvacuum" width="250" height="188" class="alignright size-full wp-image-388" /></a>Tonight I just completed the setup for the big double album technical rock band 1.5 month project.  Now I know it is likely that some of these band members I&#8217;m working with will be reading my journals here, so be warned not to take any of it too deeply.  It&#8217;s all in fun&#8230; maybe.</p>
<p>The setup went fairly well with a few problems due to the drummer.</p>
<p>First the drummer was late because his dog was &#8220;pissing diarrhea blood out it&#8217;s ass&#8221; and his wife was puking because she was pregnant and couldn&#8217;t smell it.  Man I couldn&#8217;t imagine the hell that guy is going through (not with the dog, with having a pregnant wife).</p>
<p>2nd the drummer&#8217;s setup is enormous.  He must have literally 20 cymbals. Don&#8217;t forget the rototoms and octobans.  His kit is so tightly set up, there&#8217;s almost nowhere to get the mics into place.  Before he could set his kit up he had to vacuum his carpet (see picture)!  Believe it or not, that&#8217;s happened more times than I can count.  Anal drummers&#8230; Can&#8217;t live with them, can&#8217;t kill them.</p>
<p>I haven&#8217;t worked in this studio for a few months.  It was an experience for me trying to remember how the studio&#8217;s patching from room to room was setup, along with remembering the basic functions of the Euphonix console.  The main owner/engineer was there to help, which was very good.</p>
<p>One of the tasks before we can record was to figure out how to get all the keyboard tracks into ProTools (or ProDrools as I prefer to call it).  The keyboard player, bless his heart, doesn&#8217;t know much about what he&#8217;s doing.  He didn&#8217;t even know what or if he had an audio interface with his Apple Logic Express system.  He didn&#8217;t.</p>
<p>When importing the midi files, the individual takes or chunks were all broken up into separate tracks by ProDrools.  I figured that I had to use a merge function in logic to merge each track individually first, before importing into PT.  I&#8217;m not sure if Cubase is the same, but maybe that&#8217;s an entry #3 for my section called &#8220;why protools sucks.&#8221;</p>
<p>The setup took almost 6 hours, protools issues and drummers included.  Tomorrow we start at high noon with the tracking of drums and bass.  Noon is pretty late for me.  The guys in the band have been complaining a bit about the schedule and not having enough days booked in May/June, yet they want to start at noon.  If we started at 9am each day instead of noon, we&#8217;d gain one of those precious days back every three&#8230;</p>
<p>Off to bed.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.prosoundblog.com/2008/05/23/drummer-needs-a-vacuum/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why ProTools sucks #3:  ProTools MIDI implementation sucks</title>
		<link>http://www.prosoundblog.com/2008/05/21/why-protools-sucks-3-protools-midi-implementation-sucks/</link>
		<comments>http://www.prosoundblog.com/2008/05/21/why-protools-sucks-3-protools-midi-implementation-sucks/#comments</comments>
		<pubDate>Wed, 21 May 2008 17:10:31 +0000</pubDate>
		<dc:creator>mediaguru</dc:creator>
				<category><![CDATA[Rants]]></category>
		<category><![CDATA[Why ProTools Sucks]]></category>

		<guid isPermaLink="false">http://www.prosoundblog.com/?p=441</guid>
		<description><![CDATA[ProTools sucks as a MIDI tool.  The tool set ProTools comes with is a fraction of what other applications have. The worst part I&#8217;ve run into is that ProTools demolishes MIDI data when importing it from other applications.  I&#8217;ve imported standard MIDI files from numerous other applications only to find the formatting of the tracks [...]]]></description>
			<content:encoded><![CDATA[<p>ProTools sucks as a MIDI tool.  The tool set ProTools comes with is a fraction of what other applications have.</p>
<p>The worst part I&#8217;ve run into is that ProTools demolishes MIDI data when importing it from other applications.  I&#8217;ve imported standard MIDI files from numerous other applications only to find the formatting of the tracks and the timelines are so messed up that they&#8217;re unuseable.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.prosoundblog.com/2008/05/21/why-protools-sucks-3-protools-midi-implementation-sucks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why ProTools Sucks</title>
		<link>http://www.prosoundblog.com/2007/09/26/why-protools-sucks/</link>
		<comments>http://www.prosoundblog.com/2007/09/26/why-protools-sucks/#comments</comments>
		<pubDate>Wed, 26 Sep 2007 16:41:53 +0000</pubDate>
		<dc:creator>mediaguru</dc:creator>
				<category><![CDATA[Rants]]></category>
		<category><![CDATA[Recording]]></category>
		<category><![CDATA[Why ProTools Sucks]]></category>

		<guid isPermaLink="false">http://www.prosoundblog.com/index.php/2007/09/26/why-protools-sucks/</guid>
		<description><![CDATA[I&#8217;ve added a new category: &#8220;Why ProTools Sucks.&#8221; This section will be where I voice my opinion about Digidesign&#8217;s ProTools digital audio recording hardware/software. ProTools has become the industry standard in the recording world. It&#8217;s the buzz word everyone always knows. But in my opinion there are many systems out there which can do what [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve added a new category:  &#8220;Why ProTools Sucks.&#8221;</p>
<p>This section will be where I voice my opinion about Digidesign&#8217;s ProTools digital audio recording hardware/software.  ProTools has become the industry standard in the recording world.  It&#8217;s the buzz word everyone always knows.</p>
<p>But in my opinion there are many systems out there which can do what ProTools does, even better.  Add that to the fact that you can get these systems for a fraction of what ProTools costs&#8230;  Customer service?  Yeah well i remember calling a 900 number for my ProTools questions, paying $3/minute, being on hold for 47 minutes and then getting asked &#8220;did you plug it in?&#8221;  There goes $150 bucks&#8230;  But if you have thousands of extra dollars to waste on an overpriced recording system, I guess you can pay $150 bucks to be on hold for 47 minutes.</p>
<p>CAN&#8217;T SELECT MULTIPLE MARKERS</p>
<p>I&#8217;m editing this book on CD.  It&#8217;s a 350 page book where the author has read the entire thing.  The author has a speech impediment and screws up constantly.  So there are over 3000 markers in this ProTools project, each is an edit or fix that needs to be done.</p>
<p>I&#8217;ve got the book edited and now I need to get rid of most of the 3000 markers and put new ones in.  So about 2800 of the markers need to be deleted.  Should be easy, right?  Just select a marker, hold down the shift key, then select the end of the group you want to delete&#8230;.right?  WRONG.  You can&#8217;t select multiple markers in ProTools.  You can delete ALL the markers, but you can&#8217;t say select 30 of them and delete them, leaving the rest.</p>
<p>I have the choice of deleting all 3000 markers, and losing the 200 I want to keep.  Or I can delete 2800 markers, one at a time.  Oh you can&#8217;t just hit the delete key when you have a marker selected either.  You have to select the marker, then use a pull down menu to select &#8220;clear marker.&#8221;  This process would take me close to 10,000 mouse clicks on this project.  Is digidesign willing to pay my doctor bill for ligament damage which I&#8217;ll incur from clicking my mouse so many times?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.prosoundblog.com/2007/09/26/why-protools-sucks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

