![]() ![]() The iostation 24c setup shows the clock source as “internal”. I notice one thing in your configuration though: You should still have a really good performance. While the Ryzen performs not quite as good, in my experience the difference is not to big. You should be able to get a similar performance. It also uses more than 100 VSTs (FX, Channel strips, etc.) and it runs flawlessly samples. Over here the current project I am working on makes uses 18 VSTis (among them 2x Kontakt, 2x Superior Drummer 3, 2x Repro-5, 2x Zebra, The Legend, etc.). Your Computer should be roughly as fast as my 12900k. But on cubase 12 pro its a pain with just three libraries. The speed of light also comes into play with cabling at some point - so how exact does one need to be in the grand scheme of things? I'd say do the analog loop to both the dry and parallel processed chain as recommended, and they will be sync'd as close as humanly possible.The issue is not Kontakt, I recreated the same track in Studio One and it works perfectly. Some might be closer to an even sample than others, but I doubt any converters are EXACTLY delayed by a multiple of the base sample rate. RE: Precise sub-sample delay compensation: I suppose it would be possible for someone to design an AD/DA from the ground-up that would end up having a delay that is exactly down to an even sample (no sub-sample offsets in the oversampling sections) - but I kind of doubt that exists. Unfortunately, Cubase/Nuendo don't allow "Negative Delays" on the External Effetcs (which is odd because other DAW's apparently DO!) Since the MF-II is quicker (but the ASIO latency is reported from the MF-I's AD/DA section), it will need a negative delay to match the slower MF-I's reported ASIO delays. I believe this is still an issue of the common driver being used for both the old "slower" Multiface-I and also for the newer "quicker" MF-II. Not perfect, but as close as I can get with ASIO 2.0 and Nuendo. Then, I specify the total analog I/O latency (above and beyond the ASIO's reported digital latency) in Cubase/Nuendo's "Record Offset Placement" field for sample-accurate overdubs. This issue is not as pronounced on the "Ditigal only" boxes like the Digiface and MADI cards - but I still have issues over MADI due to my setup (I run two SSL Alphalinks, one Alphalink feeds the other via ADAT which adds like 4-6 samples of latency compared to the Alphalink that is connected directly to the MADI card). There is not currently a perfect solution - Using AD/DA's with varying delays will always be a kludge under ASIO 2.0 AFAIK. If you run into a situation where you get a negative offset using 3rd party AD/DA converters through an RME PC Interface, swap the RME driver to the "Report Digital I/O ASIO Latency", and then the offset would naturally become positive at that point (but then the RME's Analog I/O is no longer sample-accurate for regular I/O needs including record offset placement - might not be an issue depending on your specific circumstance). The only way I came up with was to have RME add the ability to toggle the reported AD/DA latency in their driver. I would LOVE to see a way to report the analog and digital I/O independently, but ASIO 2.0 does not support this (so RME can't really "fix" it in the driver) - and I believe this is the only way to solve the issue apart from Cubase adding individual offsets for each input and output connection. This is where a negative delay would be needed, and Cubase cannot currently accommodate this AFAIK. ![]() I've also had issues with using digital I/O on the "hybrid" RME products (any RME PC Interface that has analog AD/DA and digital I/O - the driver will always report the analog I/O latency) when the other AD/DA converters are "quicker" than the RME's built in AD/DA conversion. Your -13 sample offset is likely a Mac driver issue as Matthias hinted at fixing (reporting the incorrect AD/DA offsets to the host). This means that as long as Cubase adheres to these reported offsets, an analog I/O loop WILL report "0" as Cubase is correctly using RME's reported analog values. ![]() From what I gather, the RME Driver should be reporting the true analog I/O latencies to Cubase. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |