Crossfade is not supported. That is to say that MusEQ recommends you do not use it and I can’t be responsible for how MusEQ behaves with it enabled. Sorry but there is enough headache just trying to figure out what the track’s native sample rate is. I don’t want to go into details because it would reveal how my algorithm works, but trust me - Apple doesn’t make this easy.
Well that’s a bit unfair. Let’s put it this way. Apple doesn’t provide any supported mechanism for determining a track’s native sample rate. So it’s not that Apple makes it difficult on purpose.
I hate to make excuses for my own work, but the sample rate matching in MusEQ works way better than I would expect considering how complex its implementation needs to be. It is literally the reason I decided to make MusEQ in the first place. I was just playing around with an idea for an implementation and it worked so surprisingly well that I built an app around it. Having said that, I sometimes doubt it will ever work 100% in all situations but that is the goal.
Playlists are a nightmare, for instance. I’m honestly tempted to state that playlists aren’t supported. It would simplify the code a lot.
The latest version includes a toggle for exclusive mode. Those of you who want to use MusEQ with SoundSource or otherwise please let me know if this works as expected. It is a fine product but I haven’t used it in some time.
I am looking forward to trying this! And I do use Sound Source with various plugins, so I’ll let you know how it works.
I want to continue using Sound Source, and while Lossless Switcher has gotten much better it is still somewhat laggy. So it will great to use something that works a lot better!
One question, does it do bit depth switching? Sample rate yes, but you don’t specify with bit depth. Thanks!
EDIT:
While it doesn’t seem to cause issues as such with Sound Source, it does lock it out regardless of whether “exclusive mode” is toggled on or off. Not sure if they can coexist? Changes in the Sound Source options/settings have no effect, and same with plugins I’m using.
The pregain is already per EQ profile (and the headroom is per headphone).
Pregain is handled automatically to the point where you don’t really need to think about it. Your confusion is likely because the currently applied pregain (that shows in the menu) can only go down aka increase in negative value. This is so that as you change EQ profiles the volume never increases suddenly or unexpectedly.
However the pregain stored in the EQ profile is calculated specifically for that profile and so will often differ from the currently applied pregain. In order to “reset” the applied pregain, you just click the applied pregain value in the menu. If this will result in a significant increase in volume, a warning message will prompt you to turn down the volume on your amplifier.
Also note that if you load 2 EQ profiles in the EQ editor, the amount of pregain applied is calculated to approximate the same perceived overall volume. This is so that you can A/B compare 2 profiles rapidly while playing music at the same perceived volume. So the pregain shown in the EQ editor may not be the same as shown in the main menu.
PLEASE let me know how that goes. I created MusEQ to solve issues that I have when EQing headphones using other EQ applications. I don’t know how applicable the solutions I chose are for other people and so far have gotten little feedback.
I am currently using 3 profiles with my he6sev2: flat, amir’s (80hz +7dB, so -7db pre) and oratory (105hz +5.5db).
When switching between them, it sounds like the volume is the same. However, I will be able to test this in more detail when I finish building my 711 clone.
I tried the free trial and am definitely seeing the value here. This is great software! Small idea for an additional feature: would it be possible to implement an edit button to the headphone name itself?
