Take - As in Pro Tools?

Beign a Logic guy for about 6 years now, I was recently in a session with a Pro Tools user and wacthed as he quickly flipped through different takes of a song via a pull down menu. No deleting, repeated tracks, folders...
Is there any such feature in Logic that I have been missing all this time?
Also, it seemed very convenient that all regions (12) had the various track names/colours applied. I only know how to give them 1 name at a time and color them later.
Any tips?

So you can
use take one of the piano with take 3 of the lead
guitar, and then, say, you decide you actually want
take 2 of the guitar youj can select it and there it
is. No hunting around the audio window, and much
tidier arranges. It's great for comping things like
vocals as well
Hmm... interesting feature. What happens if you want to mix various takes though?
I've started using folders in Logic quite a bit. I use them for structuring but also for comping with the cycle and mute feature described by Sondod, Marc and others. I pack all the takes in a folder and work from there, eliminating the screen clutter. I use the scissors+option trick to split everything up evenly and then select what I like with the mute tool, color coding the parts that are keepers as I go along.
Once I'm done I bring all the good parts on a track which i unpack, leaving only the outtakes in the folder (muted tracks will not unpack when you invoke the command, making it easy to select what goes back in the upper level arrange and what stays behind). And since you can nest folders within each other, you can keep just one outtake folder in your arrange window and have individual comps folders inside.
It sounds like a lot of work but it's actually pretty clean and fast with the right key commands. I'd love to see the feature you're talking about at work though. Sounds elegant...
Powerbook G4+iMac G5   Mac OS X (10.4.6)  

