-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fst parameter automation #13
Conversation
…ng of ROOT_DIR for location of 'mingw32-make.exe')
…t sequence of automatable parameters can be presented to the user. Though - note that also such a different ordering MUST NOT be changed in the future!
Conflict in build.bat was resolved by just using 'mine'. Conflict in src/synth.hpp was resolved by manually doing the appropriate change and some arising compile errors resulting from a now bigger amount of Int Parameters got fixed by adding some additional code.
FYI: I cherry-picked your Windows build improvements (with one or two slight modifications), and the parameter automation that I've talked about (#7) is almost complete on the (This approach also has the additional benefit of getting the automated parameters smoothed for free.) |
Windows build improvements - Cool! |
LoL, Wine (a Windows-compatibility layer which allows can run Windows applications on Linux and other systems by translating the Windows API calls) tricked me by allowing both forward slashes and backslashes as a directory separator for the Thanks for pointing it out, it's fixed in 6517121 |
Hmmm, just found out, that MIDI Learn for other FST's works in EXT64 beta - tested with 'SurgeXT' and 'blooo' (by 'full bucket music'). But it does not so for js80p 64 bit (1.4.0 or newest from main branch). |
I don't think there's anything in MIDI Learn which would depend on the CPU architecture. Also, the feature works perfectly in Reaper on both Windows and Linux, and it kinda-sorta worked in FL Studio as well. Well, apparently FL Studio swallows MIDI CC messages (except for the modulation wheel's CC 1), and the only way to get them to work is to manually assign the CC numbers to exported parameters. Basically they're doing the VST3 way of MIDI CC handling in VST2, just slightly worse. JS80P 1.4 only implements MIDI Learn for actual MIDI CC messages, but since it's broken in hosts which prefer needless complications like this, I had to also make it work with these MIDI CC proxy parameters. Long story short, if you are sure that the CC messages aren't swallowed by the host, then the only possibility I can think of is that your MIDI keyboard is configured to send CC numbers which are not supposed to be interpreted as 0-127 numbers, e.g. which are associated with on/off switches (64-69), or represent the LSB half of 14 bit controller messages (32-63), etc. |
Good news! Not sure, what 'intermediate' dev version I built and used before, but now all is good! |
Contains both VST banks as well as draft for parameter automation.
All current 'regular' parameters are automatable.
To be rejected after testing / playing around with it.
Note:
In case you want to use energyXT for trying out...
The new 64 bit beta EXT64 doesn't seem to properly support MIDI CC yet.
Thus I had to build a Windows 32 bit version of js80p to try it out together with MIDI CC recording in energyXT3 32 bit.
(The demo version of it can be downloaded here: https://www.xtsware.com/)
It is possible though to manually create automation of parameters in EXT64.