Hi Folks....I do most of my work on a dual g5, but I now have logic also installed on a new MacBook Pro, dual core intel, 3GB ram. Here's my problem. When working with quick time video, if I open the temp list window to change the smpte offset, I can't. Double clicking the smpte position TC doesn't make the text modifieable like is does on my G5...it just resets it to zero...if I try to add a tempo change, and then modify the new smpte position for that tempo change, it sets the previous tempo value to a nonsense BPM in the thousands....anyhow...all weird weird behaviour. I found the only way to change my SMPTE start time was to come at it from the synchroniztion preferences in the song settings... It's logic 7.2.3 on both my G5 and Macbook Pro....system 10.4.8 Anyone out there encountered this crazy behaviour, or have any idea what's causing it? best regards tom <><><><><><><><><>< ><><><><><><><> Tom Third Composer-Audio Post Production

--- In logic-users@yahoogroups.com, Tom Third <zeromodule@...> wrote: > > Hi Folks....I do most of my work on a dual g5, but I now have logic > also installed on a new MacBook Pro, dual core intel, 3GB ram. Here's > my problem. When working with quick time video, if I open the temp > list window to change the smpte offset, I can't. Double clicking the > smpte position TC doesn't make the text modifieable like is does on > my G5...it just resets it to zero...if I try to add a tempo change, > and then modify the new smpte position for that tempo change, it sets > the previous tempo value to a nonsense BPM in the > thousands....anyhow...all weird weird behaviour. I found the only way > to change my SMPTE start time was to come at it from the > synchroniztion preferences in the song settings... > > It's logic 7.2.3 on both my G5 and Macbook Pro....system 10.4.8 > > Anyone out there encountered this crazy behaviour, or have any idea > what's causing it? Hi Tom You're not alone! I have encountered the same problem and the only way round it has been by exporting the file to my G5 PowerPC and adjusting the tempos/timecodes there, then re-opening it on my MacBook Pro. This is one of many programming bugs to do with entering text/numbers in text/ numerical fields since Apple rewrote (made a hash of) the software. This new problem seems to be Intel specific. There's another one too; put your Global Audio Pan-Law to -3dB compensated and then raise a fader above +3.1dB - the signal disappears totally!! Best regards Toby Wood.