Jump to content

RedBaron

Member
  • Posts

    345
  • Joined

  • Last visited

2 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

RedBaron's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges

2

Reputation

  1. For the first time since switching to a mac, I'm considering moving back to a PC because of CPU spikes with a single MIDI track playing. BTW, I'm getting "scrolling bug" spikes in 10.2.4; haven't upgraded yet.
  2. "When I record a midi track its all offset" I thought the OP was talking about the timing of MIDI recordings, not audio ?
  3. Eric's pretty much said it all. The Latency Offset is for output alignment using the PDC system. The Recording Delay is for input/recording alignment.
  4. It's just a slower way to work, and potentially not sample accurate unless you have clearly defined transients to help you line things up (unless you're using a tool to align phase?). If you configure Logic correctly, recording latency compensation is sample accurate so long as everything you recorded was in sync with Logic's *metronome* in your speakers during recording. For me, moving audio (regions) around after recording kills my inspiration. I prefer to record and move on immediately to the next task. Otherwise, whatever works for you. I don't like to tell people how to work. I generally just talk about latency configuration and other technical issues.
  5. By 'chain', do you mean latency inducing plugins on the same output channel strip ('mix buss')? Or do you mean latency inducing plugins on an Aux, before the audio reaches the output channel strip? Either way, recording the signal returning to I/O plugins on output channel strips is very restrictive, and will only work sample accurately if the outboard itself is zero latency, and other strict restrictions are adhered to (see 'Recording an I/O Plugin from an Output' from this post). I suggest you create an 'output Aux' that's simply an aux that acts as a 'middle-man' just before the output channel strip. Instead of routing tracks and aux-sends straight to an output, I route them ALL through the 'output Aux' first, which is the only channel strip routed directly to the output channel strip. All other tracks/auxes go through that intermediary aux first. I never route audio direct to an output channel strip on my system, I have an 'output Aux' for each of my output pairs, and put latency inducing plugins on the 'output Aux' instead of the output channel strip. I think this is pretty much answers your question below: Yes, as I said above, use an intermediary aux and put the I/O plugin on there and only route the intermediary aux to the 'mix buss'. I/O plugins on Aux channel strips are just easier to work with. However, you'll be fine recording the return signal from an I/O plugin on an output channel strip so long as the outboard is fully analogue with zero latency (i.e. the I/O plugin's latency is exactly the same as your usual roundtrip latency). But you also can't have any latency inducing plugins before the output channel strip's I/O plugin, either on an aux (send) or inserted onto the output channel strip before the I/O plugin (but you can insert latency inducing plugins after the output channel strip's I/O plugin, and latency inducing plugins on audio or instrument tracks are OK). Basically, the output channel strip's I/O plugin must be the first latency inducing plugin after your audio/instrument tracks. ^ But on the whole, it's just easier to record an I/O plugin's return signal if you put it on an aux. See 'Recording an I/O Plugin from an Aux - Method 2', again from this post.
  6. Do you get the same mismatch when running at double SR? I should have said +1 samples at 48k. As, for Double Speed (DS) and other samples rates, here's some Ping results for the USB driver that I did a couple of years ago; double checked with (more reliable) manual loopback recordings: 44.1k = +1 48.0k = +1 88.2k = 0 96.0k = 0 176.4k = +1 192.0k = +1 And for the Firewire driver: 44.1k = 0 48.0k = 0 88.2k = 0 96.0k = 0 176.4k = -2 192.0k = -2
  7. It means that your audio interface's driver is under-reporting it's latency by 1 sample. Ping for my RME Fireface UCX reports +1 too, confirmed by RME. You then have to invert that number (i.e. convert +1 to -1) and manually enter -1 samples as your Recording Delay in Preferences > Audio > Devices. You can only specify one Recording Delay (I think we should be allowed to specify more than one Recording Delay btw), so it really only works for outboard that has zero processing latency, or for basic recording of non-software monitored sound sources. So a digital EQ connected to an I/O plugin would be recorded late, unless you temporarily decrease the Recording Delay from your default of -1 samples. See my post below for the various ways to overcome this when recording the outboard-processed signal coming back into the I/O plugin. There's also a quick summary a couple of posts below this post: Best way to record I/O plugin Hope this helps.
  8. I don't think there's anything you're doing wrong. As Eric stated, record through a bus when software monitoring with or without the External Instrument plugin. Provided that the timing of your MIDI keyboard playing or pre-recorded MIDI region results in the synth's audio being output at the same time as Logic's metronome or other quantised track i.e. everything is in sync with Logic's grid in your speakers, then recording through a bus will result in sample accurate recording of the software monitored sound source. IOW, when you play back the new audio recording it will sound exactly the same as it did during recording, to the sample. ^ Summary: get everything in sync in your speakers and record through a bus, that's all you really need to remember when software monitoring an external source. The relative timing of the synth's recorded MIDI note relative to the recorded audio hit triggered by that MIDI note is not anywhere near as accurate, as you've found out. As I stated in this post on GS, I've witnessed a misalignment (late MIDI) when simultaneously recording a synth's MIDI and the audio triggered by that MIDI, but that was whilst direct monitoring with Local Control on, so Logic wasn't being used as a MIDI Thru/router, it was just recording the synth's MIDI and corresponding audio hits. I just don't think Logic lines the two up accurately enough. I've haven't yet done the same MIDI+audio test with the External Instrument plugin and software monitoring. I should also state that the timing of MIDI recordings is my weakest area of knowledge. Up to now I've been concentrating on MIDI & audio timing for monitoring purposes (i.e. output alignment), audio PDC, and also audio recording alignment. So, I've only recently started testing MIDI recording. Just one thing, if you want a dry synth recording, feed the bus from an aux instead of the 'Send' on the External Instrument track. Eric's method is more of a 'track bounce', and any plugins on an aux or output don't get included in that 'track bounce', just the plugins on the External Instrument track.
  9. Just to be sure, are you (software) monitoring through the External Instrument plugin? Or are you just using it for MIDI and recording the synth's audio? IOW, you're direct/mixer monitoring?? Also, are there any latency inducing plugins on the External Instrument track itself?
  10. When you record through a bus, the Recording Delay is not used by Logic. In fact Logic doesn't do any Recording Latency Compensation (RLC) at all when you record from a bus. The timing of the MIDI is crucial when recording through a bus. It's the MIDI timing that determines your audio timing in new recordings. IOW, you have full control over audio latency compensation by varying the MIDI timing with region/track delays.
  11. OK, thanks for the monitoring info. I can't stress how important the monitoring method is when talking about DAW latency. Before I reply again I need to run a couple of quick tests. Please can you tell me what your latency is, as reported by Logic in Preferences > Audio. I'll then set my buffer size in Logic so that my latency roughly matches yours, and run the tests.
  12. ^FYI IIRC, you don't need to bypass any plugins inserted before the I/O plugin, unless you want a clean processed signal.
  13. Does it happen when you're recording MIDI for a soft synth? BTW, I've seen your posts about this numerous times, but I hesitate to post a reply because I can't figure out the steps needed to recreate your problem. If you give me some info, I can convert inbound MIDI messages to audio whilst simultaneously recording the MIDI, and then compare the two against a reference click/metronome coming from Logic. I also have Expert Sleepers MIDI outputs, so I can fire the MIDI messages precisely in time the Logic's metronome. Other than that, I did test the timing of MIDI recordings when direct monitoring in this post: delay when recording midi in logic x (not software synth/plugin-related) .. but that's about MIDI recordings that are LATE, not early. Also, Logic was only being used to record the MIDI, it wasn't being used as a MIDI 'Through' because the synth/keyboard had Local Control switched on.
  14. You're using external MIDI tracks, so does that mean you're direct monitoring the synth (using your audio interface), or monitoring the synth via an external mixer? i.e. you're NOT monitoring the synth through Logic/plugins.
  15. Are you talking about the setting in Project Settings > Synchronization > MIDI? I think that's just for MIDI clock, not for MIDI notes. Also, are you using external MIDI tracks, or the External Instrument plugin?
×
×
  • Create New...