Quote:
Originally Posted by Geoff Waddington
|
Now, there's CIA again, when does FBI enter the scene?
I'm sure "The control surface integration project" is a brilliant effort, and of good use to many. But that project is also limited by poor implementation of OSC in Reaper. Sure, there's always possible to do workarounds to achieve the goal, but... Why not try to fix the problem instead? If your boat takes in water, you could buy a pump, right - boat's not sinking, goal achieved. But wouldn't it be wiser to plug the hole?
Let's say I want a simple stomp box, with the the sole purpose of disable a FX on a track (i.e #28), and enable another FX on the same track. No problem with OSC. Now, in this case the problem everyone will face will be: There's no other ID to use other than the track number! What happens when a track is inserted before my track? My tracknumber becomes #29, and my stomp box controls the wrong track.
I have MANY more examples of simple controller tasks generating complex workarounds... Sometimes the boat sinks because of the weight of pump #12...
And then the frustration grows, thinking of how little code needed in Reaper (now, that's a guess from me as a "no Reaper dev") to fix this.
Again, I could fixate my eyes on the CSI "framework", but for my simple stomp box it seems overkill...