slide187

Thanks everyone... understood. And yes i just wanted to delete the VCAs that remain as there's no need for them to be there as i'll be creating new summing stacks in their place to manipulate those particular tracks. just less visual clutter, and they were at 0db anyhow. Thanks again, much appreciated.

So i have sort of a part B to this question... Here's my scenario... i had a couple of track stacks (folder type) just for organization... but i've realized i would rather have these as summing stacks, since the tracks in the stack can be processed together, and this would save me some processor power. Following the process mentioned above with my folder stacks, i select a folder stack, click flatten stack... the two tracks are then shown as they were before, but still have the bus routing from the folder stack... and now in the mixer window (as mentioned above) the folder stack is shown all the way to the right and will still control the two tracks that used to be in it as far as volume, solo and mute. even after i change the separate track outputs back to stereo out again... My real question is how do i delete the old folder track stacks from the mixer window (and from the project completely)?? since when i try to do that i get this pop-up and i don't fully understand what it's warning me about... Does this just mean i'll be deleting the old folder stacks and their association with the tracks that were in them prior to flattening?

This site is a great resource for solutions as well as prevention. I’m glad I checked here first… So if I’m counting right, regarding Sonoma, that’s one manufacturer of a class compliant device that won’t commit, 2 class compliant devices having issues, and now a couple native plugins with issues. Pretty much all I need to hear to sit tight for now. 🫤

Evidently so is the Spark, but they still wouldn’t commit to a 👍🏼

So i've been waiting so long to do the switch to Ventura that i stopped thinking about it pretty much completely. And now the Sonoma update just sorta snuck up on me. And i'm realizing that since the last big update i have forced myself to become less reliant on 3rd party plugins for that reason. So I checked my interfaces and plugins just now and found this: Plugins: Line6 PodFarm 2.5 - Ventura-✅, Sonoma-no info but they usually take months at Line6 Waves Audio - compatibility info and upgrade info are a mess... and have always been, which is why i barely use them anymore anyway and i only really found vocal rider and bass rider helpful. But those have been working long past what their site says they would, so i'm willing to gamble with them. Interfaces/hardware: Focusrite Scarlett 2i2 2nd Gen - Ventura-✅, Sonoma-✅ Spark Mini (actually pretty good as an interface). No interface specific compatibility info on their site, but it has been working fine in Monterey. Since i'm really only "totally" dependent on the Focusrite as an interface and that works with both os', do you guys think i should Update to Ventura and see how that stuff all works before moving to Sonoma? Or should i even bother with that step, and just go str8 to Sonoma in a few weeks say?

Yeah I thought about that, but these are at the same zoom level. And again within the same region. So like my first pic shows 2 adjacent regions at the same zoom and the second one is one region where the wave form just changes from one to the other. But yeah it’s def only a graphical glitch since the sound is fine. But it’s the same when you zoom in or out (until you get WAY in like your screenshots) So I agree. Not a big deal, Was just curious if anyone had seen it.

Hi all, So in a region, the sound wave graphical representation is ... an outline... and then it's not. I tried to search for this, but i don't think i had much luck depending now how its described. i noticed it while making crossfades between regions, and then scrolled back to see if it was just one region, but its actually only about half the region. no apparent audio issues tho. the region in question is also not a comp'd region. see pics.... anyone seen this? or know why it happened? for reference: Logic Pro X (10.7.6) on my iMac retina 5k 27" 2020 running Monterey 12.6.2 3.6 GHz i9 128 GB RAM AND Radeon pro 5500 XT graphics card Thanks for any info.

The more research on this bug i do, the older and older the posts get. I have now seen posts on this bug from 10 years ago, which sound exactly the same, but it's back when "Flextime" was referred to as "Elastic Audio." Apple has made no official recommendation, or fix in any of the updates and it really seems to be that they cannot mitigate the problem. It also seems that no matter how powerful the mac it runs on is, the issue still happens and is still exactly the same. The audio continues, the play head freezes, and you cant do anything until you click ok in the notification. My iMac specs are: 27" 2020 retina 5K 3.6 GHz 10-core i9 128 GM Ram............ and i still get it anytime i use flextime. So it's the inability of Logic Pro to correctly process it, rather than the machine itself as has been mentioned in some of these older posts. It seems like one of the most common "fixes" is to use the bounce-in-place function to reduce the number of tracks using flex at one time. i have yet to try that approach as i have only tried the "shutting off flex for the problem child region" but that has proven to be unreliable. Next time i get going on a new session, if it happens i'll try to bounce in-place and let the forum know how it worked out. Another method i have on deck seems super undesirable, but it just may be workable. my plan would be to track everything in garage band using that simplified interface and then export the finished stems when the "performance" of them is completed and edited, then do all my mixing and plug in editing/mastering in logic. but that just seems like a PITA last resort type of thing. Sort of like buying a Tesla and putting a Hemi in it because the battery keeps dying immediately. haha. but i digress. The other thing i may fool around with is taking that sample session that came with Logic Pro (i think it's "Colors" by Beck IIRC) and try to record a few more tracks into that session which is already pretty involved to see if i can create the error in there (that session does not have this error and it has a ton of tracks... there has to be a reason for that and it can't just be that none of them use flex.) Just some thoughts.

Not only that, for me lately once I’ve gotten rid of it, it reappears in the same session the next time I open it. EXTREMELY distracting. And a creativity murderer.

Hi all, So i'm new to Logic Pro, but not new to DAWs/recording/Apple/etc. Has there been any definitive way to prevent this error message? it is ENORMOUSLY distracting to the creative process... (something that never happens in GB... which is the most maddening of the situation... how can the dumber little brother of big fancy Logic Pro not have a problem like this when they both use flex time/pitch?) it seems to me once you delete a recorded region that had some flex editing done to it, the missing region audio is what Logic is looking for to perform the flex instructions.... so how can we make sure that when we delete a region, that Logic does NOT retain the flex data??? because the only way i have seen to prevent this is to locate the track/region on which is is happening (and good luck finding that once you're a bunch of tracks into your session) highlight that region and turn off the flex just for that spot. but this solution is unreliable at best. i guess i can try to "not do any editing to the timing" until i know i'm done recording each track but that is ridiculous to have to do with a DAW like this. i mean, what if a month down the road you decide to move a pre-chorus or add it again at the end of the song by pasting? i bet this problem rears its head again in those cases. as well, from what i have seen on the forum, there have been threads about this exact problem for the last 4 years, so i dont think it has anything to do with big sur or even Logic pro 10.6.1 being new/buggy.