You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The 'Eaten' display can be inaccurate (my guess it might be a different "bug"). E.g. I have a drum loop peaking at -6db. with ceiling at 0db and oversampling x16 the display shows eaten peaks up to 20.8 db. Might be an calculation error as the sound files is unchanged. Also with different ceiling and oversampling settings the 'Eaten' display seems off.
PS I always used hard-clip for my testing and it seems that when oversampling is deactivated the display is more accurate.
To Reproduce
Just use the plugin :)
Expected behavior
A more steady and accurate 'Eaten' display meter(?)
Desktop (please complete the following information):
VST3, v 0.6.2, Win10
DAW:
Live, Reaper, Renoise all latest version
The text was updated successfully, but these errors were encountered:
Describe the bug
The 'Eaten' display can be inaccurate (my guess it might be a different "bug"). E.g. I have a drum loop peaking at -6db. with ceiling at 0db and oversampling x16 the display shows eaten peaks up to 20.8 db. Might be an calculation error as the sound files is unchanged. Also with different ceiling and oversampling settings the 'Eaten' display seems off.
PS I always used hard-clip for my testing and it seems that when oversampling is deactivated the display is more accurate.
To Reproduce
Just use the plugin :)
Expected behavior
A more steady and accurate 'Eaten' display meter(?)
Desktop (please complete the following information):
VST3, v 0.6.2, Win10
DAW:
Live, Reaper, Renoise all latest version
The text was updated successfully, but these errors were encountered: