Plugins + Scripts BeatIt

[CuddleMocap]

@HAL9001 I'm having a big issue with BeatIt where the EQ triggers act very inconsistently. In a nutshell: after the music has been playing for a while, the triggers can sometimes become very weak and unresponsive, but if I pause and resume the music, they go back to being responsive again.
The reason why this is such a big problem for me: While I am editing dynamic lights in a scene, I am doing a lot of pause/unpause as I input keyframes into Timeline. After editing a section, I rewind back 10 seconds to review how it will look, then I move on. When the scene is finished, I watch it again from the beginning, but the lights don't look very much like how I keyframed them. This is because the triggers became weaker when the song was played for a longer period of time. Some of the triggering seems to be pretty good throughout the whole song, so I'm not sure what is causing it to be weak at other times specifically. The problem is consistent, as the same parts of the songs have very dim and unresponsive lights, every time I play it back. This problem is observable inside the BeatIt UI, as the EQ trigger will be peaking around 0.300, then after pause/resume, it will peak at 1.0.
For now, I am going to have to move away from this plugin, because I need the light show to be consistent every time someone watches it. Any ideas on how this might be fixed in the future?

 

[HAL9001]

@HAL9001 I'm having a big issue with BeatIt where the EQ triggers act very inconsistently. In a nutshell: after the music has been playing for a while, the triggers can sometimes become very weak and unresponsive, but if I pause and resume the music, they go back to being responsive again.
The reason why this is such a big problem for me: While I am editing dynamic lights in a scene, I am doing a lot of pause/unpause as I input keyframes into Timeline. After editing a section, I rewind back 10 seconds to review how it will look, then I move on. When the scene is finished, I watch it again from the beginning, but the lights don't look very much like how I keyframed them. This is because the triggers became weaker when the song was played for a longer period of time. Some of the triggering seems to be pretty good throughout the whole song, so I'm not sure what is causing it to be weak at other times specifically. The problem is consistent, as the same parts of the songs have very dim and unresponsive lights, every time I play it back. This problem is observable inside the BeatIt UI, as the EQ trigger will be peaking around 0.300, then after pause/resume, it will peak at 1.0.
For now, I am going to have to move away from this plugin, because I need the light show to be consistent every time someone watches it. Any ideas on how this might be fixed in the future?

Every frequency band measures it's maximum level while the audio source is playing to determine the relative loudness. That maximum is reset when the audio is silent or the source stops playing. I could add checkboxes to stop that from happening and instead measure and save the maximums ... and even change them dynamically via Timeline.

 

[Gabberjaw]

Hiya, I've updated from BeatIt 5 to 8, I've rewritten my .cs in the .jsons to .cslist but it still broke my scenes and it gives me an error for "macgruber" namesomething being not found, spent like 20 minutes troubleshooting then gave up, forgot to take screenshots x)

 

[CuddleMocap]

Every frequency band measures it's maximum level while the audio source is playing to determine the relative loudness. That maximum is reset when the audio is silent or the source stops playing. I could add checkboxes to stop that from happening and instead measure and save the maximums ... and even change them dynamically via Timeline.

As long as the end result is the audio triggering the same amount of intensity every time it plays back that same audio, that would be a very welcome addition for me.

 

[HAL9001]

Hiya, I've updated from BeatIt 5 to 8, I've rewritten my .cs in the .jsons to .cslist but it still broke my scenes and it gives me an error for "macgruber" namesomething being not found, spent like 20 minutes troubleshooting then gave up, forgot to take screenshots x)

Have you updated the version number of the plugin in the corresponding plugins section of the Atom? Can you send a code copy of the affected JSON part of the scene?

 

[HAL9001]

As long as the end result is the audio triggering the same amount of intensity every time it plays back that same audio, that would be a very welcome addition for me.

Could you please try this version 9 before I release it (had to rename .var to .txt to be able to attach, so please undo that)

 

[Gabberjaw]

Have you updated the version number of the plugin in the corresponding plugins section of the Atom? Can you send a code copy of the affected JSON part of the scene?

Actually I've had 6 lights with beatit in the scene and I only changed one line
Works now! My bad!

 

[CuddleMocap]

Could you please try this version 9 before I release it (had to rename .var to .txt to be able to attach, so please undo that)

I gave it a go! It looks like to resolve the issue I am having, I need to manually trigger a calibration reset during the parts of the song that have been giving me the problem. Is that the intended approach? It does seem like it will work.

 

[HAL9001]

Well, either that, or you reset once, play the song in its entirety, and save the scene with those overall calibration values. Then the responses of BeatIt should be consistent (though likely slightly different than with your approach).
A Calibration Reset will probably cause spiking outputs at first, until the maximum calibration values have been "established". If you start off with those values, there should be no spikes.

 

[HAL9001]

HAL9001 updated BeatIt with a new update entry:

v1.6 (var 9): Optional Auto Calibration Reset

At the suggestion of @CuddleMocap,

• Added an option to turn on (default)/off the automatic calibration reset on silence or playback stop.
• Exposed the calibration values per channel so they are a) saved and b) can be changed in runtime.
• Added a "Reset Calibration" trigger an UI button for manual reset.

Calibration values keep track of the maximum volume per channel and therefore determine when to trigger a value of "1" for a channel. If you want to...

Read the rest of this update entry...

 

[CuddleMocap]

Well, either that, or you reset once, play the song in its entirety, and save the scene with those overall calibration values. Then the responses of BeatIt should be consistent (though likely slightly different than with your approach).
A Calibration Reset will probably cause spiking outputs at first, until the maximum calibration values have been "established". If you start off with those values, there should be no spikes.

Thank you very much for this! I really do appreciate it. I'll put it to good use!