Thanks!
MReverb makes clicking noise when changing x position across center
-
robertszalapski robertszalapski https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=232813
- KVRist
- 173 posts since 29 May, 2010 from Austin
I'd probably call this a "bug". I expect smooth transitions when I automate the x/y position in MReverb, and it works so long as you don't cross the center x position. When you cross the center x position, I hear clicks. What's up?
Thanks!
Thanks!
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14325 posts since 15 Mar, 2008 from Czech republic
I'm afraid that's part of the algorithm, it's way more complicated than it looks like that . Simply put, different echoes are generated when the source is on the left/right side, and at the X axis there's the crossing point. I'm afraid there's nothing we can do, especially to maintain backward compatibility.
. Simply put, different echoes are generated when the source is on the left/right side, and at the X axis there's the crossing point. I'm afraid there's nothing we can do, especially to maintain backward compatibility.
-
robertszalapski robertszalapski https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=232813
- KVRist
- Topic Starter
- 173 posts since 29 May, 2010 from Austin
I figured backward compatibility would make it impossible to just change. If there's a discontinuity there, than removing it would make the plugin actually sound different, which would be bad for backwards compatibily.
However, it WOULD be nice to have this removed so that we can move the position without glitches, and from an API standpoint, it's not difficult to let this happen without breaking backwards compatibility. You'd have to add a enumeration called "room placement algorithm" with the values "original" and "smooth left/right transition" (or something like that). I've done similar with APIs in my field of work, and I've also seen it done in VST plugins.
Now, as to the implementation of the "smooth" algorithm, I have no idea because I don't know what pshychoacoustic tricks the original algorithm uses. Getting in the new algorithm might be easy, or it might be difficult. It might be easy to think of but difficult to implement or vice-versa.
Anyway, if you could at least write this down on your very large "to do" list I'd appreciate it. I understand you've got tons of other stuff in the works, though, so it might be a while before this gets addressed at best.
It's too bad because I liked moving the position around, it was a fun way idea for keeping the mix dynamic.
However, it WOULD be nice to have this removed so that we can move the position without glitches, and from an API standpoint, it's not difficult to let this happen without breaking backwards compatibility. You'd have to add a enumeration called "room placement algorithm" with the values "original" and "smooth left/right transition" (or something like that). I've done similar with APIs in my field of work, and I've also seen it done in VST plugins.
Now, as to the implementation of the "smooth" algorithm, I have no idea because I don't know what pshychoacoustic tricks the original algorithm uses. Getting in the new algorithm might be easy, or it might be difficult. It might be easy to think of but difficult to implement or vice-versa.
Anyway, if you could at least write this down on your very large "to do" list I'd appreciate it. I understand you've got tons of other stuff in the works, though, so it might be a while before this gets addressed at best.
It's too bad because I liked moving the position around, it was a fun way idea for keeping the mix dynamic.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14325 posts since 15 Mar, 2008 from Czech republic
Well, I'll check it out, but I doubt we'll make this happen. It's actually a much more complicated thing...