I'm pretty good with Logic now, but nowhere in the manual or in the wonderful MacPro tutorials does it explain WHY you would choose either "overlap"or "no overlap" when moving regions. Can someone help me with the logic behind this part of Logic!! Why would I choose one drag mode over the other? Thanks - alex

i record in 24 bit wav files. one of the turorials mentions that logic uses 32 bit floating point. questions: 1. when i bounce to make a CDDA, i always dither to 16 bit. am i right that if i did not dither to 16 bit, then it would burn a 24 bit CDDA (or, does it automatically dither to 16 bits when making a CDDA) 2. when i bounce to an mp3 file, do i need to dither to 16 bits, or does it automatically convert the 24 bit files to mp3 (which, for all i know is 16 bit). 3. i, of course, always bounce them as 24 bit files (not dithering) when i take them to be mastered. 3. when i bounce a number of songs (projects) which i want to then import into waveburner so that i can put a number of mixes on one cd to listen to to review, i typiclly bounce each song dithering it to 16 bits. then, when i import them into waveburner, they are already 16 bit wavs. then, i simply burn them to a cd (from waveburner), by simply clicking the burn icon in waveburner (not telling it that i want a CDDA, for instance). the cd always seems to play fine on all cd players (though i never told waveburner to make a CDDA, though it was burning files that were already dithered to 16 bit files,though they were still wav files). my question is, when i bounce the files from logic in order to be able to import them into waveburner, do i even need to dither them down to 16 bits, or can i just bounce in 24 bits, then import the 24 bit bounces into waveburner. when i burn them in waveburner, does it automatically convert it to 16 bits (or would it, in that case, burn a 24 bit cd out of waveburner). in other words, waveburner seems to burn a CDDA without me telling to do anything but burn -- is it thus doing all the files "bit" (24 to 16) and "type" (i.e., wav files to CDDA's) conversions on its own, or does it need to start with a 16 bit file? sorry for the long question!!!! peace - alex

Thank you so much. You cleared up my main question which was about burning from Waveburner. Now I see that I can simply import my 24 bit bounce as a wav file into Waveburner and when I ultimately burn a CD from Waveburner it automatically dithers to 16 bit and makes a CDDA file (i.e., it automatically does the whole process for making a CDDA without me having to do anything additionally to the files). I cannot tell you how much MacProVideo has helped me. The videos are fantastic, and I have recommended you to other Logic users. Peace - alex

I asked this aquestion of another Logic user, and they weren't sure either. And it is really not addressed in any of your tutorials (that I've found). You might want to add this to one. Maybe in Tips and Ticks. Two related questions: 1. What is the logic for when to use "overlap" and when to use "no-overlap?" Does some of it depend on whether you might need to further edit (changing region length) in the area you just put the new region? Or, if not, what is the logic for when to use which one? 2. Once you have finished the edit, if you used overlap, do you want to then "remove overlaps" or just leave it as it is? And why would you remove overlpas if that's what you need to do. Again, thanks so much for all your tutorials. They are THE BEST. I could never have learned this program as well without y'all. I've recommended yout o many other users. peace - alex

Am I correct in that when I make different screensets and lock them - that is, when I set track height for a new screenset, the track heights in other screensets I have made - AND LOCKED- change proportiantely to the new screenset I'm making as I set the height for the tracks in that set (the one I am now setting up)? If I'm right, is there an easy way to set different track heights in different screensets and lock them so that different screensets can have tracks of different heights? Am I just missing something obvious, or is it really not doable? Thanks as always - y'all are great. peace - alex

I often fatten tracks (copy to a new track to fatten the sound). I group those tracks and set the group settings for editing regions and sharing automation. For certain parameters like volume or pan, when I automate volume or pan on one track, the same automation changes are made to the other tracks in the same group (which is what I want to happen). However, I noticed that if I have EQ inserted on the tracks, and then automate changes to the EQ settings, the changes only affect the track I am working on and not the other tracks which are part of the same group. Am I correct in this-- that certain automation parameters (like volume and pan) will be shared for tracks in the same group, but some other parameters (like DSP's, I gather) are not shared (that is, changes to these automation parameters in one track are not reflected in the other shared tracks). Now, if I am correct, how can I copy the automation parameters for a specific parameter (EQ, for instance) from one track to another so that I don't have to manually mimic the automation changes. Copy automation from one track to another does not appear to be a choice under Options/ Track Automation. Thanks - alex

I have OS X 10.5.6 and Logic 8.02. I've used it on this computer for a year and a half with no problem. Suddenly, in a project I have been working on (with no previous problems), when I go to record, arm the tracks and then hit record, I immediately get the dreaded wheel and it won't stop - Logic freezes. And it's now doing this in other projects, so it's not just this project. I ahve to force quit it. I also notice that Finder is then frozen (after I force quit Logic). Any ideas or thoughts how to fix it? or shpould I just re-install Logic (the whole Studio, I gather would be best to re-install)? If I have to reinstall it (and hopefully that will fix it), is there any way to save my templates first ? and any way to save the most recent projects accessed (so when I go to the File / Open Recent they will be there). ALSO, AND REAL IMPORTANT, HOW CAN I SAVE MY CHANNEL SETTINGS I MADE AND NAMED AND SOME OF THE PUG IN SETTINGS I'VE TWEAKED?

Well, I am impetuous! I jsut received my update discs to go from Lic 8 to Logic 9. I have viewed thesections of the new Logic 9 Core 101 ttorial you have on your site (and have also pre-purchased the Flex Time Editing video to be released toward the end of Aug). My better judgement says I should wait for your new tutorials to be completed (and I have viewed them) before I update to Logic 9 (I am a home user, not a professional studio -- but still quite adept with the program - thanks to y'all) Any thoughts -- should I wait? Also, I assume that you will notify those of us who have already purchased the flex time video when we can download it, and how those of us who already own the Logic 8 101 tutorial can dowload the new Logic 9 101 tutorial which I believe will be free to those of us who have the Logic 8 101) peace - alex

Me too --- can't wait to get started on Logic 9

I have, of course, made a backup of my plugin and channel strip settings that I tweaked for some of my projects. I want to make sure that when I install the Update to Logic 9 (from Logic 8) that it will not create a new blank folder(s) in my Logic folder in my Library/Application Support (where my pst's and cst's are stored) and thus I lose them (and would have to restore and then put back in my projects). Also, my key commands are stored there too. I guess, does it make a new Application support folder for Logic which overwrites the folder from Logic 8? I can't imagine that the update would overwrite the existing folder, but better safe than sorry. peace - alex