• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: CPU Usage difference
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CPU Usage difference


  • Subject: Re: CPU Usage difference
  • From: Richard Dobson <email@hidden>
  • Date: Fri, 06 Mar 2009 15:16:04 +0000

tahome izwah wrote:
Well, if you ask me the reviewers at "Sound on Sound" aren't exactly
known for their competence... and I would like to think that after all
those years they should be able to do better than that and provide
some hard facts when they review products, but apparently not...
"overload indicator started flashing"... how ridiculous is that.



It varies. Most reviews are done by freelancers (did one myself many many years ago), and most are expected to concentrate on cool musical stuff, of the "hey you can do X" and "pity you can't do Y" variety. Readers typically don't like too much science in their reviews. Cubase5 came out extremely well overall; this panel on the reverb issue was a small fraction of the whole. Technical stuff tends to be relegated to sidebars in this way, but more usually to a few specialist articles by staff members or invited experts, and here the standard is pretty high.

It has to be said though, that the implications of multi-core (in all its many forms) for audio have barely been considered in the musical or technical press (or academic press for that matter), and only then in the most vague and general terms. I indeed await Snow Leopard to learn just what it offers, but will not be able to get a good idea in the absence of a quad or eight-core machine. Which is why, despite actively researching the subject of concurrency for audio in various aspects, I am myself dependent on reviewers being given express instructions to watch that Activity Monitor and report accordingly.

Unless Apple folk here can say categorically there is a way by which a plugin (or if necessary, a particular track) can rely on being able to use more than one (available) core, we will be dependent on such reviews to know a posteriori where we stand. It will definitely be an issue when the first 16-core machines roll off the production line. That may only be a year away.

Richard Dobson


_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >CPU Usage difference (From: Alex ROUGE <email@hidden>)
 >Re: CPU Usage difference (From: tahome izwah <email@hidden>)
 >Re: CPU Usage difference (From: Alex ROUGE <email@hidden>)
 >Re: CPU Usage difference (From: tahome izwah <email@hidden>)
 >Re: CPU Usage difference (From: Richard Dobson <email@hidden>)
 >Re: CPU Usage difference (From: tahome izwah <email@hidden>)

  • Prev by Date: How to Access and change mAudioData??
  • Next by Date: Re: Recording compressed audio file
  • Previous by thread: Re: CPU Usage difference
  • Next by thread: Re: CPU Usage difference
  • Index(es):
    • Date
    • Thread