![]() |
![]()
Post
#1
|
|
![]() Newbie Group: Members Posts: 17 Joined: 01-May 04 From: Coeur D'Alene - US Member No.: 42,280 ![]() |
Interesting, I answered this question for myself several months ago.
I had problems (pops, hangs, no SPDIF I/O) with the Firebox on my Powerbook 667 so I returned the Firebox and bought the Traveler. The Traveler worked much better, but now on my current system (I haven't tried SPDIF I/O yet) I have to toggle the optical input settings after booting to "wake up" audio output. Still no definitive word from MOTU (they suggested the output toggle exercise) on a real fix, but at least now once it's "awake" it works until the computer is power-cycled again. As you can see from my sig I moved up to a Quad G5 from the Powerbook. I'm in this seriously, so I seriously abused my retirement savings. So far I haven't regretted it. Logic 7.1 is actually easy to use on this system, and Reaktor 5 may occaisionally make some (unintended) strange digital-lockup noises, but the CPU is still less than 35%. The funny part was I thought the lock-up was part of the Reaktor patch I was using so I recorded it. I didn't know it until I looked at the waveform in Logic. So much for my 30 years of synthesis experience... I don't currently daisy-chain a FW drive from the Traveler, but I did on the Powerbook and it worked as a recording target drive. I do use FW400 drives on the Quad G5, but I intend to get a FW800 drive for recorded sound files. I've been told that the FW800 bus is independent of the FW400 bus (which is used by the Traveler) so I'm expecting pretty good performance. Stay tuned... -------------------- Quad G5, 4 gig memory, internal and external drives, MOTU Traveler, Logic Pro 7.1.1, Sibelius, Reaktor 5, Absynth 3, Live 5, OS X 4.4
|
|
|
![]() |
Replies
![]()
Post
#2
|
|
![]() Junior Member ![]() ![]() ![]() Group: Members Posts: 145 Joined: 24-Apr 04 From: Knoxville - US Member No.: 41,728 ![]() |
Dear Friend,
I am also using a Quad G5, and I have had Slow Disk errors while using Logic Pro since I bought it in July. Have you had this problem with your G5? I've been to the Genius Bar about 4 times, and no one seems to be able to pinpoint the problem. The Slow Disk errors happen whenever I'm using a third-party plug-in like EastWest Symphonic Orchestra or Synthogy Ivory. It also happens when I'm working with audio. The other day, I only had two audio tracks running, and the Slow Disk error kept popping up. I still use Logic on my PowerBook G4, and it screams along just fine. It's sad to have a G5 Quad that runs slower than a laptop I've had since 2003. Any ideas you might have would be greatly appreciated! Sincerely, HaHaWorld Interesting, I answered this question for myself several months ago.
I had problems (pops, hangs, no SPDIF I/O) with the Firebox on my Powerbook 667 so I returned the Firebox and bought the Traveler. The Traveler worked much better, but now on my current system (I haven't tried SPDIF I/O yet) I have to toggle the optical input settings after booting to "wake up" audio output. Still no definitive word from MOTU (they suggested the output toggle exercise) on a real fix, but at least now once it's "awake" it works until the computer is power-cycled again. As you can see from my sig I moved up to a Quad G5 from the Powerbook. I'm in this seriously, so I seriously abused my retirement savings. So far I haven't regretted it. Logic 7.1 is actually easy to use on this system, and Reaktor 5 may occaisionally make some (unintended) strange digital-lockup noises, but the CPU is still less than 35%. The funny part was I thought the lock-up was part of the Reaktor patch I was using so I recorded it. I didn't know it until I looked at the waveform in Logic. So much for my 30 years of synthesis experience... I don't currently daisy-chain a FW drive from the Traveler, but I did on the Powerbook and it worked as a recording target drive. I do use FW400 drives on the Quad G5, but I intend to get a FW800 drive for recorded sound files. I've been told that the FW800 bus is independent of the FW400 bus (which is used by the Traveler) so I'm expecting pretty good performance. Stay tuned... |
|
|
![]() ![]()
Post
#3
|
|
![]() Junior Member ![]() ![]() ![]() Group: Members Posts: 145 Joined: 24-Apr 04 From: Knoxville - US Member No.: 41,728 ![]() |
Here is some info for anyone who may be having Quad problems like myself. I found this information on some other music websites:
OSX spreads the processing load evenly for all programs EXCEPT LOGIC. This is why LOGIC often runs out of processing power instead of off-loading the extra processes onto the next CPU. This is a leftover behavior from the dual-G4 OS9 setup when Logic controlled processor load by using one CPU for audio and the other for everything else. What this boils down to is that Logic is not aware of the extra processing power available on the Quad. Also, Logic will apparently only use up to 4G of RAM, no matter how much you have installed. Why Apple has chosen not to address this yet is still a mystery. Logic is now a native app, and it is very frustrating to find this information out from third parties. The folks at Apple will not tell you this information unless you pay them a consultation fee of at least $199. Maybe these problems will be fixed when and if Apple to ramp Logic up to a true 64-bit app, but I haven't heard any news. So, I guess that's a pretty big IF. I hope this information is helpful to any other Quad users out there. Those of you more knowledgable than I can feel free to correct any of this information if it is innacurate. HaHaWorld p.s. lepetitmartien, thanks for the smley tips ![]() and MacDaddy, thanks for the apology. Good luck to you. ![]() This post has been edited by hahaworld: Mon 15 Jan 2007, 22:15 |
|
|
Posts in this topic
![]() ![]() |
3 User(s) are reading this topic (3 Guests and 0 Anonymous Users)
0 Members:
