AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Pro tools hdx compensation for delay11/6/2023 ![]() ![]() You should record the AES Return by out putting just the Aux that the Bricasti is on to a separate bus, and have that be the input for the audio track to record just the reverb not the entire vocal or session. The screen shots are confusing because you appear to be recording the "No Plug ins, Less Plugins and More Plugins" tracks, off of the main output bus 1-2 which will not give you the delay of the Bricasti AES return in isolation, but would give you the delay of the entire session. Yes I am on HD Native and I do not know for certain but I would not think that would make any difference.Īlso I did not put in any delay in the HardWare inserts tab ( even though it is an insert and labeled "M7" on the inserts tab) and shows in the I/O selection of the inserts section on the track as M7. Yes, Bricasti and my TCM3000 (AES) used to work perfect on PTHD10 with my TDM accell 3 rig. Those tracks shows the latency of the AES signal when Pro Tools have No Plug ins, few plug ins and more plug ins, as you see AES returns in different places depending how many plug ins are in the session, this is a session with only a vocal track, imagine the mess in a regular session. These are the print AES returns (AES send from Vocal Track to an AUX track that receives AES, that AUX go thru a buss to an audio track that records that AES signal, so just Dry AES, same issue happens id goes straight to an audio track) I did not put any delay in HW inserts, I am using my Digital EFFX thru AES send/Return, not as analog inserts. so the Bricasti is totally out if the Equation. ****in this test I connected the AES in cable to AES out. There are also the screenshots of the i/o settings and playback engine, i used that setting for years in TDM and Pro tools 10 no issues and anyway the AES routing is simple AES 5-6 out to bricasti In, Bricasti AES out to AES in Ram tested, 3 different sets of RAM 16GB and 32GB, did apple hardware test 4 times in the Mac 5,1 2圆 core 2.4 ghz all passed great, this is why I did the test in other Mac 4,1 same issues occurs in any test, computer, MacOS etc.I even created new Test Pro Tools session to avoid any corruption that would happen in a bad session.Ĭheck the screenshots how the bricasti returns late depending of the amount of plug ins that are in the session.and this is only a session with a vocal track!! I tested this with different Mac Pros 4,1 and 5,1, different MacOS (yosemite and even Mountain Lion), NEW SSD hard drive with fresh install of yosemite and pro tools 12.5.2 and just installed a couple of other plug ins. It is incredibly noticeable by ear as can be 100ms or more.Įven sometimes with Delay Compensation OFF sound better! I am trying to use my Bricasti via AES in/out into the session.īut the issue here is that depending how many plug ins I have in the session (master and tracks), the Bricasti return comes late, as more plug ins, more "predelay". So here is one of the issues that represents the instability of the delay compensation. I have so many issues, the sessions sounds way tighter with the playback engine in native. ![]() Seems that the delay compensation do not work as intended at all, specially with AES send return. I got HDX and really is been a nightmare.
0 Comments
Read More
Leave a Reply. |