Similar Messages

  • Sending Premiere Pro sequence to Pro Tools for automatic audio conforming

    I’m looking to implement an online-offline workflow at my production company, and I’m trying to figure out if it’s feasible to send a sequence from Premiere Pro to Pro Tools with enough metadata to take advantage of Pro Tools’ automatic conforming feature.
    Premiere Pro or Audition doesn't seem to have any kind of feature like this, so I’m turning to Pro Tools. Here’s a demonstration of the feature from Avid: http://youtu.be/Gz9e9LuIdXU
    For color grading, we’re already sending XML from Premiere Pro into DaVinci Resolve, and DaVinci Resolve perfectly automatically conforms the offline proxies to online high-quality clips suitable for grading. I’m trying to accomplish the same thing with the audio clips to prepare a sequence for sound mixing. The offline proxies in a sequence contain only compressed stereo tracks, but online audio clips have all of the separate uncompressed tracks for each microphone.
    My initial thought was that, before any offline editing occurs, I might, in the Premiere Pro Metadata panel, add the names of the sound rolls to all the offline proxies in the “Tape Name” field.
    I’m wondering if that metadata for those clips in the Premiere Pro Project Panel are included in an EDL that would be exported out of Premiere Pro, so that Pro Tools would know how to correctly choose online audio clips.
    I know EDLs contain timecode, and that seems like it would be sufficient for Pro Tools, if production only occurred within one day. However, if there are audio clips recorded on different days, at the same time of day, some audio clips in a sequence would have identical timecode, and Pro Tools wouldn’t know which clip to automatically conform. It seems like Pro Tools would choose which clip to conform by first looking at timecode, and then if there were multiple clips with the same timecode, it would resolve the conflict by identifying the specific sound roll. This is why it seems important to have the sound roll metadata included in the EDL out of Premiere Pro.
    EdiLoad looks like software that might be able to batch update sound roll metadata for an EDL already exported out of Premiere, but I’m not sure.
    http://www.soundsinsync.com/products/ediload
    Manually going through Pro Tools and assigning correct sound rolls in a picture-locked cut wouldn’t really be an improvement over manually conforming. If I have to go through a cut and locate online audio clips, I might as well just conform manually.
    So my questions are:
    When exporting an EDL out of Premiere, does the EDL include “Tape Name” metadata for Pro Tools to read as a sound roll? If not, is there another format I could use that would make this round-trip feasible?
    If not, does anyone have experience with EdiLoad? Would EdiLoad work to do what I'm trying to do?
    Is there any other way to accomplish automatic conforming, or something else that I'm missing?
    -- Seth.

    See if this helps.
    FAQ: Why are some codecs and sequence presets missing from my installation of Premiere Pro?

  • Learning Pro Tools (as an experienced Logic User)

    Hi. For my course and becuase of how industry standard Pro Tools is i want to start learning how to use it.
    Has anyone any advice on tutorials or where to start or just any general advice for me?
    Thanks, Ben

    I'm in the same situation, learning both at the same time because I'm trying to decide which way to go first, and I figure that much of the usage of one is applicable to the other, as far as software goes. In my area (Las Vegas) Tower Records just went out of business and I was able to pick up an excellent book "The Complete Pro Tools Handbook" by Jose Valenzuela... normally $50, I got it for $10. HUGE book, only about a year out of date, really takes you through pro tools from the beginning. Another thing I've found about this book is it really comes from an non-computer audio engineering point of view, takes you through the hardware extensively more so than any other book I've read, and is aimed at audio engineers coming from a non-computer pro background. I'm finding it extremely helpful, because non-computer engineering is all hardware-based. I have a couple of fantastic Logic books as well, but they say NOTHING at all about hardware and hooking stuff up and wading through all the various competing gear to accomplish that. Granted Protools has an advantage in that regard with their own hardware, but I've found reading extensive information about protools hardware and what it does in this book is helping me choose hardware for logic as well!
    Good luck in your search. I'm sure many major studios HAVE to have BOTH logic and protools in their arsenal.
    Leslie Bell
    IMac   Mac OS X (10.3.9)  

  • OSX 10.8.5 + Pro Tools 10: Very strange issues - Firewire audio interface

    I'm facing weird issues on my new system.
    When I received my new iMac, I firstly used Migration Assistant. It didn't work well so I did a clean install. I installed the Digi003 drivers first, then PT, then all the plugins. Everything is up to date. Interface and computer are connected with a Firewire 400/800 cable and a brand new Thunderbolt/Firewire adapter. The computer is used for music production only and the hard drive is almost empty (not much data).
    I know the Digi003 works fine as I used it with my former iMac which was a Core2Duo 3gHz with 4Go RAM running OSX 10.6.8 and PT 10.0.0. I used to set the buffer size  on 128 to record audio. It worked well.
    THE PROBLEMS ARE:
    1- DigiAudioCore does not auto-launch anymore. If want to play a song with VLC, I have to manually launch DigiAudioCore.
    2- PT stops (-6086) if I record with the buffer size set on 128. Buffer size on 256 is the minimum and PT still bugs sometimes even if there is only one track and no plugins in a 44.1kHz / 24bits session.
    3- CPU spikes too if I have just a couple of plugins engaged.
    4- I did some tests with an RME Fireface 800 and a Motu 828 MKII and I got the same issues (-6101). I still have to do a test with an USB interface.
    5- Sometimes the iMac bugs when I open the System Prefs but it works normally after a few seconds.
    I don't know what are the causes but it seems that there is a bandwidth problem caused by Thunderbolt/Firewire connection. I tried a brand new FW800 cable between the Fireface 800 and the computer but I got the same issues. Maybe the hard drive???
    So now I really need some help to solve once for all these problems. I hope I don't have a do a clean install again!!!
    Thanks in advance.
    COMPUTER SPECS
    iMac 27" bought october 2013
    Processor: i7 3.5gHz (Turbo boost 3.9gHz)
    Memory: 32Go RAM DDR3
    Hard drive: Fusion Drive 1To
    OSX: Mountain Lion 10.8.5
    INTERFACE & DAW
    Digi003 Rack+ (drivers up to date)
    Pro Tools 10.3.7

    Back up all data immediately as your boot drive may be failing.
    This diagnostic procedure will query the system log for messages that may indicate a hardware fault. It changes nothing, and therefore will not, in itself, solve your problem.
    If you have more than one user account, these instructions must be carried out as an administrator. I've tested them only with the Safari web browser. If you use another browser, they may not work as described.
    Triple-click anywhere in the line below on this page to select it:
    syslog -k Sender kernel -k Message CReq 'Channel t|GPU D|I/O|n Cause: -' | tail | open -ef
    Copy the selected text to the Clipboard (command-C).
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window (command-V).
    The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
    A TextEdit window will open with the output of the command. Normally the command will produce no output, and the window will be empty. If the TextEdit window (not the Terminal window) has anything in it, post it — the text, please, not a screenshot. The title of the TextEdit window doesn't matter, and you don't need to post that.

  • Two questions:  pro tools HD compatbility.  iMac vs MBP.

    I'll first start off with the question regarding Pro Tools HD compatibility. When it says "compatible", what is this meaning exactly? I'm transferring to Belmont University for Music Business/Production next semester and have contacted the studio manager and he said they mainly use Pro Tools HD in the campus studios. I already have Pro Tools LE 7 with an Mbox, so I'll be able to take projects from the studio on a firewire drive into Pro Tools LE for editing.
    But I'm curious if "compatible" means that I'll be able to open my projects recorded in a Pro Tools studio in Logic Pro later on or if it means that I could use Logic Pro with the Pro Tools HD interface in the studio and record directly into Logic Pro? The studio manager told me that all the studios are equipped with Powermac G5s and everything I need will be there, but I want the ability to take my stuff away on a FW drive (oh, another question...any recommendations on firewire drives?) and work independently on my own system. Which leads to my next question....
    In my email to him, I also asked about the importance of owning a laptop over a desktop and he said it wasn't imperative to have a laptop since the studios were equipped with Powermacs. I know if money wasn't an issue the Powermac is the best choice for audio production, but I am a student, and I cannot afford to buy a Powermac with sufficient RAM plus a display.......I was highly considering a Macbook Pro, but after realizing that I would be carrying my hard drive around more than my computer, it has me wondering about an iMac. I know the 2 gb RAM limit is a downfall for this system, but I would have that limit in the MBP also, so that doesn't affect anything between comparing the two. I have configured both systems with the education discount and Applecare:
    15" MacBook Pro: $2,898.00
    -2.16GHz Intel Core Duo
    -2GB 667 DDR2 - 2x1GB SO-DIMMs
    -100GB Serial ATA drive @ 7200 rpm
    -MacBook Pro 15-inch Widescreen Display
    -SuperDrive (DVD±RW/CD-RW)
    -AirPort Extreme Card & Bluetooth
    -Backlit Keyboard/Mac OS - U.S. English
    -AppleCare Protection Plan for MacBook Pro/PowerBook (w/or w/o Display) - Auto-enroll
    -15.4-inch TFT Display
    20" 2.0 GHz iMac: $2,056.00
    -2GB 667 DDR2 SDRAM - 2x1GB
    -250GB Serial ATA drive
    -ATI Radeon X1600/256MB VRAM
    -SuperDrive 8x (DVD+R DL/DVD+RW/CD-RW)
    -Keyboard & Mighty Mouse + Mac OS X - U.S. English
    -Accessory kit
    -AppleCare Protection Plan for iMac - Auto-enroll
    -20-inch widescreen LCD
    -2GHz Intel Core Duo
    -AirPort Extreme
    -Bluetooth 2.0 + EDR
    So, with portability no longer being a great concern, for system performance, which would be the best system? I will be using Pro Tools LE 7 for editing/mixing and Logic Pro for MIDI/creating music with virtual instruments. Any advice you have would be greatly appreciated.
    Thanks,
    Scott
    12 Powerbook w/Superdrive; 512mb; 80gb; Airport   Mac OS X (10.4.7)  

    Hey Scott.
    Check out the "Benchmark Song 2" thread on this forum. That will show some performance test on different computers.
    About the choice of computer, well, all I can say is get the best of what you can afford. Logic runs nicely on both those machines by all reports. I would also like to say that the Mac Pros (new Powermacs) should be out before the end of the year and will smoke both of these computers. And the price should be comparable to the MacBook Pro.
    X

  • New Mac Mini, iMac, or old Mac Pro for Pro Tools?

    I asked this in another thread, but just want to get more input from older Mac Pro users from different years (2008-2010..)
    I need to upgrade my Mac and am wondering what experiences everyone has had with different options for running Pro Tools and other professional audio applications.
    The FW800 port on my iMac recently broke, and rather than spend a lot on getting it fixed I've decided to just sell it to someone who doesn't need firewire and upgrade.
    I'm trying to decide between a newer iMac (3.1 or 3.4 GHz) with thunderbolt and USB 3 (but no FW), a new Mac Mini, also with thunderbolt and USB 3, or a somewhat older Mac Pro (2008-2010) with at least a 2.8GHz processor. Any thoughts from those of you who have used any of these, or who know more about computers in general than I do? Thanks.
    Another option a friend recommended was looking for a 2011 iMac as they have both Firewire and Thunderbolt, since my audio interface runs via FW.
    Thanks!

    Might want to ask this on a ProTools forum as well.
    fwiw I have a 4 core MacMini Server w 8GB RAM and a 2008 MacPro 8 core w 16GB.
    The Mini is used as a general file and A/V server when not specificially tasked with Final Cut Suite efforts.
    Unless I have serious Compressor processes running (e.g. converting h.264 to an editable format) that draws on the full cores, the mini can do a good job keeping up with the MacPro.
    What the mini won't do is take 3rd party cards or drive multiple large monitors but for digital audio it ought to be fine with thunderbolt drives.
    Good luck.
    x

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

  • Exporting out of Logic to Pro Tools

    What's the best way of exporting only vocal tracks out of Logic express 7? I need to have each track as separate .wav or .aiff files and be able to import them into Pro Tools 6.4 for a mix so they're all in time as they were recorded in Logic. I myself don't own Logic, it's the vocalist who uses it.... so I'm going to be going over to get the exports, copy them to disk and bring them back to my studio. What's the easiest way?

    The easiest (and very boring) way is to bounce each track in .wav or .aif or .sd2 and then port them into your studio.
    A shortcut (but, as quality, it's not the same as bounce) could be to freeze all the tracks and take away the frozen files folder.
    cheers
    rob

  • FCE & FCP compatibility with OMF files and Pro Tools

    I am using Final Cut Express 3.5 and want to edit a future project on it for a friend. When I am finished with the project, I was wanting to export the audio as an OMF file so that it can be mixed in Pro Tools. However, I just realized that Final Cut Express 3.5 does not support OMF exporting.
    I am trying to work around this problem and I just need some verification that my idea will work. This is my idea: Will it work if I take my finished FCE project and open it on a friend's computer that has Final Cut Pro and create an OMF file through FCP?
    If so, after mixing in Pro Tools, will I be able to import the mixed audio back into my FCE (or worst case scenario, my friend's FCP) and be able to burn the movie to DVD?

    1. Depends on the FCP version they're using. FCP5.1 or later will work.
    2. Yes.

  • Exporting AAF for Pro Tools.

    So I got an OMF from FTP into STP with no problem, only to find that I couldn't export it again - hopefully a feature in the new STP? Anyway, my only option was to export an AAF (don't have the original FCP timeline to work with) - this audio needs to go to Pro Tools.
    But my Pro Tools guy is saying he can't do anything with the AAF file if it's not consolidated into one file - like the OMF normally is.
    So - is there a way to export a consolidated AAF? I don't see the option.

    Our round trip workflow works, but still hoping for a better alternative in the future.
    Duplicate & Rename the sequence for export (just a good habit to have... "videoblah.002, 003, etc). Then clean up any potential audio / video problems; clips that are not enabled, duplicate audio, delete blank tracks, and all the stuff the seems to crowd in the back of my timeline.
    -It is a good idea to label your audio tracks for transfer (right-click> rename)
    After that I export an OMF. (File>Export>OMF) and select the settings below:
    That's just audio so for video, I export a quicktime H.264 video for ProTools DVtoolkit (video import plugin).  Protools will except H.264 .MOV files, but it will not ingest H.264 .MP4's.  It will also handle 1920x1080 files, but if I am rendering out a long project I like to keep the file size smaller by cutting the resolution in half or more.
    The audio guy then takes it from there and gives me back a 24-bit single track audio wav file.
    Thus far it seems to be a workflow, but if I want to go back and make changes, then either I have to do it all over again, or tell the audio guy specifically what needs done.
    All in all, it's not efficient as using a roundtrip workflow such as AVID > ProTools and back again in AAF form.
    Hope that helps.

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

  • Optimal Hard Drive Configuration for Premiere Pro CS5 and Pro Tools

    I am in the process of upgrading a workstation that is used primarily for multi-track audio recording in Pro Tools to use the following Adobe CS5 products for production of promotional videos in HDV (and AVCHD for the web) as well as printed marketing materials for bands and musicians: Premiere Pro, Encore, Photoshop, Illustrator and Soundbooth.
    Since Premiere Pro is probably the most demanding application of the group, I have been studying the suggested hardware configurations on this forum with great interest, particularly HARM's suggestions (including his Generic Guideline for Disk Setup) to determine which hard drives to purchase and the optimal manner in which to configure them.
    I am upgrading an HP Z800 with dual quad core 2.44 GhZ processors with hyperthreading (16 virtual cores), 12 GB of memory and an overclocked GeForce GTX 470.  Without setting up a RAID configuration (which I cannot afford at the moment), I would like to use the 4 available HDD bays in the Z800 in the optimal manner for Premier Pro, using currently available drives.  I am currently considering purchasing a 300GB VelociRaptor to use as my C drive because of the extended load times and demands placed on the drive by ProTools and the associated Waves plug-ins.
    I would appreciate suggestions to improve my following plan:  C (300GB  WD VelociRaptor) for OS and Programs; D (1 TB WD Black Caviar) for Media and Projects; E (1 250 GB WD Black Caviar) for Pagefile (approx. 18 GB) and Media Cache; and E (2 TB WD Black Caviar) for Previews, Exports and Pro Tools audio files.
    I have great respect for the knowledge of the members of this forum and eagerly await your suggestions.
    /Bill

    I very much appreciate the responses to my email because I know that all of your time is valuable and that you have chosen to use some of that valuable time to help an unknown individual.  This forum is remarkable because of the wealth of knowledge available and the willingness of so many to assist others.
    I now wish to narrow my questions to save you time and so that I can get specific advice.  I may not have not been clear that I have already upgraded to the HP Z800 with dual quad core processors and overclocked GTX 470, primarily for the improved performance it will provide in ProTools.  My question now is how to optimize its performance for Premiere Pro CS5.  Based upon my research, I am considering the following two upgrades, but I am open to other suggestions if they would provide better results at a similar cost
    1. I am considering purchasing a 600GB WD VelociRaptor ( WD6000HLXH) for my C drive on which I would place OS (Windows 7, 64 Bit) and programs in an effort to reduce loading times of large programs.  I have two questions: (1) Are members of the forum seeing a significant improvment in program loading times with the VelociRaptor because I am still not convinced that the price performance of SSD's justifies their use; and (2) There are so many models of VelociRaptors now that I want to be certain that I am purchasing the best version for my needs.  In addition to the usual 10000 RPM speed, this model has 32MB Cache and a 3.5" form factor as well as a SATA 6.0GB/s interface (which I doubt my motherboard can take advantage of but it might extend the useful life of the drive with future configurations).
    2. I currently have available for installation in the Z800 the following drives:  (1) WD 2TB Black Caviar; (1) WD 1TB Black Caviar; (2) Hitachi 1TB.  I believe that the Z800 can accept up to 5 SATA hard drives which I will have if I purchase the Velociraptor.  Although I am reasonably knowledeable when it comes to hardware, I have never set up a RAID configuration.  Therefore, it would be helpful if someone could recommend one of the various RAID configurations and brieflyexplain why it would seem to be best for my needs.  I can then focus my research on understanding that one configuration.
    I was planning to follow Scott's suggestion for my current 3 drives:  OS and programs on C (WD 600 GBVelociRaptor), media and projects on D (WD 1TB Black Caviar), export files and Pro Tools files (all live musician tracks, no samples) on E (WD 2TB Black Caviar).  However, I have been reading about the benefits of a RAID configuration so I am interested in further suggestions now that I have clarified my questions.
    Thank you all for your help.
    Bill

  • Since upgrading to OS X Yosemite I can't run pro tools LE

    I up graded my i Mac to run on OS X Yosemite 10.10.2.
    Since uploading I have discovered that my pro tools LE is not compatible with this new operating system.
    How can I address this?
    Can I uninstall OS X?  If so, how do I uninstall?
    Cheers,
    Shaughno

    Have you checked for an update to the program?
    Do a backup, preferably 2 separate ones on 2 separate drives.
    Revert to a Previous OS X - Yosemite
    Revert to former OS from Mavericks
    Revert to Snow Leopard
    Revert Yosemite to Mavericks
    If you do revert, I'd use Setup Assistant to restore your data. This process takes a while, so do it when you won't need the computer for several hours, based on my experience.

  • Using M-Audio M-Track OSX Lion and Pro-Tools 7

    Hi,
    I have a Macbook (OSX Lion 10.8.5) with Pro-Tools 7.0something , my previous Mbox2 mini has alot of noise/interference so its toast likely. I have an M-Audio M-Track I'd like to try, will it work? I just dont want to try the Mtrack (and if it doesnt work) lose my Mbox compatibility too- I'd prefer the noisy one over nothing at all. Any tips would help. Note I havent tried hooking up the Mtrack yet, I wanted advice before messing with anything

    Hi there @Millert113 
    Welcome to the Hp Support Forums!
    I understand that you are having trouble with your M-Audio Fast Track Pro. From the sound of things I would suspect the problem is related to drivers, since the device was working for you on a Windows 7 machine.
    I think it is a matter of finding a Windows 8.1 compatible driver for the device. Take a look at these pages from the manufacturer, and see if anything there helps.
    Avid - Search Knowledge Base
    Fast Track Pro Drivers
    Just look for the correct driver that is for windows 8.1 and then try it. Let me know if that resolved it for you.
    Malygris1
    I work on behalf of HP
    Please click Accept as Solution if you feel my post solved your issue, it will help others find the solution.
    Click Kudos Thumbs Up on the right to say “Thanks” for helping!

Maybe you are looking for