>> Have you guys tried disabling anti-aliased text in the preferences - >> it >> makes an astounding difference. >> >> regards David Young > > David, > > Please be more specific. I'd love to try out your suggestion. I > thought > OSX was supposed to be off-loading all these graphic kinds of things to > the graphics card? For the record, I'm having the same kind of slow, > sluggish behavior in the GUI. On a full song, it takes a few seconds > just > to select different tracks. > Somewhere in the preferences you can switch on or off anti-aliased text, which makes the text on the screen look smoother when it's on. I disabled it and it was faster, which is ridiculous if you ask me. It's not exactly a luxury anymore to have nice-looking text on your screen, is it? Weird you can't have this smooth type in Logic without having to sacrifice snappyness. But still Logic isn't snappy. It can take lots of seconds (you really have to wait a while) to just make a selection in the arrange for example. With the latest update (Logic or MacOS X 10.3, don't know which is to blame) it's become worse. Journaling is set off, so it can't be that. > dual 1.25 / 1.25GB ram > OSX 10.3.1 > LAP 6.3.2 > RME DSP Multiface Maybe this is the problem, because I have the RME DSP Multiface as well. RME gives horrible support to the Mac-platform. Their latest driver took ages and maybe you've noticed the arrogance of the programmers on their newsgroup? Maybe their driver isn't working properly. They blame Apple for it, which I don't entirely believe because other manufacterers can make good drivers, so why can't they? Maybe others can comment if a bad driver by RME can be the problem for the lack of snappyness in Logic. Remco

--- In logic-users@yahoogroups.com, Remco Muntz <rmuntz@g...> wrote: > Maybe this is the problem, because I have the RME DSP Multiface as > well. RME gives horrible support to the Mac-platform. Not so. RME were one of the first companies to release working OS X audio drivers, if I remember correctly. I've found them to be very responsive to support requests, more so than my experience with Emagic or MOTU. They can be a little twitchy responding to users-with-attitude on the support newsgroup, but that applies to Windows users as well. And judging by the current beta, it looks like OS X users are about to get power management and standalone mode _ahead_ of Windows users. > Maybe their driver isn't working properly. Works very very well here. Rock solid. > They blame Apple for it, which I don't entirely believe > because other manufacterers can make good drivers, so why can't they? They blame Apple for the lack of Direct Monitoring support in CoreAudio, and they are correct. Note that _no_ manufacturer currently provides Direct Monitoring in OS X, and there are no apps that support it anyway. The issue of CPU use for audio copy routines making multichannel audio devices use more CPU under CoreAudio compared to ASIO/OS9, is also Apple's problem. This has been noted by other manufacturers as well. There is now (in Panther) a facility to turn off any unused audio i/o channels in the driver to save CPU, but this is a workaround at best, and requires the host application (ie Logic) to support that (which it currently doesn't). > Maybe others can comment if a bad driver by RME can be the problem for > the lack of snappyness in Logic. Highly unlikely. Yes, it's slower on redraw than in OS 9 for me too, especially noticeable in screensets with lots of windows open. But that is still true if I switch to Mac built-in audio. It's much more likely to be something like OS 9 QuickDraw drawing code that has been ported to OS X, rather than re-coded, and then not especially optimized for the new platform. John Pitcairn

On 1/12/03 12:24 pm, "John Pitcairn" <johnp@...> wrote: > > They blame Apple for the lack of Direct Monitoring support in CoreAudio, and > they > are correct. Note that _no_ manufacturer currently provides Direct Monitoring > in OS X, > and there are no apps that support it anyway. > Hi John, Could you clarify that. I'm getting a horrible feeling I've just made a stupid mistake. I've just taken delivery of a PCI/Digiface combo to go in my new G5. Replacing the Hammerfall 9652 in my G4, because 1) fewer pci slots and 2) I figured that as the buffer setting needs to be set higher under OS X to suit my TC Powercore, I could get round the latency that will cause by using Total Mix. Is that not gonna work in OS X? Cheers Gareth

John - I read in several of your posts that you loop back the SPDIF for mixdown. If I try that, I get a samplerate error in Logic. Is there anything I should know, other than plugging a cable in from SPDIF out to SPDIF in? The RME is clock master. Thanks, U.

--- In logic-users@yahoogroups.com, Gareth Henderson <gareth@s...> wrote: > Could you clarify that. I'm getting a horrible feeling I've just made a > stupid mistake. I've just taken delivery of a PCI/Digiface combo to go in my > new G5. Replacing the Hammerfall 9652 in my G4, because 1) fewer pci slots > and 2) I figured that as the buffer setting needs to be set higher under OS > X to suit my TC Powercore, I could get round the latency that will cause by > using Total Mix. Is that not gonna work in OS X? It works fine. RME's "ZLM" (zero latency monitoring) offers <1ms latency when monitoring through TotalMix. What doesn't work yet, because CoreAudio hasn't supported it and no hosts support it, is the CoreAudio equivalent of Steinberg's "ASIO Direct Monitoring" protocol, whereby the host software controls the Totalmix monitoring volume directly according to the host's channel volume/pan settings. From what I can remember, that didn't work on OS9 in Logic either... John Pitcairn

--- In logic-users@yahoogroups.com, "anulsinn" <anulsinn@p...> wrote: > I read in several of your posts that you loop back the SPDIF for mixdown. If I > try that, I get a samplerate error in Logic. > Is there anything I should know, other than plugging a cable in from SPDIF out > to SPDIF in? > The RME is clock master. That's all I'm doing, and it works fine for me... John Pitcairn