Can't Save Fx Chains in New Version

[Christmas]

Hi, I am new to the forum but have been using Reaper for about 2 years now. I just got the newest version installed a few days ago and just yesterday I upgraded Windows 10 to the new 1903 version. Don't know if the Windows upgrade has anything to do with this problem or not but there you are. For some reason Reaper will not save new Fx chains. It will let me see the old Fx chains I saved before but I cannot save new ones. When I select the "Save Fx chain..." option it looks like it will work and I can enter a Fx name but nothing new shows up in the Fx list after I click SAVE. Anyone else got this problem? Thanks for the help.

[nicholas]

Hi, Just to make sure we're on the same page, do you mean that you scroll down the list of categories and the category FX Chains isn't there?

If that's the case go to Options menu on the Add Fx window, then Show in left pane list. FX chains should now appear on list.

Select FX Chains on left and your FX chains should appear in the right hand pane.

You can also do to Options on main reaper menu, Show REAPER resource path, navigate to FX chains directory to see if they are there.

If not, in Windows Explorer you can search for .fxchain files in case they are being saved elsewhere.

[akademie]

Originally Posted by nicholas

Hi, Just to make sure we're on the same page, do you mean that you scroll down the list of categories and the category FX Chains isn't there?
...

I think that it is not that case, nicholas, as OP explains here:

Originally Posted by Christmas

...For some reason Reaper will not save new Fx chains. It will let me see the old Fx chains I saved before but I cannot save new ones. ...

[nicholas]

Originally Posted by akademie

I think that it is not that case, nicholas, as OP explains here:

... which is why I also suggested this:

You can also go to Options on main reaper menu, Show REAPER resource path, navigate to FX chains directory to see if they are there.

It is possible that they might be being saved to a wrong directory ...

... or it could be something else?