[RWP] ReaAccess development update (of sorts)

Wed Sep 28 03:14:28 EDT 2011

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

i don't think reaper itself is opensource, though the api(s) to write
new code for it are well documented, i've seen the links on the reaper
site.

On 9/27/2011 9:36 PM, Kevin Brown wrote:
> I am not skilled in that area of writing programs either,...I
> thought Reaper is more of an open source software?,...I mean, It
> appears that people make lots of plugins for reaper, don't
> they?...
> 
> I wonder how much it would cost to pay someone to write an access 
> program for reaper?...
> 
> I would gladly pay for a "closer to home" accessible program for 
> reaper,...I think it would be well worth it!...
> 
> 
> 
> Original message:
>> You would think that the API  itself would be published.  How did
>> Ivan and friends learn of it? Personally, I am not skilled in the
>> art. But, it would appear that, if that project is going to be
>> successful, the one of providing access to Reaper, it needs to be
>> brought a lot closer to home. But also, what you see here is an
>> unfortunate shortcoming of volunteer efforts.  An effort like
>> this is pretty complicated, takes a lot of time and effort, and a
>> lot more likely to be successful if the person writing the access
>> pluggin also needs it personally. I wish I had the skill.
> 
> 
> 
>> ----- Original Message ----- From: "Derek Lane"
>> <derek at pdaudio.net> To: "Reapers Without Peepers"
>> <rwp at reaaccess.com> Sent: Monday, September 26, 2011 11:34 PM 
>> Subject: Re: [RWP] ReaAccess development update (of sorts)
> 
> 
>>> Too bad the decompilation of DLL's isn't practical, otherwise,
>>> the questions of being able to talk to the reaper API, add
>>> functions to said API, and talk to screan readers  of all
>>> sourts could be answered.
> 
> 
>>> ----- Original Message ----- From: "Jim Snowbarger"
>>> <Snowman at SnowmanRadio.com> To: "Reapers Without Peepers"
>>> <rwp at reaaccess.com> Sent: Monday, September 26, 2011 8:12 PM 
>>> Subject: Re: [RWP] ReaAccess development update (of sorts)
> 
> 
>>>> I guess old Ivan fell in the vodka tank.
> 
>>>> Maybe there are others around, hopefully closer to us,  smart
>>>> enough to develop a similar pluggin. One can always hope. 
>>>> ----- Original Message ----- From: "Scott Chesworth"
>>>> <scottchesworth at gmail.com> To: <rwp at reaaccess.com> Sent:
>>>> Sunday, September 25, 2011 9:22 PM Subject: [RWP] ReaAccess
>>>> development update (of sorts)
> 
> 
>>>>> Hey all,
> 
>>>>> I relay this news to RWP with the proviso that nobody
>>>>> shoots the messenger. Cyber handshake on that before
>>>>> reading any further.
> 
>>>>> As most of you will be aware, a few months back Ivan issued
>>>>> a list of features and fixes expected in ReaAccess 2.0 for
>>>>> a September release. At this point, nobody English-speaking
>>>>> involved in ReaAccess's upkeep has a clue what's going on.
>>>>> I've written to Ivan for info, but having given him fair
>>>>> time to respond and received nothing, I thought I'd fill
>>>>> RWP in on what's hot on the rumour mill.
> 
>>>>> Word on the street is that the ReaAccess project has a new 
>>>>> Moscow-based owner or owners unknown. I've heard rumblings
>>>>> that the plugin will be a paid product from 2.0 onward, but
>>>>> haven't seen anything about a price. Similarly, haven't
>>>>> been able to track down anything about a firm release
>>>>> date.
> 
>>>>> I think it's worth pointing out that this is exactly why
>>>>> ReaAccess doesn't have a proper site, doesn't have anything
>>>>> beyond the absolute bare bones of documentation, and has
>>>>> struggled to make a positive impact. Beyond the first few
>>>>> versions when time spent translating and bug swatting felt
>>>>> like time well spent, I haven't been able to justify 
>>>>> pouring resources into the project (much as I love the DAW
>>>>> it enables me to use. There have been plenty of offers of
>>>>> what would have been valuable contributions flat out
>>>>> declined by the development end of this opperation, and
>>>>> even more contributions promised that never materialised
>>>>> due to a lack of faith in the way the project has been run
>>>>> from day one. Sad to say it chaps, but it seems like those 
>>>>> reservations have been realised. If that applies to you,
>>>>> take comfort in the fact that you guessed the correct
>>>>> basket to place your eggs in.
> 
>>>>> For now, that's all I've got in the way of an update.
>>>>> Russian speakers on here may wish to investigate
>>>>> www.reaaccess.ru, perhaps there's a list like this one
>>>>> being maintained where you might be able to get more info
>>>>> from our elusive developer (or his new boss). Should you 
>>>>> have any success, 75 plus RWP's here would appreciate the
>>>>> heads up. This list will still be actively moderated and
>>>>> the latest build of ReaAccess that I have will remain
>>>>> available, until the man says otherwise.
> 
>>>>> Remember what we shook on a couple of minutes ago...
> 
>>>>> Scott
> 
>>>>> _______________________________________________ RWP mailing
>>>>> list RWP at reaaccess.com 
>>>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
> 
> 
> 
> 
>>>> _______________________________________________ RWP mailing
>>>> list RWP at reaaccess.com 
>>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
> 
> 
> 
>>> _______________________________________________ RWP mailing
>>> list RWP at reaaccess.com 
>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
> 
> 
> 
> 
>> _______________________________________________ RWP mailing list 
>> RWP at reaaccess.com 
>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOgslUAAoJEIaKvi7tbzRHSOcH/2Ea074Oj8VFucm0PRj/jLct
XxMnZzgh2Tz+Rg2d89Ooe6Q0oS86h2TNRJulfobhU/fPRV8HSfMuDjDARkEKv5sF
tNtr+ng+DjD5ohaVjMLW8UTtEz64BSLYHXjA90TkjsZ9a9HJy7WAzhshOu8n408o
JpmnGeFCTIEY4VgVOzLiq5HnM6EnmDYhi8voqz/+dFUJOSTfejx95tzs3lEmSAZ8
Fx/MlTdjKgysNunnwluH3eF0nHTV548VjhuGMITfYE7BPnzCucSG7nxbiDwiaLeM
joGUy/U4r5dak8x3Th6SZcaNeU20nshSVrzRVKtM885+cRAbSoadG6QPmcNK2q0=
=dRjE
-----END PGP SIGNATURE-----