Mute Filter 0.4.0

[norihiro]

norihiro updated Mute Filter with a new update entry:

Mute Filter 0.4.0

This is an experimental release of a mute filter.

Changes in 0.4.0

• Discard Audio by UI: Revised code when unmuted after muted within 70 ms.
• Discard Audio by UI: Added atomic-bool methods to send the mute state of the source.
• Renamed plugin binary name from obs-mute-filter to mute-filter.
• Windows and macOS: Dropped supporting OBS 27.
• Revised build flow based on my...

Read the rest of this update entry...

 

[neilis]

Tried de exe and zip windows install, cant get it to show among OBS audio filters.

 

[norihiro]

Tried de exe and zip windows install, cant get it to show among OBS audio filters.

I'm sorry for the confusion. It should be displayed as "Discard Audio" and "Discard Audio by UI".
If these filters don't appear, would you also check the log file as well?

 

[neilis]

Ok, found it, thank you

 

[l1i1l]

Hello, but you don’t seem to keep track of what is in your distributions, and how, where, what is placed after unpacking the archives. In the version for Windows, for example, you have an empty folder, the structure of other folders and files is completely strange. Check it out, please.

├───.
├───bin
│   └───64bit
│           mute-filter.dll
│           mute-filter.pdb
│
└───data
    │   LICENSE
    │
    └───locale
            en-US.ini

@norihiro

 

[KattPhloxworthy]

Hello, but you don’t seem to keep track of what is in your distributions, and how, where, what is placed after unpacking the archives. In the version for Windows, for example, you have an empty folder, the structure of other folders and files is completely strange. Check it out, please.

├───.
├───bin
│   └───64bit
│           mute-filter.dll
│           mute-filter.pdb
│
└───data
    │   LICENSE
    │
    └───locale
            en-US.ini

@norihiro

Time to describe %PROGRAMDATA% located plugins. Yes, it is "strange", but it makes more sense.

This requires you to use an installed (key word here) copy of OBS Studio (whether it's via the self-installing .exe file or installs by way of Steam or the MS Store) and to unpack the archive into %PROGRAMDATA%\obs-studio\plugins directory, typically C:\ProgramData\obs-studio\plugins directory on most systems.

The idea here is that you keep plugins in an area completely removed from where the install tree is, normally rooted in %PROGRAMFILES%\obs-studio.

Doing the ProgramData way has a few advantages:

• If you need to uninstall then reinstall OBS Studio, this will delete absolutely everything in the OBS Studio install tree, including plugins you installed, regardless how they were installed in there, regardless of whether you wanted to uninstall them or not.
• If you want to remove a plugin, you just need to remove just one directory and the contents therein. It is much cleaner than having to find all the files for a given plugin if you find you need to remove just one plugin; you might as well uninstall OBS Studio and then reinstall all the other plugins you actually do want. Which leads me to:
• The %PROGRAMDATA% hierarchy does not require elevated/altered privileges to put material into or remove material from.

Some plugins are now being offered either mainly or alternatively in the "ProgramData" format or install that way by default.

However, this method does have a couple of downsides (at least for now):

• If a given plugin does not have a package that is not in the "ProgramData" format, it can be a little labor-intensive to update a plugin. That said, it beats the alternative of losing all your plugins if you need to uninstall then reinstall OBS Studio, then reinstalling all of your plugins you actually want.
• This will not work with "portable" installs. Since the "ProgramData" format this program is in .ZIP form is the only format on offer, you will have to manually copy it into a given OBS Studio tree in the "old way".

In short, this is not "the incorrect" layout. It is, however, a different layout. You need to know how both layouts work depending on availability of some of these plugins.

--Katt. =^.^=

 

[l1i1l]

Time to describe %PROGRAMDATA% located plugins. Yes, it is "strange", but it makes more sense.

<…>

--Katt. =^.^=

Thanks for the detailed answer, I already managed to understand that a new scheme is used here ))) . It’s just that an empty folder located in the distribution kit is confusing, and since I have long been accustomed to working with the old scheme of “throwing the contents of the archive into the OBS folder in Program Files”, confusion arises, it seems like there is an error with the name and structure.

 

[KattPhloxworthy]

Thanks for the detailed answer, I already managed to understand that a new scheme is used here ))) . It’s just that an empty folder located in the distribution kit is confusing, and since I have long been accustomed to working with the old scheme of “throwing the contents of the archive into the OBS folder in Program Files”, confusion arises.

Lately, I've had been doing some work on some other plugins that require me to bounce back and forth between versions of OBS Studio, in this case, 32.0.4 (which works for me with some plugins) and others which do not, notably the entire 32.1.x train. with the plugins completely out of the tree, I have been doing installs and uninstalls of OBS Studio without worrying about the plugins going bye-bye now.

I suspect the "empty folder" is likely due to being packed in macOS which uses a Unix-type base and what you're using to unpack it showing it as an empty directory rather being a marker for the "current directory". It ALWAYS adds the "current directory" item, which is signified by a "." if you're using 7-Zip.

--Katt. =^.^=

 

[l1i1l]

<…>

I suspect the "empty folder" is likely due to being packed in macOS which uses a Unix-type base and what you're using to unpack it showing it as an empty directory rather being a marker for the "current directory". It ALWAYS adds the "current directory" item, which is signified by a "." if you're using 7-Zip.

--Katt. =^.^=

Yes, you're right, I use 7-Zip (usually). After unpacking your archive with another archiver, the folder "." didn't show up. Moreover, after this the empty folder stopped appearing even when using 7-Zip )))

 

[l1i1l]

I figured it out completely: the empty folder is displayed only when viewed through archivers (7-Zip or any other), when unpacking this empty folder does not appear. Since I usually “pull” files directly from the archive (without unpacking), that’s why I saw this folder.