SaxBlaCussionizer

"Unfortunately" is a REALLY nice way of putting it. I'm truly baffled by this, Logic keeps coming out with these new features, but this is a REALLY basic one. It blows my mind that Logic can't do this very simple MIDI routing thing. Thank you for your answer though, i'd been scouring YT videos looking for a solution. Looks like i'll have to port my tracks over to Ableton....again. cheers!

This is something that is pretty simple to do in something like Ableton, but i can't figure it out in Logic. I have a third-party VST in a software instrument track which has an arpeggiator on it - an arpeggiator that is part of the instrument itself and NOT Logic's arpeggiator. I simply want to capture the MIDI notes generated by that track in another MIDI track. I am aware of the new ability to record MIDI FX ability to "Record MIDI to Track Here" that came thru in 10.7.5, and that's not what i'm after. I'm also aware of the (perhaps out-moded?) method of (1) recording your original MIDI track, (2) setting up a second MIDI track as an 'External Instrument' and using "IAC Driver Bus 1" as the MIDI destination for the track, (3) dragging your MIDI from the original into the second track and recording. (which did not seem to work at all). I don't wish to use any MIDI FX, i simply want to record a 3rd-party VST output as MIDI. What is the correct way to do this? thank you!

No worries, it sounded like you had some experience in the area. Thanks for the help! cheers, jim.

Thanks for that, i've made a note about it. You are right about iZotope, i "thought" i had researched this earlier and found that iZotope was on 'the good list' but i was wrong about that. One additional question (though i am back up and running thanks to your help). Is it fairly straightforward and not time-consuming to switch back and forth between running Logic natively and via Rosetta2? I would always prefer to run natively, but i do occasionally need to run an iZotope plugin. Pretty much every single other plugin that i have used recently seems to run fine in 'native mode'. thanks much! cheers, jim.

This worked, thanks, i learned something today! To be clear for those coming along later, when holding the Control key down while starting Logic from the Launchpad, it'll ask if you want to start Core Audio, and you will say 'No' to that and your plugin will be disabled. It will look like you can't change it but if you right-click on it, you can choose "Disable plugin" which will remove it. And..... save your work! Thanks for the help, MUCH appreciated! cheers, jim.

BTW, it would be good to know how to "trash my preferences"?

Thanks, i will try that. I'm running Logic natively, running on a new M1 Mac Mini.

Greetings LogicalProFolk- I am using the most recent version of Logic Pro X on an M1 Mac running Big Sur 11.2.3. All my plugins have been validated by Logic including the ones that i will mention here that are causing the issue. Supposedly, the plugins used below have been validated to work in the newest Macs, though i've found that to not be true here. I created a project and am wanting to do some spectral repair on some audio created previously. I pulled in the iZotope RX Spectral Repair plugin into my track and got the following error: "An Audio Unit plug-in reported a problem which might cause the system to become unstable. Please quit and restart Logic Pro." Before it crashed, it gave me the option of saving my work, which i did. However, now when i attempt to open Logic, it takes the default behavior (which i've since learned that i can change ONCE I AM IN LOGIC) and tries to open the previous project (containing the ruinous plugin that caused the problem initially). That results in the same error and my only option is to 'Quit' again. In short, i am completely unable to start Logic now. Is there any way to start Logic in this current state and have it open a blank project for me? Or, am i going to have to uninstall/reinstall Logic? (and i'm not even sure that it won't have saved my default settings from prior Logic incarnations on my machine?) Help me if you can, i'm STUCK in the mud! cheers, jim.

Yes, at the moment i was attempting to record, but i was wanting to hear my effects as i did so (i was doing a call-response thing with a Native American flute). My original configuration WAS recording what i wanted to hear, i just couldn't create a proper take without hearing the back and forth call and response thing that i was looking for. Let me know if that helps. I was on a quick support call with Focusrite, their online chat is very helpful, if it's available.

