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.

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.

  • Trying to get this "One" sound with Logic pro 8

    Hi everyone i spent like 2 hours last night trying to get this sound with Logic Pro 8 soft synths trying to find a sound exactly like or close to this sound: http://home.comcast.net/~tommykry/Weezer%20-%20Troublemaker.mp3
    The sound can be heard at 00:19 and through out the song, its like a low bass synth kind of sound that drifts down when its hit, like a portamento kind of thing. In live weezer videos the bass player is hitting a pad on a keyboard so i know its a key sound not a bass guitar slide. ive heard this sound in trance and techno songs as well. I have Sonar 8 and pro tools 8 as well and can look there if i have too, also have an Access viress Ti, But im trying to do this all in Logic. Like i said i played around for like more than 2 hours going through most of all the Logic synths, patch after patch trying to find something close i could tweak, so if anyone has more experience with The Soft synths in Logic Pro 8 and can steer me in the right direction i would be greatful.
    Thanks
    Tommy

    In live weezer videos the bass player is hitting a pad on a keyboard so i know its a key sound not a bass guitar slide.
    He could just be triggering a bass slide sample...
    It's some kind of bass sound that bends down, in a similar style to what a bass player might do. Whether it's a real bass or a synth is difficult to say (and probably doesn't matter a great deal), but in any case it's certainly compressed, and grunged up dirty with some amp sim or distortion...
    Try that route...

  • 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.

  • 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

  • Problem with saving optimized PDF 900dpi, image is partially repeated... is this a bug in Acrobat Pro 10.1.10?

    I try to save a bigformat PDF file (1.4 Gb) with save optimize PDF. Hereby I send some screendumps to make this stuf clear. See screen after at the right; Is this problem a bug in Acrobat or due to Hardware problems? I use the newest Mac Pro with 32 Gb Ram.
    txs for rsponce!! grz. Paul

    Hello Paul,
    I am unable to replicate the issue.
    I am send you a Private message to share the sample file with me.
    Please share your file along with Steps to Reproduce the issue.
    Regards,
    Anoop

  • 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.

  • 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.

  • 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

  • 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.

  • I am having problems to run logic pro 9, there is an error display that says I need to set bonjour and that this app serial number has been used by another red user,  could anybody guide me?

    I am having problems to run logic pro 9, there is an error display that says I need to set bonjour and that this app serial number has been used by another red user,  could anybody guide me? actually, my computer can't start  since three days ago, could it be the same problem?

    Logic is the APPlication (program, app) that you are having the problem with.
    Logic Pro can take advantage of other computers on your local (home or work) network to help it do "heavy lifting" data chores by using Bonjour and a feature called Nodes.   It seems that Logic is attempting to find and connect to another machine on your network.
    Do you have Logic installed on another computer there?  That may be the source of the confilict.
    You might want to post this question in the Logic Pro Community.
    Be sure to indicate the version of Logic Pro that you are using.  I'm sure the folks there can help you out.

  • Logic Pro 9 (9.0.0).   Message You can't use this version of the application Logic Pro 9 with this version of Mac OS X You have Logic Pro 9 9.0.0.   I have been told that I can use the Logic Pro 9.1.4 Update (.dmg) which you can download from Apple Logic

    Since upgrading to lion, I can't use Logic pro, hope someone can help.  thank you
    Logic Pro 9 (9.0.0).
    Message
    You can't use this version of the application Logic Pro 9 with this version of Mac OS X
    You have Logic Pro 9 9.0.0.
    I have been told that I can use the Logic Pro 9.1.8 Update (.dmg) which you can download from Apple Logic Support, although when I try to upgrade my I get this message:
    An eligible Logic Pro version was not found in the Applications folder. This update requires Logic Pro version 9.0 or higher.

    Since upgrading to lion, I can't use Logic pro, hope someone can help.  thank you
    Logic Pro 9 (9.0.0).
    Message
    You can't use this version of the application Logic Pro 9 with this version of Mac OS X
    You have Logic Pro 9 9.0.0.
    I have been told that I can use the Logic Pro 9.1.8 Update (.dmg) which you can download from Apple Logic Support, although when I try to upgrade my I get this message:
    An eligible Logic Pro version was not found in the Applications folder. This update requires Logic Pro version 9.0 or higher.

  • 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?

  • Yosemite 10.10.1 with Logic pro X 10.0.7

    Hello guys. i just wanted to start a small conversation according to the performance of logic pro x on the latest macbook pro's (mid-2014)
    i am on a 13macbook pro running yosemite 10.10.1 and logic pro x 10.0.7...
    Everything works fine and smoothly but the there is just one thing that freaks me out. the level meters gets very laggy sometimes. for no reason.(mostly when i add new audio files but many times for no reason) . all i have to do is to make any activity in the logic's environment to "wake them up" (like opening the mixer or changing the selected channel)and then it may appear again.
    i have tried everything from clean installing to various turnarounds i found on the web . but nothing.
    i think that it might be a bug or method that logic use to spend less graphics. i don't know. i wondered if anyone else has that issue. its has nothing to do with cpu,heavy projects,etc. i have tested it in all the cases.
    so what do you think? have experienced this issue before?

    Logic Pro X + Yosemite  (and even more so + Retina) is a recipe for less performance...... at this current time...
    The graphical 'lagging' you notice is an example of this reduction in performance and has been well reported here and elsewhere.
    It's not the only affect in this drop in performance however as overall Logic performs less well with Yosemite especially with Retina Macs...
    A quick test using the Logic Benchmark test shows that particular combination of OS X and Logic Pro X indicates a reduction of at least 15% in general performance at this time... and in many cases it rises to about 30% ... with projects that ran without issue under 10.9.4 having sporadic 'Overload' issues under 10.10.1
    Currently I don't recommend installing Yosemite on any system where the use of Logic is important..... but instead, to stick with 10.9.4/5 for the time being until such issues are resolved.
    Cheers..
    Nigel

  • Define Custom Bank Messages... crashes Logic Pro X 10.0.5

    Hi all,
    Having a devil of a time setting up patch names for my Proteus 2000 in Logic Pro X 10.0.5. The Proteus 2000 requires a custom bank message format to access all of its banks over MIDI, so in the MIDI Environment I select its multi-instrument and then Options -> Define Custom Bank Messages.... EVERY time I do this Logic crashes, the custom bank messages window never opens. (The same thing happens if I right-click the multi-instrument and select Define Custom Bank Messages... from the contextual menu.) (Partial crash log below.)
    I have tried switching off my MIDI modules and disconnecting my MIDI interface, just to see if it's a hardware issue, but to no avail. I have got to this window before, in an earlier version of Logic Pro X, so I'm wondering if it's a bug with 10.0.5. Any more suggestions of things to try?
    (I'm running a 2012 Mac Mini with Mac OS X 10.8.5, Logic Pro X 10.0.5, and a Cakewalk UM-2G MIDI interface.)
    Process:         Logic Pro X [419]
    Path:            /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X
    Identifier:      com.apple.logic10
    Version:         10.0.5 (3130.19)
    Build Info:      MALogic-3130019000000000~1
    App Item ID:     634148309
    App External ID: 86112663
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [153]
    User ID:         501
    Date/Time:       2013-12-28 12:37:37.838 +0000
    OS Version:      Mac OS X 10.8.5 (12F45)
    Report Version:  10
    Interval Since Last Report:          4162 sec
    Crashes Since Last Report:           8
    Per-App Interval Since Last Report:  2333 sec
    Per-App Crashes Since Last Report:   8
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000025c

    You are not the only one. I'm trying to Define Custom Bank Messages for my Yamaha Motif-Rack ES and am getting the same problem. To me this is a MAJOR bug!!! All of my tone modules are useless with this program at this point. grrr
    Process:         Logic Pro X [309]
    Path:            /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X
    Identifier:      com.apple.logic10
    Version:         10.0.5 (3130.19)
    Build Info:      MALogic-3130019000000000~1
    App Item ID:     634148309
    App External ID: 86112663
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [147]
    User ID:         501
    Date/Time:       2014-01-09 19:11:09.243 -0600
    OS Version:      Mac OS X 10.8.5 (12F45)
    Report Version:  10
    Do I dare not buy anymore Apple backed DAW software?? They is an essential part of functionality for someone who uses external devices.

Maybe you are looking for