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

Thread Tools Display Modes
Old 01-30-2024, 08:47 PM   #1
Human being with feelings
Join Date: Aug 2019
Posts: 665
Default Recalling presets in Cockos/JSFX plugins resets I/O pins

The title says it all. I use FX on pins other than 1 & 2 about 50% of the time. If I have an FX set to I/O pins other than 1 & 2, and recall a preset, the I/O pins reset - or more accurately, Reaper recalls the saved state of the pins (usually 1 & 2).

Both JSFX (third party and Cockos) and Cockos VSTs (ReaComp, ReaEQ, etc.) do this.

3rd party non-jsfx (LV2, VST, and VST3) plugin's behavior pinpoints the issue. If I recall a preset from the plugin's preset dialog (if it has one), it doesn't touch the pins. If I recall a preset from Reaper's FX preset dialog, it changes the pins. It sets the pins to the saved state. If the plugin is on pins 5 & 6 when I save a preset using Reaper's preset dialog, if I open that plugin in a different project and set the pins to 7 & 8, when I recall that preset, it puts the plugin on pins 5 & 6 (the saved state).

This makes it super tedious to audition presets, and if someone doesn't know it's happening, it will cause lots of confusion. Who would think to check the pin configuration when recalling a preset drops the plugin out of the signal chain?

How to reproduce:
1. With any plugin on a track, set the track to 6 channels.
2. Set the plugin I/O pins to 5 & 6
3. Save the setup as a preset using Reaper's "save presets" dialog
4. Set the plugin I/O pins to 1 & 2
5. Recall the preset
6. the plugin I/O pins will be set back to 5 & 6

I'm running Reaper 7.09 on Ubuntu. I tried this on an older 6.xx version of Reaper and it was the same behavior.

I hope this gets addressed.
PMan is offline   Reply With Quote
Old 02-22-2024, 04:31 PM   #2
Justin's Avatar
Join Date: Jan 2005
Location: NYC
Posts: 15,796

I suppose we need an option for this…
Justin is offline   Reply With Quote
Old 02-23-2024, 04:26 AM   #3
Human being with feelings
DarkStar's Avatar
Join Date: May 2006
Location: Surrey, UK
Posts: 19,686

Just thinking out loud ...

A preset captures all the available parameters of the plug-in itself. The connections of its inputs and outputs is something separate.

On that basis, Reaper presets need never save the IO pin connections. Or IO pin connections stored in Reaper presets are ignored on loading the preset.
DarkStar ... interesting, if true. . . . Inspired by ...
DarkStar is offline   Reply With Quote
Old 02-23-2024, 07:36 AM   #4
Human being with feelings
souk21's Avatar
Join Date: Mar 2021
Posts: 492

I think there's definitely interest in having a default preset with non standard pin connections for example
souk21 is offline   Reply With Quote
Old 02-24-2024, 03:21 PM   #5
Human being with feelings
Join Date: Aug 2019
Posts: 665

My thought is, save the pins configuration in a track template, where there would be multiple plugins on various pins. Within a track template, the user would still want to audition presets without changing the pins configuration. I can't think of a use case where the user *wants* to change the pin config when changing a preset...

I came across this when I put Saike's Filther jsfx behind a synth on pins other than 1/2. I set the pins up, and then tried to cycle through the presets to test them. It was just by chance that I checked the pins...

A config option to disable the current behavior works for me. If anyone wants the current behavior, more power to them. I would just *love* to be able to turn it off.


Last edited by PMan; 02-24-2024 at 08:58 PM.
PMan is offline   Reply With Quote
Old 04-12-2024, 10:30 AM   #6
Human being with feelings
Join Date: Aug 2019
Posts: 665

Please give some attention to the preset/pins issue.
PMan is offline   Reply With Quote

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 12:24 AM.

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