Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
[FIXED in 2017.09] - FX chains still broken with VST 3
This has been around for ages and is the reason why I did not bother to use FX chains at all in recent years. Now I tried again, still same story. - If a FX chain is created containing just a single VST3 (!!!) plug in, ALL parameter indices are shifted by one i.e. you cannot access the first parameter at all, if you assign the 2nd and actually turn the knob, you modify the first parameter and so on ... the same shift has also always been there when trying to ACT map a VST3 plug (I assume for the same reason that there is a parameter with index 0 where in VST2 it probably starts at 1 ???)
- Interestingly behavior above does not exist if you pull the VST3 into a ProChannel strip and create a FX chain this way ... BUT I quickly managed to completely break the link between the FX chain and the VST3 GUI - don't know how, but changing knobs on the FX chain no longer adjusted anything on the VST3 ...
- In both cases if you open the plug in GUI and adjust a knob, it is not reflect on the FX chain GUI (one way road only FX chain updates VST3 GUI but not the other way) ... so display values go out of sync until you dial the FX chain knob again and overrule the value adjust on the VST3 GUI
BTW I tried this using WAVES SSL Compressor and Platinum 2017.07 (dont think it would be any different in 2017.09 as these problems have been around for a while now)
post edited by Rob[at]Sound-Rehab - 2017/10/06 18:02:14
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: FX chains still broken with VST 3
2017/10/05 06:03:20
(permalink)
sorry for the typos above ... but if I edit I'm sure the post will disappear
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
Keith Albright [Cakewalk]
Max Output Level: -68 dBFS
- Total Posts : 1117
- Joined: 2006/07/10 15:44:42
- Location: Boston, MA
- Status: offline
Re: FX chains still broken with VST 3
2017/10/05 14:25:48
(permalink)
|
azslow3
Max Output Level: -42.5 dBFS
- Total Posts : 3297
- Joined: 2012/06/22 19:27:51
- Location: Germany
- Status: offline
Re: FX chains still broken with VST 3
2017/10/06 15:17:41
(permalink)
Rob[atSound-Rehab]
This has been around for ages and is the reason why I did not bother to use FX chains at all in recent years. Now I tried again, still same story.
- If a FX chain is created containing just a single VST3 (!!!) plug in, ALL parameter indices are shifted by one i.e. you cannot access the first parameter at all, if you assign the 2nd and actually turn the knob, you modify the first parameter and so on ... the same shift has also always been there when trying to ACT map a VST3 plug (I assume for the same reason that there is a parameter with index 0 where in VST2 it probably starts at 1 ???)
I remember that was addressed some time ago. I have just checked to be sure, in my Platinum (not so many) VST3s are mapped correctly, in FX chains and in ACT Learn. And just to remember how it was broken... under X3 the behavior is as you describe.
Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc. www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
|
msorrels
Max Output Level: -70 dBFS
- Total Posts : 1025
- Joined: 2003/11/08 02:04:59
- Location: Pittsburgh, PA
- Status: offline
Re: FX chains still broken with VST 3
2017/10/06 16:13:45
(permalink)
I couldn't make this happen either, seems to work right for me. And this part In both cases if you open the plug in GUI and adjust a knob, it is not reflect on the FX chain GUI (one way road only FX chain updates VST3 GUI but not the other way) ... so display values go out of sync until you dial the FX chain knob again and overrule the value adjust on the VST3 GUI I believe is by design and how it is supposed to work.
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: FX chains still broken with VST 3
2017/10/06 18:05:44
(permalink)
Hi Guys!
Thanks for trying this and giving feedback.
I had just installed the latest official release (2017.09) and the problem above with parameter assignments shifted by 1 was gone (!!!)
So I felt a bit stupid and went back to 2017.07 to see if I was chasing ghosts, but I was not as in 2017.07 I could immediately reproduce with WAVES VST3 ... back to 2017.09 it appears fine ... rolling out 2017.09 to the main system right away ...
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|