torpedovegas
New Member
Hi folks,
I do a lot of my orchestration and mock-up work with Dorico using a 2 computer system with a host mac mini and PC running VEPro.
One of the biggest PitA of this setup is creating deliverable stems given the limited audio routing options in Dorico. It has the option to export individual tracks but with a VEPro system that means real-time soloing each instrument in serial which can take forever. My workaround to this point has been soloing my instance returns (which are Winds, Brass, Strings, etc.) and renaming the files as they're exported... still pretty inefficient.
I have been playing around with the trial versions of Audiomover's Inject which can be instantiated as an insert in Dorico, routing to Omnibus and then setting the appropriate returns in Pro Tools. I have Pro Tools receiving MTC from TXL timecode in Dorico. It works well but I have a concern about buffer size and latency. It's unclear exactly how the buffer sizes of Inject and Omnibus work together. For example, if I have my buffer size set to 256 in the Inject plugin and 256 in the Omnibus standalone app, is that an additive buffer going into Pro Tools and the printed audio is 512 samples behind? Any recommendations for compensating for this in Pro Tools? Even just nudging audio after the fact.
Also, if there's an easier way to accomplish the same end goal, let me know.
I do a lot of my orchestration and mock-up work with Dorico using a 2 computer system with a host mac mini and PC running VEPro.
One of the biggest PitA of this setup is creating deliverable stems given the limited audio routing options in Dorico. It has the option to export individual tracks but with a VEPro system that means real-time soloing each instrument in serial which can take forever. My workaround to this point has been soloing my instance returns (which are Winds, Brass, Strings, etc.) and renaming the files as they're exported... still pretty inefficient.
I have been playing around with the trial versions of Audiomover's Inject which can be instantiated as an insert in Dorico, routing to Omnibus and then setting the appropriate returns in Pro Tools. I have Pro Tools receiving MTC from TXL timecode in Dorico. It works well but I have a concern about buffer size and latency. It's unclear exactly how the buffer sizes of Inject and Omnibus work together. For example, if I have my buffer size set to 256 in the Inject plugin and 256 in the Omnibus standalone app, is that an additive buffer going into Pro Tools and the printed audio is 512 samples behind? Any recommendations for compensating for this in Pro Tools? Even just nudging audio after the fact.
Also, if there's an easier way to accomplish the same end goal, let me know.
