burntphoenix

Hi there - Sorry I haven't checked in. As far as the looper: It requires a dedicated hardware controller (anything MIDI/USB controller, preferably with 8 sets of controls); a little know-how in Logic's routing or channel setups (particularly the difference between pre- and post- on the bus sends); and about 45 minutes of your time. I am actually designing a one-hour seminar on this how-to; in which the same looper function is created in Logic 9.x, Mainstage 2.x, and Ableton Live 8.2.x without using anything but a native (or free 3rd party) delay plugin, no native "Looping" features used. Doing it this way helps you wrap your head around the concept of synced looped tracks in a live situation; something that can't be done with the current little looping pedals, with the exception of the Boss RC-50 and Electrix Repeater. As far as recording to a new channel; I believe what you are trying to do is record (as in, SAVE) your individual loop content for future retrieval. This is possible but requires you to create additional 4 stereo audio tracks to record to full-time; and a hard drive or equivalent plus fast CPU that can handle all of this read/write traffic without stuttering. Anyways I personally haven't messed around with this project since Feb 2012 as I changed USB controllers. It definitely needs revisiting. I'll post again in a little bit once it's revamped.

Here is a final file. Enclosed in the zip is a folder with 2 files: The Logic Pro 9.1.x project file itself, and, a how-to PDF if you want to create it yourself from scratch (or improve on it). Please respect the Creative Commons and file distribution caveat contained in the read-me file. I also highly suggest to read the read-me no matter what. 95% of this READ-ME file is a "How-To" exercise on building your own Looper file. You don't have to rebuild it! The Logic project file attached is ready to go. I put the info in there for the die-hard wanna-do-it-myself people and to share my thought process. You will need to define or set up your own custom midi controller assignments to get the most out of this file. If you're not sure where to start, integrating the midi keyboard-activated design that Scandor made up above is one place to begin. I tried to make it as simple as possible (there's no Environment wiring at this writing). Thanks all! Have fun. EDIT: HERE'S A QUICK TIP. I should have put this tip in the instructions; I'll add it in a later verion of the file. For now, Copy this Quick Tip: If you want Ultrabeat's drums to bypass the global effects, thus avoiding the global reverb you'll most likely use on a voice track, change Ultrabeat's channel output from Bus 56 to Bus 57. That's all you have to do; a simple change to keep your drums dry when everything else is wet. This little change can possibly make this a more usable file for some folks. Ultrabeat's channel already has its own dedicated Bus Send for Tape Delay in place, for when you want to add a little spice just on the drums. I'll make an audio demo file soon and post it on my soundcloud page, e.g. just me, Logic, and a Korg nanoKONTROL2 USB MIDI controller. Ok, maybe a mic and guitar, too. Next project is to convert this over into a Mainstage file, for the folks who use it. There's no reason why this can't be done, as far as I can see. Logic Looper for web v1 by Robert Dorschel.zip A *Functional* Logic Pro Looper project file

Okay, I finally produced a file ready for sharing. Please see the other posting, crosslinked here: http://www.logicprohelp.com/viewtopic.php?t=74436

Didn't like the outcome, but... Thanks for the quick Reply, David.

Hey there... I'm trying to create & share my Logic project file that turns Logic into a looper. This looper file involves custom MIDI Controller assignments I've made in Logic, using a Korg nanoKONTROL2; about 30 custom assignments. How do you send that custom set along with a project file? In a manner that any other Logic 9.1.x owner can open/append these custom controls into their own set without interfering with their custom settings? Or even if there is a temporary way to use these custom settings, what is it? If this can't be done smoothly... well, I'll just have to say, "this is what I did -- good luck and goodnight", regarding controlelr setups, when I upload the file.

okay okay okay I've nearly recuperated from a few challenging weeks here. I'll post it later; Here's the plan for when I get home tonight. -create the looper project file from scratch, using only Logic-native effects & instruments. -while doing this, make a screenshot PDF "how-to" for the folks who want to do-it-themselves. -test the poop out of it. -post the Logic project file and the how-to PDF here (and also reference these in the other looper post I made). I need 12-24 hours to do it right. Acceptable? In the meantime, if somebody could answer this related question, it would be great. http://www.logicprohelp.com/viewtopic.php?p=393528#393528

that's just it... in the end, once I finish the design... yup, you'll be able to record everything... the pre-loop audio, the midi data of your controller, and capture your output. It currently works for me at home. However my setrup of buses and aux channels has morphed somewhat since my original post. No matter what, well... you can create a really really basic looper using a single Delay Designer on a Bus send setup, like a pedal would work.

I'm not in front of my computer but if memory serves... Solo (click the S) the Capture track; input monitoring should be on (click the I... That's the letter I between H and J... ) on all audio input tracks, including Capture. Arming them is not necessary. You would only need to record-arm software synth tracks in order to accept midi triggers. The input monitoring on audio tracks is all you need if that's all you're using. If you wanted to record, you would need to record-arm the capture track. If you're just foolin around, don't record. You'll just fill up your hard drive. I believe (here comes the part I can't recall that's probably vital) I also had "end of line" also soloed. I hope you get it figured out and hope I didn't give misinformation. Write me back and I'll write again later on after work. I'm on east coast time 9-5er job.

