sergree / matchering

🎚️ Open Source Audio Matching and Mastering
https://pypi.org/project/matchering/
GNU General Public License v3.0
1.29k stars 151 forks source link

Any way to see exactly what matchering did to a song #43

Open Waffled-II opened 2 years ago

Waffled-II commented 2 years ago

Would love to see it possibly put out a text file or some sort that includes what exactly is different about the new master that the program makes (such as EQ changes, how much stereo spread was applied, how much louder it is compared to the original file, etc.)

This program is way more accurate than something like izotope but in izotope you can see what changes will be made in the new master and apply that difference to other tracks if you so choose, rather than making them all have the exact same mastering as a specific song. Love this program and keep up the good work <3 hope this all made sense!

sergree commented 2 years ago

Hey, thank you so much :) The standard web app (matchering-web) does not support this feature. Some of the information (but not enough) can be obtained using the CLI: matchering-cli

Here you either need to make a fork and add this function yourself, or I will try to take your request into account in further development. 🙏

isaacmuxic commented 2 years ago

I have add the follow in my fork, under get_fir() of "match frequencies.py". Put a breakpoint and run the main.py in debug mode to view the chart. That's my work around to preview EQ changes. import matplotlib.pyplot as plt fig, (ax_orig, ax_mag) = plt.subplots(2, 1) ax_orig.plot(target_average_fft) ax_orig.set_xscale('log') ax_orig.set_title('original_fft') ax_mag.plot(matching_fft_filtered) ax_mag.set_xscale('log') ax_mag.set_title('filter') fig.tight_layout() if __debug__: fig.show()

sergree commented 2 years ago

Great job, @isaacmuxic! 🤩