Replies: 5 comments 8 replies
-
|
In the OBS log files it's having an issue loading the DLL. The DLL exists in the correct folder but maybe there is something it depends on missing? 20:06:05.000: LoadLibrary failed for '../../obs-plugins/64bit/obs-asio.dll': The specified module could not be found. |
Beta Was this translation helpful? Give feedback.
-
|
I should probably leave a note of this on the discussions side. The long story short is between major versions of OBS plugins can break, where plugins and their dlls are supposed to be has changed. I'm not actively maintaining the plugin, because the underlying source code should just work. It just needs to be recompiled every once in a while against the newer versions. To that end, the last commits were added to do some automation so that I wouldn't have to do any of that anymore. Pretty sure it's supposed to be just a git commit and tag at this point. If the gui seems different you've likely hopped between older versions of the plugin based on a different library. The current one is based on Juce, in theory the plugin should just be a seamless experience where you can pick any device and it just uses the current device's settings as is. If that doesn't work for you, you may have to end up compiling the one that uses the bassasio library yourself. I'm not keeping track of or interested in what OBS is doing. I'm an ex-obs developer. Although I originally wrote the plugin originally for myself, it's really for most of you guys at this point. |
Beta Was this translation helpful? Give feedback.
-
The plugging is two versions behind OBS v29. |
Beta Was this translation helpful? Give feedback.
-
|
The OBS 28 release of the plugin should work without issue in OBS 29. https://github.com/Andersama/obs-asio/releases/tag/v3.1.1 Yes, the plugin is no longer actively maintained, but it should still work fine. |
Beta Was this translation helpful? Give feedback.
-
|
Well, all things considered the plugin's been at a fairly stable state for years at this point. I can't even remember when we switched to using Juce I'm pretty sure that was maybe a year in and the code's not exactly changed much since. I had the plugin code basically set at that point. It's kinda funny to hear someone call it abandonware after two major revisions. I think I wrote it at v17 and maybe a year later we'd have been at v18? It's been like this for a LONG time. If the commit history on this repo weren't a complete mess I could find out real quick, unfortunately this one doesn't tell the full story because the original's buried in my obs fork and this repo's technically my friend's. There was some chaos involving two people working off of two of their own repos in two different build environments very rapidly. When I say I'm not actively maintaining it, it's in part because there's nothing to do really, and partly because I'm genuinely disinterested at this point. The sticking point is mostly due to the unstable nature of asio and various device drivers not playing nice. For example the focusrite devices I've owned over the years all suffered similar intermittent problems (had nothing to do with the plugin). That and that obs can break things (that's what major revision numbers hint at) basically means for all of you who'd like to use the plugin are at the mercy of factors out of my control (I couldn't fix those problems even when I was interested). The version bumping breaking things usually has to do with the virtual interface being changed which means every plugin would need to be recompiled anyway, not every major revision's done this, but doing that definitely deserves a bump to the major revision. In short if you jump to a new shiny version X.0.0 you can expect plugins to suddenly stop working. I'm not exactly surprised people pop up around major version releases upset that things stop functioning, obviously on your end it seems like the third party messed something up. You'd never know that's what's going on really because the internal plugins are of course built with the new version so of course they'll still work. When for example I was originally putting this plugin together my development environment was that I just had it as part of my own custom obs build. If people were comfortable building plugins themselves the version bumps would be a non issue. Fortunately, I think at this point it's trivial to recompile the plugin as needed (anyone besides me could do it without having to learn to compile obs now), and Wizard here would be way more on the ball as to when obs has broken things. So all's good, not abandonware yet~ |
Beta Was this translation helpful? Give feedback.
-
|
You could just mentioned it. |
Beta Was this translation helpful? Give feedback.
-
|
I would not trust a binary executable from a non-maintainer, but sure. Let me check if the original author didn't already posted a compiled binary executable installation file |
Beta Was this translation helpful? Give feedback.
-
|
Since I/we are not expecting an updated version for OBS V29 and the future, can someone point me to instructions on how to compile OBS and obs-asio. I don't even know what language either is written in. I have done C# development 10 years ago, but retired from development when javascript became a first class language, which is a joke to me. |
Beta Was this translation helpful? Give feedback.
-
|
The https://github.com/Andersama/obs-asio/releases/tag/v3.1.1 should work just fine in OBS 29 without any need for recompile. |
Beta Was this translation helpful? Give feedback.
-
|
@charlestek in theory you could do what I could do now to "build" it yourself by setting off the automation script. If you forked the thing yourself and then push a git tag (you may need to update the automation script with a new url somewhere so that it knows to build against your fork, not sure) it should start a build in the cloud somewhere and give you back some links to artifacts to download. That and/or if you're on windows you can clone obs, follow the steps to get build obs building, clone this repository into the plugins directory, add the plugin to the CMakeLists.txt script in the plugins directory. You'll see a lot of There's an extra step you'll need which is to build Juce since you're building it yourself you don't have to go out of your way to replace the asio sdk header with your own, but you can if you'd like. The automated build has a fork of Juce specifically with some edits setup for that to happen. For windows development MSVC has builtin cmake support, makes opening/building cmake projects targeted for windows real easy to build, if you open the project folder it should run an initial cmake command that'll setup the project and then you may need to fill in some variables in the configuration editor. Not really a linux based developer so if that's your platform I don't know what the setup would be, but it's all c/c++ development with cmake, and purportedly it's cross platform. |
Beta Was this translation helpful? Give feedback.
-
|
@RicardoEscobar Do you think you could touch on the process you used to compile the plugin yourself? I attempted to compile it last night and it might be due to my inexperience with juce/projucer and cmake, but I kept getting cmake errors. |
Beta Was this translation helpful? Give feedback.
-
|
Ah, the reason I thought it doesn't work, is that this blog post says so....: |
Beta Was this translation helpful? Give feedback.
-
After upgrading to the latest OBS (v28) I lost my ASIO menu in OBS studio and get an error on startup that the plugin obs-asio has failed to load. This may be fixed in later releases of OBS (hopefully), but as of now for a workaround I tried to uninstall OBS v28 and revert back to v27 where obs-asio was working fine. Going back to OBS v27 and reinstalling the obs-asio plugin gets rid of the load error but I no longer have my ASIO OBS file menu and don't have any ASIO sources available to choose from within OBS.
I use this setup to Stream and Collaborate with other songwriters using my UAD Apollo x4 and this has enabled me to do this the way I need to. Is there any chance you know of this issue and if you will need to fix anything on this plugin? I'm not sure how many people are using this but it seems that OBS developer community doesn't have testing this in whatever test suite they use to bless release candidates? Have you ever posted in their git about adding a basic verification test for your plugin?
Beta Was this translation helpful? Give feedback.
All reactions