If this is obvious then excuse me but i found a cool way to MAJORLY reduce cpu load using Revalver.
IF, you're like me and make the patch you want before you record and rarely tweak after... (I'm used to real amps/pods) then i, by accident, discovered that if i had revalver standalone loaded AND sonar 6, if i recorded in sonar, i could record at minimal latency, minimal CPU load (only one instance open) AND it prints the distorted track directly so no fannying around, waiting for it to freeze or anything.
I prefer using WDM drivers in Sonar as i get better stability that way although i get better latency with ASIO so this way, i can use asio with Revalver standalone and then record with WDM in Sonar.
If this is widely known/in the revalver documentation, sorry. I never reasd that stuff!
IF, you're like me and make the patch you want before you record and rarely tweak after... (I'm used to real amps/pods) then i, by accident, discovered that if i had revalver standalone loaded AND sonar 6, if i recorded in sonar, i could record at minimal latency, minimal CPU load (only one instance open) AND it prints the distorted track directly so no fannying around, waiting for it to freeze or anything.
I prefer using WDM drivers in Sonar as i get better stability that way although i get better latency with ASIO so this way, i can use asio with Revalver standalone and then record with WDM in Sonar.
If this is widely known/in the revalver documentation, sorry. I never reasd that stuff!