-
-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any way to see exactly what matchering did to a song #43
Comments
Hey, thank you so much :) 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. 🙏 |
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. |
Great job, @isaacmuxic! 🤩 |
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!
The text was updated successfully, but these errors were encountered: