Jump to content

8.0.1 and 10.5.2 who's noticing BETTER performance?


Bossanova Baby

Recommended Posts

Hey,

 

I've seen plenty of posts talking about negative performance with LP 8.0.1 and 10.5.2 , but IMHO, more people are going to post about failures rather than success's. The success's are probobly spending more time working on their music instead.

 

I'm thinking about updating to 10.5.2 , but i'd like to hear from the haves, instead of the have nots.

 

Please indicate what machine you're using as well.

 

Thanks in Advance!

 

Geoff

 

macbook 2.2

Link to comment
Share on other sites

Heya,

Aluminum iMac 20" 2.4GHz, 4 gigs of RAM. I've had various issues, ot all of them Logic related. A couple weeks ago I downgraded to Tigger to try and alleviate the problems. It worked great at first but problems started creeping back.

 

So today I bit the bullet and upgraded, first to Leopard, then to 10.5.2. I just fooled around in Logic for about an hour. One thing I do notice is that projects seem to be loading slower. Not drastically, but not as quick as was the case in Tigger.

 

Initially, I had some serious problems. One track I loaded, whenever it would get to a part of the song where a specific track would play a region, ALL of the sound would disappear. If I moved the playhead to an area where there were no regions on that particular track, everything was fine. If I moved the playhead to where there was content on that track, silence. What's weird is that everything on screen indicated it was playing, meters were hopping and bopping. So I closed the project and reloaded it - wouldn't play at all. Got the spinning beachball. I was cussing pretty heavily at this point. So I force quit logic, then reloaded it. At this point, projects would load and play, but every few seconds I was getting the dreaded core audio overload message. Great, grand, WONDERFUL!

 

I went into dashboard to take a gander at iStat Pro (quicker to do than load the Activity Monitor) and, lo and behold, there's the wonderful syslogd eating up to 173% of my processor time. Well, with this going on, of course Logic's gonna choke, if it's not left with any processor to work with. So that's definitely not Logic's fault. Phew (wiping forehead).

 

I remember having issues with syslogd doing this when I first upgraded to Leopard in October. Time Machine is not running, so it's not that. It's got something to do with when an app crashes, it goes into some crazy infinite loop where it continuously writes to a database file, causing that file to grow to gigs in size. So I went into terminal, shot out a few commands, didn't kill it, so I went into Activity Monitor and force quit it from there. Deleted the db file from terminal.

 

So then I relaunch Logic. This time everything works as expected, save for the overloads each time two or more regions appear at the same moment in previously unused tracks. So playing through the song once fixes that. I've now had this particular issue in 10.5, 10.5.1, 10.5.2, 10.4.1-11 Guess someone's trying to tell me I gotta live with it. That sucks, I wish the Logic programmers would get off their butts and reorganize how new tracks are introduced. It's not like any mac doesn't have the power to "look ahead" to know when new tracks will be activated. I know it's a holdback from the early days of Logic when processing power was much less than now, but damn. Get rid of it already! It's preposterous that a machine with, basically, two 2.4GHz processors, 4 gigs of DDR2 RAM, reading content from an external drive connected via Firewire800 would choke on 2 freaking tracks of audio. I believe it's the initialization of plugin instances that does this.

 

Sorry for the rant, but because I really like everything else about Logic Pro 8 so much, just this issue is stupid. No more, no less. T'would be nice if Apple would stop worrying about translucent menubars and funky phones and actually fix this dern program.

 

Hey Apple, ever hear of "read ahead optimization"? It's not a new concept. It would apply wonderfully here. And I might be going out on a limb by saying this, but I bet a bunch of people would even appreciate it and *gasp* recommend Logic to others!

Link to comment
Share on other sites

LOL, wasn't trying to scare anyone. All in all, I LOVE this system, otherwise I'd be back to using my PC, which now lives in my closet, under some stuff. I say go for it, it's a great machine, deceptively powerful actually. You wouldn't expect this kind of performance from a "machine in a screen". I didn't anyhow.

 

All that ranting was about one issue, and it's workable. In fact, I was just thinking that, for the plugin initilazation issue, if I create tiny audio regions, stagger their positions, so that the tracks initialize before their audio content is due to play, I bet that would be an effective workaround. But I got a gig tonight and am being too lazy to try it, LOL!

 

Naaa man, get the machine. I'm can say, with reasonable certainty, that you'll love it.

Link to comment
Share on other sites

Hey Apple, ever hear of "read ahead optimization"? It's not a new concept. It would apply wonderfully here. And I might be going out on a limb by saying this, but I bet a bunch of people would even appreciate it and *gasp* recommend Logic to others!

 

Hey Noisenet, thanks for your input, I'm still shying away from the 10.5.2 update, though i guess it wouldnt be much of a risk if I used time machine to revert to 10.5.1.

Link to comment
Share on other sites

Heya Bossanova,

I did pretty much an all day session on Sunday with zero problems. A few VI's, BFD Drums and several audio tracks. Everything went really smoothly. So I guess that's a vote of confidence for 10.5.2

 

For the record, the link below is the song I did, so you can hear it's pretty involved.

 

http://www.superswamp.com/_music/cop_show.mp3

Link to comment
Share on other sites

Heya Bossanova,

I did pretty much an all day session on Sunday with zero problems. A few VI's, BFD Drums and several audio tracks. Everything went really smoothly. So I guess that's a vote of confidence for 10.5.2

 

For the record, the link below is the song I did, so you can hear it's pretty involved.

 

http://www.superswamp.com/_music/cop_show.mp3

 

Funny, i just listened to your song on Apple Discussions Logic Pro.

 

Amazing arrangement! Keep it up!

Link to comment
Share on other sites

Bossanova,

count that as a double irony, I JUST NOW read your comment there as well. How's that for timing.

 

I'm glad you like the song. It's part of an instrumental CD I've been working on for a few weeks. It's slow going cause I'm doing everything myself, writing as I go, and only working on weekends on it, but it's coming. I'm proud that there are a lot of different vibes represented on there.

 

Anyhow, thanks for your kind words!

Link to comment
Share on other sites

Well, as soon as a session opens, it's working without any problems.

 

The only issue I'm experiencing after 10.5.2 (and I'm not alone) is the very, very long time Logic is taking to open sessions. Even when creating a new fresh one.

Some people (a friend of mine for instance) are reporting 1 minute, some, (my case) are reporting 20 seconds.

 

I did a post about it.

 

http://logicprohelp.com/viewtopic.php?t=21290

 

There's also some posts at Apple DIscussions.

Link to comment
Share on other sites

Heya Dani,

I haven't created any new sessions yet, but opening an existing session does indeed take longer than before. For me it's a few additional seconds. I don't like it but I can live with it, provided it doesn't get worse over time......

 

Yeah.

 

The problem is some people are getting a full minute.

:)

 

Gotta have patience.

 

:)

 

Mine are taking 20 sec.

 

Let's hope for a fix.

Link to comment
Share on other sites

Well, as soon as a session opens, it's working without any problems.

 

The only issue I'm experiencing after 10.5.2 (and I'm not alone) is the very, very long time Logic is taking to open sessions. Even when creating a new fresh one.

Some people (a friend of mine for instance) are reporting 1 minute, some, (my case) are reporting 20 seconds.

 

I did a post about it.

 

http://logicprohelp.com/viewtopic.php?t=21290

 

There's also some posts at Apple DIscussions.

 

Exactly the same behavior here on my MacBook with 10.5.2

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...