![]() |
#1
|
|||
|
|||
![]()
Hello this is more an educational question.
i have been triying to understand how to find out how hard it is to find and patch audio dropouts and/or noise playing after X seconds in VST(3) plugins on windows. An example coming to my mind is Sinevibes Blend for example: hxxps://www.sinevibes.com/media/blend/Blend211(demo).zip (ignore the mac setup, i am interested in the windows plugin) That is not a request in general, i simply want to understand how attacking such demo versions with such a demo penalty works. So what happens? You fire up the plugin and in the middle of using it after X seconds, it will play noise or/and the audio will be silenced (audio dropout). I am having trouble understand how to find out where to patch the plugin and determine that way how hard it would be. The example above is really just one out of a lot plugin examples. VST plugins need some kind of host to run, savihost, reaper could do for that. My initial idea is that the code runs above the DSP as it even plays noise, when the plugin has its dry/wet knob on 0%, so fully dry. So directly under the audio processing main thread/function. But how to tap into that code region? Thanks for reading. ![]() Last edited by Artic; 05-15-2022 at 05:02. Reason: Added clearification |
![]() |
Tags |
audio, vst plugin |
Thread Tools | |
Display Modes | |
|
|