Menu

Config files being a little confusing

2021-01-05
2021-01-05
  • Piotr Guzik

    Piotr Guzik - 2021-01-05
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:11.0pt; font-family:"Calibri",sans-serif;} .MsoChpDefault {mso-style-type:export-only;} @page WordSection1 {size:612.0pt 792.0pt; margin:70.85pt 70.85pt 70.85pt 70.85pt;} div.WordSection1 {page:WordSection1;} --></style>

    Hello, I just wandered there while looking for a solution for a problem I was having – and then I stumbled upon a ticket #148.

    <o:p> </o:p>

    I believe I had the same "issue". IMO the source of the confusion there is the Configurator not making it clear what is in fact being used by the Equalizer APO engine.

    <o:p> </o:p>

    I use Equalizer APO with a USB headset, which i plug in both to my PC and laptop. I want to have the exact same config on both of my devices, so I figured that keeping the config file on a network drive would be the way to make both devices use the same settings, should I make any changes.

    <o:p> </o:p>

    *A little note there - I do understand that making any chances on one device won't be automatically applied on the other, I assume I'll probably have to launch Configurator each time I modify something anyway to make it read the changes.*

    <o:p> </o:p>

    So I copied the file, then did what felt "natural" to do - switch all the options in the config.txt tab to off, closed the tab, went to File->Open and navigated to the config file located on my network drive.

    <o:p> </o:p>

    Obviously this didn't work, switching the sections on and off didn't make any changes. Little did I know that...

    <o:p> </o:p>

    > Only config.txt is read by the audio engine of Equalizer APO.

    <o:p> </o:p>

    I expected the engine to use whatever was open in the Configurator app - and I believe that's the same problem Mike is having. Having an "external" config file open in Configurator makes you think that is what engine should be working with too. Gotta admit I was stuck there for quite some time until I found this ticket - it all makes sense now.

    <o:p> </o:p>

    One way to approach this may be to automatically include whatever files are currently open in the Configurator, use the config.txt located in program files solely as a list of includes, and let people keep their actual configs wherever they want. Or maybe add a button so the Configurator does that for you. Or make it VERY CLEAR somewhere in the wiki and make people RTFM :P

    <o:p> </o:p>

    <o:p> </o:p>

     
  • Peter Verbeek

    Peter Verbeek - 2021-01-05

    Yes, I was a bit confused too when I started using Equalizer APO. But back then (7 years ago) it didn't had an interface like the Configuration Editor. Basically the issue can be solved by adding a path plus a file to a device in the Configurator. I guess that's what you're proposing. That way a netwerk file can be pointed to and 2 devices may have the same config file working on it. On the other hand, if Equalizer APO did have a manual (it doesn't, only a wiki) the process of dealing with the config.txt should be in it as the first chapter.

     

Log in to post a comment.