- User Since
- Nov 11 2016, 5:33 PM (171 w, 6 d)
Wed, Feb 26
The first line says Wing version 1.03(10) - but I should have said 1.03(12)...
Sat, Feb 15
Sun, Feb 9
REALLY looking forward to checking out anything you have for the WING! Thank you for working on it!
Nov 19 2019
version 1.07 pro version works perfect with an acer chromebook N17Q5 running chrome ver 78.0.3904.70. 8 points of muktitiuch working fine. did not try connecting to console. I have screenshots if needed.
Jul 8 2019
neat idea, I also dig the idea for up/down action. it'd really be neat if there was a "round up / down" function was implemented for that, so that any jumps in value could be adjustable. I sure hope that a similar function might be applied to any controls, like the delay settings someday - then we would not even need to touch the console to get the tap tempo settings set right! right now that is really the biggest reason I have to hang around the console area for shows...
May 6 2019
Nov 12 2016
I think I am wrong, it just seems that it just wanders the timimg for it all over the place for some reason, sometimes it seems to be over 400ms of variation (enough to be a full half measure off on a delay that is over 800ms), then wander right back to be right in near perfect sync. So, how about a dumb request then? Any chance to have the option to read the current delay value from the console, and use a delay built into the app software maybe to make the button blink? I must say though, that setting the console delay in this new custom layer mode with this different hold/release method, sure is dead on, quick, and reliable!
Nov 11 2016
oh yeah, the tiny bit of lag is no biggie, it has to be triggered from a osc message from the console over the network, so it is understandable that there would be a little delay to it...
I double checked it, the tap button (where the "regular mute group buttons" are) stays in time, but lags just a bit behind. the tap button found in the custom layer, somehow oddly blinks just a bit faster than it should. I tested it with two tablets with different versions of android but your same app version, same problem on both.