[RWP] AutoHotKey A Few HotSpots
Jim Snowbarger
Snowman at SnowmanRadio.com
Sat Mar 9 16:11:56 EST 2013
In General, when creating hotspot sets, this is why it is best to use the
positioning method that is as interior as possible. That means using the
smallest window that encloses the point of interest as your reference.
Sometimes, you can't do that. If HSC can't find that window by using it's
name, or becuase focus is in there, then tou have to use larger windows,
meaning an outer window, or the application itself, which causes this kind
of problem.
AS the HSC developer, I'm quite interested in making this sort of thing more
portable.
----- Original Message -----
From: "Steve Spamer" <steve at vipaudioaccess.com>
To: "'Reapers Without Peepers'" <rwp at reaaccess.com>
Sent: Friday, March 08, 2013 4:49 AM
Subject: Re: [RWP] AutoHotKey A Few HotSpots
> Indi, there is a general off set amount from Sonar to Reaper, but it's not
> set in stone and in my experience, different controls require different
> offset amounts, if any at all. I know that sounds vague, but I can't get
> my
> head around why this is right now.
>
> I've got a plug for Sonar with a fully working HSC set...bang it into
> Reaper and apply offsets, then the world just goes mad lol. Some will
> work,
> some won't, others in child windows are all over the place...it really is
> a
> complex issue that I just can't face, so I'm keeping the set just for the
> Sonar platform at the moment.
>
> In comparison, the Omnisphere set has 1200+ hot spots and it was
> relatively
> straight forward to import over to Reaper, although time consuming. There
> were 2 distinct angles of attack that took me a long time to figure out,
> but
> that doesn't mean the same approach works with other plugs. I think you
> have to work on a plug by plug basis.
>
> Just on the point of clicking at a location. All I can say, it's great to
> be able to click somewhere and get a bit of access, but be careful, as
> many
> times, executing that spot accidently in a wrong window can result in
> hours
> and hours of frustration, it can often hit a wrong control and bugger up
> stuff, cheers Steve.
>
>
> Visit:
> www.vipaudioaccess.com
> for audio access solutions, articles, demos, to showcase your music and
> to
> basically get involved!
> -----Original Message-----
> From: RWP [mailto:rwp-bounces at reaaccess.com] On Behalf Of Indigo
> Sent: 08 March 2013 06:00
> To: Reapers Without Peepers
> Subject: Re: [RWP] AutoHotKey A Few HotSpots
>
> Jim, when I derive coordinates with my home made screen scraping method;
> It
> results in standard resolution X Y coordinates, which I think always
> starts
> the pixel count from the upper left corner of the screen, doesn't it?
> How could a button's coordinates not be relative to the upper left corner;
> where the pixel count begins; even if I begin my search from another point
> on the screen?
> I've had the issue of Reaper screen coordinates not working in Sonar, even
> for the same screenreader, don't know why.
> Someday I intend to install a reasonable size and complexity Sonar, like
> Sonar version 4, which I can get around on, and try to derive coordinates
> for the same VST synth buttons, then find, if possible, a conversion
> factor.
>
> I never use Reaper's generic plug interface, even though it works for my
> hand rolled method of finding buttons, because the more friendly synths,
> like LinPlug Albino offer some text titles on their native interfaces, and
> I'd constantly be switching back and forth between Reaper's generic
> interface and the plug's native interface.
> I think it's the word arpeggiated, or maybe the word ambient; on the
> Albino
> interface that I left click, which drops a list of presets, in that
> catagory; but then it exposes titles of other catagories, like leads,
> basses, keys.
> Like all of us, I'm sure; I'll take any clue I can find to get a toe in
> the
> access door.
> Indi
>
>
> On 3/7/2013 11:06 PM, Jim Snowbarger wrote:
>> I don't need this to work, but it doesn't. And, he's in hiding. Yeah
>> sure, quick coords over the shoulder and then voluntary exile. Just
>> like a rain soaked ausie. ... <grinn>
>>
>> Does "click" in AHK terms, mean left click?
>> These coords, are they relative to the top left corner of the screen?
>>
>> ----- Original Message -----
>> From: David P Shortland
>> To: Reapers Without Peepers
>> Sent: Thursday, March 07, 2013 12:13 AM
>> Subject: [RWP] AutoHotKey A Few HotSpots
>>
>>
>> Hi & Greetings from a drying out Sunshine Coast
>>
>> Thought I would share this with anyone who may be interested
>>
>> As I am charting my way thru the Help files of AutoHotKey and
>> learning to Script this and that, well mainly for Omnisphere at
>> present, here are a couple of co-ordinates that may be of helpin
>> REAPER, with regards to a Certain Menu not opening with Apps Key & Up
>> Arrow key
>>
>> These co-ordinates will give access to a menu that will be spoken and
> contains settings for Audio & MIDI Inputs & Outputs.
>>
>> 136, 176 is for Trak 1
>> 136, 276 is for Trak 2
>>
>> Now for those of us who may be a little apprehensive in trying to
>> write
> a script to access these co-ordinates,here its is...
>>
>> Open up Notepad and type these lines as is, or just copy them across..
>>
>> Numpad9 & Numpad1:: Click 136, 176
>> Numpad9 & Numpad2:: Click 136, 276
>>
>> Save this document as AutoHotKey.ahk
>>
>> Go to the directory where you just saved that script
>>
>> Double Click on the file and it should ask you with what file do you
> wish to run the program?
>>
>> Navigate to AutoHotKey and voila ... all should be good
>>
>> Okay, just remember that the resolution on my System is 768 x 1024 ,
>> so
> one can deduce that if your resolution is different the co-ordinates will
> not match.
>>
>> Now all you have to do when REAPER is open and you have several
>> tracks in place
>>
>> Press Numpad9 (hold it down and Press Numpad1 the Menu should open,
>> make yourselections
>>
>> Remember that this combination is for Trak 1.
>>
>> I have also used the Numpad as ReaAccess and REAPER use a lot of
> keyboard combinations and this should not interfere.
>>
>> Oh yes... DO NOT forget to press the NumLock .. it must be ON!
>>
>> I have only given the co-ordinates for two trax, because I figure if
> you want to set up several combinations of In & Outs, just coply one of
> the
> tracks to another place.
>>
>> Hopefully all will go smoothly... if not...I have left the country and
> gone into hiding...
>>
>> Take care all
>>
>> David P Shortland
>> DragonScore Productions
>>
>>
>>
>>
>>
>>
>>
>>
>> ----------------------------------------------------------------------
>> --------
>>
>>
>> _______________________________________________
>> 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