jonathankek2000 <jonathankek2000@...> wrote: >> This may seem a drastic course of action... but in my experience , >> it's almost always the quickest, and therefore cheapest way of >> resolving such issues. Logic 6.3.3 should run perfectly on OS 10.3.2. >> Running your Disk Utility or using Cocktail can tell you if your Hard >> Dr>ive is damaged, and it can also rebuild your Disk Permissions. Disk >> Warrior or Tech Tool Pro may give you the damaged file structure >> answers you need. Then, running the Apple Hardware Test CD will give >> you the other answers concerning RAM, Logic Board, and Video Card >> problems you may be having. >> I'd run those tests before I completely wiped my Hard Drive and tried >> reinstalling from ground zero. Scott replied: > already tried this on all systems.. all is fine FWIW, while I'd trust the Test CD if it said something was bad, I *wouldn't* necessarily count on it if it indicates no problems... We lost months trying to find crashing problems that turned out to be caused by bad RAM *in spite* of the Apple Hardware Test CD indicating that all was well and fine. This was one of the first things Apple Support had us run, and even on the most thorough tests, the RAM kept getting flying colors, so we moved on to other potential issues. Finally, we starting pulling and swapping RAM cards, and sure enough, the problem went away once the bad one was out of the system, and the problem has so far never returned (well over a year now running smooth). We are just getting ready to put 10.3 up, so can't speak to that yet! Of course, YMMV, and I wouldn't suggest this will be the same for all, but since this happened to us, I've heard from others that they've had similar experiences... Regards to all, Glenn @ Schadowrider

> FWIW, while I'd trust the Test CD if it said something was bad, I >*wouldn't* necessarily count on it if it indicates no problems... We >lost months trying to find crashing problems that turned out to be >caused by bad RAM *in spite* of the Apple Hardware Test CD indicating >that all was well and fine. This was one of the first things Apple >Support had us run, and even on the most thorough tests, the RAM >kept getting flying colors, so we moved on to other potential >issues. > Of course, YMMV, and I wouldn't suggest this will be the same for >all, but since this happened to us, I've heard from others that >they've had similar experiences... > Regards to all, > Glenn @ Schadowrider I agree as to the idea that all tests are not necessarily conclusive. In my case, however, Apple Hardware Test CD DID see the BAD RAM. I had 2 sticks of it.(From Crucial) When I switched the RAM to different slots, the test still found the bad RAM. For these tests I was using the "Short Test". The "Extended" Apple system test would have taken forever, even with 4 Gigs of RAM on board. If you've got the time, it COULD help, it's pretty extensive. G5s and OS X seem to be notoriously fussy with RAM. And bad RAM can cause all kinds of strange problems to your system. If you're having strange problems and kernal panics. Check you Crash Logs, and see if you can determine if RAM could be the culprit. Cheers

