Jump to content

wjm

Member
  • Posts

    33
  • Joined

  • Last visited

wjm's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thanks for the response Eric. I've looked at your links and spent all of today trying different things and getting pretty much the same results. Changing the three options to do with processing/multithreading in Preferences/Audio/Devices makes a bit of difference as to the rate of decay, but not enough to create a workable environment. Something else that seems odd is that the problem seems to be getting worse the longer I play with it - i.e. with the exact same settings I'm getting worse results now than when I fired up the computer to resume troubleshooting first thing this morning. I haven't updated to LPX 10.3 yet - do you know if there's any change this has been addressed since that first thread 4 months ago?
  2. Yesterday I opened a project I've not worked on in about a year to record some basslines with an external hardware synthesizer. The project has tempo automation that varies from 141bpm to 144bpm, and back, throughout the song. I noticed immediately that the tempo of the notes coming into Logic from the external synthesizer were lagging further and further behind the tempo of the rest of the track the longer it recorded. Begging your pardon if I'm long-winded, but I like to be as thorough as possible when asking for help. The first bassline midi note starts at 5 1 1 1 and the first note of incoming audio from the synth is recorded into Logic at 5 1 1 17, (a perfectly acceptable 17 tick latency if it remains more or less constant). Now by the time the first verse is ending at 21 1 1 1 that lag has only increased to 21 ticks - not a huge deal - but then there hasn't been much tempo change throughout the first verse, and it's this that seems to be the issue. Throughout the chorus the tempo ramps up from 142bpm to 144bpm and then down to 141bpm for the bridge. By the end of the bridge my 17-21 tick lag has now increased to a very audible 179 tick lag - the first midi note of the second verse that starts at 46 1 1 1 doesn't see its audio come in from the external synthesizer until 46 1 1 179. This lag remains more or less constant again throughout the verse (as there's little tempo change happening) and by the start of the second chorus (after a bassline pause from 62 1 1 1 to 64 1 1 1 1) that lag has increased to 201 ticks. As the tempo ramps up again the lag starts to increase even more and by 68 1 1 1 its at 240 ticks. Out of curiosity I removed all tempo changes from 68 1 1 1 onward just to see what would happen. Not surprisingly the lag did not get any worse. What did surprise me was that the it actually started to decrease, and by only 5 second later at 71 1 1 1, it was back to its initial latency of 17 ticks and from there until the end of the track it was rock solid (as there was no more tempo automation). So if the tempo changes stop the MIDI will actually drift back into proper sync. It should probably be noted that I have recorded external midi instruments from this project with all of its automated tempo changes in the past without encountering this issue. At that time I was using the same computer and the same MIDI interfaces. So whatever the issue I can't imagine that it's the hardware. But I'm running out of ideas to rectify the issue . . . and I need to get this song done. What I've tried to correct this problem: 1. Comp restart - no change 2. Unplug and replug MOTU MIDI interfaces - no change 3. tried two other MIDI interfaces (M-Audio and Alesis) - no change 4. tried two other external hardware synths - no change 5. tried both an old school External MIDI track and a new school External Instrument MIDI Plugin Track - no change 6. removed ALL other tracks from the project and ALL plugins - no change 7. tried creating a new empty project and importing only the midi file and tempo info - no change 8, put Logic in Low Latency Mode - no change 9. tried changing Logic's I/O buffer size - some minor change in the numbers, but exactly the same behaviour Here are some images to illustrate the issue. First image shows the MIDI regions and the tempo automation. The green boxes show where the punch-in images are on the timeline. On the punch-ins I've place the playhead at the start of the incoming audio note so it's position relative to its MIDI note can be seen. http://i.imgur.com/tcD5TqB.jpg http://i.imgur.com/CyJ9e0a.jpg http://i.imgur.com/LbTmgAJ.jpg http://i.imgur.com/55i6iFi.jpg http://i.imgur.com/9yHSqPy.jpg Any ideas?
  3. I see now that every project I have where I've used Binaural Panning on a track now shows this message when I open it. I didn't realize that Binaural Panning always uses Surround. I thought it was just a two channel (hence the Bi in Binaural) process that "faked" 3D sound-space. Those 5 dots circling the Binaural Panning symbol probably should have been my tip-off. So I guess the only issue here is that when updating to 10.2.1 my Advanced Additional Options all got unchecked. Nothing actually changed with the projects themselves, just my preference settings. And a big thanks to everyone for not calling me out on my extremely messy and disorganized project! It's always like this while I'm composing and then gets cleaned up and organized considerably when it's mix time . . . still an embarrassing image to share.
  4. Interesting. I don't think I've ever clicked the "ALL" button before in the mixer. It scrambled the order of my channel strips, and there sure is a lot of stuff to the right of the 2buss . . . still, I don't see anything that suggests Surround.
  5. . . . I just opened a project and had the following message pop-up: Additional option is required. Project “Another Poor Excuse For A Song V6 01” uses option “Surround” which is not enabled in your preferences. It is temporarily available while this project is active. Do you wish to have it enabled in the preferences? Enable? . . . Leave Disabled? I've never worked in surround on this or any other project, and I can't figure out what in this project is utilizing surround. I've gone through every track and every plug, etc. to now avail. Ideas?
  6. Mine as well. Where is the best place to make these kinds of requests heard?
  7. I just want to add that The Art of Sound over on the Apple Support Forums suggested I try using one of them new, fandangled External Instrument Plugin tracks instead of my old-school way of using two tracks - an External MIDI Instrument track to send the MIDI out and an Audio Track to get the audio in. Sure enough the External Instrument Plugin track works just as it should. It passes audio in my uber simple project and it passes audio in sync in my rather complex, latency laden project. It doesn't explain why the other method isn't working, but at least I can move on and make some music again. Yippee!
  8. One more interesting tidbit. Tonight I changed my target synth that was feeding Audio Track 1 from a rack synth to a keyboard synth. While none of the above behaviour changed when Logic was playing, with the new synth's keyboard I was able to verify that Audio Track 1 will pass audio like it should (with Record Enable enabled) when the playhead is stopped. I can play that synth by hand and it is properly monitored through Audio Track 1 and out the Stereo Output (to my interface and out my speakers) until I hit Play on the playhead. At that point it goes instantly silent even though I can still see the audio moving Audio Track 1's meters. In this shot you can see a very simple setup. I grabbed this while Logic was "playing". The first Track Header shows a MIDI region that is successfully feeding MIDI to my JX10 synth. In the second Track Header you can see the audio coming from the JX10 into Track Audio 1. The third Track Header is the Stereo Output track (that I clicked on in the Mixer and chose Create Track so we could see it in the arrange area next to the other two tracks). The blinking Record Enable buttons on the Track Header and in the Inspector blink on and off at opposite times, so it was impossible to grab an image that showed them both on at the same time.
  9. So I just had another weird thing happen. I switched the inputs of my Audio Track 1 to inputs 7+8 because I wanted to audition a different synth. At first I got excited because I could monitor the audio now just by having Record Enable enabled - but it was a short lived excitement because when I took that track out of solo mode it was terribly out of sync with the rest of the project. I stopped it and hit play again - silence just like before (but still I could see the audio on the track's meters. Out of curiosity I created a new audio track - Audio Track 10, and set it to inputs 7+8 . . . same behaviour - silent unless I use the previously posted "trick".
  10. Thanks for the attachment tip David. Software Monitoring is enabled.
  11. I had thought that David Nahmani's excelllent suggestion to disable the new input monitoring only for focused track, and record-enabled preference preference had solved my problem, but alas it's back today as before and doesn't respond to toggling the aforementioned preference. Here's where I'm at: Here's a problem I've been having a lot with Logic X (every version thus far). I create an Audio Track (let's say it's Audio Track 1 in my project) and select the appropriate inputs for this new track (let's say inputs 3+4 for a stereo track). I have a MIDI Track sending notes to a rack synth connected to inputs 3+4 on my interface. I Record Enable this new Audio Track 1 I've created and hit play. When I do this I can see the audio coming from my rack synth into my interface on the interface's meters, and I can see the audio coming into my new Audio Track 1 in Logic because the meters on the mixer channel show me the audio is getting to that Audio Track, but it's not being passed through to the Stereo Output so I can hear it. I check that the output of Audio Track 1 is set to Stereo Output - it is. Let's say I change Audio Track 1's output to Bus 7 out of curiosity. Still no go. Just like with the Stereo Output, Bus 7's meters stay flat even though Audio Track 1's meters are jumpin'. So now, out of curiosity, I enable Input Monitoring on my Audio Track 1 (so now both Record Enable and Input Monitoring are enabled) - still no audio passing out of the track while the track is playing, but I'm sure I can catch the tail of the audio I should be hearing from Audio Track 1 when I stop the Playhead. It's like something is stopping Audio Track 1 from passing along the audio it's clearly receiving while Logic is playing, but as soon as Logic stops playing that audio can pass through as it should to the track's set output . . . only there isn't much audio to pass when Logic isn't playing. To test this I put a long reverb on Audio Track 1, and sure enough, when I stop the playhead, suddenly audio is let out of Audio Track 1 and I can hear that long reverb tail in all its glory. And for the record I can see no difference in this behaviour whether Audio Track 1 is Soloed or not. Now I disable the Record Enable on Audio Track 1 - leaving only the Input Monitoring enabled. Suddenly the audio passes from Audio Track 1 to the Stereo Output like it should, and I can hear it, but it's waaay out of sync - enough for a couple of my 16th note bass hits to play before the rest of the tracks start. So I try putting Logic into Low Latency mode - and now the audio from my Audio Track 1 is even more out of sync than before! How much? The entire amount of latency that the rest of the project is playing through. Out of curiosity I decide to hit Record instead of Play. The audio coming into Audio Track 1 records perfectly in sync with the rest of the project as it should, but it still does not pass to the Stereo Output, (or anywhere else) so I can hear it while it's recording. Once the audio is recorded, and I have an actual audio region in Audio Track 1, I can play and hear that audio region exactly as you'd expect I should be able to. I've tried disabling and re-enabling Core Audio, disconnecting and reconnecting to my interface, quitting and restarting Logic . . . watching an hour of football . . . nothing seems to work. I'm wasting a lot of time because I can't audition my sounds prior to recording them, and I can't just record them without first knowing what they're going to sound like with the rest of the track. I'm getting nothing done and it's killing me. I've included an image here where I've soloed Audio Track 1. You can clearly see that it is Record Enabled, and that audio is hitting the track, but that there's nothing being passed to the Stereo Output. Another weird item of note that this image captures is that Inst 14 (CR78 Clav) also shows audio in it's meters at this time even though it is not soloed, and that audio is also not being passed onto the Stereo Output. Today I've found a weird workaround that works If I do the following: 1. I only enable Input Monitoring on my track 2. I then hit "play" (at this point the audio coming into Audio Track 1 can be heard, though it is out of sync) 3. While it's playing I hit the Record Enable button, so now both it and the Input Monitoring button are enabled When I do step three the track goes silent for an instance as the correct latency is applied and then it comes back, audible and in sync with the rest of the project. If I stop Logic from playing and then hit play again the track is silent again (though as always the meters still show that it's receiving audio), unless I disable Record Enable before hitting play, and then re-enable Record Enable once the track is already playing and receiving audio from my external device. So I have to do the above steps every time I stop/start my project if I want to be able to monitor the audio coming into the track in sync with the rest of the project. Any advice super eagerly appreciated. Cheers, James http://s4.postimg.org/vztiq1n4d/Logic_Pro_X_Record_Enable_Audio_Problem.jpg 3.4GHz i7 iMac | 32GB RAM | Yose 10.10.5 | Logic Pro X 10.2
  12. Actually, having got up today and restarted my iMac, and reloaded logic, the above Input Monitoring preference that I thought had solved my problem last night, is this morning having no effect on my issue. So I'm going to start a new thread outlining what's going on with my system.
  13. David, you're a lifesaver - thank you so much! I just finished writing the longest, most meticulously detailed post on the Apple Support Communities Logic thread about my issue, and then i come here and do a quick search of previous threads before posting my question, and voila! Solved! What I don't get is how it became enabled in the first place? Please tell me they didn't introduce it in an update with it automatically enabled! Anyway, thanks again. James
  14. Thanks Eric! So simple I probably would never have figured it out. . . . and very helpful too.
×
×
  • Create New...