> > And please fix the feature where you could toggle between the arrow anda > > selected tool. > > Hold option key while selecting tool from toolbox. Now everytime you > hold  down option > key that tool will appear. > Thanks! I forgot that the tool selection had to be "set" rather than just a key to toggle. I guess this is yet another annoyance. It should remember what tool you just used without telling it "rememeber what I am about to use". By the way, the Wild Transpose Bug is not necessarily a bug, but rather some crazy feature. Its written about in the manual, but its still not clear to me how its supposed to work. It seems that it takes the chord analysis track - which should just display what is there harmonically - and uses that for to drive transposes in some way that makes no musical sense.

--- In logic-users@yahoogroups.com, GAmoore@a... wrote: > > > > And please fix the feature where you could toggle between the arrow and a > > > selected tool. > > > > Hold option key while selecting tool from toolbox. Now everytime you > > hold down option key that tool will appear. > > > > Thanks! I forgot that the tool selection had to be "set" rather than just a > key to toggle. I guess this is yet another annoyance. It should remember what > tool you just used without telling it "rememeber what I am about to use". I find it quite useful that you can set your favourite tool to be chosen by the option key (or R.H. click as it was/is in Windows). Obviously you can't expect Logic to be telepathic and everyone has their own preference, so I can't quite see why this should be an annoyance. Hey, I get annoyed every time I use Photoshop, I expect to hit escape and get back to the pointer. Pete Thomas www.petethomas.co.uk - Free Logic Icons, Environments and EXS Instruments

I frequently end up with a region that is overlapped by another region and I want to bring the region that's underneath to the front (or top depending on your point of view). This is the equivalent of a drawing program's "Move to Top" feature. Is there a way to do that with Logic so I don't have to actually move the top most region to a different track to work with the one that's underneath it? Kamm

--- In logic-users@yahoogroups.com, "Kamm Schreiner" <kamm@s...> wrote: > > I frequently end up with a region that is overlapped by another region and I > want to bring the region that's underneath to the front (or top depending on > your point of view). This is the equivalent of a drawing program's "Move to > Top" feature. Is there a way to do that with Logic so I don't have to > actually move the top most region to a different track to work with the one > that's underneath it? I would avoid overlapping regions if possible. Why would you want them to overlap? To me it only confuses things. Logic doesn't give any preference to the one "on top". If they are on the same track only one audio region can play at once, even if it is "on top" the second one will play as soon the SPL gets to it. If you are talking about MIDI regions they will both play, even more confusing! Pete Thomas www.petethomas.co.uk - Free Logic Icons, Environments and EXS Instruments

--- In logic-users@yahoogroups.com, "Kamm Schreiner" <kamm@s...> wrote: > > I frequently end up with a region that is overlapped by another region and I > want to bring the region that's underneath to the front (or top depending on > your point of view). This is the equivalent of a drawing program's "Move to > Top" feature. Is there a way to do that with Logic so I don't have to > actually move the top most region to a different track to work with the one > that's underneath it? > > Kamm If there's a piece of the 'underneath' region showing, just click on it and it will come forward. If it's completely obscured by the top region, you can sometimes get it just by clicking where it is (which of course,you can't see) but usually you have to move the top one off to another track if this is the case. I just add another copy of the same track to move it off to so I don't get too confused. Sonny Keyes SKa Music Toronto www.skamusic.ca

Hi Sonny, You wrote: << If there's a piece of the 'underneath' region showing, just click on it and it will come forward. >> Nope. That does not happen. (I'm using Logic Express v7). It gets selected, but does *not* come forward. Yes. I currently move the top one to another track, but find that very annoying. I was hoping for a Move to Top function. Kamm

Hi Pete, You said/asked: << I would avoid overlapping regions if possible. Why would you want them to overlap? To me it only confuses things. >> (These are all MIDI regions) Well, when I'm recording the chorus after already recording the verse, I use punch-in recording to record the chorus. I need to overlap the end of the verse because I tend to come in just a hair ahead of the actual start of the measure. So I end up with on measure worth of overlap. I have to do the same thing for at the other end for similar reasons. Now I've got overlap at both ends. I can clean up the beginning overlap easy, but not tail end. Anyway, the overlap is unavoidable. At least for the way I record music. Hope that explains the "why"... Kamm

--- In logic-users@yahoogroups.com, "Kamm Schreiner" <kamm@s...> wrote: > > Hi Pete, > > You said/asked: > << > I would avoid overlapping regions if possible. Why would you want them > to overlap? To me it only confuses things. > >> > > (These are all MIDI regions) > Well, when I'm recording the chorus after already recording the verse, I use > punch-in recording to record the chorus. I need to overlap the end of the > verse because I tend to come in just a hair ahead of the actual start of the > measure. So I end up with on measure worth of overlap. I have to do the same > thing for at the other end for similar reasons. Now I've got overlap at both > ends. I can clean up the beginning overlap easy, but not tail end. > > Anyway, the overlap is unavoidable. At least for the way I record music. > > Hope that explains the "why"... Ah, so you have a tiny overlap. Does it matter which is on top? If they are MIDI regions they will both play. It would only matter which was on top if one was obscuring the other, and you could sort that by "create new track for overlapped regions" from the track menu. I would either merge the regions or else create a new track (same instrument) Best Regards Pete Thomas www.petethomas.co.uk

