[RWP] reaaccess could stand an update.

[jinseng at yandex.ru]

Hi folks!
2 days ago Ivan wrote he returned to ReaAccess code. He was surprised with his own previous work and now tries to recall everything for the process of updating ReaAccess could go on. I hope we will get new version of ReaAccess in september.
Yes, we all were very patient these 6 month of stagnation and now it's time to step forward in ReaAccess.
Cheers!
Jinseng.

03.09.10, 22:51, "Scott Chesworth" <scottchesworth at gmail.com>:

> Hey Derek,
>  
>  As always, very valid thoughts. As humble users, we're still stuck in
>  this tricky situation where any and all future updates to the existing
>  ReaAccess code depend on one developer. Hopefully Jinseng will chime
>  in here if there's any news about progress.
>  
>  I know, everytime you post along these lines I reply along these
>  lines. I'm sure we're equally as frustrated seeing a plugin with this
>  much potential stagnating. I guess these replies are just one more
>  electronic hand being raised in agreement.
>  
>  Scott
>  
>  On 9/3/10, Derek Lane  wrote:
>  > Hi everyone.
>  > Though I still find reaper an amazingly useful daw, especially for my needs,
>  > I think it important that the developers consider updating reaaccess to
>  > utilize the additions made in the API.
>  > The release notes for the latest version of reaper contain a section of
>  > various automation, help, and other tidbits of information, now contained
>  > within the API.
>  > I think that the reaaccess plugin would do well to take advantage of these
>  > improvements.
>  > Also, would it be possible to develop a virtual control serfice which would
>  > then give us access to any automatable parameter in any given plugin or
>  > combination of plugins?
>  > Just some thoughts.
>  
>  _______________________________________________
>  RWP mailing list
>  RWP at reaaccess.com
>  http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>  
>