> Subject: LAWP 4.04 Timing unreliable? > > I SMPTE sync'd LAWP to my BRC (30N - BRC master; Logic slave) and > transferred reference Midi'd drum tracks to ADAT, ...half way through the >song, the > guitar tracks drifted out of sync with the drum track (about 1/2 second > behind the drum tracks)!! I thought Logic was supposed to be rock solid > with SMPTE sync.... What is going on here? Am I losing > my mind or does Logic's 4.04 Windows audio engine and/or midi-audio sync > have serious problems? I Had same thing last weekend...on a Mac 7600 w/Newertech G3 250 card. Midi drifted out of sync (the audio tracks gradually lagged behind the Midi 'ti by the 2 min 30 sec point they were a 32nd apart at least. Restarting the sequence from the 2 min 30 sec point brought everything into sync but drift began again soon. Resolution: copied everything into a new song. > I am getting very tired of one problem after another with Logic (win > version). It seems I have 2 hours of problem solving for every hour of > music... Thirty six hours of productivity lost this and last weekend. And I'm a Mac music consultant to quite a few of the studios in my hometown (Vancouver BC). God help my clients, some of them were calling with their own problems and all I could say was "I'll have to get back to you but right now MY Logic system is crashing!". Stability could (and must) get better. > Message: 25 > Date: Fri, 12 Nov 1999 16:40:44 +1100 > From: pnajar <pnajar@...> > Subject: Damaged Song Error since 4.0.5 LAMP > > A few times in the last 10 days (since 4.0.5) I have booted up an > existing song in LAMP and got a "damaged song" error. Never with my > autoload, only with a song that has audio in it. After I click "exit" the > song loads and plays fine, but if I try to edit a region boundary or > something else to do with audio the whole computer crashes. 4.0.4 was > totally stable. Got this one too on the same song after upgrading from 4.0.4 to 4.0.5 - "Damaged song (ginst)" (remember: same program, different platform). Only solution: the above, copy all tracks into a fresh song. Also "too many files open (error code -42)" and another "error code -47". There were quite a few vocal edits with about 160 vocal segments tracked as separate phrases, and many small guitar regions. It stopped the session dead in its tracks and I sent the vocalists home. That's what took took THIS weekend to fix. What a disaster. Reformatted drives, installed a clean fresh OS, started logic and only re-imported keycommands from old prefs file. Same problems, "CPU too slow", "too many files open (error code -42)" and "error code -47". Downgrading to 4.0 fixed the CPU stuff and the song repair by transferring into a new song saved my client's song (or at least the work since the last backup. I'm thinking of leaving host-based HD recording altogether, I have to think of my mental health. Emagic, some input on this one? Want the song file to look at? Paul, did you save yours?