Inge

I think the finer points of music engraving is better done in Finale...

Alright, so I'm an idiot... 😄 Another new thing I (finally) got is Melodyne... it seems these behaviors arise when melodyne is active on a track (before you print the Melodyne edits) Once you disable it, the track seems to act normal. OK. Live and learn.

Hi all. So I just recently took the plunge and blew beaucoup bucks on a major update, now running the Mac Studio Ultra with the M1 and all that. Logic 10.7.7., Ventura. Things are somewhat haywire. Intermittently (?) the take folders simply don't work. I punch in, and the older take plays back while I record! A new take is created, and you can see it and select it, but it won't play back. The only thing that will play back is the oldest take, no matter if you highlight another take(s). So frustrating. What is going on? Are there some new weird functionalities to take folders that I just don't understand? Also things like: a project won't stay in low latency mode, gotta go back in and check that box each time I open the session. Mildly Annoying, though not as bad as this: Another ultra strange bug: Right after I've recorded a track, its controls don't work. Track volume sliders will move, both in mixer window and in track header, but level is not affected. It just keeps playing back at a steady volume. Until you input-disable the track and pick the track input again. Then it seems to regain normal function, after a time. Same with pan. Knob moves but does nothing. So many weird things. I almost wish I had my ancient iMac back. Expert opinions and explanations most welcome.... 🙂

Ah. I rarely bounce regions in place (except for flattening take stacks) but I see what you're saying. I do bounce whole tracks (not regions) in place a fair bit, so I sort of still wonder why the button stays on in that case. Thanks for your insight!

Hi. So I’ve noticed that when a track has Flex engaged and you bounce it in place, the Flex button stays engaged on the track header of the resulting track. This confuses me - all the stuff you did in Flex (whether pitch, quantize or whatever) is now bounced into the BIP track, right, so why would Flex still stay on? Is there any Flex stuff that doesn’t bounce into the BIP stem??

Great answer. I’m leaning toward continuing to work without one, though I ran into a producer buddy of mine the other day who almost made fun of me when I told him I mix on the screen, and it made me insecure lol. I just feel like I wouldn’t use it that much beyond play/pause and maybe the scrub wheel.

Hi all. Got a more general question this time. I’ve been a Logic user for many years, and have made some viable audio products with the DAW we all know and love. But I’ve never owned a control surface. I do all my automation and mixing on the screen. Draw automation lines, use the mouse for hand-fades etc. How much does adding this element to your home studio really improve your workflow? I should say that I don’t usually work with bands etc - on most of my projects it’s just me, playing all the instruments one by one, with maybe a guest vocalist or instrumentalist coming in to overdub something at some point. Does having a physical board with motorized faders really make a difference in your day to day with Logic? What are your experiences working with/without one?

Yep. He gave me great insight into a beat mapping issue (all my fault) a couple months ago. It makes sense that a region would redisplay like that when you drag it past a radical tempo change, which is exactly the case in this project. Duh!

Aha!! So that’s what’s doing it. Ok, that makes sense! You’re a genius! And you’re exactly right!! Thank you!

Even more info: I took the file and ran it through a re-rendering program ("Switch") and re-imported it into the session as an mp3. It STILL does the same crap! So... it must have something to do with some setting in that particular session??

One more point of info: I opened a new empty project, imported the track (exported as audio file) into the empty session, and it STILL behaves like that. So it must be something encoded into the file??? I'm baffled.

Indeed. The first region is a cut section of the whole track, which is/was a BIP. Mysterious. Bug/Glitch? I don't see a legitimate use for this kind of behavior. I even bounced the track as an audio file, reimported it into the session on another track - and it still behaves like that....

Hi guys, I got good help from this forum before. My question this time: What in the world is happening here? (See attached video). The regions in one of my projects suddenly started behaving like this: The waveforms within the regions "scroll" through the region when I move them (or nudge them.) So strange. I've never seen this behavior before. Did I check some function checkbox that makes regions behave like this?? It's only happening in this one session. (I'm working on many, the rest behave normally.) I don't even understand what the point of this is? All I'm trying to do is move some audio.... which I obviously do all the time in dozens and dozens of projects... https://www.youtube.com/watch?v=_WFCg9ZEAio

Solved! “Fuzzfilth” here really stepped up and taught me a whole new thing. Great lesson in proper beat mapping that I had no idea about.

Already did that. Works like a charm when I do it in an empty project.