maticc

You theory is debunked in my case, because the behavior isn't consistent. It will often be the same or similar spot where it occurs, but not always. Sometimes it plays fine, and then, without no change to the midi etc, it will reveal the issue. I'm using extremely simple midi as test examples. Also, it's not just "turning off when it should be on" it also doesn't trigger (on) when it should sometimes -- going from a value of 0 to 127 without effect. Then other times, that same spot does engage the sustain, as it should.

Hi, I'm having this issue (always have, I feel like.. not something new) Currently using one of NI's piano patches, which has a default polyphony of 120 .. and I'm using nowhere near that. Sustain off, often at the same spot. No reason nor sign of why it should do that. Making me super annoyed Logic is current (10.3.2) as is Kontakt (5.7.2).. But this has been a long standing issue for me; enough that I almost consciously avoid recording piano stuff because I know it's going to end in frustration

After I updating to 10.3.1, things were fine in Pitch and Time Machine, and a week later, I faced a bug for several days that rendered it useless. No matter what I entered in the output tempo (or transpose destination), the plugin would substitute it with 300 and something BPM! I had to use 3rd party software to do a Time(with Pitch) change. Random as it came, the bug left. I've been using this part of Logic without a hitch now for weeks. And BOOM! It's back. This time, a file with source tempo of 70bpm will jump to 280bpm no matter what I enter. I am trying to do a very minimal time stretch, mostly just pitch it up by 4 semitones and use Time Stretch to ensure a rounded BPM number. But no way to do it in here until this bug decides to "leave" again. Anyone familiar with this wierdness? Last time it persisted over numerous days, restarts, and across all sessions (including ones that works just days prior). No idea what makes it come or go.

Thank you very much! Exactly right. I hoped and expected it was a settings thing, but couldn't find it prior to your help. Cheers!

I am trying to record DI guitar. When arm an audio track, I hear my guitar as expected. However, immediately upon hitting Play on the transport, the record-ready audio track silences itself. I see the input meter moving to my playing, but you here nothing. I've tried on several session file (including a new empty one, with "Initialized Preferences" for all of Logic). Same trouble. All the other tracks play fine, but I get no sound from the any of the record ready tracks. I've just installed Logic 9 and latest updates on my iMac 27" (2010 model). Everything is working fine on my current 9.1.3 MacBookPro installation, and also in previous years setups (been a Logic user since v5) Another thing I noticed, which may be related (and is pissing me off!) I can't arm an audio track while the song is playing. On my other comp (and again, over the years) this has never been a problem. You might here a glitch in the output, but you can certainly engage the Record Ready button on a track during playback. Not anymore. Can't engage or disengage the 'R' button without stopping playback first. Sounds like these two things are related, but the first issue has me stopped dead in my tracks.

Thanks! Now, forgive me, but how to do access and use the floating prelisten window? I am aware of the prelisten channel (audio 256) but I have never known it to behave as you show in the screen shot. Please help me understand.. I didn't find relevant info via Google

@louis, That explains why I thought I'd seen that before. Unfortunately, that is not a fix for me.. I want to be able to browse via Folder structure on my hard drive or external drive that may be loaded on the fly This would be down via the "Browser" pane, not the "Loops" pane, which limits you because: you have to load all loops into it first and then you can only search via name or tags.. which will not work for my purposes most of the time.

louis, thanks so much for posting the pic (with good amount of inserts) one last clarification: is that filling the whole screen then, with the Dock on auto-hide mode? or is the dock also visible below that (that would be hard to believe haha) thx!

Hi, I am about to get a laptop to go mobile.. I'd prefer to get a 15" (to save some money) But I really want to know, how much of the Inspector side by is visible if Logic is full screen (with room for the doc) See attached picture.. 15.4" MBP owners, can you see the whole inspector? Can you at least set the top most insert? If the screen is not large enough to see the inserts of the currently selected track, that alone may push me to get a 17" Also, my eyes are not great for distance -- so increasing resolution is not always the best answer :/ Thanks! Inspector on the left side is not fully viewable here, but at least the top most Insert can be viewed/clicked

