Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Bug Reports

Reply
 
Thread Tools Display Modes
Old 01-14-2020, 03:58 PM   #1
mccrabney
Human being with feelings
 
mccrabney's Avatar
 
Join Date: Aug 2015
Location: Harblesburg, Texas
Posts: 2,222
Default VST3 params don't respond to next AI env points (FIXED)

edit - skip to post 2 for a better demonstration of the issue regarding vst3

i just noticed that this bit me on a project that i just completed and distributed. this resulted in a part being lowpassed out of a whole song until the very end, where the AI exists. luckily it wasn't a critical part and apparently i didn't miss it much while reviewing the masters, but this could be quite serious

issue: here, a track has an AI at the end of the project. this AI starts at 100% param value and ends at 0% param value.

expected behavior: clicking anywhere before this AI should result in the param moving to 100% value.



bug: as shown in the gif, this doesn't always happen. above, i click into the AI and then click before the AI, expecting the value of the cutoff to jump to 100%. it does once, doesn't once, and flickers strangely once.

i've noticed this in several Waves plugins as well as this HY-Filter3 vst3 plugin. normally, this works fine. maybe it's a vst3 issue? i can't get it to happen on ReaQ
__________________
° using REAPER as host/arranger/sequencer to write instrumental beat music.
° striving for a loop-based, controller-centric midi recording/editing workflow.
° colored tracks/items: optionally respect "selected track/item" theme color

Last edited by mccrabney; 02-04-2020 at 05:01 AM.
mccrabney is offline   Reply With Quote
Old 01-14-2020, 04:30 PM   #2
mccrabney
Human being with feelings
 
mccrabney's Avatar
 
Join Date: Aug 2015
Location: Harblesburg, Texas
Posts: 2,222
Default

more info: here's some supporting evidence suggesting that it is a vst3 issue. here, 2 instances of HY Filter3 are loaded: the vst version and the vst3 version, since i had both.

after hitting play and having the play cursor pass over the AI, if you then stop and move the edit cursor to earlier in the project, the parameter does not adjust to the next AI point.

sorry for the large licecap

__________________
° using REAPER as host/arranger/sequencer to write instrumental beat music.
° striving for a loop-based, controller-centric midi recording/editing workflow.
° colored tracks/items: optionally respect "selected track/item" theme color
mccrabney is offline   Reply With Quote
Old 02-04-2020, 05:00 AM   #3
mccrabney
Human being with feelings
 
mccrabney's Avatar
 
Join Date: Aug 2015
Location: Harblesburg, Texas
Posts: 2,222
Default

bump.
__________________
° using REAPER as host/arranger/sequencer to write instrumental beat music.
° striving for a loop-based, controller-centric midi recording/editing workflow.
° colored tracks/items: optionally respect "selected track/item" theme color
mccrabney is offline   Reply With Quote
Old 02-04-2020, 07:48 AM   #4
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 10,582
Default

Thanks for the report, I think we can improve this behavior.
schwa is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 01:10 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, vBulletin Solutions Inc.