Thanks for the help David, i got it figured out. It was the combination of a couple of things. For the record (for those coming along later with a similar problem)- Inside the Focusrite Control software itself: For each of your monitoring outputs (1-2 are your main monitor outputs, 3-4 are typically going to be your headphone outputs, add the inputs that you plan to use and MUTE them. (This is to avoid directly monitoring them). Then, inside Logic, there's two steps: 1) Turn on software monitoring. 2) Turn on Input Monitoring on the track you're wanting to hear the effects on as you record. Two missteps were causing my reported issue(s): 1. I didn't have my tracks muted inside Focusrite Control (which SEEMS 'counterintuitive'), so i was hearing direct input from my external sound sources. 2. I was not enabling Input Monitoring (the "I" button) next to the Record (the "R" button that we all know/love). I am coming at this with a new setup for me, new Mac and a new hardware/software interface (moved from MOTU Firewire interface because my new Mac does not support Firewire) and don't remember having to enable Input Monitoring on a track before. I don't know if i'm mis-remembering that or if it might have been my old interface's software workings. Either way, the above steps will get you there and thanks David for your help. I suspected fairly early on that a source of my problems might not reside exclusively inside Logic. cheers, jim.

Checked that, it is not on and never was. I don't know if this is a symptom of the problem or not, but when i put the effect (any effect, i've ruled out that it is a specific effect) on a bus and route the output of the track in question directly to that bus, i see NO output levels on the bus, zero. That doesn't make sense does it? That's not "the issue", i can hear the "live" version of whatever i'm recording, i just don't hear any effects when i'm playing "live" only during playback do i hear them. Anybody have any good ideas? Maybe a audio device configuration issue?

Hi- I'm moving over to a new Mac Mini M1 from a 2012 Mini and thus, i'm now in Big Sur and using Logic Pro 10.6.1. As such, i'm working thru all the things that i had set up on my old machine that i've not set up yet - finding them one..... by one...... by one. This one is baffling. I'm recording thru a Focusrite Scarlett interface and on the same channel, i've got a couple of effects. I'm hearing my dry signal as i record thru my headphones but NOT the effects. I originally had these effects on a bus, but when it wasn't working, i moved them to the track itself. The "typical" answer is to "turn on software monitoring", which was not enabled when this problem began but is now. That does not correct the problem. I have Auto Input Monitoring also set to off (although i've tried it both ways), no effect. When routing the audio to a bus, the bus was not showing any input levels either, dunno if that helps or not. But when i move the effects off the bus and back on the track itself, i do not hear them when i am recording but DO hear them on playback. This is probably a simple problem, but it's something that i configured LONG ago on my old machine and (as indicated above) all my research points to one answer: "Turn on software monitoring". And i've got that on, so the issue is deeper than that. Any help is appreciated! cheers, jim.

Thought i'd add that i'm using Logic version 10.5.1.

I'm about to KILL MYSELF (or at least pull my hair out ) but before i do, i'm hoping someone can help me with something that "seems" REALLY simple. I've got a MIDI track that i am working on in 8-bar chunks. I have the main track fader volume set to 0.00. Upon playback, when the playhead moves from the first 8-bar chunk to the next one, the volume fader on the track inexplicably drops to a -9.0db. It makes NO sense why it would do this (at least to me). The only track automation that i have/had is the track volume set to 0. I have tried deleting ALL automation on the track. The above behavior persists. I have tried creating another track and dragging my regions to it (without copying the automation). It STILL drops to -9.0db every 8-bar chunk. There is no MIDI volume curve drawn. I cannot for the life of me explain it. I've attached a screenshot that shows the volume curve at zero, yet the actual value is at -9.0. Any attempt to draw the automation using 'Touch' does not change this behavior. I can find nothing in the region inspector that would explain it. I'm frankly baffled. If anybody has a suggestion for some parameter or Logic behavior to check, i would appreciate hearing. I dunno if i've just been working on this too long and need a break or if there's something REALLY simple that i've overlooked. thank you very much if you can suggest something (probably really simple, but i need to learn this). jim.

Further info, it's just now happened a couple of times JUST on the instance of QS that i'm working on. I'm looping playback of all four tracks and just penciling in notes here or there on a single track and suddenly, the pitch of the entire track changes. But the other three tracks maintain their pitch. Baffled and a real buzz killer which really disrupts the creative process!