HoRNet wrote: ↑
Wed Jan 15, 2020 2:39 am
Wow lot’s of great ideas here! I wanted to create a better version of an “auto mix” plugin, even though we don’t advertise TrackShaper like one... I think a dialogue between instances is essential!
I'm glad to hear you welcome the challenge. I think it's a big one, to try to make something that listens to all tracks. I imagine it could get very complicated quickly. The solution would have to be some elegant simple logic, but in your case with Hornet products I think you already have an engine to borrow from. For this exercise I was using Hornet 31 on the master at 30% to soften the weirdness created by these auto-mixers not listening to each other.
You could use something similar to that engine on the master bus, and use those calculations to determine which track instances need to do more or less.
Like a in a simple rock song: drums, bass, vocals, guitar
Say your master metering reads it needs more 80hz, so it has to decide if it gives it to the kick or bass. Because if it were to just raise the 80hz frequency at the master it would be raising for all instruments summing at that point including the guitar.
If it needs more 4khz it decides not to give it to vocals because of sibilance concerns so it gives it to the guitar. That kind of thinking. So maybe it makes a handful of these decisions, and for the rest just applies something similar to Hornet 31 to wrap up the song into a pleasing frequency curve.
Another experimental idea is to have bus instances. Like instead of just at the track level and then at the master bus level, you could have summing instances in the buses. For example the idea is that a drum bus instance can try to balance the drums applying an eq curve and a specialized drum bus compressor, and doing it at that level allows for a cleaner processing, before everything sums at the master.