I guess you can check a few things. As shown in this wiki section are the checkboxes set as explained over there? How is your Yeti Classic Microphone connected? If Bluetooth then that can cause an issue. If USB then it should work, well unless the software of Yeti for this mic isn't playing nice with Equalizer APO.
Whatever you use, Josh, I'll try to support you.
Equalizer APO engine's reads and processes line by line. So in your case this is done by the engine: Config.txt is opened Device HC2 is selected Pre amp on HC2 GraphicEQ on HC2 Microphone file opened Commands in microphone file processed Back to config.txt: Mic device is selected Plugin is done on mic Of course the Microphone file needs a Mic device command in its first line. Or you could put that one before the microphone file in config.txt. Great to hear that you got it working. Btw. I'm the developer...
So i need to put an Include command under the Graphics EQ for the microphone txt file to work in the microphone. Exactly. Or alternatively, above the Device: Headphones Astell&Kern HC2 command. Everything what's beneath a Device: command is done on that device, until another Device: command is encountered by the audio manipulation engine of Equalizer APO) as all commands are sequentially processed. So: Device: A all commands which need to be performed on A (like pre amp, graphicEQ, include, etc.)...
Looking at config.txt I see the microphone won't be manipulated by Microphone (XLR2020).txt as there isn't an include command like this: Include: Microphone (XLR2020).txt
Ok.
I'm not sure about your files. For instance, I see you have included "Microphone.txt" in "Microphone.txt" itself, basically a loop. Perhaps the config.txt screenshot isn't showing it but I don't see the necessary include command. Also, I don't see the microphone selection command in "Microphone.txt" causing the VST plugins be done on all devices, input and output. Although I'm not sure why the VST's aren't working perhaps I should take a look at your files.
That's fine, Josh.
Do this with the disable VST plugins.
That means that Equalizer APO probably isn't working on your mic. Reading your first post it looks like you did everything to get Equalizer APO going. I guess you're working version 1.4.2 in which the Device Selector automatically picks an Audio Processing Object (APO) technique. But you could try if some other works. For this, go to the troubleshooting options of your mic in the Device Selector by checking the Troubleshooting checkbox and select another APO technique in the Install as dropdown box....
So when dialing the pre amp your voice doesn't change in volume in Audacity? Are you able to record your voice at all in Audacity?
It certainly could be hence the trying of the Audio subsystem options, well after confirming if the mic pre amp is working.
Yep. And after disabling these VST plugins does a pre amp work? Of course, not in Discord but in Windows or an app like Audacity? If not, then it may not be Discord related. However, if the pre amp does work, you could try the different settings in Discord available in the Audio subsystem dropdown box.
And in XLR2020.txt there is a mic selection command? I don't see it in the screenshot of your previous post.
No problem, Josh. I'm a bit confused. Looking at your newly attached screenshot I don't see the config.txt. And looking at the screenshots of your initial post I don't see the Astell&Kern (Iems) device selection command nor the needed include command for your mic.
Looking at your 2 configs I don't see an include command in config.txt for XLR2020.txt. Without this include command the Refir plugins aren't included. If you do have an include command but it isn't visible on your screenshots, you could do a basic mic config: a mic selection command and a pre amp. All other commands, especially the Refir plugins should be disabled. And don't test in Discord, just use Windows or an app like Audacity. Then dial the pre amp up and down. If the sound gets louder and...
Yes, I've also noticed that the lengths of the IR files. Looking at them they all have a lengthy zero tail. I'm wondering why this is the case, maybe the reverb length although this doesn't make any sense to me. but the convolver function in EQ APO didn't have a wet/dry mix Well, that's a thought. It should have, shouldn't it. Anyway, your way is efficient. The Peace effects panel heavily relies on the Copy: command. It works perfectly. I'm not sure why you've used the pre-mix stage. Is there something...
I don't know how this works but I don't think EQ APO has a mute function. That's right. In case of Peace it's introducing a -1000 dB pre amp behind the scenes (good guess of -300 dB!). As long as Equalizer APO is working on the target audio device such a muting after measuring a high dB could be done with a reasonable time limit, well if I understand your remarks properly. And muting by applying a zero copy command is also a possibility. Basically the negative pre amp muting is one of the first things...
Perhaps it would be nice to see if it works in practice. In other words, creating your suggested feature just to test if it's workable. The only worry I have is that Peace/Windows isn't fast enough to prevent any damage. On the other hand, now we have nothing to prevent damage.
Great idea. It would complement the existing clipping prevention feature. Unfortunately, Peace is quite slow so the muting won't immediate. Can be between 10 and 100 ms depending on one's computer and what Peace needs to process (like automated configurations). Also, there's another concern. As Peace can't get to the actual audio stream it relies on the peak values "measured" by Windows. These also have a time delay or better said a time period in which the peak value is measured (I guess averaged)....
Nicely done! Indeed, a dry/wet knob is fairly easy to implement if a user introduces an impulse response file. But I think that Peace should also have an example file, well files as the file bit rate needs to exactly mirror the device bit rate. I guess one doesn't need different reverbs per channel. Probably I'm wrong about this π If I'm not then it's only about selecting the channels.
Thanks Paul for sharing your experience and solution. Great to hear that it works. It seems that Windows 11 is getting slower all the time. I also have some audio problems but none that hinders Peace from working. Knowing Windows 11 I understand the delays you're using. Indeed, analyzing is complicated if possible at all. Glad to know it isn't Peace.
I don't have experience in browser-based audio streaming with Equalizer APO. I use Firefox and most things work fine like watching YouTube. In other words, the first thing to do is to establish if the audio streaming of your website can be influenced by Equalizer APO with the most common browsers like Chrome, Firefox and Edge. For instance, it could be that DRM bypasses Equalizer APO or that dolby or any like this is bypasses Equalizer APO. Note that Equalizer APO can only deal with PCM streams,...
bug?: buttons on right-side all link to Theme settings
Well, good job Michael. I was about to explain how it works. Anyway, I'll close this ticket. Indeed, there isn't option for others. Just for other readers: The icon displayed in the upper right corner is the icon.png file which, as Michael says, is 48x48 pixels and can be suited to your liking by making another icon and put it in the theme sub-folder of c:\program files\equalizerapo\config.
I notice that the Peace icon is enlarged thereby covering the buttons. This icon should be small so it fits in the upper right corner. Also, it seems that the icon itself isn't similar to the Peace logo. By any chance did you make your own icon and placed it in the Peace theme folder?
Great to hear. Most probably that the VoicemeeterClient.lnk file didn't exist (issue 5).
I guess you have installed Equalizer APO on Voicemeeter output A1 in the Device Selector and selected this exact device in the Peace devices list for your Peace configuration. When both are done and you can't manipulate the audio of A1 then it's usually that the VoicemeeterClient.exe process isn't running. This process connects Equalizer APO with Voicemeeter so it needs to be started at computer startup. This is done via the VoicemeeterClient.lnk link file in your user start up menu. You could use...
What kind of audio device do you want Equalizer APO and Peace on? For instance, installing Equalizer APO onto a Bluetooth audio device can be somewhat difficult.
Great effort. Thanks for notifying me π Note that Equalizer APO is only installed on the default output and input, usually the 3.5 mm jacks. Also, it could be that Equalizer APO doesn't work out of the box. For both these issues the developer of Equalizer APO pops up the Device Selector at installation (besides the info it provides on how Equalizer APO works and must be installed).
Wonderful π
No problem. That's just great! How did you solve it?
That's unfortunate. I get your sentiment. Perhaps you could try my Equalizer APO issue solver (issue no. 7). It can detect, but not repair, removed audio devices of which stuff are left in the registry. But after successful detection is still difficult to resolve the issue as you need to manually delete the trouble audio device from the registry. Other options are using the DISM and SFC commands of Windows. But I don't have any experience with these tools. Both are used for repairing Windows and...
I'm not sure. I think the default devices like a 3.5 mm jack output or laptop speakers or a 3.5 mm mic input aren't the problem. It may start with some Bluetooth or USB audio device. Unfortunately I don't have the proper answer yet. And the developer of Equalizer APO probably doesn't know either. But looking at the source code of Equalizer APO it has a problem dealing with audio devices which aren't complete or are leftover after uninstalling them. Hence the idea of using registry cleaners. But I...
Sorry Jakob for the late response. Reading your post it seems to me that this issue belongs on the Equalizer APO forum. However, as the developer isn't much responding on anything over there, we could discuss what's going over here. Over there I'm the sole responder anyway. I do the support for Equalizer APO for years now, also knowing I'm the developer of the Peace equalizer. Btw. This is made in AutoIt (AutoHotKey is a kind of fork). Peace can be controlled by WM_APP and WM_COPYDATA messages as...
Usually it's about some audio device as I'm explaining here.
Probably because both apps, the Configuration Editor and Device Selector, crash due to an audio device of which these apps can retrieve the specs. This usually happens when some remainders are left of a deleted audio device. Unfortunately this is difficult to establish and to solve. You might run a registry cleaner like Wise Registry Cleaner or the registry cleaner of CCleaner. Hopefully that solves it although not guaranteed.
Home
Home
Great to hear Alan. It could be that some effects were switched on. If so, this is visible by a green marker on the Effects button. Looking at your screenshot everything seems in order. On the Peace AutoEQ interface there are 3 Hifiman Arya Stealth EQ's available. I've compared the EQ graph to the Oratory1990 one and basically they are quite similar.
Iβm not using any VST plugins, only the parametric EQ filter's you provided for the Arya's. That confirms it's basically the same issue as of this Peace ticket post. Initially I got the same cracklings/distortion when using a Peace config from the user who's made the ticket. But somehow the cracklings stopped after downgrading to Equalizer APO 1.2.1 and upgrading again to 1.4.2. That is pretty weird! Anyway, this user had delays and some COPY: commands going on in his Peace config on which I initially...
As Oratory1990 I don't think it's your Arya headphones, especially knowing that this is reported once on the Peace forum. Some user had cracklings whilst moving the Peace window. It's unfortunate that you're having the same issue. Commonly crackling happens when having one or more VST plugins and moving a slider or whatever audio changing thing on the Peace GUI's (main window, effects panel, command window, automation window and MIDI window). This is due to the nature of the Equalizer APO or better...
Thanks for reporting back π Nice to hear that the issue got solved somehow. Indeed, probably by a Windows update although that doesn't give us a clue how's solved.
No problem, George. Indeed, perhaps the next version.
Using Eset as AV. Even though no logs of blocking anything on Eset, I tried disabling it together with Windows defender, but to the same results. Good to try but that was to be expected. What happens when you start up the computer with the FiiO K9 disconnected? Same issue? Perhaps even uninstalling device drivers, just to see which one is the culprit when you install them one after the other. Anyway, when saying "mic drivers from old cameras" this could present a problem. I wish there was an easier...
Wow, 22 ghost devices. That seems a lot. So there is yet another issue which my solver hasn't covered. I wish the developer would react on this matter. Unfortunately I don't know what it is about. There is the rare occasion of an overactive anti-malware app but I don't that's it. VirusTotal doesn't show anything on the editor nor on the device selector. Another equally rare is the crashing due to an issue of certain Windows updates. Are you on the Windows Insider Program for receiving the newest...
Then it's about one or more removed audio devices of which the registry still has an entry. This can also be checked with the Equalizer APO issue solver (issue 7). It tries to detect this. Unfortunately this app can't correct this, especially knowing it's a tricky one to correct. One needs to use a good Windows registry cleaner or the Windows utility bdism.exe or even both.
If this is a problem of corrupted registry key values in which the editor settings are stored you could use my Equalizer APO issue solver. This is issue in this app which is solved by deleting these key values so the editor creates them again at its startup.
So 1.4 also has an issue. I didn't know that. Unfortunately the developer of Equalizer APO isn't very active. He isn't responding to most posts on his project. Although the forum over there is the one to post your issue I would probably be the one to help you over there. Have you tried 1.4.2? And have you used the Equalizer APO issue solver? With it you can let remove the registry keys and values of HKEYCURRENTUSER\SOFTWARE\EqualizerAPO\Configuration Editor Reading your first post you might have...
I don't know how to easy solve this (see comments below) but at least I can tell you that 'Instant Mode' has nothing to do with it. This checkbox unchecked causes that changes aren't picked up by the audio engine of Equalizer APO. This is quite pointless so this checkbox is pointless imo and should remain to be checked all times. It must be a license issue thing, meaning FabFilter doesn't have access to its license therefor keeps running in demo mode. Equalizer APO like any Audio Processing Object...
Although this is an issue of Equalizer APO so it's best to address it on its forum I can help you here as Peace is also using of the Configuration Editor. There are a few issues which makes the Configuration Editor crash. The main one counts for Equalizer APO version 1.3.0 and lower. If you have used this and you have detached the analysis panel (the graph window) then a bug will crash the editor at the next startup. This can be solved by using my Equalizer APO issue solver (issue no. 1). Basically...
Great. 1.4.2 doesn't have this bug. And it may be that it fixes it for lower version. edited: does to doesn't
Great. 1.4.2 does have this bug. And it may be that it fixes it for lower version.
That's because it crashes. If you were using Equalizer APO version 1.3 or lower then this is caused by a bug. After detaching the analysis panel (the graph window) this bug crashes the Configuration Editor at startup. Anyway, you could resolve this using my Equalizer APO issue resolver or by deleting the windowState key value from HKEY_CURRENT_USER\SOFTWARE\EqualizerAPO\Configuration Editor by using the Windows registry editor.
Great to hear! I hope it stays that way.
It depends on the buzz. For instance, before Equalizer APO version 1.4.2 using graphic eq could result into buzzing or worse distortion. Amongst others that why my Peace equalizer app is using filters by default. But this buzzing/distortion was mainly on Bluetooth audio devices. Another cause can be the background noise. When amplifying the sound of your mic by a pre amp command (or in Peace by the pre amp slider) this noise gets amplified too. So either you put the mic closer to your mouth or try...
Is it your mic? If so try the following. First, uncheck the checkboxes as shown in the attached screenshot. This ensures that Equalizer APO (being an Audio Processing Object) doesn't get bypassed when Discord tries to use your mic in exclusive mode. Second, that is for your mic and headphones, try all Audio subsystem settings found in Discord. Some have it 'automatic', others on 'legacy'. But you need to try them all.
Btw. The volume will remain on 1-2%. The gain is increased which makes the sound louder so no worries there.
Good to hear. Automatically changing to SFX/MFX is okay. I don't know why the popup still appears but it's nice to know that your volume is a bit better.
In principle an Audio Processing Object (APO = sound enhancement software) isn't a part of an audio device driver so it shouldn't matter what driver to use. But it does happen that a 'bad' driver has trouble with the audio stream provided, in this case, by Equalizer APO's engine (the APO). For example this could be a sample rate conversion issue or simply an audio buffer issue, both causing distortions. Another issue with driver update software that it includes 'settings' for APO's or actual APO's....
By turning off enhancements the audio stream isn't going through the sound manipulation engine of Equalizer APO. If the sound from your mic sounds bad then it has to do with this engine and perhaps other enhancements (APO's) working on your mic. In other words, it's either some compatibility issue between APO's or it's this engine itself what causes the issue. Have you add anything in the Configuration Editor on your mic? Could you show your configuration files starting with config.txt?
It's all pretty confusing. At least when the pre amp can't be used we know that Equalizer APO isn't working on your mic. And when it went back to LFX/GFX then it can be about something restoring things for this mic device. That could be Windows itself, a piece of software installed with the mic or some overactive anti-malware/firewall app although that isn't very likely. I'm not sure what you can do. 2 things to check and try. First, on the mic properties page check if the 'Audio enhancements' is...
Great! Install 1.2.1 and try it. But it could be that the message keeps on popping up. In that case you need to confirm if Equalizer APO is indeed uninstalled from the "michael yo" device. If not, just use Peace by increasing the pre amp slider. If the mic gain (say volume) is increased then you're done. If it isn't and you're sure that Equalizer APO remains installed on the mic you need to go through all APO techniques available in the "Install as" dropdown box. First pick SFX/EFX and restart your...
It is confusing. The 2 error messages are actually about 2 separate things. The first one is with the update checker app of Equalizer APO 1.4.2. The second is an issue of the automatically uninstallation of Equalizer APO on your "michael yo" device. So both need to be addressed differently. So firstly the "This application failed ...." error popup should be dealt with by removing the automatic startup of the update checker. This is a "task" Windows performs at startup. The task need to be removed...
Looking at the error message I see that the update checker is still in the Windows Task Scheduler. It should have been removed at the uninstallation of version 1.4.2. In your case you need to remove it manually in the Windows Task Scheduler. If you don't know how to, you could download my Equalizer APO issue solver. When run with administrative rights (right click menu -> Run as administrator) it can remove this for you. There's remove button under issue 6. The other popup could be a matter that...
Sometimes that isn't enough. In Peace I do: net stop audiosrv net stop audioEndpointBuilder net start audiosrv And when using Peace it's under the button "Restart Windows audio service" on the "Debug and Testing" tab in the settings. But one has to start Peace with administrative rights.
Sometimes that isn't enough. In Peace I do: net stop audiosrv net stop audioEndpointBuilder net start audiosrv And when using Peace it's under the button "Restart Windows audio service" on the "Debug and Testing" tab in the settings. But one has to start Peace with administrative rights.
Sometimes Equalizer APO 1.2.1 works or even 1.1.2. I don't know why and the developer probably doesn't know either. But it's worth to try. Note that both versions don't have the Device Selector. In their case its the Configurator in which you manually pick the APO technique. But you're now familiar how to do this. Unfortunately, it also needs a computer restart to invoke any troubleshooting option change. This can be quite annoying when trying many options. I recommend trying SFX/EFX first.
And in trying the troubleshooting options you did click the 'Ok' button to invoke a changed option? I guess when it went more quite a new driver has been installed, probably with a Windows update. Perhaps you can find an older or newer one for this Realtek mic device. Unfortunately it can be tricky to find anything good for Realtek devices. Looking at the testing by the Device Selector none of the APO techniques work but that isn't always the case. I guess you have tried them all. It needs what's...
This can be done in Peace in 3 ways. Probably the easiest way is to right click on the Peace icon in the Windows system tray and click 'Start Peace at Windows startup'. When there isn't a check sign at the left of this menu item you know Peace isn't starting any longer. Another way is to use the shortcut interface under the Shortcut button. After selecting 'In Windows startup' clicking the Remove button removes the Peace startup shortcut which started Peace at Windows startup. And thirdly, there's...
Do you mean the Configurator or Device Selector? The Configuration Editor doesn't show the devices status. Anyway, it's a neat trick. Also, when Equalizer APO on devices gets uninstalled by a Windows update usually starting the Device Selector / Configurator fixes that.
I don't get it either. It seems to happen in rare occasions but in what occasions I don't know. It seems that dll's of Qt which are just for creating interfaces so the interface of Device Selector and Configuration Editor. Sometimes these dll's flagged as malware and therefore blocked. Perhaps Windows Defender is a bit overactive. At a next update it could be suddenly solved.
This seems to happen sometimes. It may be that the developer doesn't know why this happens. Maybe during the installation something is going wrong all the time. The folders of Equalizer APO should look like the screenshots. You could verify if this is the case on your computer.
Good luck, Amir.
I'm not fond of using AI (llm's). In this case ChatGPT is plain wrong. Equalizer APO like any audio processing object works on USB audio devices. However, some devices like your Fifine AM8 aren't playing nice. This could be due to several issues but not what ChatGPT said in this case.
Just to be sure that Equalizer APO can't work, uncheck the exclusive mode checkboxes as shown in the attached image. Some recording/streaming apps want to have exclusive access to a mic so no other app is able to record/stream. But that bypasses any Audio Processing Object (read sound enhancement) like Equalizer APO.
If you can't get Equalizer APO to work on your mic then VB-Cable by VB-Audio might offer a solution by installing Equalizer APO on this VB-Cable and redirect your mic input through this cable. But I'm not an expert on this. Usually one installs Voicemeeter (also by VB-Audio) and installs and uses Equalizer APO on one of its virtual devices A1 to A5. These devices are fully supported by Equalizer APO, that is when the VoicemeeterClient.exe of Equalizer APO is running. Unfortunely I'm also not an expert...
Smart thinking. I don't know what's going on. Perhaps I can take a look at your configuration files. Could you attach them to your next post? I doubt that I can figure it out but I can give it a try.
Are you familiar with the troubleshooting options for an audio device in the Device Selector? These options are accessed by selecting your Fifine AM8 and checking the 'Troubleshooting options' checkboxes. Usually the 2 'Use original APO' checkboxes are greyed out, meaning there aren't any. But if they are available uncheck both and click the 'Ok' button to apply this change. If there still isn't any sound then try the remaining 2 APO techniques available in the 'Install as' dropdown box. Note that...
Using the pre amp to make the sound louder is okay only in moderation as it will introduce high 'clipping' at higher values. To prevent this, as it may cause audible distortions, Windows intervenes by reducing the overall sound, in principle by applying a dynamic negative pre amp. So the higher the pre amp you set the more fluctuations you get. But this is better than high distortions through clipping. Generally speaking it's about using the pre amp carefully so the fluctuations aren't audible whilst...
Did this Fifine AM8 come with its own software you needed to install?
The only thing I know is that the sampleRate variable is the value of the current audio process, meaning the process of the current selected device, not the one selected by the device selection command. I guess it depends how the APO (audio engine) of Equalizer APO is handling things. It should be as I explained but it may be more complicated of which I'm not aware of.
I'm not sure what you're saying. Equalizer APO has channels up to 8 which of course for a stereo system only the first 2 can be used. And Equalizer APO supports the creation of virtual channels on which any command can be performed.
Unfortunately the developer isn't forthcoming in letting us know when the next update is coming nor what features are in the pipeline. The last couple of years only insignificant feature were added.
I understand. Sorry, that I can help on the road you want to follow. The best of luck.
Lenovoβs Realtek APO layer rejects shorthand. Total BS. Read below. Commands that look valid but Windows 11 ignores on Lenovo/Realtek Complete nonsense. Equalizer APO is an Audio Processing Object (APO). As such it either works or it doesn't. It has nothing to do with Windows 11 ignoring things on Lenovo/Realtek. Where do you get this rubbish. To be clear the Include, Copy, Preamp and Filter commands will work if Equalizer APO is working (the APO I mean). Of course one can't address channels which...
Please stop using Copilot. It produces rubbish. As developer of the Peace equalizer, a popular interface for Equalizer, I can tell you that those commands aren't even a good starting point. I can't make heads or tails of it. Mind you I'm using Equalizer APO commands for Peace for the last 12 years in order to create the best interfaces for the Peace users. Interfaces for equalizing, bass boosting, voice improvement, home theater setup, etc. etc. So either you dive in the commands yourself if using...
First of all Equalizer APO isn't my project. Second, I'm here to help you and others so what goes wrong when you're trying Equalizer APO? You aren't very clear on the issue you have encountered.
That isn't a reply I was looking for. What do you need? Btw. Stop using Copilot. It produces nonsense.
Well, it looks like a total mess. What do you want to do on your audio device?
Release of Equalizer APO issue solver 1.4.0.0
Home
What audio device are you talking about? If a mic then at least try the unchecked exclusive mode checkboxes as shown in the screenshot. If an output device like speakers then in principle these checkboxes need also to be unchecked. However, apps don't usually set an audio device in exclusive mode (which bypasses any APO like Equalizer APO) but at least try it. And change the audio output technique. For instance in Discord there's a settings called 'Audio subsystem'. Try all different options over...
There was no "Include" thing, and it got restored...? Nop. The reset feature isn't resetting any commands you use. Amongst others it resets the "Instant mode" checkbox. When this checkbox is unchecked changes aren't applied any longer. In other words, this checkbox is pointless and confusing.
I'm not sure either so could you make a screenshot of the Configuration Editor and also attached all your config files? Perhaps I can figure it out.
Great to hear you have found a solution through restoring. I wonder what happens when Microsoft does push this in some new update. I hope things keep on working.
Home
I guess you're using the Configuration Editor of Equalizer APO. Did it work before and not now? Anyway, the audio engine of Equalizer APO (equalizerapo.dll) is only monitoring the "config.txt" file. Any other file isn't monitored unless you point to it by adding an include command in config.txt. Note that the graph will always show the current selected file even if this file isn't processed by the audio engine.
I understand. And you did the usual things so that's good thinking and doing. One thing you need to check. If your Peace configuration has an audio device selected this device might point to a former one which the Windows update removed. Generally Peace is pretty good at finding the new installed device but it might not in your case. It's easy to check. After loading a config look if the device is the last one in the Peace devices list and if the device is mentioned above it. That's the new one....
No problem. So you have done whats being said in this section of the wiki. Have you tried all APO techniques in the "Install as" dropdown box? Remember that for any change in the troubleshooting options you need to invoke it by clicking the "Ok" button. Unfortunately the developer hasn't implemented an "Apply" button.