• SONAR
  • Screen Capture cannot hear SONAR
2017/10/15 16:40:34
zoffmeister
Hi there. I am trying for the first time to screen capture a SONAR session. I downloaded OBS as it is well recommended as a great free solution. I think my problem must be to do with how Windows handles audio.
 
My interface is an Apollo. My Master output track in SONAR is sent to Apollo MON (the main monitor output on Apollo). 
When choosing audio device in the Windows sound payback device settings my only option for Apollo is called Apollo, i.e. Windows cannot see individual Ins and Outs. Not sure whether this is a relevant problem.
Anyway, inside my OBS screen capture software I chose Apollo as the option for desktop audio. I press Play in SONAR, I hear the audio, I see the meters in Apollo Console jumping up and down (all as expected) but the meters in OBS show nothing. I go to the Windows playback devices box, I see that Apollo is set as the default as it should be and is ticked but the little meter shows nothing even though SONAR is playing and coming through Apollo fine. Now when I open my browser and lets say play a YouTube video, that audio is of course sent to Apollo, I see the Apollo meters dancing just like they do when I play SONAR, however now I also see the meters dancing in the Windows Playback devices box and therefore also that sound shows up in OBS. So I can play anything else on my PC - YouTube, Spotify, etc and that audio shows up in Windows and Apollo, but when I play SONAR it only appears in Apollo. Therefore SONAR is the only audio I cannot route to other apps. Why is this? What is going on? Is it that other apps send there audio to Windows which then sends it on to the Apollo, whereas SONAR sends straight to Apollo and bypasses a vital stage that I need for what I am trying to do?
 
Please help explain what is going on here and tell me how I get around this problem.
Thanks in advance
2017/10/15 17:00:02
Anderton
I don't know of any screen capture software that works with ASIO. You have to use the "what you hear" or "stereo mix" with native Windows drivers, which your computer may or may not support. And if it does support Windows drivers, it might not work with WASAPI shared, which is ideal for this situation.
 
Lacking that...the way I did the videos for my Advanced Workshop videos was to use two interfaces, a Windows one for Vegas and ASIO for SONAR.
2017/10/15 17:18:49
zoffmeister
Thanks Craig. I thought this might be the problem. These damn ASIO ignorant apps. 
I think my only option at the moment is to send the audio out and record it to minidisc. I'll then have to record it back in again before syncing it to the video. This is all much more of a faff than I hoped. :(
 
2017/10/15 18:15:33
Rasure
I use OBS https://obsproject.com/download and when I want to screen capture from sonar I just change my drivers to "WASAPI shared" within Sonar, then back to ASIO when I`m done :-)
2017/10/15 18:18:40
Anderton
Yes, WASAPI shared is a fine solution but as I mentioned, not all computers support it nor do all computers support "stereo mix." For example my desktop works with WASAPI, but my [actually more modern] laptop doesn't.
2017/10/15 18:54:30
simeon
I use VB-Audio Banana which is a virtual audio mixer that can combine multiple audio inputs, etc.
It is a great companion to OBS Studio.
You can find it here: https://www.vb-audio.com/Voicemeeter/banana.htm
2017/10/15 19:44:32
ramscapri
 
Hi Dean,
 
Its unusual why your Windows 10 Pro is not able to see individual ins and outs. I don't know how Apollo exactly works in this regard but I use Roland Octacapture and Windows 10 Home in my laptop can see all individual stereo inputs and outputs of Octacapture. 
See below screenshots of my sound devices :

 

 
 

 
 
You may want to check your manual for Apollo why individual stereo inputs and outputs are not shown in your sound device options in Windows. It could possibly be some setting.
 
Moreover, recording into the Windows Voice recorder app directly from Sonar works for me even with ASIO as the selected driver. 
You can record directly from individual audio tracks depending on what output is selected for the audio track. The output should be one that is routed to the main playback of Windows which in turn is connected to the main stereo recording input representing the system sound.
 
The key is not only the "Playback" devices but also the right default selection under "Recording" devices in Windows.
In my case, I keep "MAIN" as the default under recording devices which routes all stereo sounds from Windows and also the main stereo output from Sonar directly into a Windows app for recording. This could even include your live mic input into your interface if you want to mix it directly with the playback from Windows or Sonar.
 
Hope above helps in some way.
 
Cheers...
2017/10/16 09:31:37
zoffmeister
Hi there. Thanks for suggestions. Unfortunately I can't change to WASAPI, Apollo works with ASIO only I think.
As far as showing multiple outputs to Windows, yes I'm pretty sure on my previous system using an RME Fireface that was the case. Obviously that doesn't happen with Apollo.
2017/10/16 11:10:01
ramscapri
zoffmeister
Hi there. Thanks for suggestions. Unfortunately I can't change to WASAPI, Apollo works with ASIO only I think.
As far as showing multiple outputs to Windows, yes I'm pretty sure on my previous system using an RME Fireface that was the case. Obviously that doesn't happen with Apollo.




 
 
Hi Dean,
 
What is the Default Device selected in your Recording section tab under Sounds ? Just in case you haven't checked.
 
Playback is fine but for recording system or Sonar output into another app, the Default Device selection in the Recording tab is important. It needs to be your Apollo option selected as default there as well.
2017/10/16 11:46:12
gswitz
If there is an input recording, like a line in, just route mains from your interface to that input.
12
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account