|
|
Dual Processor Support, i have a question :) |
|
|
|
Fri 27 Sep 2002, 17:00
|
Newbie
Group: Members
Posts: 11
Joined: 13-Aug 02
From: Hanover - DE
Member No.: 6,841
|
hello! im using logic 5.2 on os9. currently only one processor is computing the plugins, the other one computes the gui afaik. will that change in the future, perhaps with osx/audio units, so that both processors are used for computing the plugins? thn for any hint! rage
--------------------
|
|
|
|
|
Sun 29 Sep 2002, 19:15
|
Newbie
Group: Members
Posts: 11
Joined: 13-Aug 02
From: Hanover - DE
Member No.: 6,841
|
nobody? ...
--------------------
|
|
|
|
|
Mon 30 Sep 2002, 02:27
|
Moderator In Chief (MIC)
Group: Editors
Posts: 15,189
Joined: 23-Dec 01
From: Paris - FR
Member No.: 2,758
|
Sorry but I saw your post 2 days ago and after moving it (you bad boy spank spank) I forgot to answer (too many bad boys) In OS9, mutiproc support is define at the app level, so DP uses both procs on task-to-do basis. Logic is different as it affect one proc to midi and the other to audio, not the best way to do but at least they use both. In OSX, multiproc support is at the os level. That is the system decide, the app follow so that everything runs with the power it needs, which can use both procs. On the exact brewing, a developer maybe could give us a bit more light but for me it's enough. On the intricacies of audiounits etc. a thread is already here about, with a link to the docs from apple upon if I remember well. Anyway, first thing is to have a biproc mac
--------------------
|
|
|
|
|
Mon 30 Sep 2002, 08:17
|
Advanced Member
Group: Members
Posts: 351
Joined: 12-Aug 02
From: London - UK
Member No.: 6,795
|
On the audio path. there is very little interest of attempting to use both processors at once; since it's sequencial in nature - ie you need the output of plugin 1 as output of plugin 2. Now one could imagine using 2 processors for 2 tracks, however, one must know that synchronising threads is not only hard to do, but also very expensive as far as the processor is concerned. especialy, achieving sample accuracy is next to impossible, even with "real time" threads. he more tracks you'd have, the harder it would get. So it migth be that an application like an audio one would use more CPU power to keep in sync than whats gained by using 2 CPUs. So, for the pure audio, thats the answer: KISS (Keep it Simple, Stupid ;-)) It is much easier for everyone to sequence multi tracks using one thread, so, why bother ? However, there are many other things an application can do with 2 CPUs. Like the VST plugins could use a separate thread to run their snazy windows in etc. That very much everyone to itself at that point.
--------------------
|
|
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
|
|
|