mraskovsky

I shall give that a try, thanks! Just did it and duh! Often times the obvious solution IS the solution. I was was overthinking this as much as possible. You've saved me from a major hair pull!

I use the I/O plug in to rout groups of tracks to an external HW device, but when I use the same I/O on the mix buss, it (naturally) creates a feedback loop…but why? The way I understand the I/O plug into work is to literally route the audio out of one set of out puts, thru a device and back on to the output. Now if this feedback loop is to be expected and the only way to utilize the I/O hardware set up is to buss all tracks to an AUX, insert the I/O hardware there and allow the AUX to route to the Stereo Buss.

The manual does not indicate that this is a feature.

I have an arpeggiation I created in Waves Elements 2 plugin. My goal is to record that midi data into a LPX project/track to further manipulate and use with another synth. I've tried using MIDI FX Freeze to no avail and also tried the recommendations of the IAC Driver, but they seem to be rely upon the LPX arpeggiator. I did try recording the Arpeggiation as dry Audio, convert it to MIDI and have it drive the plugin, but the results were less than satisfactory Seems to me that there should be something in the LPX Environment that would allow me to route the data. Thanks for reading, Cheers

apologies if this is previously covered, but I did not find the exact situation: Client had a dozen 2" 24 tk reels converted to 48k WAV files. If the SMPTE T/C was copied over to TK 24, is it possible to use that signal to drive the Logic clock/sequencer? Thanks

My project setting is at 88.2 as is my hardware (Scarlett 18i20) When auditioning Apple Loops, they play back at double the speed, but will convert when imported into the project. Is there a means to have the browser react to the correct sample rate?

David, Thanks for all of your input. I have resolved the issue. Quite simple actually. I went back into AMS to the aggregate, confirmed clock master and restarted the Mac. Now, all of the inputs and outputs display as expected and the MPA digital inputs are available as inputs in LPX. I appreciate the website and refer it to clients on a regular basis. Mikey

David (BTW, a long time fan and advocate of the site), I have resolved my issue. My MPA comes into the Scarlet via lightpipe and shows up in LPX as Mono Inputs 11/12 or as a Stereo Pair. So that's resolved. My next goal is to understand why the aggregate (Scarlett/Pro40) shows one set of available inputs when creating a new track:/Users/michaelraskovsky/Desktop/Screen Shot 2020-02-18 at 7.27.56 AM.png And another in the Inspector:/Users/michaelraskovsky/Desktop/Screen Shot 2020-02-18 at 7.28.17 AM.png

Thanks for the reply. To be more concise, when I had the Pro40 as my only interface, I was able to bring up the MPA as a digital source on inputs 11-12, connected via light pipe. Now that I am connecting the Scarlett and the Pro40 via light pipe, the MPA doesn't seem to show as a digital source. Cheers, Mikey

Thx for the reply! Along with the two of you chiming in, focusrite also sent me some info. My Scarlett is acting as the clock master but until I read the focusrite email, did not have the correct light pipe configuration. I will fix that this evening. My only remaining question is whether I can have my ART MPA digital outs via SPIDF show as inputs along with the Pro40 coming in on lightpipe

I have a Focusrite 3rd gen 18i20 and have created an aggregate with a Focusrite Saffire Pro40. When I create a new audio track in Logic, I can see that there are 40 (mono) available inputs to choose from, yet when I select Create and the channels strip is viewable, I have only 20 inputs to choose from. 19 and 20 are the inputs 1 and 2 on the Saffire. Am I missing something in the Focusrite Control app? Thanks Mikey

Thanks, I’ll try that. I did try quantizing at 32nd notes and there is no phasing

I have a set of TD-17 V-Drums (quite nice aside from the Hi-hat). I'll play along with one of my Logic Projects and will select the MIDI region and quantize it to 16th notes. When played back, those notes that are "fast notes" (16ths or above) will playback with a degree of phasing, not egregious, but still affecting the sound. I've toggled the usual suspects (input monitoring, channel select, local on, etc.) but the culprit seems to be quantization. Anyone else experience this? Please don't suggest "play it better" Ha! Thanks Mikey

No flex and this has been around prior to 10.4 Is it reproducible on your machine? Thanks

Yes, Thanks