In this epic length video I run through an explanation of actually setting up the Universal MIdi Encoder for the Wyvern using PuTTY terminal program running on my laptop.
That config process using Q&A is pretty pedestrian for 21st century software. Have you designed a more friendly interface since Jan 2017? If not, then a worksheet should be available to fill in ahead of the long interrogation.
Pistons would be wired just like stops. Grouped into 12 with one common line just like the keys and stops. Assign another midi channel for them and then use the midi auto-detect feature in the hauptwerk software to assign the relevant events to the pistons on the virtual organ. Basically everything can be treated just like the keyboards, stops, thumb pistons, toe pistons/studs etc. Hope that helps...
That config process using Q&A is pretty pedestrian for 21st century software. Have you designed a more friendly interface since Jan 2017? If not, then a worksheet should be available to fill in ahead of the long interrogation.
What if you want to add pistons? How would one incorporate pistons into this process? I don’t see an option for programming pistons.
Pistons would be wired just like stops. Grouped into 12 with one common line just like the keys and stops. Assign another midi channel for them and then use the midi auto-detect feature in the hauptwerk software to assign the relevant events to the pistons on the virtual organ. Basically everything can be treated just like the keyboards, stops, thumb pistons, toe pistons/studs etc. Hope that helps...
@@sussexbob182Sure, but for completeness and clarity this config program should cater explicitly for pistons, too. Maybe by now it does.