They'd better focus on higher ed. I know first-hand of multiple universities that have completely dropped Final Cut Pro (the platform they previous taught) to Adobe. That's hundred of video editors being minted every year that are being educated about Apple's abandonment of the professional marketplace in a failed bid to chase the "prosumer" market. Turns out there are hobbyists, there are professionals, and vastly fewer prosumers.
I've been saying it for years; Apple's abandonment of professionals blunts the tip of the testimonial spear, and it will cost Apple in the long run.
I don't see it that way exactly. I actually look at the lack of Final Cut Pro Studio updates as more of an abandonment. It wasn't even 64-bit. It was clear that it needed an overhaul and Final Cut Pro X if anything, was evidence that Apple wanted to be active in this space. They just made some bad decisions with the new version with the biggest one being a total lack of legacy support so you couldn't even open a current or recent project and hit the ground running. A good way to test out a new version is to see if it can handle the jobs you use the old one for. Having to rebuild those old jobs from scratch is a non-starter, especially without feature parity and it's a little insulting that they took the time to implement iMovie imports regardless of it being easier to do.
There was also the issue of volume licensing that made it clear they didn't even plan it to be multi-user/collaborative. Further evidence was lack of options for sharing projects and the media library that couldn't reconnect files. Working with other apps too - they put everything into Events but how are you supposed to open an Event in After Effects, save it out and have FCP know you've done it? Every time you change a piece of media, FCPX thinks you broke the connection. FCP didn't even bother asking, it just updated without skipping a beat. It is perhaps safer with projects that share media as it discourages changing shared Events but sharing media files between apps is way more important. To discourage changing shared media, it should just issue a warning.
I do think some positive PR will help but they really need to address the core design issues. If it's not possible to export an edit and email it, to export directly to a multitude of formats and resolutions without using Compressor, to share imported media with other apps for editing seamlessly, to edit natively without transcoding to ProRes first (or at the very least having to disable auto-rendering because it's not smart enough to know when it needs to render) then it's less functional than the old version and that needs to change. With Pro Apps, they need to get away from the idea that they dictate how everything is going to be. That's fine for consumer apps because the people at Apple know better. The people at Apple don't know the workflows better than the people who use the software for a living. That's not to say they should bend to every whim, there are places they should dig their heels in like moving people to tapeless media and database-based projects. They just need to start listening to the right people in the industry and maintain an open dialog. The secrecy thing is playtime and it's not necessary here. Pro Apps aren't impulse buys so surprises don't really have the same effect.
Students have started moving to Windows and Linux in large numbers.
Do they realise that Avid and Adobe products run on the Mac too or is this just hyperbole? Given that you used the phrase 'large numbers', you must have a ballpark figure.
They will this year. Marvin knows more about all this.
The chips to wait for would be the Ivy Bridge E5-2600 v2. They are scheduled for Q3, which is July-Sept:
Intel has an IDF event in April and one in September. We'll see what they say on April 10th, they might at least have demos of the E5 chips. I'd rather hear Intel announce that they are skipping Ivy-Bridge altogether and going to Haswell and that way they'd have support for DDR4 memory, USB 3 and SATA 6G.
The [2009 8-core] MacPro completed the task in 35 minutes, the MBP in 37. That is not a huge gap in time and the iMac has a lot more horsepower than the MBP. Then factor in the cost of the machines and that iMac starts looking pretty attractive.
Lots of Mac Pro owners don't want to hear that though so it won't change the rhetoric. Some people just won't accept a substitute for the MP. Even if you compare a MP1,1 to a 2013 MBP, it's fingers in the ears time. Maybe in another few years.