I am going nuts having to preview in Finder, etc. I don't always want to hear a loop shifted to the tempo and key of my song file! And some situations are just plain stupid, for example: You song file is 140bpm, and you preview a percussion loop that is 70bpm (exactly half time). It fits perfectly as is.. yet Logic shifts up to an ridiculous double speed!? I've seen other people frustrated by this as well.. and sometimes the replies dismiss it as a problem, but it is certainly a problem. We need preview options! I really hope this happens on the next upgrade. EDIT TO CLARIFY: I want to be able to do this via the Brower panel, which lets me browse through files on my hard drive. Not the "Loops" pane, which requires loops to have been loaded to Logic and limits the ways in which they can be searched/browsed

Thanks for this! One problem for me: I copy the automation from one instance of a plugin, to an another instance of essentially the same plugin, next insert down on the same track. Automating the same parameter (Wah pedal).. On the new copy, it shows the automation, but each "point" that usually shows a value, says "unused" and the automation won't be acknowledge by the plugin. Now, funny thing.. I delete the old instance of the plugin (and clear it's automation).. then I move (cmd-drag) the new instance into that insert spot. It moves the associated automation, and "refreshes" itself or something and now works (and shows number values instead of "unused" Anyone care to comment on what's happening here and how to make it work as expected without the extra steps? In this scenario, I was updating a song with instance of Guitar Rig 3 to Guitar Rig 4 .. theoretically this shift automation feature should work perfectly for this job, but it gave me a small headache.

Yup, my sig has changed in the 10 months since I originally replied to your post. But the forum guidelinesare still alive and well. Uh, no... To do what you want to do, create a new blank region (using the pencil tool) for which the L and R edges completely surround the automation on the aux track. With your automation prefs set to "always" or "ask", OPT-drag that region to the new location. Of course, you have to have the aux assigned to a track in the arrange page and have automation view enabled. Well, you indirectly helped me fix the problem. By forcing me to check if it's decided to work yet.. and in my current config of Logic 9.1.1, it has begun to work as it did previous to my Logic 9 upgrade. If you read my first post, I describe exactly what you suggest..drawing and empty region on the track, and copying it ("have automation view enabled" is not necessary). What I was facing was a bug, but wasn't sure at the time... I always did this up technique to a certain point, and in Logic 9.. it stopped working for me. I got so frustrated, I stopped trying. Until now (I'd switched to copying it within the automation view) Thanks for the help.. I wish I'd written more articulately in my first post, and you would've seen I was dealing with a bug in a procedure I was accustomed to doing in previous (no bugged) versions. Interesting that this worked for others in Logic 9.0, are you sure?

Thanks, this is not what I was hoping for. I know all the basics of editing within the automation lane. I want to copy the automation as part of a region (midi or audio) when it move or copy it in regular track in the arrange. As you know (unless you choose to turn it off) when you move a region, Logic asks "Do you want to move the automation?" If you choose yet, it goes with the region being moved... assuming you're on an audio track or MIDI track. Why can't I treat the automation on Aux tracks like this? Instead I must edit just as you suggest, even though Logic acts like it will move it (if I put an empty region there, and duplicate it with option-drag, Logic asks if I want to copy it.. but when I say yes, it messes it up and doesn't put it on the right track).. ski, There is no longer such a link in your sig. I'm guessing #5 is some kind of posting rule, rather than a direct answer to my Q. I am happy to oblige if you would kindly direct me to that link. But I think maybe my question has been interpreted as a "damn, this newbie didn't read the manual" -- which is NOT the case. This is a unique question issue imo.

So glad they fixed that bug where Kontakt randomly re-loads it's instruments (especially when opening large sessions, or deleting unused tracks in the arrange) And the detailed Release Notes is very much appreciated, thank you for that Apple. Don't stop that pratice please.

Say I'm flying the chorus around to a few spots in the song, and I want to use the same automation.. However, the automation I want to copy is on a buss (aux)... What I used to do, was draw in a blank region (Logic 8) and I could copy that, and it would pull the automation with it (all automations tracks, of course) I Logic 9.0.1 when I try this, it copies the region when I option-drag it, but instead it creates it on a new copy of the buss track at the bottom of my arrange window.. and it doesn't copy the automation data What's your trick for this? Must be a common thing with and obvious way to do it that I'm missing.. EDIT: Technically it's an Aux track, which routes to a buss..this is how Logic sets it up in 8 and 9 (very handy) previous versions just made a buss by default (and you couldn't add sends etc)