- #CAPTURE DESKTOP AUDIO WITH SOUND SIPHON INSTALL#
- #CAPTURE DESKTOP AUDIO WITH SOUND SIPHON PRO#
- #CAPTURE DESKTOP AUDIO WITH SOUND SIPHON MAC#
Problem is getting the sound into PT as audio. I am really able to make so much more out of the same cpu.
#CAPTURE DESKTOP AUDIO WITH SOUND SIPHON PRO#
But doing this, it allows me to add a bunch more kontakt instruments, and uses cpu space outside pro tools!
I already have a maxed out PT project, or close to.
#CAPTURE DESKTOP AUDIO WITH SOUND SIPHON MAC#
I have been mucking around with kontakt stand alone.Īnd basically what happens is, if i assign midi tracks in pro tools to kontakt's virtual midi (i believe this is only on mac kontakt), and set kontakt at 32 samples. You might as well just use it as a plugin in PT. Therefore, since PT performance itself is great at 128 buffer or higher (256 buffer at 88k+) per my dsp usage topic, using patchwork in standalone mode is completely useless for PT. Set Patchwork to 128 and it still pops and clicks every couple of second. It works fine if it's the only thing open at 64īut even just one cpu intensive synth in patchwork, when pro tools is open as well, even on a totally blank pro tools project with just one midi track, i.e pro tools is not doing any VI or FX processing of it's own, and Patchwork pops and clicks. The major issue is though, it has shocking low latency performance. So the only usable way i found is to use channels 2 through 16 of IAC bus one in pro tools. as i can NOT disable the midi keyboard input hardware in Patchwork. If you choose channel one though, it will always play even if PT midi track is nor armed. IAC one is routed to host it seems, so that's how you work it. This is using the most basic device on a macbook pro, setting loopback to monitor using the onboard output, and no mic or anything on the input, just the loopback virtual audio stream. It causes massive distortion in pro tools when you arm an audio track to record the virtual loopback input. No matter what latency it is set at, i tried 32 through 1024 The aax on the other hand, is awesome for using VST plugins directly in pro tools. if they just added some features and tightened up the performance, this would have been brilliant. The basic structure of it is so darn good, and so friendly to use. The buffer goes back to 512, all the midi inputs enable. The worst fault of all is that audio and midi preferences default on every start. This was the main deal breaker for me.įor example, many of the synths I inserted could not select a vsti channel, so they'd play no matter any midi channel i had selected in pro tools, that was set to iac out. this is no issue for kontakt but a big issue for the massive amount of vsti's out there that just receive omni channel midi. You can NOT select midi channel per instrument. It uses multiple cores properly from what I could tell. this was the big con, as well as it not liking 32 buffer. I always mark a negative for any app that doesn't have a proper minimum 7 day demo.Ĭrashes on exit pretty much all the time with multiple plugins. It also includes the suite of plug and mix plugins which are great, but they will only work in the chainer.ĭemo limitation is obnoxious, 5 second cutout every 45 seconds. I prefer it in many ways to patchwork cause i like the big mixer and the built in waveform/spectrum/phase analysers.
#CAPTURE DESKTOP AUDIO WITH SOUND SIPHON INSTALL#
This report is a bit sad, as it was so close.įirst, make sure you install the VST or the stand alone will not work. I'll now try to get a virtual loopback working somehow with soundflower/sound siphon/loopback and see how I go. Obviously, i am not going to waste any more time, testing all those stand alone VI's and apps hosting them, with nexus. Just change to that when you want to record and the latency is usually only double the chosen, so 32 in kontakt would be 64 in PT.Ī lot of cheek asking top dollar for this IMO. do all the other routing only when you want to record.Ī virtual router like loopback is going to be much more useful (tests pending). But you can only monitor it in realtime when the aux track it is on is set to the master out.
So you only hear it when it is time to record to the audio track. Unless the transport is going and recording, you can NOT hear the nexus signal in this scenario. To record, you have to put it on an aux, then arm an audio track with the aux as an input. I couldn't play to the click, not even close. Which is the actual latency you get playing it too.Ĭompletely, 100% useless, and i have no idea how anyone could use this. When having kontakt at 32 samples, nexus in PT to receive, audio records ~4600 samples late. Unfortunately, nexus is completely useless to play standalone VI's in realtime. I am adding back 10 plugs at a time and so far ok. PT has scanned it this time and is working and ilok seems working. Ok, i removed all my aax plugins and have added some back including source nexus.
0 kommentar(er)
