![]() ![]() Please correct this and don't charge us for it in a new update (software/hardware). This is a problem AVID and it seems as if you don't care. I have found a number of threads explaining the same exact problem, some, including myself, have sent sessions to AVID for their research and we have yet to hear anything back. I have been troubleshooting with avid tech support for a couple of months and they haven't given me the solution yet! I too have switched to HDX a couple of months ago and have been having the same exact problems. 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. that is causing the difference in the start times of those tracks, and is not actually any delay in the Bricasti channel itself. which is what your 1st screen shot is showing as the inputs for the recording on the "No Plug ins-Less Plug ins- More Plug ins " tracks.And that is the cumulative (uncompensated) delay from adding plugins. I think it is because you are recording off the main output Bus 1-2. This is what I did and again as you see first off the output from my Bricasti is very low level compared to output from the Vocal Track ( it is only the actual parallel % mix output from the Bricasti) where it looks like your tracks are showing the output from the entire session And I would do so with Delay Compensation turned on. To show only the output from the Bricasti. The first thing you should do for correct diagnostics is record the output of the Bricasti to an unused bus pair and use that bus pair as the input for the Audio tracks. I again refer you the total difference in the signal levels between what you are showing as recording from the Bricasti and what I am showing. or actually a delay in the Bricasti channel I do not think is because of using HDX per se. So back to the OP I think your issue is in setup or routing ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |