|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#11
|
||||
|
||||
Re: Pro Tools Studio 2022.9 problems. Please help me
Thanks again for your reply bro.
Honestly I don't understand how to use the hardware as an insert... :confuso: If I connect, for example, a mono gear to channel 1 of the Lucid i.e. Adat 1 (out of the gear ---> in 1 Lucid and in of the gear - > out 1 Lucid), how do I In Pro Tools create an insert? Into insert menus (of I/O Setup) I have to place the "small square" M in the matrix (see attached photo). Ok, but where? Sorry, maybe that's a trivial question, but I just don't know how to do it... But it would actually be very convenient for me. Avid responded to my request like this: May I please know if under Options you have Delay Compensation enabled and Low Latency Monitoring disabled ? Please double check the next steps to calculate the Hardware Insert Delay to be set on I/O Setup: https://avid.secure.force.com/pkb/ar...e-Insert-Delay https://www.youtube.com/watch?v=Lb5I...annel=MixbusTv ( as this video explains if you change to a session with different sample rate you may have to recalculate, also please, disable Ignore errors during playback/record on the Playback Engine window) Please let us know how everything goes or if the issue persists (you can attach screenshots and video to your response if its helpful for demonstration). I was hoping for better help, but .... Now I try to create an insert on the analog ports of the Audient and see what happens. Meanwhile, I made a small video with the phone (I apologize for the bad quality) from which I show the problem more clearly, using a kick sample. You can download it here: https://we.tl/t-WavpkkP2mS Thanks again for the help, I hope to find a solution |
#12
|
||||
|
||||
Re: Pro Tools Studio 2022.9 problems. Please help me
Quote:
Input 15 Output 23 If I understand correctly, input 15 corresponds to analog input 3 of the second Lucid unit, while the output 23 corresponds to the analogue output 7 of the second Lucid unit, correct? So I would have to physically connect the gear between the Lucid's input 3 and output 7, right? If so, i guess it needs a patchbay, otherwise i would have to continually plug and unplug the cables... |
#13
|
||||
|
||||
Re: Pro Tools Studio 2022.9 problems. Please help me
Ok, I did some tests and yes, I can connect an input and an output of different numbers (for example in 6 and out 2) BUT I lose 4 mono insert points (having 24 total outputs and 20 total inputs).
So the last gear that I could use in insert, would be "insert 20", connecting the input 8 and the output 4 of the second Lucid ("losing" 4 outputs of the converter). Thanks for your help! |
#14
|
|||
|
|||
Re: Pro Tools Studio 2022.9 problems. Please help me
OK so you have the hardware insert working? If not a hardware insert is added the same way as a software insert (i.e. plugin) but selected the insert>I/O menu. If you are unsure on any of this, it's all well described in the Pro Tools Reference Guide.
As for "losing I/O"... it's still there. If you really need to you can use interface built-in analog I/O or even a combination of interface built-in analog I/O and the ADAT I/O to do inserts. But presumably you want to use some I/O for actual inputs and outputs not just H/W inserts. So is it working now? No problems? You've measured the actual latency and corrected for the negative offset by entering a negative value in the delay comp +/- field. Did you confirm latency is exactly corrected for if using the ID44 analog I/O for inserts. And Pro Tools support is asking about if you are using LLM because they are thinking about something else going on... which is a bug in delay compensation with hardware inserts that happen only if you use LLM and also have a software plugin following a H/W insert. I and others have reported that bug, but support seem a little lost with it. If you are affected by this it will throw off delay compensation by 2 x 1024 or 2 x 2048 samples (for higher sample rates). Which is 2 x the high-latency domain aka disk buffer size used by Pro Tools depending on the session sample rate. And you are not close to that huge offset. Don't worry about this for what you are doing. |
#15
|
||||
|
||||
Re: Pro Tools Studio 2022.9 problems. Please help me
Quote:
Quote:
Quote:
Quote:
Thanks for your help bro!
__________________
https://www.youtube.com/watch?v=43yQkZyEZ5w&t=64s https://www.youtube.com/watch?v=vHorLVi1aLY Last edited by Simonluka; 10-20-2022 at 12:36 AM. |
#16
|
|||
|
|||
Re: Pro Tools Studio 2022.9 problems. Please help me
Quote:
Your initial complaint was phasing, hopefully you have this fully solved. If not you should be able to measure the latency using clicks though your ADAT inserts and adjust that (33 sampels or so?) and cure any phasing. One measurement made at the sample rate you work at (with latency comp enabled when you make the measurement) and that should apply to all inserts using those ADAT boxes. It literally should take a few minutes to do. Yes Pro Tools really needs several improvements and at least one bug fix (the LLM one) with hardware inserts, but if you know what you are doing it can work. |
#17
|
||||
|
||||
Re: Pro Tools Studio 2022.9 problems. Please help me
Quote:
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Pro Tools 2022.4 on Mac Studio M1 Ultra | Selle Sellink | Pro Tools | 47 | 06-05-2023 01:42 PM |
Pro Tools Studio 2022.6 and native M1 support | Mishabou | Pro Tools | 1 | 07-23-2022 01:02 PM |
Pro Tools Studio 2022.5 repeatedly freezing on M1 | Theduude21 | Pro Tools | 0 | 06-26-2022 01:51 AM |
Mac Studio M1 Max Problems with 2022.5 Playback Engine | operator | macOS | 7 | 06-24-2022 08:43 AM |
Pro Tools Studio 2022.05 is not showing video in the clips list | Kewbass | Windows | 3 | 06-23-2022 10:35 AM |