Avoid resampling of output?

[RattusSolarus]

I just installed Matchering 2.0 locally in Docker and it works really well. However, even with source and target files of 24 bit 48kHz it resamples the output to 44.1kHz.
Is there a way to avoid resampling and produce output files at 48kHz?

Thanks for your great work on this magic software btw!

[sergree]

Hey, @RattusSolarus!
Docker version supports only 44.1khz.
If you need 48khz, you need to call Matchering Python library directly and edit it's config.
Example:
https://github.com/sergree/matchering/blob/master/examples/edited_config.py
It will require Python enviriment installation and some coding.

[RattusSolarus]

Thanks @sergree ! I'm not really a coder but with some trial and error, and a lot of head-scratching, I managed to get the venv set up and matchering-cli working with edited config file. Working in 48kHz now!

Any chance the Docker version will support 48kHz in the future? It's easier to use than cli, and prettier. :)

I also like the suggestion in issue #14 , not necessarily to influence individual parameters but just to apply a percentage of the full changes like a dry/wet mix control. Hermann Brummer has this as a "Morph" control in https://github.com/brummer10/MelMatchEQ.lv2 but that is a 1 in 1 out plugin and EQ only so not suitable for stereo mastering.

[Analog4Lyfe]

I work at 96k and deliver at 96k. Wish this was available.

[RattusSolarus]

I work at 96k and deliver at 96k. Wish this was available.

You can edit the config file to whatever sample rate you wish. As segree said above, Docker version is only 44.1kHz but set up the Python library and use matchering-cli like I did.

[Analog4Lyfe]

I work at 96k and deliver at 96k. Wish this was available.

You can edit the config file to whatever sample rate you wish. As segree said above, Docker version is only 44.1kHz but set up the Python library and use matchering-cli like I did.

I’m using it via unraid. Id have to figure out how that’s done.