[RWP] reaaccess could stand an update.

[Monkey Pusher]

will you please post a link to tommorrows audio for those of us who
can't listen live please thanks.

On 9/3/10, Derek Lane <derek at pdaudio.net> wrote:
> which is exactly why no one has heard a single reaper reference podcast from
> yours truely.
> However, tomorrow at 2 eastern, my show WDGLFM, will take a break from its
> normal format to do an extensive review/tutorial on reaper, maybe answering
> a lot of the starter questions on this list, and getting in to recording,
> mixing, some of the plugins, how the structure works in reaper, and, for
> example, what all can be done with the items on a track.
> The station on which I broadcast is called TBRN, and the site, believe it or
> not *pretends to gasp* is at www.tbrn.net
> I figure it's easier to do a live show, with a few recorded segments than a
> podcast on something which has a questionable future in terms of development
> from the access front.
> ----- Original Message -----
> From: "Scott Chesworth" <scottchesworth at gmail.com>
> To: "Reapers Without Peepers" <rwp at reaaccess.com>
> Sent: Friday, September 03, 2010 7:59 PM
> Subject: Re: [RWP] reaaccess could stand an update.
>
>
>> Indeed, it's good how you find a new angle to post from each time.
>> Given that none of the previous angles you've come at this from are
>> redundant yet, it's serving the dual purpose of building up a wishlist
>> if/when development starts again.
>> Can't say for sure how much work would be required to make the
>> wishlist a reality, having never seen the source, but the project has
>> never been short of offers of contributions on a development level.
>> Open source is surely the most efficient way forward for ReaAccess,
>> especially now that we have a consistent contact within the Reaper
>> development team, the techniques used so far would be educational for
>> them for starters.
>>
>> I always meant for my longterm input to the project to be producing
>> training material. With the future so uncertain though, I haven't been
>> able to justify the time that would need to be spent on creating that.
>> I still use Reaper for whatever I can in the meantime of course
>> because it's a breath of fresh air to work in such a snappy DAW, but
>> for now I don't see that we have much choice other than to play the
>> long game and see what happens natively from Reaper HQ. Dunno about
>> anyone else, but I need to know where a project is headed before I
>> throw time at writing and recording tutorials.
>>
>> Scott
>>
>> On 9/3/10, Derek Lane <derek at pdaudio.net> wrote:
>>> Well, at least one thing is interesting in our exchanges, actually 2.
>>> The first is that my arguments slightly change and develop along with
>>> reaper.  *smiles*
>>> Finally, your valid point has more and more evidence to the continuing
>>> interest in reaper.
>>> We'll keep this up as long as necessary I'm sure.
>>> If this one developer has given up the project, it'd be nice to have the
>>> source available.
>>> I don't know who on this list is a programmer, but given the work flow of
>>> most modern development tools, isn't all the work already done?
>>> Wouldn't it be the case that the only major update necessary is to send
>>> more
>>> from the API to the code already in place which communicates with screen
>>> readers?
>>> ----- Original Message -----
>>> From: "Scott Chesworth" <scottchesworth at gmail.com>
>>> To: "Reapers Without Peepers" <rwp at reaaccess.com>
>>> Sent: Friday, September 03, 2010 2:51 PM
>>> Subject: Re: [RWP] reaaccess could stand an update.
>>>
>>>
>>>> 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 <derek at pdaudio.net> 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
>>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>