--- In logic-users@yahoogroups.com, "Pete Thomas" <pt@p...> wrote: > Ah, so you have a tiny overlap. Does it matter which is on top? If > they are MIDI regions they will both play. It would only matter which This is actually yet another wondrous 'L7 Bug'. It was discussed a few weeks back when I first ran into it. Unlike earlier versions of Logic, no amount of clicking on a hidden region will bring it to the 'top'. It's extremely annoying and serves no useful purpose. I have lots of old songs where an imprecise edit left two overlapping regions, say between two different takes in a 'comp' track. In this case, you can't just use "tie regions by length/ position'. You want to examine each track in close-up and fine tune the edit point where one ends and the other starts. In Logic7, this is no longer possible without shifting one of your overlapping regions to another track! Just what I need, another 'workaround'. Hey, maybe they should change the name of the program from Logic 'Pro' to Logic Workaround? You know, I used to be bugged just because L7 had so many old bugs still crawling around and biting me now and then. Now I'm more annoyed at the NEW bugs that have been thrown in as a bonus. I'm getting real tired of waiting for the 'inevitable' fix. Has anyone out there actually paid the outrageous 'support' price and gotten any idea if Apple has any timetable for FIXING this rapidly multiplying swarm of binary pests?

Hi Pete, << >>Ah, so you have a tiny overlap. Does it matter which is on top? If >>they are MIDI regions they will both play. >> >>You are certainly right that it, strictly speaking, doesn't matter. However, >>I'm kind of a neat freak in this respect and it just bothers me to have them >>overlapping. Yes, it's a sickness, I know. <grin> << >>I would either merge the regions or else create a new track (same >>instrument) >> Although I'd prefer to just use the same track, that's a workable alternative. Thanks, Kamm

Hi Timsonian, You wrote: << >>This is actually yet another wondrous 'L7 Bug'. It was discussed a few >>weeks back when I >>first ran into it. Unlike earlier versions of Logic, no amount of clicking >>on a hidden region >>will bring it to the 'top'. It's extremely annoying and serves no useful >>purpose. >> Well, that's encouraging actually. If it used to work, they may bring that functionality back. It certainly seems to me that bringing the clip to the front is what *should* happen. That is actually what I expected. You also wrote: << >>You know, I used to be bugged just because L7 had so many old bugs still >>crawling around >>and biting me now and then. Now I'm more annoyed at the NEW bugs that have >>been >>thrown in as a bonus. I'm getting real tired of waiting for the >>'inevitable' fix. Has anyone >>out there actually paid the outrageous 'support' price and gotten any idea >>if Apple has any >>timetable for FIXING this rapidly multiplying swarm of binary pests? >> As a Sonar user I can definitely say that Sonar has far fewer bugs than Logic. However, I still find myself drawn to Logic. I can't quite place my finger on why yet, but I do enjoy Logic. Both programs are extremely powerful. And I don't use the word "extremely" lightly. This list has been very helpful in getting me past the few stumbling blocks I've encountered so far. Thanks to all of you! Kamm

> I guess this is yet another annoyance. It should remember what > tool you just used without telling it "rememeber what I am about to > use". This is actually a very powerful feature, esp. considering that you can set your "option tool" independently for every editor window in Logic. BTW the "arrow with the squiggly line" is the automation tool. How are you curving your automation without it? Brian :::::::::::::::::::::::::::::::::::: Logic Audio Pro 7.0.0 PowerMac G4 933MHz OS X 10.3.6 1 GB RAM MOTU 828mkII - driver v1.09 - CueMix v1.4

> > > > And please fix the feature where you could toggle between the arrow and a > > > > selected tool. > > > > > > Hold option key while selecting tool from toolbox. Now everytime you > > > hold down option key that tool will appear. > > > > > > > Thanks! I forgot that the tool selection had to be "set" rather than just a > > key to toggle. I guess this is yet another annoyance. It should remember what > > tool you just used without telling it "rememeber what I am about to use". > > I find it quite useful that you can set your favourite tool to be > chosen by the option key. Hi, Sorry but this bothers me. Now we have at least half a dozen LUGgers in this thread talking about setting the second tool with the option key. Does everybody agree with that? Then I must have a different version of Logic Pro 7 than others. Option key does nothing here...instead when pressing the command key I can select a second tool from the palette, the tool which can be later called up again when holding down that very same command key. Strange. regards, Tommi

