|
|
Post by kcatthedog on Jan 20, 2022 9:09:49 GMT -6
|
|
|
|
Post by drumsound on Jan 20, 2022 10:01:52 GMT -6
interesting
|
|
|
|
Post by bgrotto on Jan 20, 2022 10:05:02 GMT -6
Very interesting. I'm eager to test this in PT. Could be a massive boon to my HDX rig / workflow. Especially for remote mix work, and for teaching.
|
|
|
|
Post by svart on Jan 20, 2022 10:21:56 GMT -6
Hmm. Reaper did this with ReaStream and ReaRoute and you can even do it outside of reaper using ReaPlug.
|
|
|
|
Post by bgrotto on Jan 20, 2022 10:35:01 GMT -6
Hmm. Reaper did this with ReaStream and ReaRoute and you can even do it outside of reaper using ReaPlug. I mean...waves did plugin eq with the Q10. Might as well have stopped there, eh?😉 |
|
|
|
Post by svart on Jan 20, 2022 11:01:24 GMT -6
Hmm. Reaper did this with ReaStream and ReaRoute and you can even do it outside of reaper using ReaPlug. I mean...waves did plugin eq with the Q10. Might as well have stopped there, eh?😉 I don't get it |
|
|
|
Post by subspace on Jan 23, 2022 13:02:29 GMT -6
Very interesting. I'm eager to test this in PT. Could be a massive boon to my HDX rig / workflow. Especially for remote mix work, and for teaching. I've been testing this with PT all morning. Main machine is a 2014 MBP running PT 2021.12 on Catalina with a Carbon interface. Carbon is connected with a TB2>Ethernet adaptor, then I'm using a USB>ethernet adapter for a second ethernet connection to the router. Second machine is a 2012 Mini with an Aphex 500 USB audio/MIDI interface, connected to the same router via it's ethernet port. Previously, I used the Mini to host VIs and reverbs with a low buffer and just patched analog between the interfaces. Now I'm patching the VIs out of LPX into PT using Connector, as well as creating sends from PT back into LPX to the hosted verbs. It works pretty smoothly, though you do have to massage the buffer settings to ensure you don't get drop-outs. I'm trying the resampling feature to run LPX at 48k while returning the FX to a 96k PT session right now, which it handles pretty transparently. Next test, swapping the USB interface on the Mini for a MOTU 16A and try 16 instances of Connector for an additional 16 channels out of PTs @ 96k feeding the desk. |
|
|
|
Post by Quint on Jan 23, 2022 18:18:08 GMT -6
This is interesting to me because it may mean that I could go with a cheaper Mac Mini to run Luna and then still use my PC for hosting and playing sample libraries and just pipe that over to the Mac via BC Connector.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jan 24, 2022 0:34:52 GMT -6
Does it also turn DAW audio (via plugin) to CoreAudio virtual I/O? Or does it need two plug-in instantiations to communicate inter-app?
Trying to not have to buy the absurdly-priced Source-Nexus, an app that should sell for 45 bucks and instead costs $250 or 299 or something inappropriate.
|
|
|
|
Post by thehightenor on Jan 24, 2022 1:48:52 GMT -6
I mean...waves did plugin eq with the Q10. Might as well have stopped there, eh?😉 I don't get it I think he was saying plug-in development doesn’t ever stop at any one product - at least I think that’s what’s he’s saying? |
|
|
|
Post by subspace on Jan 24, 2022 7:24:46 GMT -6
Does it also turn DAW audio (via plugin) to CoreAudio virtual I/O? Or does it need two plug-in instantiations to communicate inter-app? Trying to not have to buy the absurdly-priced Source-Nexus, an app that should sell for 45 bucks and instead costs $250 or 299 or something inappropriate. Nope, you need a receiving instance to communicate, nothing additional shows up in CoreAudio. I was able to stream 16 instances out of PT into LPX, which were then routed out the 16A DACs from the second machine. Discovered a connection issue with the MOTU that side-tracked me before I got around to testing a full duplex routing configuration. It requires a time adjuster plug-in to align the Carbon I/O with the buffered Connector I/O on the MOTU, but adding the 16A's 32 ins and outs via a second Mac seems to work fine, in addition to adding the plug-in processing power of the second DAW. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jan 24, 2022 12:18:46 GMT -6
Does it also turn DAW audio (via plugin) to CoreAudio virtual I/O? Or does it need two plug-in instantiations to communicate inter-app? Trying to not have to buy the absurdly-priced Source-Nexus, an app that should sell for 45 bucks and instead costs $250 or 299 or something inappropriate. Nope, you need a receiving instance to communicate, nothing additional shows up in CoreAudio. Too bad. Would have been a great hook into Zoom, OBS, etc. |
|
|
|
Post by wiz on Jan 26, 2022 17:17:58 GMT -6
Does it sync two DAWS on same machine? When sending audio or midi from one to the other how does it maintain timing? Starting and stopping the Daws at the same time?
|
|
|
|
Post by wiz on Jan 26, 2022 17:24:11 GMT -6
Does it sync two DAWS on same machine? When sending audio or midi from one to the other how does it maintain timing? Starting and stopping the Daws at the same time? Found the answer no it can’t |
|
|
|
Post by Quint on Jan 26, 2022 18:22:58 GMT -6
Does it also turn DAW audio (via plugin) to CoreAudio virtual I/O? Or does it need two plug-in instantiations to communicate inter-app? Trying to not have to buy the absurdly-priced Source-Nexus, an app that should sell for 45 bucks and instead costs $250 or 299 or something inappropriate. Nope, you need a receiving instance to communicate, nothing additional shows up in CoreAudio. I was able to stream 16 instances out of PT into LPX, which were then routed out the 16A DACs from the second machine. Discovered a connection issue with the MOTU that side-tracked me before I got around to testing a full duplex routing configuration. It requires a time adjuster plug-in to align the Carbon I/O with the buffered Connector I/O on the MOTU, but adding the 16A's 32 ins and outs via a second Mac seems to work fine, in addition to adding the plug-in processing power of the second DAW. Do you have the Carbon and the Motu synced together with word clock? What kind of latency are you getting? Is it low enough for tracking? |
|
|
|
Post by Quint on Jan 26, 2022 18:25:35 GMT -6
|
|
|
|
Post by subspace on Jan 28, 2022 0:38:05 GMT -6
Nope, you need a receiving instance to communicate, nothing additional shows up in CoreAudio. I was able to stream 16 instances out of PT into LPX, which were then routed out the 16A DACs from the second machine. Discovered a connection issue with the MOTU that side-tracked me before I got around to testing a full duplex routing configuration. It requires a time adjuster plug-in to align the Carbon I/O with the buffered Connector I/O on the MOTU, but adding the 16A's 32 ins and outs via a second Mac seems to work fine, in addition to adding the plug-in processing power of the second DAW. Do you have the Carbon and the Motu synced together with word clock? What kind of latency are you getting? Is it low enough for tracking? Not even close to low enough for tracking, all the PT monitoring is sub 1ms through Carbon, the 16A latency was 20ms with the buffers cranked up enough to be glitch proof. Not a problem for offsetting playback on a stemmed out mix. Only software drift correction, no hardware sync, ran my reverb send/return test with the DAWs at different sample rates and Connector doing the sample rate conversion to a Lex 300 hardware insert. |
|
