Open rhelsing opened 2 years ago
To further improve the process (lots of ideas flowing today), some of the mixing process as well as the mastering could be taken into account. If source separation were applied to the reference, you could allow uploading of mixgroups/stems of your track. From there, the levels could be matched more accurately. Additional best practices could be applied around sidechaining of the mix groups based on the kick in the drums.
Suffice to say, I would love to help contribute to this project. I have been producing and programming for 10+ years.
Hello! Thank you for your interest in Matchering. I would like to help you in your endeavors, but I'm not sure I have the opportunity right now.
I can only share some materials:
This video explains how current matchering works: https://www.youtube.com/watch?v=pHYQpIBDVzg
This is the root core of Matchering: https://github.com/sergree/matchering/blob/a05b1a8f429222b9179f3d476e6488a1b5915e31/matchering/core.py
Thanks again! 😍
Getting a similar tonal balance on the most high energy (and low energy) sections of a track is crucial for matching a sound.. as well as the other items that this library aims for. This could possibly be achieved with a dynamic EQ with N bands. Applying the matching of the values already compared within these bands may improve the result.
If it would be possible to identify intensity levels of a song and apply these parameters to corresponding sections of the input song, the result may also be substantially better.
Being able to tweak the percentage application of these values would be very useful as well. (wetness)
I'd like to help work on these features if you can point me in the right direction.