atkAudio
Member
https://github.com/atkAudio/PluginForObsRelease/releases/tag/0.36.0 does this work better?
- Thread starter atkAudio
- Start date
No, I'd just started trying that before your message but it's still the same
atkAudio
Member
ok. With 0.36.0 I'm able to route audio with DeviceIo2 to Voicemeeter default virtual input, and from VM to hardware. There was a bug where device enumeration would hang if Voicemeeter had taken presumably exclusive access to audio device, but that should now be fixed.
I'm using the full 5 inputs to monitor and adjust sound levels then routing that to Zoom. My aim is to get rid of Voice Meeter and go direct from OBS to Zoom but I still need to use a virtual cable. Even that simpler second method isn't working even with 0.36.0
I'll make sure I'm trying the latest 0.36.0 and let you now
Tyr808
Member
Hi! A heads-up in case anyone else lands here with the same symptom.
After updating to OBS 33 (Windows 64-bit), OBS crashed on launch with a dialog titled "JUCEWindow: obs64.exe – stack-based buffer overrun". Because the JUCE name was in the title, I assumed it was atkaudio. I was on 0.35 and also tried the 0.36.0 pre-release, with the same crash on both.
It turned out atkaudio wasn't the cause. I split my scene collection into halves and tested each one until I found the problem. Removing every atkaudio source still crashed, while a blank collection with a fresh PluginHost2 and my full Waves VST3 chain loaded fine. The real culprit was xObsAsyncImageSource 1.1.0: any collection containing an "Image (Async)" source crashed on launch. Once I switched those sources to the built-in Image source and disabled that plugin, OBS 33 launched normally with my full atkaudio setup (MOTU M2 ASIO through PluginHost2) intact.
My guess is that the JUCE window just happened to own the thread or window when the overrun was caught, so the dialog took its name. I'm posting this so nobody chases atkaudio for that error. Thanks for the plugin, it's the core of my audio setup!
After updating to OBS 33 (Windows 64-bit), OBS crashed on launch with a dialog titled "JUCEWindow: obs64.exe – stack-based buffer overrun". Because the JUCE name was in the title, I assumed it was atkaudio. I was on 0.35 and also tried the 0.36.0 pre-release, with the same crash on both.
It turned out atkaudio wasn't the cause. I split my scene collection into halves and tested each one until I found the problem. Removing every atkaudio source still crashed, while a blank collection with a fresh PluginHost2 and my full Waves VST3 chain loaded fine. The real culprit was xObsAsyncImageSource 1.1.0: any collection containing an "Image (Async)" source crashed on launch. Once I switched those sources to the built-in Image source and disabled that plugin, OBS 33 launched normally with my full atkaudio setup (MOTU M2 ASIO through PluginHost2) intact.
My guess is that the JUCE window just happened to own the thread or window when the overrun was caught, so the dialog took its name. I'm posting this so nobody chases atkaudio for that error. Thanks for the plugin, it's the core of my audio setup!
atkAudio
Member
Release 0.36.0 · atkAudio/PluginForObsRelease
improve PluginHost2 standard editor features groups better handling of missing plugins/device direct access to parent source Chord Analyzer plugin analyze chords from MIDI provides VST3 chord con...
github.com
Hi, The 0.36.0 above and the release 0.35.0 and the last 0.35.0 release candidate I downloaded don't work with Eugene Muzychenko VAC cables. The prior 0.35.0 release candidates and prior releases all work with VAC cables.I've now also now rebuilt and reuploaded the files to ensure those are indeed the latest.
Release 0.36.0 · atkAudio/PluginForObsRelease
improve PluginHost2 standard editor features groups better handling of missing plugins/device direct access to parent source Chord Analyzer plugin analyze chords from MIDI provides VST3 chord con...
regards,
David
Tyr808
Member
What's your usage with it looking like? I actually use that exact virtual audio cable myself. My set up is using pluginhost2 to have my audio interface operate in ASIO mode and bypass most of OBS's audio system. This relies on VAC to handle the devices necessary to accomplish the routing though. My Audio interface is a Motu M2.
I have no idea if I've set things up in a standard fashion or not, I'm entirely self-taught on audio stuff. Essentially the goal here is to use ASIO, have every audio source separated so I can have different streaming locations receiving different audio as well as having everything on tracks for a recording so I can get rid of things like a friend on discord being loud in a moment I wanted a clip of, etc.
The other thing I use this for is to feed my processed mic back into a VAC so other programs can receive that instead of only OBS having the nice mic.
If there's anything you want me to test or confirm for you as far as VAC settings go, let me know!
VAC v4.71
atkAudio
Member
Eugene Muzychenko VAC should now work
Release 0.36.0 · atkAudio/PluginForObsRelease
improve PluginHost2 standard editor features groups better handling of missing plugins/device direct access to parent source Chord Analyzer plugin analyze chords from MIDI provides VST3 chord con...
github.com
Exclusive mode is still an issue which I've had to use as Low Latency mode would not keep different audio sources syncedEugene Muzychenko VAC should now work
Release 0.36.0 · atkAudio/PluginForObsRelease
improve PluginHost2 standard editor features groups better handling of missing plugins/device direct access to parent source Chord Analyzer plugin analyze chords from MIDI provides VST3 chord con...
Wow, that is impressive.
I have a RodeCaster Pro unit with 4 mics for which I was using Asio4All and OBS-Asio to split out the Mics. Asio4All would fail at times requiring a reboot in the middle of a broadcast so I was very happy when atkAudio came on the scene.
Three of the mics are used for both singing/music and audience members speaking. To pickup the audience talking I have a lot of VST3 plugins to pick up the quieter voices but filter out non speech sounds. So all of my wiring is done per source to spread it out.
I also pickup recorded music played via VLC (I still don't know why we can't have a decent playlist media player in OBS), and audio through the Media source. So there is a bit of level matching and syncing between audio sources.
I've just bought a Korg nanoKontrol2 to help centralise sound levels and media playing but I'm wiring it in through the atk Midi control. What are you using inside the pluginHost2?
regards,
David
Tyr808
Member
Thanks! I just built this entire filter graph inside of an atkAudio Ph2 OBS Output node source because I didn't know where to actually plant it so to speak. It's basically a dummy source that exists solely to have the PluginHost 2 filter attached to it.
It all basically starts from my audio interface and mic.
The next node is my waves VSTs for my mic cleanup, the DeviceIO2 is how I get that cleanup mic to route back out of atkaudio and into a virtual audio cable to then use the line on the recording end of that same VAC to operate as the mic device that I'd select in game or discord.
The "My Monitor" is just directly outputting on my Motu M2 over asio into my headphones, and then the "phDesktop" and so on is the way that it feeds into OBS (OBS output source within the filter graph) so I can have those different sources separated and able to be applied to tracks. With the Korg Nanokontrol 2, I have it set so the faders control the various audio sources, and then the knobs above each fader are the gain for my end only, if I wanted a difference in my personal music levels vs stream, etc. or so I can disable my mic's hardware monitor and virtually monitor the processed chain and make sure it sounds clean. It's low latency enough that I *could* speak through it, but the zero latency hardware monitoring path built into my m2 is much more desirable.
atkAudio
Member
Release 0.36.0 · atkAudio/PluginForObsRelease
improve PluginHost2 standard editor features groups better handling of missing plugins/device direct access to parent source Chord Analyzer plugin analyze chords from MIDI provides VST3 chord con...
github.com
this should handle exclusive windows audio devices