- What We Do
- About Us
- Contact Us
Avid released the following a little while back and it is still in place.... Apple has released OS X Lion (Mac OS X 10.7). As of this writing Pro Tools 9 and all earlier versions of Pro Tools software are not compatible and will not work with OS X Lion. We are currently working with Apple in order to provide a compatible release of Pro Tools and will notify you as soon as this work has completed.Read More
Avid is tracking reports of kernal panics on HD Native systems after updating to Mac OS X 10.6.8. At this time they recommend that HD Native customers do not update to 10.6.8. I have to say I always wait until Avid/Digi approve the new version of the OS before updating, in fact I am still on 10.6.6 here.
Avid has identified an incompatibility with the early 2011 17" MacBook Pro (model MC725LL/A with Thunderbolt port) when used with a Magma ExpressBox1 expansion chassis and a Pro Tools HD Native Card. The following error message, "Unable to find an Audio Interface attached to the first HD card", is seen when launching Pro Tools HD 9 with an Apple MacBook Pro (early 2011 model) and Pro Tools HD Native hardware. For additional details, see Knowledge Base article 396031 Please Note This is only with HD Native core cards in the specific configuration listed above. Other qualified MacBook Pro models do not have this incompatibility: Pro Tools HD 9.0 Qualified Apple Computers
I came across this report on the Designing Sound blog in a post by Miguel Isaza. Miguel posted... Sound Designer John Kassab, who shared the Harry Potter interview with us some days ago, has sent me very interesting report he just finished about the state of post-production film sound in both conceptual and technical ways. The text includes some introductory theories, detailed analysis of different topics, and also interviews with sound professionals from different sides of the world. Project Description: To investigate creative, technical and workflow innovations in post-production film sound in London, New York, San Francisco, Los Angeles and Wellington. Highlights: The highlight of this project was being able to meet with such great cross section of visionaries in all corners of the English-speaking world at this particular moment in film sound history. Major Lessons and Conclusions The greatest lesson I learned is that the digital domain is creating many changes to work flow and collaborative methods in film sound and the global industry seems to be going through something of a metamorphosis. As a result, the focus of many topics in this report concern how the industry is evolving as the result of digital and computer based solutions. Download PDF here. Having read it, I have found many parallels in it for other industry sectors including my own in radio production. In the report John listed a number of developements he would like to see added to Pro Tools. I thought I would use a portion of this report to ask AVID to revise and add a few things to make our working processes a little smoother. This list was compiled in collaboration with Derek Vanderhorst, and Stephen Gallagher. 1. Can you please introduce ability to open multiple sessions so we can rebalance sessions or even cut similar scenes and copy/paste between them? 2. Can you introduce automation for the bussing assignments? 3. What about clip based automation? 4. A 64 bit floating point would be nice, too. 5. At least 1000 tracks even if voices are limited. This would be great for rebalancing and carrying all the elements to the stage in one session. 6. More than 192 voices, please. Most other audio editing applications are dependent on the CPU. Can’t delay compensation be used to free these shackles? 7. Can we have Audiosuite handles and non-linear processing ‘undos’? It’s really frustrating for sound designers and my desktop is covered in screen shots so I can keep track of my processes manually. Also, and ‘undo’ for accidently deleting plug-ins would be great too. 8. LKFS metering in Phasescope? 9. A persistent monitor section when opening/closing sessions for things like headphone mixes would also be nice. 10. So would Multi-mono plug-in presets that are actually presets for all mono components. 11. Please add the ability to add busses from the mix window. 12. Customizable key commands would be great to provide more efficiency for our talented brothers and sisters who prefer to work with other DAWs. 13. Please let us save clips with the layout automation in tact to drag and drop into another session like you can in Nuendo. 14. When will we be able to right-click on a stereo region to flip the left and right track? 15. Please let us be able to record the sound the ‘scrubbing tool’ makes. This will be particularly useful for sound designers who like to perform their sounds. 16. Can you please give us the option to bounce a project without having to sit through it in realtime. Make a warning pop out at us if you are concerned about anything, but please give us the option to hit “ignore”. Most importantly, don’t make it crappy so you can say “I told you so”. Other software companies have been making really good ones for years. Please make it like that. I wonder if these have been submitted to the Pro Tools IdeaScale site? If not we should. Thanks again John for a very stimulating report and I look forward to more in the series.
Avid announced this on Christmas Day! Avid is pleased to announce that Mac OS X 10.6.5 is officially qualified with all versions of Pro Tools 8.0.4 and higher, including: Pro Tools HD, LE, and M-Powered 8.0.4 Pro Tools HD 8.1 Pro Tools HD 8.5 (for HD|Native systems only) Pro Tools 9.0 Pro Tools HD 9.0 Also qualified are the current versions of the following: Pro Tools SE 8.0.3 Pro Tools Essential 8.0.3 If you are updating your system from an earlier version of Mac OS X 10.6 (Snow Leopard) to version 10.6.5, the following update is recommended: Mac OS X v10.6.5 Update (Combo) For information on Pro Tools version compatibility and requirements with different OS versions of Mac and Windows, see the Pro Tools Compatibility home page: www.avid.com/compatibility Or click on the Pro Tools Compatibility link at the top of the forum. I am hoping to create a new boot drive with a clean install of everything as I have been cloning drives for several years now and so I am taking the opportunity with Snow Leopard to start from scratch. However I am doing it on a fresh drive so I don't mess up my current working Leopard boot drive or the back up of it that Super Duper updates every evening for me. I will keep you posted on my developments over the next month when hopefully I will have some time to do it.
I have been getting a number of calls from clients asking what to do when they get this message... Quite often it comes up when they have moved a session on a drive from one system to another, its fine on system one but this message comes up on system 2. So what to do? Go into the Workspace window which you find in the Window menu of Pro Tools and when it opens it will look something like this... We are interested in the letters in the A (audio) and V (video) columns. The letters set the status of the drive. Any drive that isn't formatted correctly will be set to T (Transfer) drive as these drives can only be used to transfer sessions from one system to another. They cannot be used to host active Pro tools sessions. However it is my experience that these settings can 'change' on drives that can support Pro Tools sessions, so it is useful to know how to reset them. You will notice from this screen shot that 'Work Disk 2' is set to T which is what caused the error message above. Assuming the drive is correctly formatted, to reset it back to normal, click on the T and a little menu will appear. Change it to R if you want to be able to Record onto this drive or if you want to prevent recording onto the drive you could set it to P so you can Playback a session from this drive. Now that Work Disk 2 is set to R, the session will open and all will be fine. Another way to solve this, especially if a drive repeatedly goes back to T or P on one system but is fine on another is to delete the Volumes folder in Unicode - Databases - Digidesign - Application Support - Library on the start up drive of the system that won't play ball. Be careful though, not to delete the Catalogs folders though as this is where any catalogs you might have created are stored. Once you have put the Volumes folder in the bin and emptied it, restart the computer and when you relaunch Pro Tools it will create a new Volumes folder. You could of course use the excellent Pro Tools Prefs and Database Helper application to do this for you, just select the Volumes button from the options..
Folk have been having some problems when buying Mac friendly pre-formatted drives like a Seagate FreeAgent Desk for Mac as it comes pre-formatted with GUID partition map. I you have an Intel Mac then that will NOT cause you a problem. However if you have a PPC or you are going to end up at a facility that still has Power PC Macs you will need to reformat it to the Apple Partition Map before it will play with Pro Tools nicely. This little problem slipped in with the introduction of Intel Macs and Mac OS 10.4.6 when GUID Partition Table support was introduced. The default mode when formatting drives now on Intel Macs is GUID Partition Table. If you put this drive onto a Power PC Mac like a G4 or G5 then you are likely to get 9131 errors in Pro Tools. You can check if your drive is partitioned with a GUID Partition Table using Disk Utility. If you select the higher level icon in the drive list in Disk Utility, in the bottom section it will show what partition map has been used. Any drive formatted on an Intel Mac will use a GUID Partition Table. You will need to use the Options menu in the Partition tab to force Disk Utility to select Apple Partition Map. Alternatively just format the drive on a Power PC Mac and it will be formatted with an Apple Partition Map. If you have an incorrectly formatted drive you will need to move all the material off it to reformat it with the correct partition map. So if you do buy a pre-formatted Mac friendly drive then check it with Disk Utility first and pre-format it BEFORE you put anything on it. It is in the Pro Tools documentation but it has caught me out!
There have been a number of additional posts on this thread on the Digidesign User Conference since I posted the main findings here. But this one caught my eye as being in the same vain as the first. There had been some discussion on whether a USB to VGA adaptor might work so 'Mubeau' tried it and posted his findings... I´m on G5, HD3, 2PTs screens, PT 7.4, VVTR and Canopus (on the PT mac and on the VVTR System, depending on the project) Today i tried a USB to VGA/HDMI external video solutions. (displaylink). Results: 1. I would not use this for video playback (even SD has no good playback) 2. it was usable for the PT Mixer or HD content or something similar. BUT: it also eats up power from the CPU, of course. WHAT TO DO NOW?: I have to upgrade my MAC since the G5 dual 2,5Ghz is getting to slow for me. HD 3 accel with decklink (my favorite setup) means: PCIe expansion (I really dont want this!) I would also love to use a third video monitor. Having said this: has anyone of you tried the new 3 x PCIe Expansion Box I would be very surprised if this expansion bow would work with Pro tools. How many times have we been here before? Anyone up for an experiment?
This is a reproduction of the first post of a thread on the Digidesign User Conference by the user "Nucelar" who decided to create a thread and outline the options, pros, cons, and costs of all the different options for displaying video with Pro Tools. Pro Tools video Output options: 1. QuickTime to desktop monitor (1st or 2nd monitor port, with or without DVI-video adapter) System requirements: Any Mac or PC with a secondary DVI or equivalent monitor output PROS: Cheapest solution. Low latency. Good quality when DVI or VGA is used. Handles most codecs Quicktime can play back. CONS: You only have one monitor left for Pro Tools. Uses CPU for video decoding, thus less power available for other tasks (such as RTAS). Output only. Does not output a native video signal: may cause visible tearing due to refresh rate not equal to frame rate. PRICE: Adapter 19 US$ from Apple + cable for example here & here Note: If you're on a Mac Pro or G5, you could use a Matrox DualHead2Go on your primary DVI output to connect one more monitor, but it's not approved by Digidesign. 2. Canopus converter (ADVC110 is the most popular and approved by Digidesign) System requirements: Any Mac with Firewire port (Firewire 400). FW 800 to FW 400 adapter cable may be needed. Should be used in a dedicated Firewire 400 bus, not in the same bus as interfaces or audio hard disks. PROS: Cheap hardware. Controlled latency (about 18 quarter frames) . Captures SD analog video in DV format as a bonus (using third party application). Frees CPU from video decoding. CONS: Mac only. Video must be available in DV format. SD only. Composite or S-Video output only. Irregular and unpredictable sync PRICE: about 200 US$ WEB: ADVC family 3. Avid MOJO SDI System requirements: Any Mac or PC with Firewire port (Firewire 400). FW 800 to FW 400 adapter cable may be needed. Must be used in a dedicated Firewire 400 bus, not in the same bus as interfaces or audio hard disks. PROS: Direct Compatibility with Avid video files (MXF). No latency with avid video. Captures video directly into Pro Tools session in sync. Frees CPU from video decoding. CONS: Quite Expensive. SD only. Struggles with codecs other than Avid's. PRICE: 2500 US$ WEB: Avid Mojo SDI 4. Digidesign Video Satellite LE System Requirements: Main system must be Pro Tools HD. Needs a second computer dedicated exclusively to video output. Connects to the main PT system via Ethernet. Secondary computer could be a Mac Mini, but then you're stuck with the drawbacks of desktop video quality. For best performance, secondary computer should be a Mac Pro with a Decklink HD card. (see Post #2) PROS: Dedicated, stable, scalable and flexible solution from Digidesign. Frees main CPU from video decoding. CONS: Relatively Expensive, hassle of second computer PRICE: Mac Mini+ Mbox micro + Video Satellite = aprox. 1200 US$ PRICE: Mac Pro + Decklink HD +Mbox Micro+ Video Satellite = aprox. 4200 US$ WEB: More info on the Video Satellite LE 5. Avid Video Satellite WEB: More info on the Video Satellite 6. Chase video deck System requirements: Pro Tools System with Machine Control ability and of course a pro video deck. PROS: You can use professional deck for direct playback and layback. No capture or conversion needed. CONS: Very specific workflows. Tape-based, linear. Additional wear of deck heads. Downside when editing: forward-selecting to picture is not possible because PT only outputs positional info when selecting backwards. PRICE: You don't want to know the price of a digibeta deck. Notes:The Rosendahl Bonsai Drive can be used as a standalone non-linear VTR, eliminating the drawbacks of tape-based decks. SD only. 7. Blackmagic PCI Card System Requirements: Any Mac Pro with a free PCI-e slot PROS: Very good price/performance. Digi approved solution. Accepts all Quicktime-playable codecs. Very good video quality. Controlled latency. CONS: It uses CPU Power for video decoding. Does not capture into Pro Tools or handle Avid video, unlike Mojo. PRICE RANGE: from 200 US$ (Intensity) to 1000US$ (Decklink HD Extreme) WEB: More info the Blackmagic web site 8.Virtual VTR Third party software installed on a secondary Macintosh computer for dedicated video playback and recording."Can be externally controlled via Midi, Sony 9-Pin protocols or TCP/IP, and can also synchronise playback, chasing timecode, even in multi-channel configurations." PROS: Basically the same as Video Satellite LE CONS: Basically the same as Video Satellite LE, Mac Only PRICE: Software is around 1000 US$ WEB: More info on Gallery web site "Nucelar" has done an excellent job in producing this compendium and it provides an excellent resource to help all those who need to display video within Pro Tools sessions to choose the option that suits them best. I have gone for a Canopus ADVC 110.
Recently there have been two threads on the Digidesign User Conference on this subject. One asking about the best codec to put the least strain on the host CPU usastra asks I have a session for a live concert with a quicktime movie using the H264 codec. When the movie is online it crashes very often, especially if I set the cursor to a new place in the timeline. If the movie is offline PT is way more stable (though still with the occasional crash).. I was wondering if the session could be made more stable if I render the movie with a different codec and which codec would be best so I would have the least CPU strain? The other commenting on the load playing an mp4 file has on the host CPU. Roger Stauss asked... I've been using an Mp4 vid to ease the up/download time. The PT session runs with some latency. It's very smooth with a QT DV. Is there a way to smooth out the session operation? (I run Video on separate drive) I have compiled the best responses from both threads below... Chief Technician advised simply... Use the DV codec. c.evans agreed... Agreed. The DV codec works well on my system, but what really helped is adding the Canopus ADVC 110 and sending my video out to an external monitor. Also, it is very important that your video is playing from a separate drive than your audio. I even use the internal SATA buss for my video when using firewire for video. It also helps to have a third party PCI firewire card to add some beef and options to your system. Craig F chipped in... mp4 is a intraframe codec same as h264 hence heavy CPU usage. José Luis Díaz explained... Always choose intraframe codecs (DV, Motion JPEG-A, Photo JPEG, etc). Always avoid interframe codecs (H264, Sorenson, etc). Interframes codecs demand much more brute force from CPU than intraframe codecs. Intraframe codecs only compress the data of one frame regardless any adjacent frame. But to decode a simple interframe stream of frames (like H264) the CPU of your computer will dedicate a lot of its cycles just for that simple moving image because it must to compute differences and similarities between frames. Check all this with Activity Monitor App. Play a PT session with an interframe movie. Them the same with a intraframe movie. Jon_Atkinson added.... Digidesign Technical Support have gone on record here a few times saying that H264 has been the root of many PT related QT problems. "A can of worms" was, I believe, the phrase used.... usastra responded... Thanks for all the replies! For now, I have converted the videos to mjpegB and the session runs much smoother! I will experiment with other codec later. philip888 asked.... What are you using to convert with? usastra replied.... Quicktime Pro Rick Sanchez confirmed.... A couple of solutions I found that worked well for me. 1. Once you've downloaded the video, use Quicktime Pro to transcode it to DV. If you have a fast computer, it's pretty quick to do. Usually much quicker than the download time. 2. Tell the editors to send you Motion JPEG A video instead of MP4/H.264. It's still very small and plays well with ProTools. One of the falsehoods about H.264 is that it is not a frame accurate format. This is not really the case. It can have a variable frame rate, but that is a setting when you do the original encode/capture. What it is, is a long GOP (Group of Pictures) format. Much like Mpeg2. In the first frame, all of the pixels are captured. In between the first (key) frame the next (user selectable) key frame, the computer looks for differences between the the Key frame and the next frame and only encodes anything that has changed. If the pixels (say a non-moving background) stay the same from frame to frame, it just fills in the blank with already captured pixels. Then when the next Keyframe comes around again (I think the default is 24) it captures all of the pixels and starts over. It's much like creating an audio ambiance fill track for a scene. You only need a few seconds of fill and then you loop it until there is the next change in ambiance. I take no credit to the advice I have quoted here but do confirm it from my own experience.
There is a growing thread on the Digidesign User Conference on 9019 and 9031 errors on Pro Tools 8.0.3 It was started by Nathaniel Reichman asking... Since moving from the various 8.0.1 releases to 8.0.3, I frequently get the message: "DAE is having trouble keeping up. Your disk may be too slow...firewire, etc., etc. (-9019)" which is followed by a beachball and then: "DAE error -9031 was encountered." And this repeats until we quit the app and relaunch. Sometimes hours go by with no problem, sometimes we get this 3 times in an hour. We haven't seen this in PTHD, only on the PTLE/CPTK system listed below. We tried trashing databases and volumes folder. After some system and workflow checks Reichman confirmed... Nothing has changed in my typical post workflow or drive usage since PT 7.3. Thanks for posting, but I really doubt the non-contiguous file theory. If that were true, none of my projects would have worked with any version of Pro Tools. For now, I blame the .3. "Garnoil" responded.... Ok, so it must be .3. I am on 8.03 and although I had one massive, annoying, problem (0922 too many files corruption), 8.03 *at least for me*, has been a great improvement. I run HD2 and push it to the limit, I mean 192 voices (160 tracks+) + full HD film at 2k resolution. So far, so good but of course there are lots of bugz to fix, some worse than others. Good luck! Then Digi Tech Support weighed in... I see you have an eSATA hotswap tower in there - is that what you're using for playback/record? If so, have you tested with other drive types? 9019 is a drive error related to drive communication speed - we usually see it on PC's where drives are not in DMA mode. The 9031 error is usually related to having illegal characters in the drive, file or folder name - is that possibly the case here (keep in mind that previously fudged illegal character acceptance is no longer possible, so what may have 'worked' before no longer will)? Reichman responded.... Yes. And I know it's not officially approved, but it's performed flawlessly every since PT 7.3 on a G5. I thought I cleaned out all of my illegal characters in the PT6-7 transition. Thank you for writing back so quickly. I'll report back if I learn anything. The "smpkeys" chipped in.... I just experienced this same problem. I've been on 8.0.3 for about 2 weeks and have not seen this, however , tonight I was using the playlist lanes view for the first time, and that's when it occurred. All my drives are internal SATAs - 1 for OS, 1 for audio, 1 for samples. Not using any video in my session, and no illegal characters. Reichman - have you found a solution with your setup? Reichman replied... Haven't found a solution yet, primarily because it is happening infrequently now. Occurred once yesterday when opening an AudioSuite plug-in window. Every time it does happen, it will continue persistently until I save, quit and restart PT. When I get out from under this mountain of work, I'll try another drive type for a while and see if that helps. For the record PT 8.0.3 is really stable. For PT8 doubters, now is the time to get on board (is Frank Kruse reading this? :) ) Digi Tech Support came back with a request... Can you guys do something for me - after you experience the error, quit Pro Tools as soon as possible after it, then send me your LogFiles folder from inside your Pro Tools folder. Zip it up and send it to: vi [at] digidesign [dot] com. Put the thread number (265212) and '9031' in the subject of the message. "Sunzate" added... I'm getting these errors right now with a midi-only session, controlling the PLAY EastWest orchestral plug-in. Never seen it before today. Recently updated to 8.0.3. Let me know how I can help. Then "Oroz" asked... I'm getting the DAE error -9031 a lot! Can you further explain what do you mean by illegal characters in the drive? How can I solve it? Digi Tech Support replied... Your Pro Tools Reference Guide has a list of unsupported characters. You should make sure that no drive, folder or file name contains any of those characters. This error on Mac is also caused by incorrect drive format. I would recommend backing up your audio/video drives and erasing them using the Disk Utility, then copy the data back and test again. Oroz asked... Do you think that it may be because I'm recording to a partition (dedicated to audio) of the internal drive? If so, would a USB external drive be a solution? Since I'm on an iMac there's only one Firewire 800 port. I have read successful stories from guys using USB drive as an alternative but I'm not sure. Digi Tech Support replied... Recording to a partition or to a USB drive is not recommended or supported and definitely could be a cause for these errors. Please see the General Troubleshooting thread for more details. With an iMac that has only one FW800 port, get a FW800 to FW400 cable to connect to your drives and interface. smpkeys posted... Just happened to me again on Saturday. This time when it happened, I was changing the output of a channel. Digi, I've zipped and sent my log file using the directions posted earlier. One more thing - I had trashed prefs about 2 hrs before this crash. So a couple of lessons from this thread. You cannot use USB drives for Pro Tools sessions. USB needs processor time to negotiate the data transfer on and off them and does it when it gets round to it. Where as Firewire has dedicated chips on the interface to manage the data transfer in a timely manner. You must have correctly formatted drives irrespective of what platform you are running on. On the Mac platform that must be Mac OS Extended with journalling. I recommend you format your drives with Disk utility rather than any 3rd party formatting software. Check the characters that are used for naming anything. Drives, folder, file names.
This is a scary bug that somehow has slipped through the beta testing process. If you want to read all the posts then click here, but here is a synopsis of the issues and suggested work rounds... nhaudio outlined the basic problem... Just updated ProTools to 8.0.3 on two systems and have found a major problem: If I save and close a session that has a video file in it (.dv which is going out firewire to a Canopus ADVC110), when we try to reopen the session, ProTools 'Unexpectedly Quits' when trying to rebuild windows (the last few status updates you get when a session is opening). Sessions with no video file open fine, no problem whatsoever. We can't work like this! We open various tv commercial sessions all day, and rebooting each time is brutal!!! Digidesign pitched in very quickly and asked for crash log file details... In Pro Tools 8.0.3, we added better and more robust logging to help track down problems like the one you are seeing. When Pro Tools crashes, some information about the crash is written out to a log file. The log files are kept in the "LogFiles" folder that is next to the Pro Tools application. Here's what you need to do... 1) Reproduce the crash you are seeing. 2) Look in the LogFiles folder and find the latest log file. The file name ends with .dlog 3) Email this "dlog" file There is no need to do it now as the list of posts confirming the problem grew very quickly and Digidesign quickly confirmed they could reproduce the problem... We can now reproduce this bug in our test lab. We're still investigating what is going with this bug and are trying to narrow down the root cause of the issue. It looks like there is some combination of changes that were made in Pro Tools 8.0.3 and updates to the Apple QuickTime software that introduced this issue. I'm glad to see there are several workarounds for this problem, albeit not particularly nice ones. Bob Brown Principal Software Engineer Also two workarounds came through from users. The first came from nhaudio… I've found a workaround for now. It seems if the Canopus is powered off when I launch a session, it opens fine. Then I can turn the Canopus back on and work as normal. So for now, I plan to turn it off before opening any session to keep workflow... well... flowing. And the second from stustan… I also have the exact problem but I have a different work around that is 100% effective. Instead of bothering with the Canopus Box which is out of easy reach, I rename the pix folder by adding an X to its name. PT 8.0.3 LE then opens perfectly with the relink window informing me it cannot find pix. I then relink to the renamed folder and all is well. The next time I need to boot the session I rename the folder again, usually back to the original name and go through the above steps. My pix folder's name then flip flops between Pix Folder and XPix Folder Then diamondscwin chipped in to say… at the moment it seems to me that Quicktime playback and 8.0.3 is broken... people in this thread are reporting issues with Blackmagic cards, AVID Mojos, Canopus boxes and just desktop playback... only cure regardless of OS is rolling back to 8.0.1 so I dont think its apples fault. Then uno1234 was one of several that suggested… We are reverting all our 4 systems back to 8.01. As nasty as that 8.01 bug list is, we just can't deal with firewire out crashing anymore. How exactly does an official software release get so bungled up like this? Was there no beta testing in a simple post production workflow? Is there ANY accountability at Digidesign anymore? Also to note that the 8.0.3cas1 update hasn’t fixed this problem so it would seem that for video post facilities using video peripherals should say on Pro Tools v8.0.1 for now.
Digidesign have made this announcement...Pro Tools Compatibility with Newly Released Apple ComputersOn March 3rd, Apple, Inc. released new versions of the iMac, Mac mini, MacBook Pro, and Mac Pro. We have completed our testing and are pleased to announce that Pro Tools LE and M-Powered 8.0 systems are compatible with these new Apple computers.In addition to the previously announced Pro Tools HD 8.0 compatibility with the latest Mac Pro "Nehalem Processor" models, the late 2008/early 2009 MacBook Pro models are now qualified with Pro Tools HD 8.0 systems (Magma ExpressBox1 Pro or ExpressBox4 expansion chassis required).For the most recent information about Digidesign products and updates regarding the qualification of the new iMac, Mac mini, MacBook Pro, and Mac Pro, please check the compatibility pages at the Digidesign web site.
Good news! This has come form the Waves Support web site...Waves is pleased to announce that our entire V6 product line (installers V6.0.8) now supports Pro Tools 8. This includes support for Waves Surround plug-ins under PT LE and PT Complete Production Toolkit.Known IssueWhen using the following TDM plug-ins on PC with Pro Tools metronome active, Pro Tools freezes.EnigmaMetaFlangerMondoModSuperTapGTR StompsTo avoid this scenario, either deactivate Pro Tools metronome, or use the RTAS versions of these plug-ins.You can get more info from the Waves Support site.