Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clock pulse missing on tempo changes in Reaper #649

Open
taji opened this issue Apr 17, 2024 · 8 comments
Open

Clock pulse missing on tempo changes in Reaper #649

taji opened this issue Apr 17, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@taji
Copy link

taji commented Apr 17, 2024

Version

24.04

Plugin type

VST3

OS

Linux (PopOs 20.04)

DAW / Host (if applicable)

Reaper 6.34

Description

To reproduce (see the attached Reaper project file:

  1. Launch Reaper
  2. Add a track | Insert new Cardinal vst3 plugin instance (I used the multi channel version)
  3. In Cardinal, insert the following modules: Host Time & Host Audio
  4. Wire the Step output from the Host Clock module to the Host Audio module's input pin 1.

image

  1. Right click on the track and select Render/freeze tracks | Render tracks to Mono stem tracks

CardinalMissingClockPulse-Issue2

  1. View the rendered audio clip at the 60 bpm and 120 bpm tempo changes.

EXPECTED: Both tempo change points should have a clock pulse firing at beat 1.
ACTUAL: The 60 BPM has the clock pulse, but the 120 BPM does not.

CardinalMissingClockPulse-Issue1

NOTE: Issue is not happening in VCV:

image

@taji
Copy link
Author

taji commented Apr 17, 2024

Here's the rpp file for reproducing in Cardinal.
Reaper-Cardinal-ClockPulseBug.RPP.zip

@falkTX
Copy link
Contributor

falkTX commented Apr 17, 2024

thanks for the great report!

if you can please check if the same behaviour happens with other formats. so clap, lv2 and vst2.
that will help a lot in understand the issue better

@taji
Copy link
Author

taji commented Apr 18, 2024

Yes, will do. But it may be early next week as I'm out of touch this weekend.

@taji
Copy link
Author

taji commented Apr 28, 2024

I'm returning to this to test CLAP, VST2 and LV2. I can't get CLAP plugins to load. I copied Cardinal.clap folder to ${HOME}/.clap. Reaper scans the folder successfully. But when I load the CLAP version of Cardinal in Reaper, I'm seeing this error message:

image

Do I need to install other files? Maybe the standalone application goes in /usr/local/share/cardinal?

TIA

@taji
Copy link
Author

taji commented Apr 28, 2024

Testing LV2 plugin, I'm seeing the inverse of the VST3 issue: at the 60 BPM we do NOT see the clock pulse event but at 120 bpm we do.

image

@taji
Copy link
Author

taji commented Apr 28, 2024

Testing VST2 fx plugin. I see the same missing spike at the 120 bpm marker:

image

@taji
Copy link
Author

taji commented Apr 29, 2024

@falkTX : any thoughts on getting CLAP working? I'd like to complete my testing.

I'm returning to this to test CLAP, VST2 and LV2. I can't get CLAP plugins to load. I copied Cardinal.clap folder to ${HOME}/.clap. Reaper scans the folder successfully. But when I load the CLAP version of Cardinal in Reaper, I'm seeing this error message:

image

Do I need to install other files? Maybe the standalone application goes in /usr/local/share/cardinal?

TIA

@dromer dromer added the bug Something isn't working label Apr 30, 2024
@taji
Copy link
Author

taji commented Apr 30, 2024

@falkTX : I see my problem is a duplicate of the issue here: #583

I'll monitor the discussion and test once a solution is provided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants