Overall: 183 141 182 21
30-Day: 202; 7-Day: 180; Yesterday: 1732
TapeStop emulates the warping effect that occurs when stopping a reel-to-reel tape machine while playing. Stopping the "virtual tape" will progressively slow the affected track down to a complete halt, while starting the virtual tape again will accelerate the playback up to normal speed.
Unlike a physical tape machine though, TapeStop ensures that, once restarted, the affected track remains aligned with the rest of the project, as if it had never been stopped.
Start and stop times are adjustable up to 2 seconds and can "snap" to (fractions of) the beat allowing for simple and precise automation control.
To get this to load in Linux, Reaper specifically, simplify the folder structure. Manually copy the plugin (.so) the json and the graphic elements out of their subfolders and just have them loose in the TapeStop.vst3 folder.
4 stars now for the bug fixed. now about the latency: the daw i'm using is bitwig. it usually deals with latency correctly but it has a limit to how much latency a track is allowed to have. idk, i think it was 1sec or so. could it be that you try to send a longer latency to the daw with your plugin? apart from that i know no latency-bugs of bitwig.
hey. cool tape stop plugin. i like the temposync feature. unfortunately it doesn't latency compensate the signal and the audio engine breaks when both time parameters are on 0. maybe check if you accidently left some edge cases that can stream nans and infs into the audio buffer.
fix these and i edit this comment and give you 5 stars, because the temposync feature is something that i really wanna have :).
Thank you very much for confirming that the bug was in fact fixed. As for the latency, what you say is rather interesting. The plugin has (and advertises) a latency of precisely one second (half of the max stop/start time). I wasn't able to find anything regarding the maximum latency compensation in Bitwig, can you point me so some resources? Perhaps though 2 seconds start/stop time is overkill. I could lower it to 1 second (so 500ms latency) if that means working better with Bitwig...
Thanks for the info. I just uploaded a patch. The crashes with start/stop time of zero might have been due to a division by zero. As for the latency compensation, the plugin actually does advertise its latency to the host, and it is up to the host to compensate for that. I could verify that latency is compensated in Reaper and Studio One 6, while for instance Ardour does not seem to compensate it. Which DAW are you using?