02-16-2022, 12:49 AM
(This post was last modified: 02-16-2022, 01:06 AM by TheOldPresbyope.
Edit Reason: ETA footnote
)
Well, that was easy.
It took me just a few minutes to get the hang of the user interface after downloading the amd64 binary for my Linux laptop. Then I quickly created a YAML file for my Sennheiser headphones including crossfeed and copied it to moOde.
How nice to be listening on headphones with both compensation and crossfeed. Previously, I was choosing either crossfeed or PEQ-based compensation but couldn't choose both. I was too lazy to figure out how to configure CamilllaDSP manually to achieve both. [1]
I also built a similar YAML file for my Etymotic ER3SE earplugs but I haven't had a chance to test it yet.
As for the interface, yes, there are countless headphones in the database but as soon as you shorten the list someone will be complaining that their favorite was excluded. I didn't have any trouble finding the entries for the two devices I have.
Perhaps one change would be to loop back to the "Which headphones..." query if a user enters an unrecognized string, the way it does if only one letter is entered. (Guess who mistyped Sennheiser the first time!) One can always Ctrl-C out of the program. Possibly also, there might be a hint that 2 or more letters suffice to begin a search.
Some knowledge of CamillaDSP is required to use this tool effectively but that's life. It's a bit of a Swiss-Army knife. Users should do their homework.
Thanks for your contribution.
Regards,
Kent
[1] ETA - To be clear, bitlab had outlined to me how to go about it; not getting it done was me.
It took me just a few minutes to get the hang of the user interface after downloading the amd64 binary for my Linux laptop. Then I quickly created a YAML file for my Sennheiser headphones including crossfeed and copied it to moOde.
How nice to be listening on headphones with both compensation and crossfeed. Previously, I was choosing either crossfeed or PEQ-based compensation but couldn't choose both. I was too lazy to figure out how to configure CamilllaDSP manually to achieve both. [1]
I also built a similar YAML file for my Etymotic ER3SE earplugs but I haven't had a chance to test it yet.
As for the interface, yes, there are countless headphones in the database but as soon as you shorten the list someone will be complaining that their favorite was excluded. I didn't have any trouble finding the entries for the two devices I have.
Perhaps one change would be to loop back to the "Which headphones..." query if a user enters an unrecognized string, the way it does if only one letter is entered. (Guess who mistyped Sennheiser the first time!) One can always Ctrl-C out of the program. Possibly also, there might be a hint that 2 or more letters suffice to begin a search.
Some knowledge of CamillaDSP is required to use this tool effectively but that's life. It's a bit of a Swiss-Army knife. Users should do their homework.
Thanks for your contribution.
Regards,
Kent
[1] ETA - To be clear, bitlab had outlined to me how to go about it; not getting it done was me.
