Only at 4,096 is it not particularly noticeable. At the lowest setting, 64, it is still audible. It is most noticeable at the middle settings like 256 and 512. For the Audio IN Core Audio module, I have to set the block size to the highest value, 4,096 or I get this weird vibrating, flanging-like effect. And it offers 24bit options while Virtual Audio Cable topped out at 16bit.īoth of them do experience a weird behavior in Rack. Even though it hasn’t been updated in three years, it seemed happy enough on my Windows 10 box. That seems to have alleviated the freezing and crashing.īut then I uninstalled it and installed another product, VB-Cable to try it out. On a whim, today, I tried unchecking the options in the Sound Control Panel to “allow applications to take exclusive control” of both Virtual Audio Cable and my PreSonus ASIO drivers. It wasn’t too difficult to figure out, but Rack froze and crashed copiously as I attempted to configure the Core Audio module to use it. When I posted on Facebook, folks suggested a couple of other “virtual audio cables.” I tried a two yesterday and today.įirst, I tried Virtual Audio Cable from Eugene Muzychenko. You can listen to it directly through REAPER, before it gets even passed to the Virtual Audio Cable. I didn’t have the energy to figure it out. I tried setting it up again this time with Rack and gave up.
I was never quite sure what I was doing with it. I’m on Windows, and I’ve used Jack before with Reason. I think I asked on the Facebook group for ideas for bringing audio from other apps, like the browser, into Rack.
0 kommentar(er)
