Reaper apparently doesn't correctly report the play_state value to JSFX.
According to the official JS documentation, when Reaper plays back a project, the play_state value is 1. When playback is paused, it should update the play_state value to 2, but instead it just stays at 1, letting the JSFX think the project is still playing.
This has been reported and discussed in 2011, in 2014 and in 2018 on official forums and bug trackers already. Sadly, the broken play_state behaviour is still broken in Reaper version 7 in 2024, a mere 13 years later.
Until the play_state behaviour is fixed in Reaper, the "halt on playback pause" feature in Wave Scope will not work.
The Wave Scope has a setting that should halt the display whenever Reaper is paused, so that what's currently visible in the display stays there and doesn't vanish off to the side.
Reaper apparently doesn't correctly report the play_state value to JSFX.
According to the official JS documentation, when Reaper plays back a project, the play_state value is 1. When playback is paused, it should update the play_state value to 2, but instead it just stays at 1, letting the JSFX think the project is still playing.
This has been reported and discussed in 2011, in 2014 and in 2018 on official forums and bug trackers already. Sadly, the broken play_state behaviour is still broken in Reaper version 7 in 2024, a mere 13 years later.
Until the play_state behaviour is fixed in Reaper, the "halt on playback pause" feature in Wave Scope will not work.