Mmmm....
A few questions:
- Does that use just one input on the adcon leaving the other 7 free to be used for audio?
- Are there any interference / crosstalk issues when you use both hands on those controls?
- To help determine if it's possible in Scope as it stands can you describe how you would treat the signal at the Max/MSP end?[/quote]
Ok, These are two different Things:
When i used the adcon than of cause i did nö multiplexing- i just send an sinewave to the Pots, than send the outcome to the adcon (One converter and Adat Channel per Pot) and readout the rms value in max. That Way you easily get the nob Position. I think that should Not be to difficult to do in scope too at least in modular by using Envelopes fallowers- if its possible to Chance a mrc Objekt in sdk that it has 8 or 16 Audio Inputs it should Not be a Problem to Extrakt the Level as a value for further use as control... Of cause this Way nö crosstalk is going on- but that method is also somehow inefficient.
The multiplexing idea is only metioned related to the Initial Topic of the Tread - Building a dedicated converter from scratch- bacause using a whole adat channel for one control would be a waste of bandwith and costs a lot of audio io..
Whatever comes Out will be Kind of Special and Never will have the Ease and Workflow you currently have with cc controls in Overall scope. I gues for standart use of Control surfaces there (hopefully) other solutions will come up- might be osc, copperlan or whatever you have in mind...also for Manual controll a few milliseconds of Delay Caused by methods using the Host CPU would Not be a Problem. Using Audio/Adat Is more relevant for
Modular task where realtime processing is needed and a Lot of Signals going in and Out of the Box at the Same Time..