moonboy

I'm having similar issues, and there are no group tracks empty of regions. Using the flex tool in the top half of the region SHOULD stretch everything between that and the next marker on either side (useful for just nudging the timing of a long section) but when using flex on grouped (quantised locked) tracks, it stretches everything to the left, but treats the next transient marker to the right (dashed line) like a manual flex marker.

Didn't know about that - thanks!

Not necessarily, any keyboard or midi controller is just sending messages to the software. Mine is an Arturia Keylab 61 Essential, which is inexpensive, but purpose made for controlling software so I wouldn't have expected this issue. It's less than a year old so if it happens again I'm replacing it.

I've had similar issues - erroneous pitch bend data causing software instruments to go out of tune with each other. Even seen it happen whilst recording and my keys shifted by a semitone! I found the problem for me was in the Arturia Keylab controller piano, not in Logic, as it only ever happened when that keyboard was connected. I performed a factory reset on the keyboard and it fixed all the pitch problems. Re calibrating the pitchbend wheel is another suggestion, if resetting your midi controller doesn't fix it.

I have had this exact issue many times. When phase locked editing, Logic treats untouched (dashed) transient markers as flex markers (always auto-anchoring and stretching from the next transient marker to the right, but to the left it seems to make a choice). The auto anchored markers to left and right don't become white, they stay grey dashed, but they are anchored. As grubmanus says, often if a section of audio is a bit rushed, using the upper half flex tool to stretch the whole section with one edit is often the perfect (and fastest) solution, but impossible with this behaviour. Your workaround worked for me, thanks David. It's a real shame that you can't use the upper half (single marker) flex tool with phase locked editing. Will just have to keep zooming in/out to keep checking all the appropriate regions are still selected when flexing multiple tracks with that tool and group editing disabled, as mistakes are easy like that!

I've just encountered this as well and noticed something else happening - enabling flex pitch moves the timing of the whole region by a few bars but also copies the entire region over the top of itself when this happens - sometimes the shifted timing is in the region underneath so what you see doesn't correspond to what you hear until you delete the copy on top. Quite strange! My workaround so far is bounce in place the sections I want to flex pitch, flex them, then bounce in place again and move them back to the original track and turn flex off.

I also had similar to this recently - but it was only on newly created tracks. Create a new audio track and it would come with a flashing mute button and no sound, but the rest of the project was fine. No soloed tracks or channel strips in the arrange/mixer/environment (for only one mute button to be flashing then all other unmuted tracks would have to be soloed, right?) Not sure what caused it, but the solution was to "Reset Channel Strip" under 'setting' at the top of the mixer.

Thanks David, yes that fixed it! I didn't think to try that as I haven't changed the tempo! I had no idea that the key signature would affect audio through a function related to tempo - I haven't seen a mention of this before - only that changing the key sig affects apple loops and midi display. So 'follow tempo' basically treats the audio region as a kind of apple loop then? Also I've read that 'follow tempo' only appears in the inspector for regions recorded in that current project, however in my current project 'follow tempo' appears in all the vocal tracks which were imported from my collaborator's Garageband project, and most of the audio regions I've recorded straight into the logic project don't have 'follow tempo' in the inspector (but do have 'flex'). I'm a bit confused about when this feature is supposed to show up now!

Hi, here it is. No change I can see in the inspector when it transposes. After the key is changed the audio plays back fine on first play, but if you hit play a second time from the start of the region, it's transposed. I'll do a screen recording to demonstrate...

Yes I thought it might be corruption, but not encountered it before. A fresh project sounds like a good idea, thanks for the reply. Interestingly - the vocal pitch shift is pretty successful, much less glitchy than flextime and much less laborious than the time and pitch machine... whatever the corruption is has created quite a powerful tool, if it were to be controllable!

A strange thing... When I change the key signature in the list editors, it warps the audio pitch of the lead vocal. Eg. changing key from C maj to A maj (so I can use the score display for a midi keyboard part) pitches down the vocal audio by 3 semitones. But NOT any other audio in the project! The vocal track has not got flex enabled. It appears to affect the vocal whether or not the channel is selected when I change signature. I'm pretty sure that changing key signature is only supposed to affect display of midi notes only? I set up a new blank project to try and replicate the effect but I can't - so far it's only happening in one project I'm working on - any ideas what's causing it?

Ah ok then... Thanks David

Hi, any reason why I don't see an 'Arrange' tab in Preferences > Display? I looked this up and apparently in Preferences > Display > Tracks tab there should be a section called 'Appearance' where you can customise the colour/background/grid lines, but in mine this section is not there, all I have in the Tracks tab is one checkbox for Shaded Loops. Is this anything to do with the fact I'm running version 10.2.4?

Lesson learned when I first did this without an audio device plugged in! I would never open Logic with mics active and speakers on, but the automatic switch to built in mic caught me out. I just tried what you said and yes, this must be the cause of it. Opening any project without the audio device causes input buttons to disappear on the track headers.

Once one is pushed, it stays lit, even if you are not listening to the input on that track (preferences set to 'input monitoring only for focused track'). I could avoid it by always turning the button off again when I'm not monitoring the track, but with the preferences set that way I guess it doesn't always matter. Maybe that was a lazy habit of mine to leave some of them on, but it's easy to not notice they're on if they're not displaying in the track header! (They only display on the channel strip so if the mixer is not open, you miss it.) Screen sets won't help if the issue is that display of input buttons is not working. They are checked to display in the 'Configure track header' settings. You can see the track header changing width as you toggle this setting, as if it's making room for them, but they do not appear. Correct - feedback happens when you open the project. Sorry I wasn't clear - I didn't mean 'hit' the play button, I just meant playing back from Logic through a PA.