atkAudio
Member
atkAudio updated atkAudio Plugin with a new update entry:
0.26.1
Read the rest of this update entry...
0.26.1
Read the rest of this update entry...
- Thread starter atkAudio
- Start date
Hey there again. Looks like the issue with the sound is gone. Thank You for Your work - as a sound guy I really appreciate the plugin. Please, let me know what is you way to be supported back. Thanks again
p.s. A question here: I miss the sound not to be present in the OBs's 'Virtual Camera' ...A lot of time I need to send a video/audio to 'Teams', Zoom' for example, so my question is: is there a way to have an output that will embed the sound in the 'virtual camera' feed?
Hi, love the plugin.
I'm on windows 11, version 0.26.1.
My overall setup:
I have an external audio interface, where I use input 1 for a microphone, inputs 3/4 for additional input, and then various other audio captures. I output back to the audio interface for monitoring. I've ended up using the Plugin Host2 graph to handle the routing between OBS and my interface. I do a sub mix of all my other sources (plus inputs 3/4), and then sidechain that against my mic, which then all goes into a main mix, which is the only thing enabled for output to OBS' tracks. I have an additional route from the main mix back to my audio interface for monitoring. I'm avoiding monitoring via OBS' built-in functionality since it's more latent, and introduced huge drift/sync problems last time I tried it).
A few things I've come across:
Finally, more of a feature request:
A post-fader option in the source mixer would be huge. Since I'm only routing the main mix to OBS' output, it would let me use all the faders in OBS' audio mixer rather than having to go into the source mixer's properties to adjust gains. I guess I could route everything into a second host2 graph instead of using a source mixer, because it has a "Follow Source Volume" option there, but that's a lot less convenient.
I'm on windows 11, version 0.26.1.
My overall setup:
I have an external audio interface, where I use input 1 for a microphone, inputs 3/4 for additional input, and then various other audio captures. I output back to the audio interface for monitoring. I've ended up using the Plugin Host2 graph to handle the routing between OBS and my interface. I do a sub mix of all my other sources (plus inputs 3/4), and then sidechain that against my mic, which then all goes into a main mix, which is the only thing enabled for output to OBS' tracks. I have an additional route from the main mix back to my audio interface for monitoring. I'm avoiding monitoring via OBS' built-in functionality since it's more latent, and introduced huge drift/sync problems last time I tried it).
A few things I've come across:
- In the host2 graph, I have input 1 routed to an OBS output, and 3/4 to a second OBS output. If I close and re-open OBS, the wiring for inputs 3/4 to the second OBS output disappears, and I need to manually connect them again. Input 1 to its output persists just fine.
- I get names like "Ph2Out1" and "Ph2Out2", which I'd like to rename. And, while I can rename them in obs, when I restart obs, it recreates them under the original auto names, while ALSO leaving non-functioning sources with the names I had changed them to.
- Additionally, if I had put them in a group, they are recreated outside of the group. (Though, if I do not rename them, they seem to stay in the group).
Finally, more of a feature request:
A post-fader option in the source mixer would be huge. Since I'm only routing the main mix to OBS' output, it would let me use all the faders in OBS' audio mixer rather than having to go into the source mixer's properties to adjust gains. I guess I could route everything into a second host2 graph instead of using a source mixer, because it has a "Follow Source Volume" option there, but that's a lot less convenient.
atkAudio
Member
PluginHost2 is undergoing major overhaul, so the current helper/source model might be deprecated in the future.
Meanwhile try this https://github.com/atkAudio/PluginForObsRelease/releases/tag/0.27.1 . Added the Post-Fader to Source Mixer.
atkAudio
Member
atkAudio updated atkAudio Plugin with a new update entry:
0.27.1
Read the rest of this update entry...
0.27.1
Read the rest of this update entry...
atkAudio
Member
atkAudio updated atkAudio Plugin with a new update entry:
0.30.1-rc1 Pre-release
Read the rest of this update entry...
0.30.1-rc1 Pre-release
DeviceIo2 with advanced routing
PluginHost MIDI, and audio routing
PluginHost2 internal multithreading
PluginHost2 bug fixes
PluginHost optional multithreading (adds latency)
general UI improvements and bug fixes
improved internal audio and MIDI routing
and more
Warning: includes compatibility breaking changes, needs plugins re-scans, etc.
Feel free to report bugs.
Read the rest of this update entry...
hey I can't really confirm this yet. but I strongly FEEL like v 27 is causing audio cut outs. take it with a grain of salt. I've regularly encountered these issues over years with different hardware. never knew how to fix it. I just know it started again now after I went to 0.27. uninstalled and re-installed 26. but at the moment it feels like it's also happening there
there is also definitely an issue (both v 27 and 26) that OBS won't shut down properly if the plugin is active. I always get the notification to start in safe mode. I deactivated the atk plugin with the new plugin manager, closed obs (wouldn't close properly at first and gave me the safe mode notification), ran in normal mode, verified atk was off, closed obs and restarted again. now it worked. after re-activating atk in the plugin manager and restarting because of the OBS prompt, obs started like normal. I closed obs and restarted - OBS did not properly shut down
I've had a feeling before that if you save your filter graph and atk tries to load it again next time it causes some issues. one of the things is that it will try to keep re-creating Ph2Out1. But right now even when I stopped using the saved filtergraph, I can't get rid of the OBS startup issue
I've had a feeling before that if you save your filter graph and atk tries to load it again next time it causes some issues. one of the things is that it will try to keep re-creating Ph2Out1. But right now even when I stopped using the saved filtergraph, I can't get rid of the OBS startup issue
atkAudio
Member
https://github.com/atkAudio/PluginForObsRelease/releases/tag/0.30.1 have you tried this?
I haven't because I don't want to have to potentially re-do my entire setup right now.
also I have found in latencymon that it looks like issues with wdf0100. so definitely none of the audio drivers directly. therefore it might not actually be an issue with your app. I'm trying to pin point it further. at the moment i'm suspecting a hardware issue in particular with a KVM switch.
I'll try and keep you posted but for now probably your application is fine. I'll open obs and have it run while latencymon keeps observing to try and verify this. currently on version 0.26
edit: although the safemode thing keeps happening :D
atkAudio
Member
it could be in the plugin as well, but the shutdown should be clean in 0.30.1-rc.
I have since uninstalled the plugin. still insane issues every once in a while with latency spikes. I can't pin point what it is but I'm also extremely unlucky and / or unskilled with these things. multiple pieces of hardware over more than a decade and I'll eventually run into something like that. I'd be quite confident at this point that your application isn't what was causing it
atkAudio
Member
Well, in that case good luck. "It'll get sorted out eventually." :)
Thank you. I think I've found it. The spotify app. I remember others and me having this issue in the past. I noticed that it regularly spiked during song changes. But sometimes even just starting to play or skimming through tracks with the slider caused it. HW accel on or off didn't matter. Tried the web app and no lag spikes. Then I uninstalled spotify and re-installed with winget but made sure to use the app ID Spotify.Spotify instead of the MS Store version. Not sure if that matters but Microsoft = bad I guess lol. So far so good. As always thanks for your feedback, it eventually helped me pin point the issue further!
I had been using the old
It has not been maintained and this plugin looks promising.
Is there any tutorial for ASIO mic input routing? Nothing I do seems to workk. Added as device, then applied filter for I/O and can only get Input 1 to send audio through this plugin (same as standard windows audio device).
This is not VST, this is purely an ASIO mic input device.
andersama ASIO plugin to enable access to my Tascam Series 208i (20 input / 8 output) device.It has not been maintained and this plugin looks promising.
Is there any tutorial for ASIO mic input routing? Nothing I do seems to workk. Added as device, then applied filter for I/O and can only get Input 1 to send audio through this plugin (same as standard windows audio device).
This is not VST, this is purely an ASIO mic input device.
Seeing as how I cannot edit my old post:
-Create ATK Mixer (dummy does nothing)
-Keep defaults
-Apply filter for devide I/O to the mixer
-Open I/O filter and select ASIO, then my TASCAM Series 208i ASIO
-Check Input 1, Input 2, Input 3, Input 4 (mics 1-4)
-Check nothing for output (is it necessary?)
I can see levels of mic 1 when input 1 is checked, but it is "left" channel; similarly if I check mic 2 the right channel fills according to the input from mic 2; mic 3 (when checked) shows a small green bar at the bottom for the audio device in OBS but there is no bar (as I'd assume the channel cannot display as OBS only has L and R channels for each audio device). Forcing Mono in the ATK mixer and in OBS does not fix this. Mic 1 is recorded as the left channel, mic 2 is recorded as right channel, and mic 3 is not recorded. If I uncheck mic 2, mic 3 becomes the right channel.
In addition, there is a slight <1s delay compared to the old andersama plugin.
To explain the old behaviour: previously I'd be able to add an ASIO device input in OBS, then select the ASIO controller device and then a source for the L channel and another for the R channel (so to get joint stereo you'd just use the same source for both). In this case I could have each mic be a separate input listed in OBS.
There does not seem to be a similr way using this plugin: after creating an device i/o, you cannot make another input in OBS that affects the same device i/o or you get an error the device cannot start. So effectively one device i/o filter can "touch" the AIO device at a time.
-Create ATK Mixer (dummy does nothing)
-Keep defaults
-Apply filter for devide I/O to the mixer
-Open I/O filter and select ASIO, then my TASCAM Series 208i ASIO
-Check Input 1, Input 2, Input 3, Input 4 (mics 1-4)
-Check nothing for output (is it necessary?)
I can see levels of mic 1 when input 1 is checked, but it is "left" channel; similarly if I check mic 2 the right channel fills according to the input from mic 2; mic 3 (when checked) shows a small green bar at the bottom for the audio device in OBS but there is no bar (as I'd assume the channel cannot display as OBS only has L and R channels for each audio device). Forcing Mono in the ATK mixer and in OBS does not fix this. Mic 1 is recorded as the left channel, mic 2 is recorded as right channel, and mic 3 is not recorded. If I uncheck mic 2, mic 3 becomes the right channel.
In addition, there is a slight <1s delay compared to the old andersama plugin.
To explain the old behaviour: previously I'd be able to add an ASIO device input in OBS, then select the ASIO controller device and then a source for the L channel and another for the R channel (so to get joint stereo you'd just use the same source for both). In this case I could have each mic be a separate input listed in OBS.
There does not seem to be a similr way using this plugin: after creating an device i/o, you cannot make another input in OBS that affects the same device i/o or you get an error the device cannot start. So effectively one device i/o filter can "touch" the AIO device at a time.
atkAudio
Member
https://github.com/atkAudio/PluginForObsRelease/releases/tag/0.30.1 try this. It has DeviceIo2 which might be able to do what you're describing. You can also use PluginHost2 as patch bay to access all channels of audio device, from Options and so on.
atkAudio
Member
atkAudio updated atkAudio Plugin with a new update entry:
0.30.1
Read the rest of this update entry...
0.30.1
Read the rest of this update entry...
jonesnatelye
New Member
Thank you very much for sharing this GitHub link. The plugin from the 0.30.1 release sounds really worth trying, especially with the DeviceIo2 feature you're mentioning, which has the capability to do exactly what you need. Additionally, utilizing PluginHost2 as a patch bay to fully access audio device channels through the Options menu also opens up many interesting customization possibilities. For OBS users needing complex multi-channel audio management solutions, this plugin could become a powerful support tool in improving stream or recording quality.