[RWP] Recording inputs menu, meter readings, and contacting Reaper developers
Jim Snowbarger
Snowman at SnowmanRadio.com
Mon Aug 4 11:45:54 EDT 2014
All I can say is that alt+p is not a key that is assigned to jaws in the
standard reaper key map that came with reAccess.
So, I dont' think it is jaws that is deciding what gets said there.
----- Original Message -----
From: "Ernest McCullough" <emccullough1 at nyc.rr.com>
To: "'Reapers Without Peepers'" <rwp at reaaccess.com>
Sent: Sunday, August 03, 2014 9:40 PM
Subject: Re: [RWP] Recording inputs menu, meter readings,and contacting
Reaper developers
> On a somewhat unrelated note:
> How do I get Jaws to announce the different states of ripple editing? When
> I
> press Alt P, it just says ripple editing.
> Any help would be greatly appreciated.
> Thanks.
>
> -----Original Message-----
> From: RWP [mailto:rwp-bounces at reaaccess.com] On Behalf Of Indigo
> Sent: Sunday, August 03, 2014 1:51 PM
> To: Reapers Without Peepers
> Subject: Re: [RWP] Recording inputs menu, meter readings, and contacting
> Reaper developers
>
> Thanks for these tips, David.
>
> On 8/3/2014 4:52 AM, David P Shortland wrote:
>> Hi & Greetings from The Land Down Under,
>>
>> Not sure if this is what you want Indy, but Control plus Left or Right
>> Bracket gives you the beginning and end of and Item.
>>
>> Usually I do this to Select any item in a given track.
>>
>> With Control plus Shift plus Right Arrow this will select items to the
>> right of your current position...
>>
>> Ergo Control plus Shift plus Left Arrow will Select items to the Left
>> of your current position.
>>
>> I just recently completed a Radio Musical where I had many many Items
>> on a trak, and found it very easy to Select a particular Item and then
>> to hit TAB to brin up a very short Item Parameters Dialog box.
>>
>> Yes, I have also found that the Control plus Up Arrow three times plus
>> Applications Key does bring up the extended I/O Menu...
>>
>> Kind regards
>>
>> David P Shortland
>> DragonScore Productions
>>
>>
>>
>>
>> -----Original Message----- From: Indigo
>> Sent: Sunday, August 03, 2014 9:58 AM
>> To: Reapers Without Peepers
>> Subject: Re: [RWP] Recording inputs menu, meter readings, and
>> contacting Reaper developers
>>
>> Hi Oreo Monster,
>> If the input menu that you don't get reliably with Mac is the one that
>> you get with PC from repeated presses of the tab key, when a track is
>> selected, it's always there for PC, and certainly should be made
>> reliably available for mac as well.
>> I arm the track for recording, also set record monitor on, or monitor
>> item on, with that menu, and don't know how I'd do without it.
>> There's another more extensive recording input menu reached on a PC by
>> ctrl+3up arrows, then a single press of the applications key; with
>> ctrl+many
>> input and output options, also monitoring options.
>> On the PC you always hear how many items are on a track, with shift+a
>> or
>> ctrl+shift+right or left arrow, but on the PC I find it difficult to
>> single out a particular item.
>> It's easy enough to select item 1, but if you press ctrl+shift+right
>> arrow too many times you select all of the items on that track that
>> are to the right of the cursor, when what I'm actually trying to
>> select is only the second or third item, etcetera, on that track.
>> I have to begin again with selecting an item, because I am fuzzy about
>> exactly how to unselect unwanted items.
>> Maybe someone else has an obvious PC tip on how to do individual
>> selection of items, but speaking the item numbers is very reliable on PC.
>> Also, speaking track numbers and what synth or effect is on a
>> particular track is totally reliable on PC.
>> You Mac users should ask for better Mac access on Cockos Forums,
>> listing these specific instances of difficult access.
>> Indi
>>
>>
>>
>>
>> On 8/2/2014 4:47 PM, TheOreoMonster wrote:
>>> Mac wirse, putting the track list in containers to make it easier to
>>> navigate, Showing the input menu and meters and tracks properly
>>> sho/speak their state e.g. if its a track, a bus, or a folder track.
>>> Would be also nice if they spoke how many items were on each track
>>> more consistently. Right now it only seems to do this when its on the
>>> last track in the list. Let me know you think.
>>>
>>>
>>> On Aug 1, 2014, at 11:23 PM, Victor Tsaran <vtsaran at gmail.com
>>> <mailto:vtsaran at gmail.com>> wrote:
>>>
>>>> Hi guys.
>>>> I tried on multiple occasions. I hear Frank is asking for help but
>>>> with all the help given, I still do not understand what kind of help
>>>> they need. These guys are such pros and they can't figure out
>>>> accessibility?
>>>> I think perhaps what they rather need is a prioritized list of our
>>>> needs. They've made toolbars accessible, however, there are still a
>>>> fair amount of pitfalls. For example, what do you feel are the
>>>> biggest pinpoints in Reaper's lack of accessibility?
>>>>
>>>> To be fair, building accessibility into an application which is full
>>>> of custom controls is much much harder in Windows than it is on the
>>>> Mac. The easiest way for Reaper debs to eliminate accessibility
>>>> barriers is to use as many native controls as possible, which, as we
>>>> know, is not always possible due to the majority of sighted people
>>>> who wants it cute and pretty! :)
>>>>
>>>> So, perhaps we can use this thread to agree amongst ourselves as to
>>>> what we need first? Keep in mind that the needs of Mac users will be
>>>> different from those on Windows.
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, Aug 1, 2014 at 2:30 AM, Indigo <33indigo at charter.net
>>>> <mailto:33indigo at charter.net>> wrote:
>>>>
>>>> If any of us can actually get access problems expressed clearly,
>>>> it's possible to converse with Justin Frankel and other developers
>>>> on the forums.
>>>> I myself am satisfied with Reaper and ReaAccess; just work simply,
>>>> and hunt for workArounds, but if it irritates enough, someone
>>>> could join the Cockos Forums and express clearly what would make
>>>> access better, it might be included in the next update.
>>>> If the changes don't hurt the sighted user, like so much text that
>>>> thclutters the screen to the point sighted users can't find the
>>>> icons, it might happen.
>>>> We could ask for total tool tips that would appear when hovering
>>>> over icons for a selectable time; , or text labels that can be
>>>> switched on and off in the menus, or an all text-based layout we
>>>> could select from the view menu.
>>>> I don't know about the tool box used to write Reaper, but I looked
>>>> at SynthEdit, which has a field to provide text labels for each
>>>> bit map image, but developers just use text to remind themselves
>>>> of what their icons do during program writing, then go back and
>>>> delete the text later, so the screen isn't so cluttered.
>>>> A text label switch isn't too much to ask for.
>>>>
>>>> On 7/31/2014 3:28 PM, Scott Chesworth wrote:
>>>>
>>>> In my experience, Reaper development tends to be heavily tied
>>>> in with
>>>> and influenced by forum activity. So, Vic's approach of
>>>> starting a
>>>> thread where votes can be placed is probably the right one.
>>>> Unfortunately, we don't have the numbers to bring about
>>>> activity with
>>>> a flurry of votes when you compare accessibility posts to
>>>> bugs and
>>>> feature requests intended for all users, but previously,
>>>> accessibility
>>>> tweaks and improvements have happened just before a major
>>>> version
>>>> number increment, so with us currently at 4.7 and version 5
>>>> probably
>>>> appearing in the not to distant future, now is definitely the
>>>> time to
>>>> be visible on the forum. I'm not saying any of this to
>>>> discourage
>>>> anyone from contacting developers directly btw, just filling
>>>> David in
>>>> on how the Reaper development cycle seems to work overall.
>>>>
>>>> Hth
>>>>
>>>> Scott
>>>>
>>>> On 7/31/14, David Eagle <onlineeagle at googlemail.com
>>>> <mailto:onlineeagle at googlemail.com>> wrote:
>>>>
>>>> Hi Vic, I haven't changed the appearance, apart from doing
>>>> the things
>>>> recommended in the SWS Extensions manual, and that was
>>>> just a couple of
>>>> very minor changes in preferences. I think it might be a
>>>> good idea to try
>>>> getting back to the original configuration and seeing what
>>>> you can achieve
>>>> from there. Then we can at least work out why you're not
>>>> getting the menu
>>>> whereas Patrick and I are both able to find them.
>>>>
>>>> For the time being, it looks like the Re-console is going
>>>> to have to be
>>>> your work-around.
>>>>
>>>> On the subject of the DB readings issue: are those
>>>> concerned going to
>>>> contact the developer? I don't think there's any one
>>>> particular person
>>>> lobbying for Reaper accessibility like Slau and Protools,
>>>> so perhaps the
>>>> way forward with Reaper is for all of us concerned to
>>>> contact the
>>>> developers. Obviously the good thing about this mailing is
>>>> that we can
>>>> discuss problems to make sure they are universally
>>>> applicable before
>>>> emailing them, rather than confusing them with problems
>>>> that are only
>>>> present for one individual. I think that we Mac users are
>>>> in the fortunate
>>>> position to have a very accessible Reaper and so I don't
>>>> think it would
>>>> take a lot of effort and time to maintain and improve
>>>> accessibility in
>>>> future releases, which, according to the reaper website,
>>>> are frequent.
>>>>
>>>> So, I think it would be wise for those concerned to
>>>> contact the developers
>>>> about the DB meters issue. I'll paste a copy of the email
>>>> to this mailing
>>>> list once it's sent. Let's just hope they'll be open to
>>>> starting a dialogue
>>>> on this. I've only been using Reaper for a week, and have
>>>> only started
>>>> posting on here for a week, so I maybe jumping the gun in
>>>> assuming that
>>>> attempts to talk to Reaper haven't been made already.
>>>> So I apologise if I am going over ground that's been gone
>>>> over many times
>>>> before but to no avail. I still think however that the
>>>> more people who
>>>> speak up will help the people at Reaper to see this as
>>>> something to take
>>>> more seriously, especially if we start the discussions by
>>>> alerting them to
>>>> how brilliantly accessible Reaper currently is for the Mac
>>>> and Voice-Over.
>>>>
>>>> Thoughts welcome friends.
>>>>
>>>>
>>>> _________________________________________________
>>>> RWP mailing list
>>>> RWP at reaaccess.com <mailto:RWP at reaaccess.com>
>>>> http://reaaccess.com/mailman/__listinfo/rwp_reaaccess.com
>>>> <http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com>
>>>>
>>>>
>>>> _________________________________________________
>>>> RWP mailing list
>>>> RWP at reaaccess.com <mailto:RWP at reaaccess.com>
>>>> http://reaaccess.com/mailman/__listinfo/rwp_reaaccess.com
>>>> <http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com>
>>>>
>>>>
>>>> _______________________________________________
>>>> RWP mailing list
>>>> RWP at reaaccess.com <mailto: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
>
> _______________________________________________
> 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
>
More information about the Rwp
mailing list