danielrudrich / oomphsc Goto Github PK

Well, or at least good... fine with me!

Make the visualization use decibels instead of linear rms values.

Still to be defined if this should be made switchable or hardcoded.

Would be nice to have a toggle between Peak and RMS. We're doing some tests now and the RMS value is super low for impulse sounds, but what we need is the peak data so that we can make some spikes in the visuals.

When not visible on the screen the plugins stop sending data.
At least this occurred between Reaper and TouchDesigner in our tests, if the FX window in Reaper was closed TouchDesigner would no longer receive any data. Once the FX window was opened and Oomph was on the screen, then TouchDesigner would receive the data.

Would be nice to have a toggle, which is off by default, for the bands. Start by only sending the full RMS data, and then if you check the box the bands appear and will be sent also.

As we already split the signals into bands and compute their energy, it would be cool to use this information for an onset detection in time domain.

Some kind of spectral flux log filtered, but instead of DFT, a time domain frequency split. Not sure if it will work well, but would be interesting to check out.

I see that the plugin sums both channels to mono, and I think with ambisonics this works in most cases, however we've seen from working with artists that the majority of the time the artists are taking an existing stereo track that they've made and therefore there are a lot of Stereo encoders in use, and the use case here is often that the stereo sound has two very different sounds or ping pong delay effects occurring in the two different channels. With the Oomph summing to mono we can't have two different events happening occurring at the two different locations in the visuals. I think it might make sense to do like Waves here and make two separate plugins, one mono and one stereo so the artists can choose what type of data they want to send and when.