Weird auto punch bug in Logic Pro X

I set up for an auto punch. Hit record and the auto punch works fine, however it creates what looks like a midi punch on an adjacent track, that wasn't even selected. I can delete this weird midi punch and reconnect the audio file and the adjacent track, so nothing is lost. But this is not right and a bit of a hassle.
I'm running OS 10.8 on a dedicated Mac Mini, with nothing else running. This Mac Mini is totally dedicated for the recording studio.
I've cleaned permissions, and it seems to do better for a while, but then, randomly it will reoccur.
I'm not seeing this anomaly anywhere else in the Community.
Any advise?

I can actually recreate this behaviour.
1. Create two audio tracks with identical inputs
2. Set a punch in and out point (1 bar)
crucial: 3. Select the first track and record arm the second track
4. Set the playhead before the punch-in point, hit record and play some random MIDI
I got this:
However, when I disarm audio 4, it's as it should be: audio gets recorded on audio 3, and the MIDI does not get recorded at all. So it seems it's a matter of making sure no unselected track is armed.

Similar Messages

  • Could not load Module... A known bug in Logic Pro 7.3 with Snow Leopard?

    I know this issue has been discussed before, but on my brand new MacBook Pro it's still an issue, so can someone please help me out with this?
    Here goes:
    Loading Logic 7.2.3 in Snow Leopard:
    The previously selected audio interface is not available
    The built-in audio inputs and outputs of the computer will be used instead for this session.
    <ok>
    Could not load Module "FW-1884" (-43)
    <cancel>
    Could not load Module "HUI" (-43)
    <cancel>
    Could not load Module "Logic Control" (-43)
    <cancel>
    Could not load Module "TranzPort" (-43)
    <cancel>
    Logic loads, and everything seems to work just fine.
    <selecting a plugin ---> Bass Amp>
    CoreAudio:
    Resource not found. (-10109)
    This happens no matter which plugin I choose - Bass Amp, EXS 24, ES1 etc…
    <Continue>
    The plugin loads, and works, but the display is in "Controls" Mode. Trying to switch to "Editor" Mode resulsts in the same error as above.
    Is there anyone out there who knows why this happens?
    Thanks
    Warbler

    Given that so many things are funky, I'd suspect that one or both of the following is occurring:
    1) Your Logic Pro application/installation is corrupt. Logic is failing loading control surface modules which should be in the application bundle. Reinstall.
    2) You have an incompatibility between Logic and the necessary system frameworks because Logic is too old/your system/OS is too new. You can't expect to hold back on an old version of an application and press forward with the OS (or vice versa) forever - eventually, something will break, and you'll have a large leap to get things working again.
    It's probably better to stay on the update train unless there is a specific reason to get off, or at least, freeze your computer/OS version at the same tim as you freeze your application.

  • Is this a bug in Logic Pro?

    I use a MAC G5 with Logic Pro 7.2.1 - I play a Korg Triton through a Motu Micro Express Midi interface to access the sounds in Logic as well as my Ivory Grand Piano Plug In. A Mackie Control Universal is my interface.
    Ever since I got geared up last March I noticed that when I changed files (song projects) from client to client during the course of the day that my Ivory track would show up transposed a step down. Not limited to the Ivory track sometimes a Bass track, maybe a Bass from Apples Jam Packs, would be transposed.
    I never have messed with the transposition of any Logic track, I don't even know how to do that, but I have transposed a song or two in the Ivory Grand Piano Plug In Window.
    It was my understanding that once you close the Logic file that it would remember the parameters of that file the next time you opened it.
    Well something very telling happened yesterday. In the morning I worked on a clients song. It was a song that early on I may have transposed the Ivory track to help the singer. I closed out of that file and when I brought up a file of another client's work their Ivory track and their Bass track were transposed down a step. Keep in mind that the day before that client's track played down perfectly in the right key and I'm sure I closed the file with it in the right key. And obviously all the audio tracks remained in the original correct key.
    Here's the kicker. Fearing that I would mess up my client's song I quickly closed the file without saving any changes and completely closed Logic. When I rebooted Logic Pro and reopened their file the Ivory Grand piano track and the Logic Bass track were in key again!
    This has happened quite a few times to me but only now have I realized that completely closing down Logic fixes the problem. ie - If I just ping pong from one file to the next without closing Logic down I have this transposing problem on the Midi instrument tracks.
    I'd like to remedy this because it's time consuming to close down Logic between every client. Any ideas? Thanks

    InnoMan, I experience frequent problems with Logic Pro that require quitting and relaunching the application. I'd say in a typical 3-hour session working with Logic, I end up doing this about 4 or 5 times. The glitches I experience sometimes involve transposition of notes.
    Tell me, when your track gets transposed, does it actually appear transposed, or does it just sound that way? In other words, does the region become magically set to transpose (say, set to +4 or something)? Or, when you go into the region, have the notes been moved?
    If neither of these things is happening, but the track just sounds wrong, then that's a problem I've been having. I have a bass line that repeats throughout a track, and it's all in key (A). Recently, I moved that baseline further along in the track. I changed nothing. The first time I listened to it, it all sounded fine. Every subsequent listening, however, sounded like the notes had been transposed to a completely different key. The region had not been transposed, and the notes in the region are still in A. However, it sounds completely off.
    I tried completely recreating the region, instead of using a copy from earlier in the track. That worked on the first listen, however again, subsequent listenings and the notes are off.
    I'm guessing that upgrading to Logic 7.2.1 might make a difference (I'm using 7.1.1). However, Apple wants me to give them $50 for this experiment, and given Logic's reliability so far (pretty bad), I'm loathe to give Apple more money for this thing.
    Anyhow, let me know your experience. Thanks.

  • I have found a bug in Logic Pro 10.0.3.

    In the Environment Window, go to "Clicks & Ports" & create a new object.
    Go to Fader/Specials/Cable Switcher.
    In the parameter window- Set the Style to "As Text", then change the Range to anything other then 0-127.
    Instant crash every time.
    Also, if you can double click on the cable switcher to edit it, it is full of random symbols and text.
    Any help?
    Thanks,
    Rychard

    You can do that from within the app, under menu Logic Pro X;
    Regards

  • An Open Letter to Apple About Bug-Ridden Logic Pro 7.1.1

    The bile rises in my throat as I write this, as it has all day struggling with the innumerable bugs in Logic. That's right, not pilot error, but de facto B U G S. Dangerous bugs.
    Today's tale is about 2/4 measures. In the score I'm writing I have a 2/4 measure. Big deal, right? Problem is, I've had to re-insert this ******* 2/4 measure about 4 dozen times today, because every time I undo an edit -- one that occurs many editing-steps after I inserted the 2/4 time signature -- the time signature disappears. Oh yes, and this signature can't be retrieved with undo/redo.
    This bug is akin to the one I reported previously where, after inserting numerous markers one after the other, and then undoing the next edit, all of the markers disappear (and can't be retrieved with undo/redo).
    Sound familiar? See a pattern forming?
    Two days ago I was working on a record for a high-profile artist. The question arose as to why, at one point in the track, the click's loud downbeat click was playing on the 3 and the soft clicks on 1, 2, and 4. The answer? Same bug! There was a 2/4 measure in that piece too, and when I undid an edit, the 2/4 measure disappeared. You want to talk about embarrassing? Want to talk about time-wasting effort?
    How wonderful for us professional Logic users that my "For Apple Employees Only" thread -- which asked that someone from Apple/Logic respond to the various problems that people were posting here -- was locked. Talk about the exactly wrong response from Apple/Logic. Couldn't be more wrong in your approach if you tried harder.
    So, Apple/Logic. What are you going to do about the plethora of other bugs that riddle this otherwise grand program? What are you going to do about your severe lack-of-communication problem? After spending $1K on your software, we deserve to know.

    William. Sorry to hear about your troubles. At times I've been tempted at times to go back to 4.8.1! In fact I'm going to be doing just that when I do a live TV performance next week where the artist I'm working with is performing live to a few sequenced tracks.
    I can imagine the difficulties that programmers may have to face in fixing bugs in a complex program such as Logic, but it's a situation that doesn't elicit my empathy for them. That's their job.
    I guess I could sum it up in the form of a quasi-parable: a composer gets a gig to write a score in the style of Bach, but he's much more well-versed with Schoenberg. Despite the composer's assurances that he can do the job, the music ends up sounding like some strange hybrid of the two. It would be quite understandable if the client were upset because he was promised an authentic-sounding, baroque score. No one feels bad for the composer, because he took a job that he wasn't qualified to do, and ultimately didn't deliver what he promised.
    Similarly, I feel hoodwinked by the promise of satisfaction implicit in the notion of purchasing the best that Apple has to offer, i.e., the most powerful computer (which my dp G5 was at the time), lastet OS, and expensive software published under Apple's aegis.
    I agree with you that there's incompetence and irresponsibility at play here. To the latter point, any decent beta tester would have discovered some of the more basic bugs in Logic 7.1.1. And here we are, vis a vis this forum, essentially publically beta-testing Logic's latest offering with zero feedback from the company, despite the fact that our respective problems are absolutely tangible.
    To the former point, I'm wondering if it's the programmers themselves who are not up to the task here, if it's management that have fallen asleep at the wheel, or some combination of the two.
    I've learned that as of last year a fellow named Bob Hunt was the product manager for Logic. If he's still currently the PM, and the feedback and problem-related posts here haven't been enough to prompt him (or someone in an official capacity) to publically address our respective issues, then I'd venture to guess that there's a problem somewhere at the top.

  • Anyone using Antares Auto-Tune 5 with Logic Pro 8 on a Mac Intel?

    I just bought the upgrade from Auto-Tune 4 to Auto-Tune 5 since v4 didn't work with the Intel machines, and I'm using a Mac Pro.
    After trying to tune one simple part of one song, I'm going nuts. The plug-in is full of bugs, it seems -- mostly in graphical mode. Is anyone else either successfully using this set-up or experiencing major bugs with it?

    I'm thinking it's an Intel thing.
    When I try to use the various tools in the graphical view, the plug-in will just basically stop responding. I can't close out the plug-in window, and sometimes the "options" window of AT 5 will pop up for no reason and freeze. Its "cancel" and "OK" buttons are non-functioning at that point.
    I've hard to force quit Logic a few times now, which pains me to say. Not to mention that it's setting my project back.
    Antares doesn't have a forum, and I can't find anything else about this apparent anomaly online anywhere.
    Unrelated: I've had problems with Drumagog in LP8 as well. If I try to drag the Drumagog pop-up window around the screen, the only thing that moves is the semi-transparent LP 8 "container". The actual Drumagog window stays put as the LP 8 window that frames the Drumagog window moves about. Very strange.

  • Bug in Logic Pro?

    Hello, I have experienced a strange behaviour. Please try the following things:
    1. Create a project which uses Space-Designer Plugin for a Audio Track
    2. Save Project and Close Logic
    3. Start Logic again and open the project
    4. Bounce the project BEFORE doing anything else, espacially don't start playback (PCM, Offline, whole project)
    If I do that, the bounced file is rendered without the Space-Designer effect. It seems, that the Space-Designer is only rendered, if playback has been started once.
    Do you have the same problem?
    Thank you very much,
    Tobias

    Tobias wrote:
    these things you describe I have not experienced till
    now - but it doesn't make things better. To we have
    to accept these bugs? I have paid a lot of money for
    the software... the least thing is to try to "report"
    the bug.
    True, acknowledging the bugs doesn't make the situation any better in the immediate. But there are many benefits to posts such as yours in bringing the buggy/errant behaviors to light; I strongly believe that as important as it is for people to know how the program works, it's equally important for them to be made aware of the ways in which it is broken, unpredictable, or otherwise buggy. In this way, people can avoid invoking features or otherwise using the program in ways that are known to cause problems.
    I would like to suggest that you not only file a bug report at the Logic Feedback webpage, but also post your bug on the bug report/workaround section of www.logicprohelp.com
    You wrote, "we have to accept these bugs?" In a sense, yes, because Apple/Logic does not often release patches or bug-fixes, even for long-standing yet minor bugs. Assuming that your problem is indeed a problem and not pilot error, about the only thing you can do is make both users and the company aware of the problem and wait/hope for a fix.

  • How to save kontakt sample files in Logic Pro X project?

    Hi,
    I'm using Kontakt (Komplete, Native Instruments) as my samples for my midi in Logic Pro X, and my sample libraries are stored in an external hard drive which I bring around.
    I need to send my Logic file over to another computer which will not have my hard drive that contains my sample libraries.
    Is there a way to save my Kontakt Sample midi files together with Logic's folder, so when I open Logic without my ext Hard Drive, the midi can still be read?
    I tried clicking Save As --> Organize my project as a "Folder", and ticked EVERYTHING --- Audio Files, EXS instruments and samples, Ultrabeat samples, Space Designer impulse responses, Movie file, Include Apple Sound Library Content.
    But when I unplugged my external hard drive (which my sample files are stored), and clicked open that logic file which i saved, windows pop up saying it cannot locate my samples.
    Is this a bug in Logic Pro X, or am I doing something wrong?
    Or is it totally not possible to copy sample files over?

    skylurker wrote:
    I tried clicking Save As --> Organize my project as a "Folder", and ticked EVERYTHING --- Audio Files, EXS instruments and samples, Ultrabeat samples, Space Designer impulse responses, Movie file, Include Apple Sound Library Content.
    <snip>
    Or is it totally not possible to copy sample files over?
    Hi
    Logic will not copy over any 3rd party samples etc. If you really need to, you would need to copy the appropriate libraries manually, though with Kontakt, some libraries would need to be re-authorised.
    CCT

  • Transposition errors in logic pro

    I place the following events in the chord track: at beginning of measure 1 E7, at beginning of measure 5 A7. If I then select a MIDI bass loop while playing the track, it palys the loop along with the track and makes the right chord change to an A7 pattern at measure 5. But if I pick up the loop and drop it into the arrange area at measure 5, it plays the pattern in D, not A. What gives? Isn't this a bug? I can overcome this by repeating the loop from the E7 area and selecting the "as a clone" option, in which case it transposes correctly, but I shouldn't have to do it that way. Why doesn't it transpose correctly when you just drop it in?

    This is definitely a bug in Logic Pro 9. Do the following experiment:
    Create an empty project, key of C. Place an F anywhere in the chord track after the first measure. Drop a MIDI loop in place where the F chord appears. The loop will sound in B flat. Check the score or piano roll: it is written in B flat (the bread and butter bass loop number 1 is good for this, as it just repeats the root note). Now delete that and put an F chord at beat 1, measure 1. Drop a MIDI loop there and it will sound in F as it should. Any MIDI loop dropped in after the first measure will transpose twice as many half steps as it should (according to what's written in the chord track) from the root note. For example in the key of C, a C# after the first measure in the chord track will produce a transposition to D in a dropped in loop. This error is consistent and occurs in all keys, and only on MIDI loops, not audio. It is an obvious bug, probably fixable by changing a few lines of code. Does Apple fix these kinds of bugs in their software, and where should I reprt it, other than here?

  • Logic pro x export audio to movie

    Hi!
    I'm running into problems when exporting a quicktime movie from Logic Pro X with a cue. The weird thing is, on my computer, the exported video plays back properly (outside of logic) with the music, and everything is fine and well – but when I send that file to the director, there is no music in it!! On her computer it only has the films SFX track. I saw other threads about trouble actually getting the audio to export, but I think I'm doing that fine.
    Here's what I've been doing:
    Bounce all music together with the film's audio track, so that ALL the audio is on one track.
    Click export audio to movie, select the track.
    Am I missing something? This is super weird.
    I'm using Logic Pro X, on Yosemite 10.10.1
    Thanks in advance!
    Mike

    First of all, did you listen back to the QUickTIme file after the bounce? Are you saying that you hear you score and when the director plays "the same" quicklime file" she hears only the SFX? That would be strange, unless she opened the quicktime file and messed around in the properties window.
    About the Movie export. You don't have to bounce your music fist. Whatever your state is at the moment in your Project that is what you "Export to video". There is only one  (often overlooked) step. After you click ok in the Save Dialog, there is one extra "Choose tracks to export" window coming up (see screenshot). It shows you the audio track(s) that are embedded in the original quicktime file. LPX 10.1 now has a new checkbook to make it clear:
    Check: You include the original audio track with your mix
    Unchecked: You don't include the embedded audio track and only your  Logic mix will end up to be the new audio track of the new quicktime file.
    Hope that helps
    Edgar Rothermich
    http://DingDingMusic.com/Manuals/
    'I may receive some form of compensation, financial or otherwise, from my recommendation or link.'

  • In logic Pro, when I open up an audio track and load an audio file, there is no sound. I will finally get a sound out of one of the audio tracks after opening at least 5 of them alternately. Is anyone familiar with this kind of bug? It's really frustratin

    In logic Pro, when I open up an audio track or software track and load an audio file/loop or software file loop, there is no sound. I will finally get a sound out of one of the audio or software tracks after opening at least 5 of them alternately. Is anyone familiar with this kind of bug? It's really frustrating as this takes much time to complete work.
    os x, Mac OS X (10.6)

    I'm not sure I follow your words Fuzzynormal. You've helped by offering the insight that my issue in Logic Pro 9 is not a bug but a feature. But fell short of enlightenment by being a judge of character and of how one should interact in this forum. You insinuate that I haven't tried to solve the issue on my own when in fact I have. These forums are always my last resort. You further suggest that I am complaining. This is not a complaint. It is a genuine issue that I cannot figure out. Then you think that Brazeca is holding my hand and being a nice guy. Brazeca is helping people like me who might not be as adept at using Logic Pro as probably you are.This community forum was established to raise questions, answers and dicussion to help Apple's customers better undertand their operating systems and related issues. You are doing a disservice by not contributing positively and by trying to make this forum what you want it to be. You may have all the time in the world to try figuring out stuff but we are not all like you. We all have different schedules and different levels of understanding. And that is what this forum is for - to help people move forward. If you can't contribute positively then keep silent. And by the way, you say to "read the words that are printed down to explain to you how that works" what words are you talking about? Why don't you be of some help instead of trying to own this forum. 

  • When i editing in the piano roll windows, after 10 at 20 editing steps my logic pro 9 crashed down. Every time. Is this a bug?

    When i editing in the piano roll windows, after 10 at 20 editing steps my logic pro 9 crashed down. Every time. Is this a bug?

    Maybe find a local who can translate for you. I don't know what to tell you for dealing in another country for service on your computer.
    I can offer you something you can do if you want to give it a try. You'll need a backup of your data in your Home folder because you need to erase the drive. You'll also need a solid, preferably fast, internet connection.
    Install or Reinstall Lion/Mountain Lion from Scratch
    Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
    Boot to the Recovery HD:
    Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Erase the hard drive:
      1. Select Disk Utility from the main menu and click on the Continue button.
      2. After DU loads select your startup volume (usually Macintosh HD) from the
          left side list. Click on the Erase tab in the DU main window.
      3. Set the format type to Mac OS Extended (Journaled.) Optionally, click on
            the Security button and set the Zero Data option to one-pass. Click on
          the Erase button and wait until the process has completed.
      4. Quit DU and return to the main menu.
    Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Install button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible
                because it is three times faster than wireless.

  • Logic Pro 5.1 ch plugin subwoofer channel bug report

    hello,
    I had found out that Native Instruments absynth 5.1 ch synthesize sofware , which in stand alone mode
    outputs the subwoofer channel audio properly, does not output subwoofer channel audio in Logig Pro surround
    plugin in 64 bit mode.
    I contacted  Native Instruments about this and after a certain time, they say that they did deeper invstigation
    and found out that it is the Logic bug.
    I just don't know how to bug report to the apple, so I put this here.
    Please confirm and fix it.

    The crashed thread (7) mentions logic's preferences file. (com.apple.logic.pro). Drag it to the desktop (so you can reclaim you key commands if it works) and restart logic. Logic will create a new preferences file. Worth a try..

  • Logic Pro (and Garage Band) guitar bug.

    This is a rather irritating bug that happens constantly on my set up. I can play guitar for a couple of minutes then the sound cuts out but then plays after about a three second delay. This happens in both Logic Pro 9 and Garage band but not in Ableton Live or other apps.
    At first I thought it was an interface problem (UA-101) till everything worked without a hitch in Ableton Live. The interface lights also show no delay. I've got a new MacBook pro with Leopard on it with latest versions of Logic and Garage band.
    Anyone else seen this before or know of others that have had this problem. Any suggestions of what I could do to fix it?

    Well I dont get this but I use Apogee Duet, so there could be the difference. Process buffer range could make some difference, set it to low in Preferences/Audio. The other obvious thing is to check the buffer size in preferences is set as low as possible.

  • Logic Pro X - workaround bugs

    Hi!
    Logic Pro X is still a new release (10.0.3 when writing this) and there will of cource be updates to fix bugs. But meanwhile, why don´t share some workarounds for bugs that occur?
    My first tip which for problems with recording audio is to bounce what you have and go back into Logic Pro 9 and do the recording and then cut/edit all the takes before taking it back to Logic Pro X and continue to work.
    Does anyone else having problems with recording? My LPX just quits after some time of recording when I hit the rec-button.
    My first workaround for this was to use the command "Save a copy as..." since it seems to work some more minutes before crashing.
    It clears unused memory in the file in some way I think.
    Before saving as a copy the file is always about 100Mb bigger.
    Any more workarounds?

    Does anyone else having problems with recording? My LPX just quits after some time of recording when I hit the rec-button.
    No, not here.. I finished a 10 track  1 hour live recording this weekend without issue..
    If Logic just quits, do you get an error msg, a crash log or failing that look in your console logs to see what is causing the problem.. and post up what you find/see

Maybe you are looking for