I'd like to see if anyone else experiences this problem. It'll help with my troubleshooting. Periodically, when I try to bounce a mix - or layback audio to a Quicktime from a Logic 8 project - Logic will give me the spinning beach ball, and I have to force quit. Sometimes I'll get the crash notice (and the "crashed" save), sometimes not. When I do get a crash notice, the crash report almost always has Ivory at the top of the list. However, when I reopen the song - it bounces fine. It also seems that the longer the song is open, the more likely it is that a crash will occur. Perhaps there's a compatibility problem with the Ivory plugin? I use Ivory in almost everything I do, so it's a fairly constant - and irritating - issue. Thanks in advance for any help or advice. Other pertinent facts: Dual 2.3 G5, Motu 828 Mk II (but also happens at home with an Apogee Duet, so it's more likely a software issue), Logic 8. Fred Story

--- In logic-users@yahoogroups.com, "fstory2000" <fred@...> wrote: > > I'd like to see if anyone else experiences this problem. It'll help with my troubleshooting. > > Periodically, when I try to bounce a mix - or layback audio to a Quicktime from a Logic 8 > project - Logic will give me the spinning beach ball, and I have to force quit. Sometimes I'll > get the crash notice (and the "crashed" save), sometimes not. When I do get a crash notice, > the crash report almost always has Ivory at the top of the list. However, when I reopen the > song - it bounces fine. It also seems that the longer the song is open, the more likely it is > that a crash will occur. > > Perhaps there's a compatibility problem with the Ivory plugin? I use Ivory in almost > everything I do, so it's a fairly constant - and irritating - issue. > > Thanks in advance for any help or advice. > > Other pertinent facts: Dual 2.3 G5, Motu 828 Mk II (but also happens at home with an > Apogee Duet, so it's more likely a software issue), Logic 8. > > Fred Story > Fred, I haven't experienced that problem, but I don't have that plug-in either. Is it a CPU intensive plugin? If it is or even if it isn't I would try freezing that track so that the plugin isn't running realtime with the bounce. Often with CPU intensive plugins there is a issue with bouncing and latency and the time it takes for the audio to process through the plugin. You also may want to bounce in realtime ( I don't know if you are bouncing offline). That too may give the plugin extra time to process the audio. I think the freezing of the track however may be the best and most obvious fix. If all that doesn't work, an increase in the buffer size would probably give the CPU more time as well, but that is really the last resort since with a Dual 2.3 G5 and an Apogee you shouldn't have any latency issues. Ivan

--- In logic-users@yahoogroups.com, "Ivan Walker" <loco_7even@...> wrote: > > --- In logic-users@yahoogroups.com, "fstory2000" <fred@> wrote: > > > > I'd like to see if anyone else experiences this problem. It'll > help with my troubleshooting. > > > > Periodically, when I try to bounce a mix - or layback audio to a > Quicktime from a Logic 8 > > project - Logic will give me the spinning beach ball, and I have to > force quit. Sometimes I'll > > get the crash notice (and the "crashed" save), sometimes not. When > I do get a crash notice, > > the crash report almost always has Ivory at the top of the list. > However, when I reopen the > > song - it bounces fine. It also seems that the longer the song is > open, the more likely it is > > that a crash will occur. > > > > Perhaps there's a compatibility problem with the Ivory plugin? I > use Ivory in almost > > everything I do, so it's a fairly constant - and irritating - issue. > > > > Thanks in advance for any help or advice. > > > > Other pertinent facts: Dual 2.3 G5, Motu 828 Mk II (but also > happens at home with an > > Apogee Duet, so it's more likely a software issue), Logic 8. > > > > Fred Story > > > > > > Fred, > > I haven't experienced that problem, but I don't have that plug-in > either. Is it a CPU intensive plugin? If it is or even if it isn't I > would try freezing that track so that the plugin isn't running > realtime with the bounce. Often with CPU intensive plugins there is a > issue with bouncing and latency and the time it takes for the audio > to process through the plugin. You also may want to bounce in > realtime ( I don't know if you are bouncing offline). That too may > give the plugin extra time to process the audio. I think the freezing > of the track however may be the best and most obvious fix. > > If all that doesn't work, an increase in the buffer size would > probably give the CPU more time as well, but that is really the last > resort since with a Dual 2.3 G5 and an Apogee you shouldn't have any > latency issues. > > Ivan > I've noticed the same issue with my G5 Dual 1.8Ghz x 8 gig ram. this seems to happen when I have lots of plugs opened or I am working with quite a few e.g. Sampletank/Philharmonic/Virtual Guitar etc. What I have found is the longer time that I'm working the more likelyhood of a crash at bounce. So I nearly always close Logic and re-boot. Don't know how I'll go with LogicStudio 8, as I just loaded it yesterday and have had that much of a run. Regards, Chug.