Electri6ity Midi Files Download
Ivy Auteri
Logic X 10.0.7 on Yosemite 10.10.1. I had about six separate regions on one software instrument track. Two of them, when bounced, were then out of key on the resulting audio track. Bouncing the entire project or just the region had same result. I duplicated the whole midi track and bounced it in one piece and the areas out of key remained in the resulting audio file. So I then started bouncing each region separately and was somehow eventually able to get all the regions bounced to audio files and stay in key. Since the midi notes stay the same throughout this, it is very weird that bouncing goes haywire for certain regions when the regions themselves sound fine when left as midi tracks. I assume that it is some corruption of the particular regions that manifests when you bounce, but how odd... I have seen this occasionally before on Logic 9 and 10 on different OS versions. I thought it might have just been bad plugin instruments or effects or whatever, but this seems to happen with different inserts and different software instruments. So far though it has oddly always been on various software "guitar" parts and no other instruments though.
This time it was "RealGuitar" with "UAD realverb" and a "TH2" amp. I tried bouncing the entire project, then right clicking the entire track selected and bounce that, then selecting individual regions and right click "join/bounce" menu to bounce them individually which ended up working if I selected each one separately and not all or several regions at once for some reason.
Since it is only on bouncing that pitch is effected, does that speak to a Logic corruption issue rather than something generated by one of the plugins? Midi itself is never effected and sounds fine. Anyway, this thread over at Apple seems to be the closest to my experience:
The sample rate comment is not out of line ... did you check for that? Is the entire bounced audio file out of key or does it have some parts out of keys and some that aren't? And by how many semitones (approximately) is it out of key?
I don't know exactly how much it goes off, but it hurts to hear it. I still have to do more troubleshooting on this first. It clearly is something getting corrupted where there is no visible cause (no automation) and it is individual region based as opposed to track based and it it can be bounced correctly if you keep fiddling with bouncing the regions, so that's why I think is is probably down to some sort of project corruption.
Put a couple off CC events at the beginning of all your midi tracks.. RESET all Controls, PITCHBEND, MODULATION to 0.. see if that helps.. I created a 10 even CC control seq, I put at the beginning of all my midi tracks.. It sets a number of parameters, and makes it easy to modify individual tracks or sections of a track.. Just don't let it play the same time as MIDI data is trying to play. I change the MSB/LSB/PROG where necessary if using external hardware..
As another test.. DELETE all Automation, on a copy of song.. This will rule out a few things.. I've had midi tracks out of tune because of a hanging pitchbend . Never had an issue with RealGuitar screwing up.. I would assume something in Logic is doing it..
Had this happen again this time with Vir2 Electri6ity on LPX 10.1. I guess I need to look at events and see what is going on. Maybe a clue is that I tend to use the pitch bend wheel on software guitar instruments and that seems to be the only instruments that this ever happens on. And since it is two entirely different guitar instruments and different amp sims, maybe the pitch bend trigger is getting wacky. I saw another similar thread on this here: viewtopic.php?f=1&t=111819&hilit=out+of+tune
I do have multiple regions and some trigger the wrong pitch (at least a half or full step up in key) and some seem ok. Freezing the track doesn't help, bouncing the entire track is the worst, bouncing each region to a new track is really the only thing that works correctly. If I join the regions it gets messed up on the bounce. I wonder why it is mostly on the "bouncing: that these pitch triggers come in to play. rarely does it happen if I just play the original track (although it did happen there on one region once and then the next play was fine) Again the workaround is bouncing each region of that track to a separate new track, so that would indicate there must be some left over pitching trigger maybe at the end of some of the separate regions? If so, it may be something in the workflow since I do tend to record a part, maybe cut the end a bit and start a new region. Any ideas on how not to end up with these extra pitch bends in the future? Thx.
7fc3f7cf58