How configure Behringer UMC202HD to be 1+2 as an Stereo input with Sonar Bandlab?

[Gilberto Strapazon]

I have an USB audio interface Behringer UMC202HD connected to a Roland M-16E mixer and so to my synthesizers.

PC is an I7, Windows 11 and Sonar Bandlab.

All drivers and softwares are updated to current version

The current driver is BEHRINGER_UMC_Driver-V5.57.0

 

So here the problem:

Windows say the UMC202HD have 2 input lines.

Sonar show the options:

• Input 1 (Mono). This is my Left channel.
• Input 1+2 again show as Mono!
• Input 2 (Mono). This is my Right Channel.

 

And the result signal 1+2 is a very strange mix.

 

See attached image.

In the Audio devices and Driver configurations there's no option to select this as being Mono or Stereo.

I really need assing 1+2 as being an stereo input.

Some ideas?

Thanks in advance

[Sock Monkey]

. You sure that’s the ASIO driver?   Not Asio4all? 

[57Gregy]

2 hours ago, Gilberto Strapazon said:

I have an USB audio interface Behringer UMC202HD connected to a Roland M-16E mixer and so to my synthesizers.

PC is an I7, Windows 11 and Sonar Bandlab.

All drivers and softwares are updated to current version

The current driver is BEHRINGER_UMC_Driver-V5.57.0

 

So here the problem:

Windows say the UMC202HD have 2 input lines.

Sonar show the options:

• Input 1 (Mono). This is my Left channel.
• Input 1+2 again show as Mono!
• Input 2 (Mono). This is my Right Channel.

 

And the result signal 1+2 is a very strange mix.

 

See attached image.

In the Audio devices and Driver configurations there's no option to select this as being Mono or Stereo.

I really need assing 1+2 as being an stereo input.

Some ideas?

Thanks in advance

My guess would be that the Behringer cannot deliver a stereo signal at 192k. Try a lower sample rate, like 48k.

[Glenn Stanton]

@Gilberto Strapazon in your image - it looks like you're using the WASAPI setting... 🙂 

definitely do the following checks (in order):

• UMC ASIO - set to 192K
• Windows OS sound setting - verify 192K - turn off any other sound targets/sources (my sound reference sometimes does weird)
• Cakewalk - set preferences to ASIO driver and sample rate 192K
• add Audio Track - select UMC ASIO S (stereo) - arm it and test recording

in my setup, the 202HD works as expected @ 192K  - stereo (as well as any of the other speeds below it (i didn't test 384K))

Edited Thursday at 05:50 PM by Glenn Stanton

[Sock Monkey]

 @Glenn Stanton   your screen shot shows what is missing from the OP. Theirs doesn’t say ASIO. That’s why I asked. Hopefully they have download the correct driver. 

[sjoens]

Check for this:

[Gilberto Strapazon]

Solved!

Thanks guys!

I desinstalled the unit again, disconected the cables, all this was done before.

But I found.

In the "Audio Options" anything results a Mono result. Except for the "Wasapi Shared", the only I was unaware. I see no reason for a exclusive versus shared option, for sure I need to read again the manual.

But now I get an stereo result.

Yeahhh!

 

[Sock Monkey]

Too bad seems the OP didn’t read our answers and is still using the wrong driver. 
 

For the sake of others who may read this. Driver facts: 

Audio interfaces  and Daw’s communicate and work together and  latency is only synced when using ASIO drivers.
Most all real audio interfaces have a manufacturer supplied driver that needs to be downloaded and installed from the manufacturer website. 
Audio interfaces that don’t have a driver should be avoided. 
Asio4all is not an option and same with Realtek ASIO. They are known to cause issues with Cakewalk. 
 

If you don’t own an interface then use Windows WASAPI drivers. 
Shared is just that, you can run other audio apps at the same time and they share the driver. 
Exclusive is just that. The app will have exclusive use and other apps won’t have sound. But Exclusive mode has lower latency than shared. But still not as low as ASIO. 
 

Behringer web site can be misleading as it might direct you to the Asio4all driver. but keep looking as they do have a good ASIO driver for most of their interfaces and the X series mixers. 
 

It because the company is very Mac oriented and Macs have their own drivers. 

Edited yesterday at 05:52 AM by Sock Monkey