You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my case, I consider a bit tedious that Nabla always decides to activate recording monitoring, it is quite common for us to work with things that do not need record monitoring.
For example, I use a guitar pedalboard that sounds by itself without the need for Reaper, I want to minimize latencies and I don't want to listen to it for two. Sometimes I also connect a USB microphone and work with a pedal board (USB audio interface) + microphone (another USB audio interface), which forces me to use asio4all to record both at the same time(2 interfaces). If I worked with recording monitoring, the latency would be horrible. Or... maybe y wanna play an acoustic guitar and I prefer to not hear it when recording....
In my case, I consider a bit tedious that Nabla always decides to activate recording monitoring, it is quite common for us to work with things that do not need record monitoring.
For example, I use a guitar pedalboard that sounds by itself without the need for Reaper, I want to minimize latencies and I don't want to listen to it for two. Sometimes I also connect a USB microphone and work with a pedal board (USB audio interface) + microphone (another USB audio interface), which forces me to use asio4all to record both at the same time(2 interfaces). If I worked with recording monitoring, the latency would be horrible. Or... maybe y wanna play an acoustic guitar and I prefer to not hear it when recording....
I have created this fork to leave recording monitoring manual. Could it cause any problems? Is there any form to configure the original Nabla to not monitor records?
https://github.com/juanan95mh/NablaManualRecordMonitoring
The text was updated successfully, but these errors were encountered: