Absolutely. On Jun 26, 2010, at 7:45 PM, Scott Chesworth wrote:
> Ah cool, so at least any nifty stuff we can get going to report > statuses of things in mix/edit windows etc should carry over to all > the versions. > > On 6/26/10, Slau Halatyn <[email protected]> wrote: >> Hey Scott, >> >> The UI for all Pro Tools systems is virtually the same. The differences, for >> example, however, might be within plug-in windows where there might be extra >> options within a TDM plug-in versus an RTAS. Most of the time, though, the >> plug-ins are pretty much identical. >> >> HTH >> >> Slau >> >> On Jun 26, 2010, at 5:18 PM, Scott Chesworth wrote: >> >>> Ah, well saying that I was underwhelmed by QuicKeys was perhaps a bit >>> premature. I'd spent a bit of time working with version 3 to see how >>> feasible it was to fix up a few weaknesses in those Logic scripts that >>> have been doing the rounds, but never got very far into figuring out >>> how to update them to be version 4 compatible before I got sick of how >>> often the system would go cold turkey on me if I tried to do anything >>> too quickly. Version 4 sounds good from what you've said though, the >>> import/export options sound like they've been tidied up for a start. >>> >>> Writing documentation for this kinda thing can neatly fit into my job >>> description where I am for the next few months, so that part should be >>> covered at least. The biggest flaw I can see so far is that although >>> I've got the time and inclination to put hours into this, I'll only >>> have LE systems at hand to test on. Having had no experience of >>> M-Powered and few encounters with HD, I dunno how much of a biggy >>> that's likely to be... do you? >>> >>> Scott >>> >>> On 6/26/10, Bryan Smart <[email protected]> wrote: >>>> We may be forced to go the free route. Doesn't look like there is any way >>>> to >>>> protect work produced with either QuicKeys or Keyboard Maestro. That's >>>> great >>>> for users bank accounts, but too bad for their patience. I'd be happy to >>>> coordinate an effort, and put in bits and pieces of work on the >>>> functionality. I'm not up for writing lots of technical documentation and >>>> tutorial stuff, though. If someone doesn't take on that part, though, the >>>> list will be swamped with people asking how to do the same things over >>>> and >>>> over. >>>> >>>> I took another look at the latest version of QuicKeys. After some >>>> thought, I >>>> think that we'd be better served by using QuicKeys. It can do all of the >>>> stuff that Keyboard Maestro can do, including controlling VoiceOver >>>> through >>>> Applescript, which I didn't know it could, but it also supports features >>>> like variables and basic functions, which we'll need for anything >>>> complicated. >>>> >>>> Because of how QuicKeys organizes itself, each macro function is >>>> compartmentalized in to what it calls a shortcut. So, people can create >>>> shortcuts on their own, send them to me, and I'll combine them with the >>>> master set of shortcuts. I can export the master set as a single file. >>>> That >>>> file is the current distribution. I post it on the Googlegroup. To use >>>> it, >>>> people just download the file, and use the File menu in QuicKeys to >>>> import >>>> it, and they get all of the current shortcuts in one go, already mapped >>>> to >>>> hotkeys that will only trigger inside Pro Tools. >>>> >>>> I think that this will work, but I'm not sure what happens when someone >>>> upgrades. What if I change a hotkey assignment? If they import the new >>>> version, that won't necessarily delete all of the old shortcuts. >>>> >>>> I think that this could work, though. >>>> >>>> I also didn't know that QuicKeys is free now. You get it for free for 30 >>>> days. After that, it still works, but it will nag you every now and then >>>> to >>>> pay. >>>> >>>> Bryan >>>> >>>> -----Original Message----- >>>> From: [email protected] [mailto:[email protected]] On >>>> Behalf >>>> Of Scott Chesworth >>>> Sent: Saturday, June 26, 2010 11:00 AM >>>> To: [email protected] >>>> Subject: Re: boom? >>>> >>>> Last known official statistics indicate that I'm 40 percent less >>>> bastardly >>>> than the leading pusher of commercial screen readery, as well as being >>>> 873 >>>> percent poorer. Too poor in fact to buy anyone elses macros, so please >>>> don't >>>> send that email to the Keyboard Maestro developer lol. >>>> >>>> On a more serious note, I currently have access to a set of perfectly >>>> working tech-savvy eyes one day per week regular as clockwork, and would >>>> be >>>> keen to put time into a project such as this for free distribution. >>>> >>>> Cheers >>>> Scott >>>> >>>> On 6/26/10, Bryan Smart <[email protected]> wrote: >>>>> Oh, come on. You won't give up 30 to 40 percent of your life to help >>>>> us all out? And, of course it should be free. Don't you know that >>>>> blind people are too poor to afford your expensive macros just so that >>>>> you can get rich off of us? You're just like those screen reader >>>>> companies. hahahaha. >>>>> >>>>> Yeh, if making such macros is a sinchy simple thing that hardly takes >>>>> any time, then a few people might be able to throw a little bit of >>>>> free effort in here and there as needed. For a complex effort, though, >>>>> no one is going to spend all of the creating, testing, and, most >>>>> importantly, documenting time, if they can't be compensated in some >>>>> way. We all have much more fun things to do with our free time than >>>>> program and write technical documentation. >>>>> >>>>> Keyboard Maestro does have a few little accessibility problems, but >>>>> nothing too big. VoiceOver can see all of the control, but few of them >>>>> are >>>>> labeled. >>>>> Fortunately, most of the unlabeled controls have help tags that tell >>>>> you what they do. I plan to send a message to the author, asking him >>>>> to put in the labels. If he doesn't, though, we can always label the >>>>> controls with VO. >>>>> In a few of the macro creation dialogs, though, there are issues, like >>>>> how setting a macro hotkey can sometimes cause the program to be stuck >>>>> in a loop sending that key through to VoiceOver, over and over. Not >>>>> sure what's going on there. That's probably more something to do with >>>>> both VoiceOver and Keyboard Maestro trying to take over the keyboard >>>>> at the same time. We could probably use the program as-is, but a >>>>> little bit of touch up would make it nice. >>>>> >>>>> I'm also going to ask the author about what could be done to >>>>> protect/sell macros. If the work is simple, that might not even be >>>>> necessary, but it would be nice to have that option. Pro Tools might >>>>> not require such detailed macros, but this tool could help with other >>>>> apps, and they might. >>>>> >>>>> Bryan >>>>> >>>>> -----Original Message----- >>>>> From: [email protected] [mailto:[email protected]] On >>>>> Behalf Of Scott Chesworth >>>>> Sent: Saturday, June 26, 2010 4:44 AM >>>>> To: [email protected] >>>>> Subject: Re: boom? >>>>> >>>>> Ah, really glad to hear that someone's discovered an alternative to >>>>> QuicKeys. I spent a few days using it and was a bit underwhelmed, this >>>>> sounds much more powerful. $36 doesn't seem like a pricepoint that's >>>>> through the roof, but so far as I can see there'd be no way to tie >>>>> these macros down to a serial to sell your work on as the HSC folks >>>>> have started doing on Windows. Don't get me wrong, I'm half glad about >>>>> that, but it does make me wonder how much input the effort would get >>>>> if the only return scripters will get are donations or helping their >>>>> fellow human. >>>>> >>>>> On 6/26/10, Bryan Smart <[email protected]> wrote: >>>>>> I don't know of any way to import samples in to any of the synths. >>>>>> >>>>>> You can only control a synth or effect's automatable parameters. >>>>>> That's stuff like the current settings or modes. Any action that >>>>>> wouldn't normally be adjustable by a pop-up menu, slider, or knob is >>>>>> usually out of the question. You can't select instruments in >>>>>> Structure because you need the inaccessible browser in Structure's >>>>>> native UI, and you can't change samples on pads in Boom because the >>>>>> buttons to do that are in its inaccessible UI. >>>>>> In Boom, you can edit pads, but you can't load new samples. >>>>>> >>>>>> There is a macro package called Keyboard Maestro. It is like an >>>>>> upgraded QuicKeys. It can control apps through their user interfaces, >>>>>> and move/click the mouse, as well as simulate typing commands. It >>>>>> also can use Applescript, which means that it can control VoiceOver, >>>>>> speak through the VoiceOver synthesizer, and control open >>>>>> applications through their Applescript support. Using it in >>>>>> combination with VoiceOver, we should be able to make scripts for any >>>>>> application that can: >>>>>> >>>>>> Quickly move the VoiceOver position to a particular area of a >>>>>> program, like a key to quickly jump you to the ruler, the first >>>>>> track, or a specific track. >>>>>> >>>>>> Read anything that VoiceOver sees without moving your VoiceOver >>>>>> cursor, such as making a hotkey to announce your position or the >>>>>> selection. >>>>>> >>>>>> Perform hot spot clicking, such as making a hotkey that will click on >>>>>> a location of the screen containing a button that VoiceOver can't see. >>>>>> >>>>>> Create keyboard shortcuts to activate menu commands that lack >>>>>> shortcuts. >>>>>> >>>>>> Create shortcuts to take you directly to a commonly used page of a >>>>>> dialog. >>>>>> >>>>>> Perform inaccessible program functions by controlling the program >>>>>> with AppleScript. >>>>>> >>>>>> The only sucky thing is that it can't automatically respond to events. >>>>>> So, it can't watch the screen for a clipping meter, or for a change >>>>>> in a control, and report that change to you automatically. Still, it >>>>>> would be useful. >>>>>> >>>>>> I have to look at it a bit, but it looks promising. >>>>>> >>>>>> Bryan >>>>>> >>>>>> -----Original Message----- >>>>>> From: [email protected] [mailto:[email protected]] On >>>>>> Behalf Of clarence griffin >>>>>> Sent: Friday, June 25, 2010 3:35 PM >>>>>> To: [email protected] >>>>>> Subject: boom? >>>>>> >>>>>> I have a question for those who are using the softh synth drum >>>>>> machine called boom for PT. Are you able to import sounds in to it, >>>>>> or is it just what it is and can't be expanded? I was just wondering >>>>>> what my options are for bringing in sampled drums? >>>>>> >>>>>> GF >>>>>> >>>>>> >>>>>> >>>>> >>>> >> >>
