Scott Righteous

I'm not doing any editing - just rendering a flex track to a new track, or doing a bounce in place. The zero crossing relates to cuts and edits done on an audio region.

I have some loops at 124bpm, which I want to stretch to 136bpm. I set a flex method and look at the waveform and it looks good. I also want an audio file I can use without keeping it on that flex track, so I can do other edits and export to a sampler. But when I bounce in place, or even just record the flex track into another track, the loop never works as it should. Flex is working, but it's way inconsistent on the bounced audio. Here is a screenshot of the Flexed loop, it's noise and such, I don't care about pitch correction, just altering the BPM accurately. Here is what that file looks like after bouncing, or after re-recording the Flex track into a new track. Some parts end too soon, others on time, but then other parts start too soon. No matter what settings I use for Flex, the audio file looks good in the flex track, but never when bounced.

I now fixed it, it was something really stupid. The link button in the region editing screen got un-clicked. But the behaviour was unexpected - it would not open any regions from the arrange time-line, any one you tried to open only opened the last region edited (I assume before the button got un-clicked?)

So yup, I did that of course, and to my surprise it did not fix the issue. I can edit audio regions, but when I open any midi region, the same one opens instead - I can't edit any other regions. This is quite bonkers.

I've been working on a track all day. Now, for some reason, when I open a region, it doesn't show me what midi data is on that region, it shows me what is on another region at that point in the timeline. I can check many regions, and each one shows the wrong midi-data, which is un-usable. Has anyone else had this issue?

Every time I update Logic, some setting I had forgotten about gets changed, and my workflow suffers. This time it's a particularly weird thing that might even be a bug. However I'm hoping someone understands the issue and knows the fix. I like editing midi regions while a song is looping through that region. I have turned off all 'catch' options in the preferences, and turned off the ones that appear only when you right click on the playhead icon (kinda hidden options, but they are in my screenshot). However the damn region moves around. I'm trying to move a note but while I grab it, the damn region slides sideways off the screen and now I'm screwed. I unclick the playhead icon, and then when the loop replays, it clicks it! The setting gets changed and I can't turn it off. How do I stop Logic from having regions follow the playhead? I want to edit them while they stay static on the screen. Whatever this setting is, I have not had this issue in 20 years, but now I can't edit midi regions while playing a loop. ??

Logic has a sidebar on the right for all the audio files you have pulled into, or generated in your project. Is there a way to break that up into different tabs? I find I want to work with breakbeats, and only want to see that list, then I want to work with other audio material, and having this one giant list is not always easy to manage, particularly if I wasn't the one naming the files. I would prefer all similar material be kept together.

I can give it a try. My past experience with Aggregate Devices was that it was a buggy feature like the old node feature. Possibly this has been improved. I'm curious if this is now the norm? Do people have 3 Roland devices aggregated with their main audio interface and find everything to be smooth sailing? I single out Roland, because they often now have audio via usb, but no plug-in to manage it. Elektron and Access use plug-ins so that the USB audio doesn't interfere with your main audio device.

I use an RME FF UCX as my audio interface. I have a number of synths and drum machines that support audio via USB, but have only now decided to try and use that feature. If any one devices becomes the audio interface, it's useless really. Is the only option to create an aggregate device of all the USB audio enabled hardware? That seems like it would be processor intense, and prone to audio issues. Although I can't really see how useful this audio via usb feature is, if you have to use the outputs of your drum machine to monitor your track. Am I missing something obvious here?

Well now I feel silly I was monitoring the signal going into logic, not coming out of it, so I didn't hear the metronome and forgot it was even there! Sorry for the entire post!

Here is the project, with audio files. 80 bpm dub breaks.zip

I want to revive this thread because just today I noticed a similar thing, and assume some setting I usually ignore was updated by an update My setup is very simple. I record a single track into Logic X, no other tracks have anything on them. I can see my track input is hovering around -10, with occasional bursts up to -8. Great, no clipping. While recording, the master output is clearly off by -10db. It hovers at zero with occasional bursts to +2 clipping in the red. After I record my track, I check the audio, and it's max vol is -8, and when I play that back, the master output hovers at -10 not zero. Essentially when playing back, my master bus is 10db quieter than when recording.

My usual workflow involves setting up tracks with plug-ins and whatever automation I want, and then recording these down to another track. In some cases I have a stereo source which I want to end up as a mono track. So I don't want to bounce, nor will "bounce in place" work - I just want Logic to do this recording from one track to the next, offline. Is there a way to do that? Sometimes I have an hour of spoken word material I want to process and bounce down to mono - but I don't want to bounce out of the main stereo output - again I want to record down to a new mono track. It seems wrong to sit through an hour of real time recording!

I really think Logic X has a bug when it comes to automation. If I make a multi, and put volume automation on two different midi tracks, you can't choose to only use one of those. The power button, and mute button do nothing. In fact if you delete the second track in the arrange window you now have a single track of automation, but the second track of automation still affects the track! To get rid of it, you need to make a new channel object with the midi track you originally used to generate the automation, and then delete the automation. If deleting an entire track in the arrange window does not remove it's automation, that must be considered a bug. A bug that has persisted for many years.

I am reviving an ancient thread - because I have finally made the move to Logic X, and unfortunately can't find a workflow that seems reasonable. The new feature for 'alternate takes' will apply automation to every take, so you can't have variations of automation. This seems really, really bonkers, as automation might easily be the thing you want to try variations of. I am using a USB compliant synth - and created a multi for this. If I make two tracks with different midi channels going to the same port there is no way to mute automation on these tracks. I even tried the suggestion of turning the power button off, as was indicated by volovicg but this did not work. Possibly if your port is a synth, you can't do this, and must actually use an external midi port and midi cables. Am I missing something really obvious? It seems the only way to have variations of automation, is to take all the regions on your track, convert to one giant region, and apply the automation at the region level. This is really limiting, if you need to change your arrangement and then have to cut verses and chorus's out of your giant region. Is there some easy way in Logic X to have alternative versions of automation for a given external synth?