--- In logic-users@yahoogroups.com, "tomppa38" <tommi.saarela@m...> wrote: > > > > > > > And please fix the feature where you could toggle between the > arrow and a > > > > > selected tool. > > > > > > > > Hold option key while selecting tool from toolbox. Now > everytime you > > > > hold down option key that tool will appear. > > > > > > > > > > Thanks! I forgot that the tool selection had to be "set" rather > than just a > > > key to toggle. I guess this is yet another annoyance. It should > remember what > > > tool you just used without telling it "rememeber what I am about > to use". > > > > I find it quite useful that you can set your favourite tool to be > > chosen by the option key. > > Hi, > Sorry but this bothers me. Now we have at least half a dozen LUGgers > in this thread > talking about setting the second tool with the option key. Does > everybody agree with that? > Then I must have a different version of Logic Pro 7 than others. > Option key does nothing here...instead when pressing the command key > I can select a > second tool from the palette, the tool which can be later called up > again when holding > down that very same command key. You right, it is Command key. The one with the apple on it. To the right of the Option key. Pete Thomas www.petethomas.co.uk - Free Logic Icons, Environments and EXS Instruments

> Hi, > Sorry but this bothers me. Now we have at least half a dozen LUGgers in this > thread talking about setting the second tool with the option key. Does > everybody agree with that? Then I must have a different version of Logic Pro 7 > than others. Option key does nothing here...instead when pressing the command > key I can select a second tool from the palette, the tool which can be later > called up again when holding down that very same command key. Strange. > > regards, > > Tommi You are correct, it is not the Option key, it is the Command key. Also, holding down the Control key brings up the magnifying tool, so now you have three possibilities without going to the palate. James

"Pete Thomas" <pt@p...> wrote: > > You right, it is Command key. The one with the apple on it. To the > right of the Option key. > > Pete Thomas > www.petethomas.co.uk > - Free Logic Icons, Environments and EXS Instruments Oooops. That was my post on the option key. Must upgrade/replace RAM in brain as memory is obviously failing. Sorry about the confusion and thanks for clarification that command is the correct key. Doug

>>>Unlike earlier versions of Logic, no amount of clicking >>>on a hidden region >>>will bring it to the 'top'. It's extremely annoying and serves no useful >>>purpose. >>> >>> >>> >Well, that's encouraging actually. If it used to work, they may bring that >functionality back. It certainly seems to me that bringing the clip to the >front is what *should* happen. That is actually what I expected. > > The behavior has changed, and whether you agree with it or not, it is not a bug. The regions' visibility is exactly equivalent to their audibility. The audibility is determined by whichever region started latest. The previous "topping" behavior did not change the sound, so in a very apple-like way, Logic now puts the audible region on top. Overlap two regions and drag one around and you will see. If they would simply add translucency to overlapping regions, it would work perfectly IMO. -smeet

--- In logic-users@yahoogroups.com, Sumit Das <smeet@i...> wrote: > > > >>>Unlike earlier versions of Logic, no amount of clicking > >>>on a hidden region > >>>will bring it to the 'top'. It's extremely annoying and serves no useful > >>>purpose. > >>> > >>> > >>> > >Well, that's encouraging actually. If it used to work, they may bring that > >functionality back. It certainly seems to me that bringing the clip to the > >front is what *should* happen. That is actually what I expected. > > > > > The behavior has changed, and whether you agree with it or not, it is > not a bug. The regions' visibility is exactly equivalent to their > audibility. The audibility is determined by whichever region started > latest. The previous "topping" behavior did not change the sound, so in > a very apple-like way, Logic now puts the audible region on top. Overlap > two regions and drag one around and you will see. If they would simply > add translucency to overlapping regions, it would work perfectly IMO. Well, in my opinion, if this is not a bug then it is definitely a step backward. Although it does reflect the sound that is heard it becomes very difficult to alter the sound that is heard because I might need to grab the end of the region which is on the bottom to shorten it, but currently this is not an option without first moving the top region. It used to be a bit easier. It's not a big deal just unnecessary addtional steps. -Xavier

> The behavior has changed, and whether you agree with it or not, it is > not a bug. The regions' visibility is exactly equivalent to their > audibility. The audibility is determined by whichever region started > latest. Hmmm. What about 2 midi regions? The first, even though it can be overlapped by a second, continues to play underneath it. Jon

> What about 2 midi regions? The first, even though it can be overlapped > by a second, continues to play underneath it. Right! And there simply needs to be a better way to access overlapping regions than moving one region to a different track. That is certainly not what I'd call elegant. Kamm

--- Kamm Schreiner <kamm@...> wrote: > > > > What about 2 midi regions? The first, even though > it can be overlapped > > by a second, continues to play underneath it. > > Right! And there simply needs to be a better way to > access overlapping > regions than moving one region to a different track. > That is certainly not > what I'd call elegant. > Amen! This drives me crazy. There must be a better way. JP

> Well, in my opinion, if this is not a bug then it is definitely a > step backward. Although it does reflect the sound that is heard it > becomes very difficult to alter the sound that is heard because I > might need to grab the end of the region which is on the bottom to > shorten it, but currently this is not an option without first moving > the top region. It used to be a bit easier. > > It's not a big deal just unnecessary addtional steps. > > -Xavier I am about to move from logic pro7.1 to 7.2.1, and i had been told that this overlapping regions issue had been fixed in this upgrade. is this not the case? simon