yes I realize that, and yes it is for a live performance track. I might need to "break out" of the sequence and do an improv with another artist, and have our tempos match. some of my softsynths AND hardware synths are getting MMC midi clock from Logic, which only happens when then transport is running. If I have a global tempo... well heck, I want the control and don't want the computer to question what I'm doing. No matter, I'll just have 2 projects running, and switch to the 2nd project that does NOT have a tempo CC in effect.

Ok, I sent mixed signals misinformation: of course in the end I want to be able to record midi and or audio data. The primary objective at this point is to just get stuff to work, period, as more-or-less a rack o'gear like Mainstage first... And then be concerned with editing ability at a later date. I was actually answering to Scandors questions and trying o avoid confusing him. I ended up confusing you Yes, I was doing the direct wiring wrong. I needed to put in a channel splitter as Scandor mentioned. My problem was compounded by putting in a Y-cable, to 2 transformers, to make one controller play on 2 channels... Turn created a big ol midi loop by wiring it to an iac bus without a 'dead-end'. I can see that now, after my morning coffee has kicked in.

Scandir: to answer a few questions: -No, I am not hitting record. -for some reason, I cannot wire directly to instruments... I believe it's because I have a mix of external midi devices, soft synths ... And end up with a logic fatal error midi loop situation. One device in particular requires a loop: the Akai Me20A. Anyway, I discovered direct cabling causes issues. Unless of course, I'm doing it wrong. Can you post a quick screenshot of a "proper" direct wiring to a track channel? - I DEFINITELY want and need to go the midi channelization route. I wish I could handle all interfaces and devices externally to Logic and just send one IAC in/out midi feed to Logic. If I could, then all of my problems would be solved! - I thought of the group settings too, but that idea quickly gets shot down by multichannel instruments which I already have assigned as a group. Specifically, Stylus RMX as a multichannel group for channel volume, and I mute each of the 8 outs manually (korg nanokontrol buttons-top row). The other is Omnisphere... Similar setup, channel volume is grouped, and each of 8 parts can be muted via the bottom row of buttons on my korg nanoK. Since those are already in groups, I can't assign them to a secondary group for record-arming. It's more important to have live control over the volume levels. Eventually I'll get there.

I have a project that has various tempo changes in the global header track. Is there a way to override the that tempo while the transport is running, without stopping, and without having to address a dialogue box that pops up? Try it in a new project to see what I'm talking about... Just set a tempo in the global tempo track, press play, then try to change tempo in the transport display. Sure would lve to be able to change that on the fly!

That why I haven't posted a file yet. I'm refining it so it should work on anybody's rig. And road testing it in a show in a week.

Never a dull moment with Shiv.

Logic is extremely powerful and folks only use, like, 10% of it's features. Right on par with how most folks barely scratch the surface of Photoshop's abilities. If you want Logic to do something really, really specific, you have to dig a little deeper into the environment settings and create it yourself, or, set up some sort of bus/aux audio routing getup. As far as TL;DR... http://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn't_read