atkAudio Plugin

atkAudio Plugin 0.31.13

Ran two podcasts yesterday (90+ minutes each) and neither the Active output channels: nor the Active input channels: switched away from their assignments!

One thing we did notice though was a "click" or "pop" would sometimes be audible when we would change scenes in OBS. I saw this issue discussed earlier in this thread (I think? not sure if its related) but I was wondering if this has anything to do with some of the settings in the checkboxes shown here:
1770061428541.png
Can you explain what each of these checkboxes does?

I am wondering if we should un-tick the Follow Scene item since we do not use scene visibility to direct if the audio being captured from a source is being used. The audio from the scene is "always on" so should not change no matter what scene is live in the "Program".

Vern
 
Ran two podcasts yesterday (90+ minutes each) and neither the Active output channels: nor the Active input channels: switched away from their assignments!

One thing we did notice though was a "click" or "pop" would sometimes be audible when we would change scenes in OBS. I saw this issue discussed earlier in this thread (I think? not sure if its related) but I was wondering if this has anything to do with some of the settings in the checkboxes shown here:
Can you explain what each of these checkboxes does?

I am wondering if we should un-tick the Follow Scene item since we do not use scene visibility to direct if the audio being captured from a source is being used. The audio from the scene is "always on" so should not change no matter what scene is live in the "Program".

Vern
Make things simple:

Create a separate scene for audio, e.g. "Audio Scene".

Put all your audio sources and related filters etc into this "Audio Scene".

Then, use this "Audio Scene" as a sub-scene in your other scenes, where you want the audio to be active.
 
Make things simple:

Create a separate scene for audio, e.g. "Audio Scene".

Put all your audio sources and related filters etc into this "Audio Scene".

Then, use this "Audio Scene" as a sub-scene in your other scenes, where you want the audio to be active.

Though that does sound like a neat idea, I don't think that will work the way we are configured.

We use VDO.Ninja to host an online "room" for our cast members. VDO.Ninja then creates discrete URL for each cast member that delivers both their video and their audio. We use individual scenes for each cast member with an individual browser source. Each browser has its own atkAudio DeviceIo filter which allows us to capture a discrete audio signal from each cast member as an individual channel on our mixer. This works really well and allows us to manage each voice as a discrete signal and make individual adjustments for each cast member including EQ, compression, filtering, auto-mix, gating, side-chain compression and matrix signal routing. The setup is like this:
  • Host- XAIR ASIO- Output Channel- 9
  • Co-Host- XAIR ASIO- Output Channel- 10
  • Backup Host- XAIR ASIO- Output Channel- 11
Then, each of these video+audio sources is used in *dozens* of scenes in different combinations with different visibility, different transforms, different combinations of visibility, different masking, and even different aspects (we simulcast to vertical as well as horizontal video).

If I understand your suggestion, I would be placing all three browser sources in a single "Audio Scene" which would preclude the video component of each browser source from being used as individual sources in the (literally) dozens of other scenes we have created to mix & match layouts.

I am guessing the reason for the occasional "pop" is that the atkAudio DeviceIo filter is restarting/reinitializing or otherwise changing its stream delivery when I change scenes in OBS..? If this is the case, would unchecking the "Follow Scene" checkbox keep this from happening?

Vern
 
Though that does sound like a neat idea, I don't think that will work the way we are configured.

We use VDO.Ninja to host an online "room" for our cast members. VDO.Ninja then creates discrete URL for each cast member that delivers both their video and their audio. We use individual scenes for each cast member with an individual browser source. Each browser has its own atkAudio DeviceIo filter which allows us to capture a discrete audio signal from each cast member as an individual channel on our mixer. This works really well and allows us to manage each voice as a discrete signal and make individual adjustments for each cast member including EQ, compression, filtering, auto-mix, gating, side-chain compression and matrix signal routing. The setup is like this:
  • Host- XAIR ASIO- Output Channel- 9
  • Co-Host- XAIR ASIO- Output Channel- 10
  • Backup Host- XAIR ASIO- Output Channel- 11
Then, each of these video+audio sources is used in *dozens* of scenes in different combinations with different visibility, different transforms, different combinations of visibility, different masking, and even different aspects (we simulcast to vertical as well as horizontal video).

If I understand your suggestion, I would be placing all three browser sources in a single "Audio Scene" which would preclude the video component of each browser source from being used as individual sources in the (literally) dozens of other scenes we have created to mix & match layouts.

I am guessing the reason for the occasional "pop" is that the atkAudio DeviceIo filter is restarting/reinitializing or otherwise changing its stream delivery when I change scenes in OBS..? If this is the case, would unchecking the "Follow Scene" checkbox keep this from happening?

Vern
As long as you are reusing the audio+video sources, instead of having discrete sources per scene. Otherwise you'll be running "NumberOfSources * NumberOfScenes" audio filter chains, even though only active scene data is used for output.
 
As long as you are reusing the audio+video sources, instead of having discrete sources per scene. Otherwise you'll be running "NumberOfSources * NumberOfScenes" audio filter chains, even though only active scene data is used for output.

Ok, I think I understand.. That said, just to clarify my understanding-

If the "Follow Scene" box is CHECKED then
  • The audio stream from DeviceIo is stopped when the scene containing the source source is inactive (hidden)
  • The audio stream from DeviceIo is started when the scene containing the source source is active (visible)
If the "Follow Scene" box is NOT CHECKED then
  • The audio stream coming from DeviceIo is continuous and ignores the visibility of source

If this is accurate, would the DeviceIo stream stopping/starting be responsible for the periodic "clicks" we heard when changing scenes/visibilities? If so, would leaving "Follow Scene" uncheck avoid this issue?

Sorry if I'm asking a lot of questions here.. I just want to learn more about how the plugin works so we know the best ways to use it :)
 
Ok, I think I understand.. That said, just to clarify my understanding-

If the "Follow Scene" box is CHECKED then
  • The audio stream from DeviceIo is stopped when the scene containing the source source is inactive (hidden)
  • The audio stream from DeviceIo is started when the scene containing the source source is active (visible)
If the "Follow Scene" box is NOT CHECKED then
  • The audio stream coming from DeviceIo is continuous and ignores the visibility of source

If this is accurate, would the DeviceIo stream stopping/starting be responsible for the periodic "clicks" we heard when changing scenes/visibilities? If so, would leaving "Follow Scene" uncheck avoid this issue?

Sorry if I'm asking a lot of questions here.. I just want to learn more about how the plugin works so we know the best ways to use it :)
audio stream to/from device keeps running, follow scene basically controls fading and muting data, so there isn't any discontinuity e.g. from device on/off.
 

Hi,​

I downloaded 0.31.13 I am using OBS 32.1.0.-rc1 on an intel Mac Os Ventura.​

Atkaudiodelay doesn't seem to be working, but Audio Device io2 does and plugin host seems to load correctly, but not sure it works as I haven't used it for anything yet. Thanks for all your work.
 

Hi,​

I downloaded 0.31.13 I am using OBS 32.1.0.-rc1 on an intel Mac Os Ventura.​

Atkaudiodelay doesn't seem to be working, but Audio Device io2 does and plugin host seems to load correctly, but not sure it works as I haven't used it for anything yet. Thanks for all your work.
delay is not "delay effect", its a simple line delay which delays the audio signal
 
Back
Top