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

Automation "Touch" mode not working in Reaper #219

Closed
alfonso73 opened this issue Dec 13, 2020 · 7 comments
Closed

Automation "Touch" mode not working in Reaper #219

alfonso73 opened this issue Dec 13, 2020 · 7 comments
Labels

Comments

@alfonso73
Copy link

alfonso73 commented Dec 13, 2020

Hi!
My enviroment : Windows 10 (64bit), Reaper 6.18dev1212 (64bit), Camomile 1.07 VST3, Sample Rate 44.1 kHz, ASIO buffer 64 samples

Steps to reproduce :
Load a Camomile VST3 plugin and try to automate any of its parameters using Reaper automation "Touch" mode.

Observed Results :
Except (sometimes) the very first automated parameter the parameters doesn't respond to automation and stay at their level.

Expected Result :
The parameters should respond to their movement/automation when automated in "Touch" mode.
BTW in all the other automation modes they respond as expected.

I've found similar problems with other Juce based VST3 plugins as for example here...
asb2m10/dexed#244

Here's something that might give some clue
https://forum.juce.com/t/touch-automation-toggles-beginparameterchangegesture/21528/23

Here's a video showing the issue https://youtu.be/JYpSg-vJfLc
(the constant rhythmic glitch you here is related to buffering issue in OBS recording so nothing related to Reaper or Camomile)
ohh...and i realized that Camomile VST3 isn't visible beacause i'm video recording the reaper's windows only. But you can see the parameters being automated while i'm moving Camomile's sliders i put i my patch.

@alfonso73
Copy link
Author

hi @pierreguillot! Do you have any idea on what's goin' on with Camomile and Reaper's parameter automation in "Touch" mode?
thanks
ps...i'm trying to build some VST using else libraries and as soon as i resolve some polyphony issues i'll share it.

@pierreguillot
Copy link
Owner

No, I didn't have the time to test yet... sorry. I'll try to do it soon.

@alfonso73
Copy link
Author

Thanks for your reply @pierreguillot. Let me know when and if you need some testing when you'll have the time to look into it. best!

@pierreguillot
Copy link
Owner

I tested on macOS with the plugin AlmondOrgan and it seems to be okay. I'll test on Windows later today.

Can you ensure that the plugin is not muted and so on? Because if the DAW doesn't call the audio callback of the plugin, the messages might not be sent to the plugin and retrieved.

Is there any error message in the Camomile console? And can you share a basic patch that reproduces the problem?

@pierreguillot
Copy link
Owner

I tested on Windows and there is no problem either.

@alfonso73
Copy link
Author

Hi @pierreguillot. Yes you're right. I just realized that i was messing with the whole VST3 parameter management in my pd patch. I've adopted your [gui.link] abstraction and your smart naming convention ($0-parametername, $0-parametername-sld-s, $0-parametername-sld-r, $0-parametername-nbx-s, $0-parametername-nbx-r). Everything works fine.
thanks!
PS i wonder if this repo is the correct place for make some request about your Camomile examples. I don't want to clutter your developing space.

@pierreguillot pierreguillot added question and removed bug labels Jan 5, 2021
@pierreguillot
Copy link
Owner

PS i wonder if this repo is the correct place for make some request about your Camomile examples. I don't want to clutter your developing space.

Yes, please create an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants