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

HO-DirAC automation not recording in Reaper #44

Open
hectorC opened this issue Sep 20, 2021 · 6 comments
Open

HO-DirAC automation not recording in Reaper #44

hectorC opened this issue Sep 20, 2021 · 6 comments
Labels
help wanted Extra attention is needed

Comments

@hectorC
Copy link

hectorC commented Sep 20, 2021

For some reason it seems that any value changes for the Yaw, Pitch and Roll parameters do not get recorded in the corresponding automation track, even though the automation is set to Write. If I move any of those parameters in the VST's UI, while Reaper is recording automation, nothing gets recorded. This is the same in the case of controlling them using OSC messages (which is what ultimately I'm trying to do). What's strange is that the automation values in the track header do change (both the red knob and the green number). Additionally, the only way for automation to be written is if I manually move the red knob in the track header (see attached image for reference), doing this also changes the parameter in the plugin. Other plugins are working as expected.

image

@hectorC hectorC changed the title HO-DirAC automation not recording properly in Reaper HO-DirAC automation not recording in Reaper Sep 20, 2021
@sguyader
Copy link

sguyader commented Sep 22, 2021

It seems like it's more general than that, I have the same problem with ambiENC, which doesn't record the azimuth nor elevation automation envelopes from the plugin UI in Reaper. The automation is written only by moving the sliders from the track envelopes or directly writing on the envelopes.

Edit: are you running the beta version of Reaper for MacOS arm? I just found that in fact the automation problem seems to come from bridged VST's: the same happens with other non native plugins. If I try to write the automations in the clang build (intel code) there's no issue.

@leomccormack
Copy link
Owner

Hi! I'm not actually entirely sure why the parameters are not writing automation data here. Are any other plugins (also from other vendors) having the same issue?

Indeed, @sguyader bridged VSTs can cause all sorts of issues. 64-bit REAPER is recommended.

@merijn76
Copy link

merijn76 commented Oct 7, 2021

Hi, I have the same automation issue, with the SPARTA panner, and I do run Reaper64 (Mac, Mojave), and have disabled bridging. Just tried with the brightness panner from SoundParticles, and writing automation from their GUI works, so appears to be a SPARTA GUI thing, unless I'm missing something..?

@hectorC
Copy link
Author

hectorC commented Oct 8, 2021

Hi! I'm not actually entirely sure why the parameters are not writing automation data here. Are any other plugins (also from other vendors) having the same issue?

Indeed, @sguyader bridged VSTs can cause all sorts of issues. 64-bit REAPER is recommended.

I'm having this problem with 64-bit versions of Reaper and plugins on a Windows PC. Other plugins are working fine.

@hectorC
Copy link
Author

hectorC commented Oct 8, 2021

Here's a video showing the problem, in case it can be of any help.

bandicam.2021-10-08.17-59-54-820.mp4

@leomccormack leomccormack added the help wanted Extra attention is needed label Oct 28, 2021
@Greaseball0815
Copy link

I have exactly the same problem. The automations are not recorded when the source is moved in the GUI. This is definitely a bug in the plugin and not in Reaper, because it behaves identically in Ardour.

SpartaRoomSim.mp4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants