atkAudio Plugin

atkAudio Plugin 0.34.0

Hello, sorry to bother but would anyone know a quick way to basically use atkAudio to Bypass Windows Audio and directly take the Mic input instead, kinda like an ASIO setup I think, but with atk instead?

I have a Behringer Audio Interface that is suffering from intermittent drops, and their site recently also has been having issues in in downloading drivers (not sure if they would help) so I'm curious if there is a way I could save my situation.

Cheers!
i dont think switching from windows audio to asio, or any other driver type, would help in this case. Sounds more like hardware performance issue, or the audio interface itself is starting to fail.
 
i dont think switching from windows audio to asio, or any other driver type, would help in this case. Sounds more like hardware performance issue, or the audio interface itself is starting to fail.
I know exactly what you mean, but I tested out 3 OBS-Likes Softwares and Audacity to make sure.

All 3 OBS-Like Softwares had the same exact drops (audio suddenly drops or putters out for like 2-10ms) at intervals.

Audacity was completely clean (even if I on purpose set the wrong settings to cause drifting) and it held the audio channels.

If I disconnect and reconnect my XLR Cable with the Interface, the audio works well in OBS, until the next time I boot up OBS again.

If I connect my Microphone directly as a USB (but limited to 16 bit) it works without any issues it seems like regardless of setup.

Everything I read so far sounds like that infamous "Windows Audio - external Audio Interface" driver issue that seems to plague some people (especially in Windows), and the only way I can be sure if it isn't something else (DPC Latency-GPU video recording stuff) is by trying the ASIO-Like setup.

I read from some people that setting up a lightweight DAW could be another solution with the same CPU cost, but that would be beyond my abilities/budget right now.

My only solution I could test out would right now would be atkAudio, but everytime I try and setup my Microphone as the Input and set the Output, OBS seems to not like that, and ends up locking up for a minute or two (since my previous experience with atk was to do the simple sidechains, ducks, filters).

Sorry if it's a bother, cheers in advance!
 
Hello! After installing new updates plugin, the audio plugins always stay on top. Before they only stay on top while I set them up, saved and closed. Now they are always flying next to my OBS cluttering the screen... Did something change? IS there a way to hide them?
 
Hi,

It's a great product and I looking forward to converting over to using it fully but I am getting a number of crashes when renaming and duplicating scene collections and when changing scene collections .

I am using OBS 32.1.2 and atkAudio 0.33.0 and now 0.32.2 with the same results.

I have reduced the scene collection to one scene which has one atkAudio Source Mixer with default settings and one PluginHost2 filter containing the default Audio Input and Audio Output, MIDI Input and MIDI Output and one OBS Output. When renaming or duplicating this Scene selection I get the attached crashes.

thanks,

DavidG
 

Attachments

Hi,

It's a great product and I looking forward to converting over to using it fully but I am getting a number of crashes when renaming and duplicating scene collections and when changing scene collections .

I am using OBS 32.1.2 and atkAudio 0.33.0 and now 0.32.2 with the same results.

I have reduced the scene collection to one scene which has one atkAudio Source Mixer with default settings and one PluginHost2 filter containing the default Audio Input and Audio Output, MIDI Input and MIDI Output and one OBS Output. When renaming or duplicating this Scene selection I get the attached crashes.

thanks,

DavidG
https://github.com/atkAudio/PluginForObsRelease/releases/tag/0.33.1 try this. Please test extensively and report if there are any issues.
 
atkAudio updated atkAudio Plugin with a new update entry:

0.34.0 Pre-release

  • update to JUCE 9
  • Tools > atkAudio Midi to OBS
    • use generic MIDI controller for volume, scene change, transitions
    • parameter feedback for motorized faders/buttons (mute, volume, monitoring)

Read the rest of this update entry...
 
Thanks for the plugin - it is doing the whole capture side of a 3rd-order ambisonics project for me, 16 discrete channels from REAPER into OBS as four tracks of four. Posting the one step that took me a while to find, in case it saves someone the search.

My setup: Windows 11, OBS Studio 32.2.1, atkAudio 0.33.1, REAPER 7.78 over ReaRoute.

An OBS Output node is stereo by default, and nothing in the OBS source's Properties changes that. The control is inside the PluginHost2 graph: right-click the node itself (not a port), choose Configure Audio I/O, and set the Input Configuration's Channel Layout - I used Discrete #4. Repeat for every node; each one left at stereo quietly costs two channels.

08_PluginHost2-configure-audio-io.png

right-clicking the node itself, not a port

09_PluginHost2-discrete-4.png

Input Configuration has a numbered bus; Output Configuration below it has only + and -, no bus. Stereo is ticked, Discrete #4 highlighted.

Only the Input Configuration matters. The dialog draws an Output Configuration too, but there is no bus under it, which matches ObsOutput.h declaring an input bus and no output bus.

Why it is worth knowing: with nodes at stereo and OBS offering six tracks, the ceiling is 6 x 2 = 12 channels, so 16 is simply unreachable however many nodes you add. And there is a hard per-source ceiling of 8: processBlock casts the input-bus count to OBS's speaker_layout, and anything above MAX_AUDIO_CHANNELS becomes SPEAKERS_UNKNOWN, which OBS documents as falling back to stereo. So the dropdown will cheerfully offer 7th Order Ambisonics, but nothing wider than 7.1 (8 channels) can actually cross into an OBS source. In my project I only needed 4 per node to match one OBS track, but that ceiling is worth knowing if you needed more. A wide bus might still be useful inside the graph itself if you are using it to host VSTs.

10_PluginHost2-wired-graph.png

the finished graph, one Audio Input fanned out to four OBS Output nodes, four channels each

One question: is the stereo default deliberate, or is following the OBS track width something you would consider? Happy to open a PR adding a line about this to the README either way.

Two OBS-side gotchas that cost me time but are not yours: Settings > Audio > Channels sets the width of every track, and REAPER's engine idles when OBS takes focus unless the tracks are record-armed.

(This came out of an open-source project I run streaming 3rd-order ambisonics with 360 video - full setup instructions at https://github.com/mormegil6/hoa-360-stream/blob/main/docs/obs-windows.md, if you're curious.)
 
Thanks for the plugin - it is doing the whole capture side of a 3rd-order ambisonics project for me, 16 discrete channels from REAPER into OBS as four tracks of four. Posting the one step that took me a while to find, in case it saves someone the search.

My setup: Windows 11, OBS Studio 32.2.1, atkAudio 0.33.1, REAPER 7.78 over ReaRoute.

An OBS Output node is stereo by default, and nothing in the OBS source's Properties changes that. The control is inside the PluginHost2 graph: right-click the node itself (not a port), choose Configure Audio I/O, and set the Input Configuration's Channel Layout - I used Discrete #4. Repeat for every node; each one left at stereo quietly costs two channels.

View attachment 120768
right-clicking the node itself, not a port

View attachment 120769
Input Configuration has a numbered bus; Output Configuration below it has only + and -, no bus. Stereo is ticked, Discrete #4 highlighted.

Only the Input Configuration matters. The dialog draws an Output Configuration too, but there is no bus under it, which matches ObsOutput.h declaring an input bus and no output bus.

Why it is worth knowing: with nodes at stereo and OBS offering six tracks, the ceiling is 6 x 2 = 12 channels, so 16 is simply unreachable however many nodes you add. And there is a hard per-source ceiling of 8: processBlock casts the input-bus count to OBS's speaker_layout, and anything above MAX_AUDIO_CHANNELS becomes SPEAKERS_UNKNOWN, which OBS documents as falling back to stereo. So the dropdown will cheerfully offer 7th Order Ambisonics, but nothing wider than 7.1 (8 channels) can actually cross into an OBS source. In my project I only needed 4 per node to match one OBS track, but that ceiling is worth knowing if you needed more. A wide bus might still be useful inside the graph itself if you are using it to host VSTs.

View attachment 120770
the finished graph, one Audio Input fanned out to four OBS Output nodes, four channels each

One question: is the stereo default deliberate, or is following the OBS track width something you would consider? Happy to open a PR adding a line about this to the README either way.

Two OBS-side gotchas that cost me time but are not yours: Settings > Audio > Channels sets the width of every track, and REAPER's engine idles when OBS takes focus unless the tracks are record-armed.

(This came out of an open-source project I run streaming 3rd-order ambisonics with 360 video - full setup instructions at https://github.com/mormegil6/hoa-360-stream/blob/main/docs/obs-windows.md, if you're curious.)
Nice! In future releases nodes in Ph2 graphs will default to OBS channel layout.
 
FYI this update has broken DeviceIO for me, it doesn't bring any audio in from input when an ASIO device is selected. Rolled back to 33.1 and it works fine.
 
Back
Top