Sunvox with midi encoders, light-up pads, etc
Posted: Sun Oct 01, 2017 7:04 pm
Hey hey forum buddies,
I am awaiting delivery of a class-compliant midi controller keyboard (arturia minilab mk2) which has "endless" rotary controllers which send midi cc messages, and LED-illuminated pads. I was wondering how sunvox deals with these. So, some questions hopefully someone can help me with:
1) If I map an encoder to a specific parameter of a specific module, will sunvox be able to update the controller value if I change it in the software (e.g. with the mouse)? This would help avoid parameter jumps when touching the encoders.
2) If I load a saved sunvox song file which has midi controller assignments already created before it was saved, will it be able to send the current cc values of the assigned parameters out to the controller? This would make it possible to load different songs without the "parameter jump" issue when touching an encoder for the first time.
3) I am aware that the module bypass and mute options are not directly midi controllable - i figure there's probably a workaround but haven't got round to looking into it. Assuming this is doable, the same questions as above really: can sunvox send some kind of snapshot of midi cc values either on project load, or if values are updated e.g. via the mouse? This would enable me to see which effects are "active" by looking to see which pads are lit up. Alternatively, if someone has a workaround or a different way of achieving a similar result I would love to hear it.
I am awaiting delivery of a class-compliant midi controller keyboard (arturia minilab mk2) which has "endless" rotary controllers which send midi cc messages, and LED-illuminated pads. I was wondering how sunvox deals with these. So, some questions hopefully someone can help me with:
1) If I map an encoder to a specific parameter of a specific module, will sunvox be able to update the controller value if I change it in the software (e.g. with the mouse)? This would help avoid parameter jumps when touching the encoders.
2) If I load a saved sunvox song file which has midi controller assignments already created before it was saved, will it be able to send the current cc values of the assigned parameters out to the controller? This would make it possible to load different songs without the "parameter jump" issue when touching an encoder for the first time.
3) I am aware that the module bypass and mute options are not directly midi controllable - i figure there's probably a workaround but haven't got round to looking into it. Assuming this is doable, the same questions as above really: can sunvox send some kind of snapshot of midi cc values either on project load, or if values are updated e.g. via the mouse? This would enable me to see which effects are "active" by looking to see which pads are lit up. Alternatively, if someone has a workaround or a different way of achieving a similar result I would love to hear it.