![]() | All Advertisers |
| |||||||
| Notices |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| adat sync question | cchord59 | So much gear, so little time! | 7 | 29th August 2006 01:30 AM |
| Sync Question? | macr0w | So much gear, so little time! | 8 | 4th July 2006 08:01 PM |
| Hello all-HD24xr-BRC sync question | TheHappyBlaster | Low End Theory | 1 | 15th May 2006 09:30 AM |
| Fireface Clock Sync Question... | Matthew Murray | So much gear, so little time! | 0 | 12th May 2006 04:17 PM |
| Amek Big sync question | DeadPoet | So much gear, so little time! | 1 | 23rd June 2004 08:30 AM |
![]() |
| | Thread Tools | Search this Thread | Rate Thread | Display Modes |
| | #1 |
| Gear nut Join Date: Nov 2005
Posts: 105
| A sync question! Hi everyone, I have been using my distressors as an insert from my Digi 002 unit (via output/inputs) and am getting a very obvious latency problem. Is there any way of inserting my distressors using Protools Le and avoiding these latency issues? Thanks in advance, RAH |
| | |
| | #2 |
| Lives for gear Join Date: Oct 2005 Location: Boston
Posts: 624
| One of the ways I work around the latency issue is by printing the track, which in your case is going through the Distressor. I would do this by making the track output one of the 002's outputs. Then create a new track and makes its input the input from the Distressor. A couple minutes later your Distressor track will be printed. You can then nudge the track around until the dips and peaks line up. Plus, you then make the Distressor available for other tracks.
__________________ Zach Winterfeld Chariots of Fire, "you can't put in what God's left out" "It is slightly illegal, but who the f@*k cares at this point." |
| | |
| | #3 |
| Gear nut Join Date: Apr 2006
Posts: 93
| I use a PTLE system at home, and sometimes use outboard gear in mixing. I also have another computer set up, also running LE, that is dedicated to Altiverb, that I connect via analog I/O, so there's latency involved there as well. The way I deal with it is to send all my tracks not to an output, but to an aux track (labelled "mix buss"). I insert Timeadjuster on the mix buss, set to the amount of delay it takes for the reverb signal to make the round-trip (calculated using a null test for each sample rate and buffer configuration). The mixbuss aux outputs to my main monitor output, and I return the reverb directly to that output as well. Latency solved, and you don't need to print anything. The only issue is when doing fader moves, I usually need to disable TimeAdjuster, or I'd be making my moves late, since I'm hearing the audio delayed anywhere from a few ms to 100ms. When I use outboard gear in the mix, I'll set the output of the track I'm using it on to the main output, and then add TimeAdjuster to the track to get it back in sync with my (longer) Altiverb delay. If you're just using a couple pieces of outboard, all through the same D/A/D path, just figure out the delay using a null test, and set up a mix buss aux for all your tracks but the ones going outboard, with TimeAdjuster set to that delay time. Once you get it set up, it's easy, and the best part is that you don't need to print anything or do anything out of real time.
__________________ www.studiorhythm.com |
| | |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
| |