Steinberg UR242

[IvDen]

OBS 27.1.3
Win 10 20H2/19042.1466

Plugin Version
3.1.0

Describe the bug

Choose Device: Yamaha Steinberg USB ASIO
OBS Chanel 1: UR242 Input 2 // or 1/3/4
I has no signal on line but i see it in Steinberg Control Panel

If i use in OBS Line (Steinberg) w/o ASIO i got a signal.

Log:
2022-01-26 18-03-17.txt

[Andersama]

The error from the log appears to be from here:
https://github.com/juce-framework/JUCE/blob/0abbba3b18c3263137eeaeaa11c917a3425ce585/modules/juce_audio_devices/native/juce_win32_ASIO.cpp#L588

Which is roughly the earliest type of failure you could possibly have, the drivers might not be to spec if the library can't setup input buffers automatically. These are the function calls from the asio api. If you have audio software that makes use of ASIO like a daw and your device works normally let me know.

[IvDen]

@Andersama i'm using Adobe Audition (latest) w/ ASIO and it work good.

[Andersama]

In Adobe Audition does the program allow you to specify the channels / sample rate etc?

[IvDen]

@Andersama Yes it does.

[Andersama]

Ok, I'd make a note of those settings, I don't remember if we had a debug build which logged everything, but the next step would be to double check that the settings reported by the device match up with the ones you have which work. If you're inclined programmatically you could log the settings the plugin is about to use here:

obs-asio/src/asio-input.cpp

Line 357 in cef5c61

sample_rate = device->getCurrentSampleRate();

[IvDen]

@Andersama i'm trying to resolve an error w/ false LIBOBS_FOUND:
CMake Error at external/FindLibobs.cmake:106 (message): Could not find the libobs library Call Stack (most recent call first): CMakeLists.txt:19 (include)
while building the plugin w/ my additional log.
Could you suggest how can I solve this?

[Andersama]

I can't quite remember because it's been so long, but I think that's because the repository is setup to build as an external plugin so it expects to be able to find a header file for libobs. When I used to do this though I'd normally build the plugin directly as part of obs. I'm pretty sure it was easier. I think all you had to do was add the folder underneath the obs plugin directory and add it as a subdirectory, you'll likely need to edit the CMakeLists.txt file eaither way.

Ok I vaguely remembered, we definitely used to build it as an internal plugin, see how pkv built it here:
https://github.com/pkviet/obs-studio/tree/master/plugins

If you're able to build and compile that fork, you'll be able to mess with the plugin's source code as needed.