Jump to content

Chrispire

Member
  • Posts

    33
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Chrispire's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. You are one inventive dude Atlas007! Probably too much hassle to take that route though. This Gnaural program I found will do what Logic used to be able to do so effortlessly. Yes, I'd rather use Logic, but Gnaural is pretty easy to use too. Cheers!
  2. Good question Atlas007. Binaural beats are not the same as "beats" in the usual sense of the word. They are a specific type of sound that occurs when you combine two sine waves together that have slightly different frequencies. The sound waves cancel each other out periodically as they move in and out of phase with each other. This makes them sound like they are "beating". For example, if you combine a 100 Hz sine with a 105 Hz sine you'd hear a 5 Hz beating sound. These sounds are sometimes used for therapeutic purposes (i.e. relaxation and sleep induction).
  3. Found a really basic program called Gnaural. It was designed to create binaural beats and allows very accurate control over sine waves. It's a standalone program so not nearly as convenient as using a plugin inside Logic, but it will probably do the trick. Thanks to all, and if anyone has any other great ideas for creating specific, accurate sine frequencies with fine automation control in Logic, please chime in.
  4. It would be at least 5 years ago. Could even be 8 years ago. Not sure I could find, install or run a version of Logic that's that old!
  5. No luck with MOscillator. Automated frequency changes jump up and down in audible steps. I presume this is because Logic's way of dealing with a wide range of possible values (i.e. 20 Hz to 20,000 Hz) is to divide them into a limited number of increments. If this is the case then the same problem will probably arise with all oscillator type plugins. Sigh.
  6. Good thinking Atlas007. Unfortunately in my case this still won't give me the level of control I need. For example, one of the things I sometimes use TestOsc for is to create binaural beats, which are comprised of two sine waves panned hard left and right, at very specific frequencies. I need to be able to modulate those frequencies within 0.1 Hz accuracy over long periods of time (anywhere from 10 min to an hour or more). I've been using Logic for 20 years and in the past I used TestOsc to achieve this, but at some stage the plugin changed so that automated frequency changes would move in steps, rather than a smooth transition. What I want to achieve would actually be very simple with a plugin that allows accurate frequency automation, and it was achievable in the past, but it looks like Logic can't do this anymore.
  7. I'd considered that, but unfortunately I need to be able to specify the exact frequencies within 1 Hz or smaller increments. For example, I might need to slide from exactly 110 Hz to 105 Hz. I could probably get close with EXS24 tones by fiddling around with pitch bending, but unfortunately this is one of those occasions where close enough is not good enough. (Still, I'll try this approach and see how close I can get). Being able to produce sine waves is not the problem. Being able to set and modulate their frequency accurately is. The simplicity of the TestOsc plugin is great because you can enter specific values into it. Where it falls down is in the big stepladder increments it applies to frequency changes. I wonder if there are any other frequency generating plugins that might offer more precise control?
  8. I want to automate the pitch of Logic's TestOsc plugin to create a smooth pitch sweep with a sine wave, but unfortunately TestOsc's pitch can only move in very chunky increments. For example, try automating a sweep from 300 Hz to 100 Hz over 30 seconds. You will hear the pitch jumping in 10 Hz increments until it reaches 200 Hz, and will then move in 5 Hz increments. For sound design purposes I need accurate, automatable control over the pitch of sine waves. Seems like an incredibly basic, fundamental task for any audio production software, but Logic has been unable to do this for years. Can anyone think of a workaround???
  9. Logic's T.O isn't capable of fine frequency adjustments and it can't accurately automate frequency adjustments. For example, between 100 and 200 Hz it can only create frequencies in 5 Hz increments. I understand the programming reasons behind this, but it's a big problem nonetheless. It is quite limiting in some sound design situations and it also means that the T.O cannot be used for accurately testing frequency response in an acoustic environment. Try this. Create a track with the T.O on it and try to set the frequency to 111 Hz. It's not possible with the mouse, but if you type the value directly into the T.O then it sticks...for the time being. Now open automation on that track and create another automation point so that the frequency will sweep from 111 Hz to 125 Hz. Done that? It all looks fine for now, but try to move the 111 Hz node left or right. The moment you do so it snaps to 115 Hz. Logic simply cannot produce that 111 Hz frequency. I do need to be able to create accurate oscillator frequency sweeps in my work, especially low frequency sweeps. At the moment the T.O just goes bump, bump, bump as it moves though those frequencies in big steps.
  10. I don't think this is fixed in 10.2. The problem is that Logic's T.O's only seems to be capable of moving in large frequency increments. i.e. Between 100 and 200 Hz it can only create frequencies in 5 Hz increments. I understand why this is the case, but this is actually quite limiting in some sound design situations. Try this. Create a track with the T.O on it and try to set the frequency to 111 Hz. It's not possible with the mouse, but if you type the value directly into the T.O then it sticks...for the time being. Now open automation on that track and create another automation point so that the frequency will sweep from 111 Hz to 125 Hz. Done that? It all looks fine for now, but try to move the 111 Hz node left or right. The moment you do so it snaps to 115 Hz. Logic simply cannot produce that 111 Hz frequency. I do need to be able to create accurate frequency sweeps in my work, and Logic 10.2 can't do that at the moment. It's actually worse now than it was in version 9.
  11. I'm so glad this has helped some people. I've had such trouble with it in the past and no-one ever seemed to have a solution for it. Just like angelonyc mentioned above, I used to take screenshots of projects that were affected by this problem and then reconstruct them from scratch as a last resort. I had literally taken screenshots of my latest project, was about to trash a weeks work and was midway through writing this thread when I discovered the "delete redundant automation points" function. After all these years it saved me at the absolute last moment.
  12. I've been using Logic since version 3, and the following problem has been an issue since version 6 at least. No one I know has ever solved it. Let's say you are mixing a project and you want to insert some space in the middle somewhere. So you select all the regions to the right of that area and move them as needed. This works fine for a little while, but behind the scenes, Logic is slowly developing a nasty problem that ends up causing it to become so slow that it's unusable. If you repeat this action of moving lots of regions at once, you might notice the spinning colour wheel of death for a few seconds as Logic figures out where to place all the regions and tries to move all the automation. The more you use this function of moving large amounts of regions the worse it gets. After a while, that spinning wheel will lock you up for 5 minutes before the regions actually move. If you get to this point, then even the most basic commands cause the spinning wheel of death. Moving a single region might take 20 seconds to complete. Revealing the automation on might take 10 seconds. Simply scrolling from one place to another - chug chug chug - takes forever. Lodging support requests has never yielded a solution. In forums, people suggest that your project is corrupted, and this might be true, but I've recently (finally) discovered the action that causes this problem in a repeatable way, which suggests a genuine bug. The action is moving all the regions after a certain point in your project, along with the automation. When a project comes to its knees like this, your project information can look really wacky. The one I'm working on now says that it has just 355 regions and 55 MILLION EVENTS, which is completely off the charts. *** I was just about to finish this post with a negative remark about how annoying this problem is, when all of a sudden, after 6+ years of struggling with this issue from time to time, I discovered the "Delete Redundant Automation Points" function. (Where is the facepalm emoticon - I really need it now). It fixed the problem. Holy cow. What an epic sense of relief. I thought I was going to have to re-mix an entire 30 minute orchestral performance. I decided to finish this post and publish it anyway, just in case this problem has someone else stumped. I know of a few people who will be just as relieved as I am that this is no longer a problem.
  13. Thanks for the info. Bugs I can live with in the knowledge that they'll be addressed some day.
  14. I use the capture recording function quite often to capture midi performances that I wasn't actually recording when I played them. In LP9 I could arm multiple instrument tracks to record simultaneously and Logic would capture my performance into a region and then add copies (aliases) of that region to all the other tracks I had armed. In LPX, I don't get separate regions on all the tracks I arm. All I get is a single region with multiple takes inside it. For example, if I arm 4 instrument tracks to record (so I can hear them all together while playing) and then play a performance that I like, hitting the "capture recording" button creates a single expandable region with 4 takes inside it. Three of the four takes will be empty, as I was not looping my performance as I played it. This just seems like weird behavior to me. Is this an update that I just don't understand properly yet, or a bug?
×
×
  • Create New...