Jump to content

45rpm

Member
  • Posts

    1,288
  • Joined

  • Last visited

45rpm's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. If you prefer to work in the Arrange window, Logic can indeed pitch audio nondestructively in the Arrange window. This is done with the Transposition parameter. And for certain categories of audio where this parameter is unavailable, you can make it available.
  2. Maybe your MOTU is longing for a factory reset. I'm just channeling beej. It seems to be the issue du jour.
  3. I don't think that will help. Try this: create a new OS X user account (in System Preferences/Accounts). Login as that user (via Apple Menu > Log Out). Open Logic. Same problem?
  4. Hey redlogic, thanks for the correction, you're absolutely right. I never would have noticed if you hadn't pointed that out. I have been using a version of the pdf with a created date of 9/17/09, containing 1340 pages. But you prompted me to download a fresh version (from here: http://documentation.apple.com/en/logicpro/), and I see what I just downloaded has a created date of 3/16/10 and contains 1342 pages. How sneaky of them! I like to post page numbers, and I had no idea that they were at risk of becoming obsolete, so thanks for noticing and for speaking up. Now I know I need to be careful about that.
  5. The technique you described (about doubling and re-doubling items) is clever, and I bet there are other places where that technique would be useful. So you probably helped some people by introducing an idea that maybe they hadn't thought about. Also, I think it's always good to know alternate ways of getting an equivalent result. So these are reasons why you saying what you said was a good thing.
  6. That's great news. Thanks for updating the thread and letting us know. I'm glad to hear that your problem has been solved. In case anyone else wants to see how this procedure works, I've created a folder with a few small files that can be used for that purpose. If you drag them into Arrange, they look like this: http://content.screencast.com/users/logic.45rpm/folders/Jing/media/e4fef372-80c2-4056-812d-d1d65c4e1f97/00000041.png There are two groups of files, A and B. Notice that the A files do not fit the grid, and they have a regular stereo icon. Follow Tempo and Transposition are not available for these files. They are plain, ordinary wavs. They contain no tempo information (e.g., they have not been Acidized). The B files are Apple Loops. They fit the grid, and they have a distinctive looping icon. (Factory Apple Loops have a different icon, because they are compressed. A visual guide to these icons, or glyphs, is here.) Follow Tempo and Transposition are available for these files. I converted the A files into the B files using the same procedure that Matt used to convert the 336 loops in his Deadmau5 Xfer collection. You can do the same thing on your own machine. Trash the B files, and apply the procedure to the A files. You will have recreated the B files. What's important to notice about the six A files is that they vary with regard to number of beats, tempo, file size, duration, and bit depth. Nevertheless, in every instance Apple Loops Utility is able to properly calculate tempo and number of beats. It's able to do this simply by examining the duration of the file, and also making certain clever assumptions about the file. Those assumptions are clever because they are usually correct. For example, they are correct for 100% of the 336 loops that Matt converted. More details about how this works are explained in the thread that Matt referenced. The key word in that sentence is "should." The steps you described should be enough to get the correct result, but they're not. You can demonstrate this with the folder of A files that I provided. If you apply your exact procedure to that folder, the result will be new files that don't behave like Apple Loops (e.g., they don't follow tempo). Why? Because ALU has a bug that interferes with proper batch-saving under certain conditions. Part of what I did is find a simple way to defeat that bug. The correct procedure is simple, but it's not quite as simple as what you said. If it was that simple, this thread probably would have been a lot shorter (both in terms of number of comments and in terms of elapsed time).
  7. When you have a region you want to extend through your entire song, it's easier to just select it and press L (which means "loop").
  8. I've done this sort of thing a lot. Mostly with pop music, but the same technique should work fine. As melodea said, you need flex, but that's just part of the solution. I would start by beat mapping performance A. Now the Logic grid follows that performance. Next use flex to make performance B follow the Logic grid. I think you'll find this easier than just using flex to try to directly match B to A. And I think you'll find that the end result is quite good. If you need help with the details, just ask.
  9. This problem with delay has been discussed on a number of occasions. For example: http://www.logicprohelp.com/viewtopic.php?t=52633 http://www.logicprohelp.com/viewtopic.php?t=43135 http://www.logicprohelp.com/viewtopic.php?t=48513 You might find a workaround here: http://www.logicprohelp.com/viewtopic.php?p=293377#293377
  10. I don't have any personal experience using this feature, but the Fantom-G apparently has its own audio interface, built-in (pdf):
  11. If you've just created a recording and you want the transposition option to appear, there's a slightly easier way to make that happen. Just click on the checkbox for Follow Tempo. I think it's fair to call that a bug, but it's easily addressed. Most audio that Logic sees as non-transposable can be easily converted into audio that Logic sees as transposable. Here's how you do it. Select the non-transposable region. On the Arrange local menu, select Audio > Open in Apple Loops Utility. (If a dialog appears, just press the default button.) In ALU, select Looping. Press command-S. Press command-tab to switch back to Logic. Your region is now transposable. In some instances, the length of the region will change. If so, just uncheck Follow Tempo, and that problem will be corrected. Transposition will still be available. If you want to preserve the Follow Tempo feature, but also notice that the region length (i.e., tempo) is wrong, just turn on Flex. In most cases, the region will snap to the proper, original length automatically. If not, just grab the top-right corner and stretch it yourself. When the color turns neutral, you'll know you have reached the proper length. This procedure is related to the procedure I referenced here. In both situations, we're using ALU to create a looping Apple Loop. What's interesting about your situation is that we're creating a looping Apple Loop even though we have no intention of ever looping it. We're strictly interested in some other qualities that happen to be possessed by looping Apple Loops: Follow Tempo and Transposition. By the way, above I say "most audio" only because there are some extra steps required if the audio material is more than about four minutes long. But if you're filled with an urge to transpose, say, Alice's Restaurant (18:34), you can do that, using a slight variation on the above procedure. Correct. But usually when we create an Apple Loop that we actually intend to use as a loop, we use Region > Add to Apple Loops Library. And when we do it that way, Logic makes the Looping button unavailable unless certain conditions are met. This is a problem. The procedure I described above gets around this problem.
  12. Yeah, I know, I already saw that thread. But if he finds out that his seemingly mysterious problem has an easy solution, maybe he'll change his mind. There also might be some future merciless_g's out there who manage to avoid his confusing experience on account of spotting this thread first.
  13. Edit > Cut/Insert Time > Insert Silence Between Locators (⌃⌘Z) If you set the ruler to display Time (and not just Bar), you can stretch the Cycle Range while watching a help tag that will let you see when the range is exactly 30 seconds in length. Especially if you take advantage of zooming. This also might be relevant: "Positioning Bars to Frames," p. 1191-1192.
  14. FWIW, here are a couple of other threads that seem to be reporting the same issue: http://www.logicprohelp.com/viewtopic.php?t=56223 http://www.logicprohelp.com/viewtopic.php?t=56461
  15. It sounds like you've done a bunch of things in Logic to make your song pretty loud, right? And you play it in Logic and it sounds pretty loud. And then you bounce it, and you play the bounce, and the bounce isn't nearly as loud as how your song sounds inside Logic, right? When you do a bounce, by default Normalize is on. Normalize often means 'make everything a little bit louder.' But in your case, I think Normalize means 'this better get turned down because there is clipping here.' That's what Logic will do, by default, if you try to bounce a song that has levels that are too high. I think this is the situation you're in. Try this. Select File > Bounce. In the dialog that appears, look for the Normalize control. Set it to Off. Now create your bounce, and listen to it. Is it louder than the last bounce? This might solve your problem. But just listen for distortion, because you might be getting some of that, along with the loudness.
×
×
  • Create New...