194,600 users have contributed to 42,924 threads and 257,981 posts.
In the past 24 hours, we have 2 new thread(s), 8 new post(s) and 118 new user(s).
It depends a lot on the chosen Output Format in MIR 3D, and also on your audio hardware, but in any case: It doesn't come completely unexpected.
Did you check MIR's own buffer size in its Preferences panel? The more time you allow MIR to perform its calculations, the better.
In MIR 3D preferences it is called latency and this is what I'm referring to. Anything below 4096 results in loud crackling. Logic Pro itself does not even allow an I/O buffer size (latency) greater than 1024.
The output format is stereo with HOA downmix, and the audio interface is ULN8 at 44.1KHz
Then it might indeed be the case that this machine isn't able to cope with the load, sorry to say so. :-/
Usual workaraounds encompass "freezing" a few tracks, or using Bus/Group tracks with one common instance of MIR for several instruments routed to this bus - ideally ensembles of the same or similar instruments, eg. "1st Violins", or "Low Brass".
I don't know the interface you're using, but it might also be worth trying different hardware with different drivers, just to see if it changes anything.
HTH,
It surely did cope with bigger projects with the e-licenser version of the same thing. I never bothered to change the defaults, and this was up to 48 instrument instances in VEP7 + MIR + Logic Pro on the same machine with the same interface. Now I'm using MIR directly from Logic Pro and having latency problems, that's why I asked.
Cannot freeze or group more because I'm balancing the whole score, and using MIDI CC automation only.
Not a big problem for me now, but it shows that comparing to the e-licenser version, this one would benefit from further performance optimization.
No need to beat around the bush: The fact that MIR renders everything in 3rd Order Ambisonics internally now certainly takes its toll. But of course I'll forward your findings to the developers, maybe they can do something about it.
Kind regards,
Is this still the case if and when we are mixing older projects using stereo output formats? Or if the Ambisonics blend control is pushed towards 1st order ambisonics maybe? Is MirPro3D just universally going to be always processing 3rd order ambisonics even when our mix environment is only stereo or perhaps at best 2D planar surround? and thus going to be hitting the Cpu harder?
It surely did cope with bigger projects with the e-licenser version of the same thing. I never bothered to change the defaults, and this was up to 48 instrument instances in VEP7 + MIR + Logic Pro on the same machine with the same interface. Now I'm using MIR directly from Logic Pro and having latency problems, that's why I asked.
Just curious, did you try mixing this project with MirPro3D being used inside Vep7 instead of directly in Vep7? VeP7 adds more buffer and latency...in addition to MirPro's additional latency. Well all that latency sucks while tracking, but while mixing, it doesn't matter...maybe that will help in the meantime?
Also make sure you don't have the track selected in LogicPro that has the VePro plugin...putting it in live mode.
Also make sure you don't have the track selected in LogicPro that has the VePro plugin...putting it in live mode.
Did you write to VSL's support already? I can't test Logic here, but I know for sure that quite a few of my colleagues do and of course also did during development, so I suspect a specific issue with your setup.
Thanks for your patience!
Not yet, I wanted to get a few opinions first because it's a new product. If you think it is something worth looking at, I will contact them. Thanks!
