ah, back to the real issue: yes there is an elevated FR, at the BOTTOM of the list, IGNORED. yes it has lots of votes but it doesent have enough, or at least not enough to warrant the feature beig added thats why i started this thread. and this thread is a good summary of the workarounds available for us for now. as for the control surface and my bitchiness, it started when yertogh posted a vote that he can wait forever relative to this cause. otherwise, the ahhaaaahh thing was humour, you know, wanting send support, finding complete surface support, only to find one send only supported... and the report about the broken link was just a fact. and the anger expressed in the initial post was just that, partly internally justified anger (which is my feeling its not anyone elses responsibility) not bitch. bitch means the intent to injure, anger is really sadness pushed into the background.
--------------------- 98 328i Slower does not mean safer.
focussed: if it shows the send channel name, as well as even more so than the receive channel name. make sure the channel # is 1 to 1 with scroll wheel, ie 1 scroll wheel click to one channel hey, it needs a channel # and a send # knob doesent it, ie channel 7 send 5... now, i wonder if the one interface could have me learn a send by learning that knob as it does, then when i change channels, have the learn stay with the first channel that was selected, (there could be a button called 'multi send' that when off the learn stays with the knob when channels changed), then when i change the channel with your lower left channel knob, the UI scrolls through the channels, where if a current channel had a learn on already, and i learned again it would have a new learn assignment. IE even though the first learned knob isnt on your Gui anymore, the control surface send would still operate... this would eliminate a GUI with multiple sliders, its like a control surface mapper. anyway, as it is now its an excellent way to assign sends on the fly, options this looks like the end all temporary workaround.!!!
the mapper function really would be more like a utility that doesent reside in a single channel strip... actually it doesent even need to be in a channel strip at all though thats the easiest implementation... since i control usually only one send per channel, thats why i liked the v 1.7 channel control residing on the plug, IE that way i dont have a plugin slot per send, taking up GUI space on my mixer all over the mixer on many channels, just 'one rea to control them all!'... anyway theres a lot of potential here...
yea! that pretty much does it... oh yeah, i was looking at having it address more than one channel at once too. btw, showing the track selector as a param knob allows 1 to 1 scroll wheel values, just not in the js style gui, so thats fine. -cheers
--------------------- In Chicago? www.euroteknik.com