On Issue 2, I think what is happening is that you are saving your midi assignments per preset. If you open up the bottom panel “control” you will see an entry in the table for each midi assignment. If you select “Global”, it will save the assignments across all presets. Can you check if this works ok for you.
On Issue 3, yes there is a hiss that we have in the demo version, we’re going to add this to the demo restrictions window that appears on launch, you’re not the first to ask about this!
You’re posting in the correct forum! Looking forward to hearing how you get on.
finally I got to install and test the beta2
the GUI is now working
what I miss is a way to assign the modwheel as a modulation source
when I don’t want to assign it via the midi mapping, because I don’t want a global assignment of it,
ok I can edit each preset, but that is a bit cumbersome,
it would be much easier, if I could just make a right click on any circle under any parameter and choose the modwheel as modulation source. Or maybe aftertouch/pressure or …
I noticed when I load a preset for the sequencer LFO and edit the preset I need to save it before I reload the whole patch,
else it loads the unedited preset with the patch,
that could be confusing for users. I think the sequencer steps should be saved within the preset.
beside this the midi learn works fine here in reaper 4.xx
I did a short midi mapping automation test record here:
I mapped midi controllers from my keyboard to the filter mode, cutoff and resonance and recorded some
modulation this seems to work fine.
I will test more
after testing a bit more and playing a while
I wanted to assign the modwheel to a paramter via the midi learn,
that crashed reaper here