I recently installed Stylus on a G5 dual OS 10.2 running LAP 6.3.3. Immediately after installing, Logic began crashing whenever I tried to open autoload or any file that was created using it. Spectrasonics syas that autoload is corrupt (how'd that happen?) and that I must trash it. My question is: Is there a wasy to keep my environment? I'd hate to have to redo all of those patch lists etc. My second question is: Is there a way to save my midi tracks and reload them into new songs? Thanks, JP

Has anyone seen this: I enter some text in the score window. If I select it and go to <Text> menu / <Size> and try to increase the size, it changes fonts, not size! This used to work in OS9 but seems broken now in OSX (LAMP 6.3.3) Regards - Colin

On 2/28/04 5:38 PM, "james page" <jimmymio@...> wrote: > I recently installed Stylus on a G5 dual OS 10.2 > running LAP 6.3.3. Immediately after installing, Logic > began crashing whenever I tried to open autoload or > any file that was created using it. > Spectrasonics syas that autoload is corrupt (how'd > that happen?) and that I must trash it. > My question is: Is there a wasy to keep my > environment? I'd hate to have to redo all of those > patch lists etc. James, Find an older "pre Stylus installation song" that you previously worked on using your autoload and delete all the tracks and other stuff that you don't want...until it looks like your original autoload...then save song as "autoload". > My second question is: Is there a way > to save my midi tracks and reload them into new songs? You can copy midi tracks from older songs by simply dragging the tracks from song to song. ...open instance of song with track to be copied...open song to be copied to... Select and drag (or use copy/paste commands) track or part of it into new song to predetermined track and position. Once it's there you can manipulate it like any other. Pay attention to things like tempo changes and non-destructive changes. Normalize the tracks before copying for instance. Make sure the track parameters are the same as original or whatever you want the copied track to now be. Hope this helps. Craig

--- Craig Beaumont <cbeaumont1@...> wrote: > Find an older "pre Stylus installation song" that > you previously worked on > using your autoload and delete all the tracks and > other stuff that you don't > want...until it looks like your original > autoload...then save song as > "autoload". Thanks Craig but I'nm a little confused. I thought that all songs that were started from the corrupt autoload would also be corrupt. In fact, I believe I tried exactly what you suggested and Logic still crashed as soon as I opened any of these songs. I will definitely try your method for midi transfers once I can get a clean autoload. Thanks, JP

On 3/1/04 1:08 AM, "james page" <jimmymio@...> wrote: > --- Craig Beaumont <cbeaumont1@...> wrote: > >> Find an older "pre Stylus installation song" that >> you previously worked on >> using your autoload and delete all the tracks and >> other stuff that you don't >> want...until it looks like your original >> autoload...then save song as >> "autoload". > > Thanks Craig but I'nm a little confused. I thought > that all songs that were started from the corrupt > autoload would also be corrupt. > That would be correct. But I'm assuming that there must have been a time (pre Stylus installation) when your autoload was NOT yet corrupted, and that would be when you did an earlier song project. So if you have an earlier project, open up the song and go from there. Craig

On a fine day, 01-03-2004, Craig Beaumont wrote: >On 3/1/04 1:08 AM, "james page" <jimmymio@...> wrote: > >> --- Craig Beaumont <cbeaumont1@...> wrote: >> >>> Find an older "pre Stylus installation song" that >>> you previously worked on >>> using your autoload and delete all the tracks and >>> other stuff that you don't >>> want...until it looks like your original >>> autoload...then save song as >>> "autoload". >> >> Thanks Craig but I'nm a little confused. I thought >> that all songs that were started from the corrupt >> autoload would also be corrupt. >> >That would be correct. But I'm assuming that there must have been a time >(pre Stylus installation) when your autoload was NOT yet corrupted, and that >would be when you did an earlier song project. So if you have an earlier >project, open up the song and go from there. Maybe worth noting that in the past several users have experienced problems when their Autoload got too old. I.e. if your Autoload is still from e.g. the 4.x era and you're now at 6.3, some sort of incompatibility might creep in. It thus seems to be a good idea to recreate your Autoload from scratch after a big Logic revision. Tedious, I know, but I (and others) have done this quite a few times, and personally I've never suffered from the kind of weird problems this thread is about (and which seem to pop up every couple of days in this group). Just press Option and then pick 'New' from the File menu. Logic now creates a new song that's not based on your Autoload, with all possible Audio Objects in the mixer. Now just copy/paste environment stuff from your old Autoload in the new song, and save as new Autoload. -- Hendrik Jan Veenstra h @ k n o w a r e . n l Omega Art: http://www.omega-art.com/

--- Craig Beaumont <cbeaumont1@...> wrote: > That would be correct. But I'm assuming that there > must have been a time > (pre Stylus installation) when your autoload was NOT > yet corrupted, and that > would be when you did an earlier song project. So if > you have an earlier > project, open up the song and go from there. Thanks Craig, actually all of my songs and my autoload are pre-Stylus and everything worked fine till I loaded Stylus. I never knew that they were corrupted till Spectrasonics suggested that was the source of my problem. JP

--- Hendrik Jan Veenstra <h@...> wrote: > Just press Option and then pick 'New' from the File menu. > Logic now creates a new song that's not based on your > Autoload, with all possible Audio Objects in the mixer. > Now just copy/paste environment stuff from your old > Autoload in the new song, and save as new Autoload. The curious thing is that I've only been using Logic since ver.6 and my autoload is 2 months old. However it seems i may have to use your "tedious" remedy anyway. Thanks, JP