NO problem Doug, better late than never 'grin'. As long as it takes and all that good stuff.
Ok, I'll do my best to be clear.The sets seem to be converting just fine, but aren't triggering as they did before.
I think that your right, the position of the hyperactive windows gets messed up, because I can re-focus them and things work again, but that's a lot of work because as you said, these are complex setfiles, and it takes a while to find things on screen sometimes and also to remember exactly what you did.
I'm not sure what Tom is doing with the forge right now, I know he let some folks on the midi-mag have his sf8 sets, and made some noises about maybe working on 9, but a lot of us aren't doing the forge upgrade because they really haven't done anything new in years, just repackaged the same old stuff and priced it again, you know how it goes, and of course, broke accessibility.
I like 7b because it doesn't require dot framework, also the looping previewefeature works better, in 8 on my machine, even if I set things properly it tends to quit on me after a few loops, 7b tends to be the more stable and reliable, isn't that funny about software, it seems to have a half-life where it reaches a sweet spot, and then goes to pott sometimes.
Anyway, I know dot framework is supposed to make things more compatible over different platforms, but for functionallity the forge is the same 2 track editor.
Anyway, back to the window-eyes thing, what would cause the sets to become a pixel off, is this an osm thing, or something because of a change in we7 setfile engineering to improve something and what's the easiest way to fix windows must I manually reset all of them, seems like I tried the auto offsets but you got to find the screen cordinates again to do that right?
I started to re-do all these for we7, and I guess I could if I had to but that's a butt load of work and I have these setfiles working so nicely with we6 and it's so stable. I think that you can use soundforge audio studio in trial mode and it'll act the same way, problem is I don't have a bare image to install it on to varify this.
Feel free to send these to anyone who might be able to test or help out, I think Tom probably has santioned these to be passed around now, it might be cool to give me a curtesy call and ask, but he's been pretty open handed with these but you know how it goes, the more heads the better someone around here's got to be running forge 7 and is also an advanced setfile person.
Thanks and let me know if you find anything further if you can. I'll do the same.I've been busy putting together a desk today, being mister mechanic, but I'll ghost we7.1 back on the machine when I've had some sleep and torture her somemore and see what I can find.
At 10:05 AM 7/15/2009, you wrote:
Chris,The problem is I don't have Sound Forge to play with these sets. But I'm still a bit confused. At one point it sounded like you said the conversion process broke the set because you could look at a pre-converted set and see the windows settings and look at the post-converted set and the settings were no longer they same. Is this truly what is happening or are the settings exactly the same but for whatever reason the hyper windows are not firing as they were so you are making the determination they must have gotten mucked up on the conversion?As I mentioned, these sets are very complicated and without me having Sound Forge I can't do much. So can you just focus on two of the sets to determine what is going on? Meaning get the one set going that is to use a hyper active window to switch to another set. Then figure out what is to make that hyper fire. It is possible the hyper window is just a pixel off or whatever. Again, I don't even know what hyper we are talking about or what it is trying to fire on.Regarding Tom Kingston, he has Window-Eyes 7.1, does he have this issue or has he abandoned the sets?I understand you may have gone over all this with others are at GW but as you mentioned, you have my personal attention to this problem so please be patient as I don't have the information you may have already given.Regards, Doug Chris Belle wrote:Hi Doug?For a number of reasons, I am very, very glad to be getting your personal attention on this matter.I will be happy to post another archive of setfiles to gwmicro and try to outline my problems as best I can.These setfiles were originally made for soundforge 8 by Tom Kingston and I beta tested for him and moded them to work with soundforge 7b, you can check my other emails I believe I wrote about this.I'm sure you work with Tom regularly still.Anyway, his setfiles use loader sets which are associated to modules in soundforge and when certain hyperactive windows see a given plug-in, they load the appropriate set.This makes it possible to associate a different set with each plug-in since there's no way to actualy associate a set with each plug-in by the plug-in name or window name.Anyway, my sets work beautifully with 6.1 until I upgrade to we7 and then they no longer load correctly.Also the hyperactive windows don't work correctly anymore, some of them work, others don't read anymore.For instance, I have in the graphic eq section of sound forge two setfiles that load from the loader sets.They never get loaded, the datawin setfile, I forget the exact names, I'll check sf7datawin.000 which is the main soundforge view window when you open it up is all you see.Now when I try and load the approapriate sets manually, step through what would normally happen, load the sf7loader1.000 which looks for the eq sets and loads them sometimes it'll find them on some plug-ins, but if I skip this step and just load the right sets, for the eq, II use two eq sets for the graphic eq one for the 10 band and one for the 20 band, following the good doctor kingston's structure, well, these windows just aren't accurate anymore. Anyway, the hyperactive window triggers on has focus, and then speaks a windowand then it. activates a window.YOu can see this functionallity broken when you install the we7 upgrade with hyperactive windows.Of course I can re-build the sets, and do then all over again, but unless something really improved in we7 to make orphaning setfiles necessary, this is really drastic.So I will post these setfiles to you again.My colleagues at All Digital Audio whom I work closely with has been able to re-produce this behavior on their machines.I've re-produced it on two of mine.So unless given other information to shed light on this, I consider this to be a very serious we bug.Regards, Chris. At 07:43 PM 7/14/2009, you wrot e:Chris,The information you received was not correct. The set association change was done from 5.5 to 6.0 and the 6.0 readme.txt file did explain the change and consequence and resolution very clearly.Since you are having issues from 6.1 to 7.0 this is not the case. I don't remember the set file issue you are having but how about this?Please send me the 6.1 version of the set file and the 7.x version of the set file and specifically tell me what window, whether it is a standard or hyperactive and what the 6.1 format has for the coordinates and what the 7.x has for the coordinates or whatever the discrepancy is. This will allow me to verify what happened if indeed there was a conversion problem.Also, given how bad this problem is for you using this one application, have you noticed any other set files with the same problem? It seems likely if the set file conversion has issues that it would effect all or many of your other set files. Also, keep in mind when we update our factory sets, we run them through the exact same wefixset utility that you are using.Regards, Doug Chris Belle wrote:Hmmmm, now this is very interesting.I was told that there were some very minor changes in setfiles to improve them but they shouldn't break.If setfiles get broken this bad and if this is a known thing or something that is a sacrifice for the better from an engineering stand-point, then something should be put in the readme to the effect, because it's not minor, it's major, because lots of hard work can be hosed.There wasn't enough follow-through or attention given to this last year when this should have been addressed.For us non-programmer types, setfile creation is the closest thing to a configurable environment we have, maybe until scripting grows up to where window-eyes gets something as comprehensive and powerful as say the Snowman's hotspot clicker, for jaws, smile.At 03:22 PM 7/13/2009, you wrote:I have an idea, the coordinates might be different by a few pixels, but the way set files are associated has changed from 6.1 to 7.1 very greatly, so you will have to do the associations all over again. Hope this helps. on Monday 07/13/2009 Chris Belle([email protected]) wrote > Hi Chip? > > I did do exactly what you suggested, and got no where. > > I have since been able to duplicate this problem with a competent > technician colleague who I work with regularly, this morning as a > matter of fact. > > Sure enough, setfiles that work well for soundforge 7b with we 6.1 > will break badly under we7 and not load correctly, hyperactive window> cordinates will be messed up, and associations for loading will be messed up.> > I was told that this was probably something specific to my machine. >> Now I have good evidence that it is not so and that window-eyes is at fault.> > At 11:18 AM 7/13/2009, you wrote:> >why don't you send the set files to support, with a detailed explanation> >of how things work under 6.1, and a detailed explanation of what it > >takes to see they're broken under 7.1? > > > > > > > > > > > > > >------------------------------ > > > >Chip Orange > >Database Administrator > >Florida Public Service Commission > > > >[email protected] > >(850) 413-6314 > > > > (Any opinions expressed are solely those of the author and do not > >necessarily reflect those of the Florida Public Service Commission.) > > > > > > > -----Original Message----- > > > From: Chris Belle [mailto:[email protected]] > > > Sent: Monday, July 13, 2009 1:10 AM > > > To: [email protected] > > > Subject: Re: FW: 7.1 stability problems > > > > > > I've gotten the same here on several ocasions. > > > > > > After abandoning we 7.0 in frustration because of a failure to> > > communicate to gwmicro my issues for various reasons I won't go in to> > > here, I decided to give we7.1 a test drive. > > >> > > To their credit, one issue that's seems to have been resolved is the> > > drag and drop issue, it now seems to be working. > > > > > > This was broken in the we7 release. > > > > > > My test drive of it with levelator with we7.1 seems to work now. > > > > > > One very serious problem I am having with we since the whole we7 > > > cycle began is the issue of setfiles being broken between > > > we6.1 and we7. > > >> > > I have some very extensive and very well written soundforge setfiles> > > written by my good friend Tom Kingston whom I beta tested for > > > last year. > > > > > > These setfiles add a lot of functionallity and usability to> > > soundforge 8, and I modifyed them to work with my prefered soundforge> > > 7 installation. > > > > > > When I upgraded to we7 in any of it's incarnations, these setfiles> > > neither load correctly, and window cordinates are messed up, and all> > > kinds of strange things happen. > > >> > > I've had some very brief conversation with gwmicro over this but have> > > never gotten this satisfactorily addressed. > > > > > > There is no change with we7.1, the setfiles are still very broken. > > > > > > The basic structure of the setfiles is this, there are two loader> > > sets which are associated with different modules in soundforge, and > > > hyperactive windows will trigger and load the appropriate setfile as > > > needed for any given window, so when you want to create a new setfile > > > for a new part of the forge, you just make a new setfile and load it> > > with a hyperactive window from one of the loader sets. > > >> > > Pretty slick, kind of what I used to do with the ram locations with> > > vocal-eyes and branching remember when we only had 10 hyperactive > > > windows, my have we come a long way. > > > > > > something changed in we7 which broke these setfiles. > > > > > > Any enlightening information would be appreciated. > > > > > > Regards. > > > > > > > > > > > > At 04:36 PM 7/12/2009, you wrote:> > > >I am having the same problem. If you move around to quick in windows> > > >explorer or internet explorer w e will crash. > > > > > > > >Edward > > > > > > > > > > > >-----Original Message----- > > > >From: Chip Orange [mailto:[email protected]] > > > >Sent: Sunday, July 12, 2009 3:29 PM > > > >To: [email protected] > > > >Subject: RE: 7.1 stability problems > > > > > > > >Yes, Bill, I was; then I switched to dec-talk access 32, > > > from Eloquence, and > > > >things do seem much better. why not try that and see if it > > > makes a big > > > >difference; it will help them a lot, in tracking it down, if > > > you find this > > > >out. > > > > > > > >Chip > > > > > > > > > > > >-----Original Message----- > > > >From: Bill Holton [mailto:[email protected]] > > > >Sent: Sunday, July 12, 2009 2:32 PM > > > >To: [email protected] > > > >Subject: 7.1 stability problems > > > > > > > >Hi. > > > > > > > >Is anyone else having trouble with 7.1 when you start moving > > > fast around the > > > >computer? I have WE 7.1 stop talking on both my XP and > > > Vista machines, both > > > >using eloquence, if I start keying around too fast with > > > either Windows keys > > > >or WE hotkeys. The rest of the sounds on the PC work fine, > > > and it's not > > > >locking up, but it takes speech about ten seconds to start > > > again. Other > > > >times it doesn't start again, and the only way to get WE > > > back is to do a > > > >hard reset. > > > > > > > >On my Vista machine, I also have a problem I have had ever > > > since I started > > > >using Vista, only now it happens more frequently. Speech > > > will die, the > > > >other sounds are working fine, and the only way to get WE > > > back is to turn > > > >the machine off or do a start menu restart. Then, just > > > before Windows shuts > > > >down, the speech comes back fine, for about two seconds, > > > then the machine is > > > >restarted. This is very frustrating. Anyone else having > > > this situation? > > > > > > > >Thanks. Bill > > > > > > > >Bill > > > > > > > > > > > > > > > >If you reply to this message it will be delivered to the > > > original sender > > > >only. If your reply would benefit others on the list and > > > your message is > > > >related to GW Micro, then please consider sending your message to > > > >[email protected] so the entire list will receive it. > > > > > > > >All GW-Info messages are archived at > > > http://www.gwmicro.com/gwinfo, and can > > > >be searched through and sorted using the search form at the > > > bottom of the > > > >page. > > > > > > > >If you wish to unsubscribe from this list, send a message to > > > >[email protected] and include leave gw-info in the body > > > of the message. > > > > > > > >If you reply to this message it will be delivered to the > > > original sender > > > >only. If your reply would benefit others on the list and > > > your message is > > > >related to GW Micro, then please consider sending your message to > > > >[email protected] so the entire list will receive it. > > > > > > > >All GW-Info messages are archived at > > > http://www.gwmicro.com/gwinfo, and can > > > >be searched through and sorted using the search form at the > > > bottom of the > > > >page. > > > > > > > >If you wish to unsubscribe from this list, send a message to > > > >[email protected] and include leave gw-info in the body > > > of the message. > > > > > > > >If you reply to this message it will be delivered to the original > > > >sender only. If your reply would benefit others on the list and > > > >your message is related to GW Micro, then please consider sending > > > >your message to [email protected] so the entire list will > > > receive it. > > > >> > > >All GW-Info messages are archived at http://www.gwmicro.com/gwinfo,> > > >and can be searched through and sorted using the search > > > >form at the bottom of the page. > > > > > > > >If you wish to unsubscribe from this list, send a message to > > > >[email protected] and include leave gw-info in the body > > > >of the message. > > > > > > If you reply to this message it will be delivered to the original > > > sender only. If your reply would benefit others on the list and > > > your message is related to GW Micro, then please consider sending > > > your message to [email protected] so the entire list will > > > receive it. > > > > > > All GW-Info messages are archived at > > > http://www.gwmicro.com/gwinfo, and can be searched through > > > and sorted using the search > > > form at the bottom of the page. > > > > > > If you wish to unsubscribe from this list, send a message to > > > [email protected] and include leave gw-info in the body > > > of the message. > > > > > > > > > >If you reply to this message it will be delivered to the original > >sender only. If your reply would benefit others on the list and > >your message is related to GW Micro, then please consider sending> >your message to [email protected] so the entire list will receive it.> > > >All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, > >and can be searched through and sorted using the search > >form at the bottom of the page. > > > >If you wish to unsubscribe from this list, send a message to > >[email protected] and include leave gw-info in the body > >of the message. > > If you reply to this message it will be delivered to the original > sender only. If your reply would benefit others on the list and > your message is related to GW Micro, then please consider sending> your message to [email protected] so the entire list will receive it.>> All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search> form at the bottom of the page. > > If you wish to unsubscribe from this list, send a message to > [email protected] and include leave gw-info in the body > of the message. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici [email protected] If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it.All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the searchform at the bottom of the page. If you wish to unsubscribe from this list, send a message to [email protected] and include leave gw-info in the body of the message.If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it.All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the searchform at the bottom of the page. If you wish to unsubscribe from this list, send a message to [email protected] and include leave gw-info in the body of the message.-- Doug Geoffray GW Micro, Inc. Voice 260-489-3671 Fax 260-489-2608 http://www.gwmicro.com If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it.All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the searchform at the bottom of the page. If you wish to unsubscribe from this list, send a message to [email protected] and include leave gw-info in the body of the message.If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it.All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the searchform at the bottom of the page. If you wish to unsubscribe from this list, send a message to [email protected] and include leave gw-info in the body of the message.-- Doug Geoffray GW Micro, Inc. Voice 260-489-3671 Fax 260-489-2608 http://www.gwmicro.com If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it.All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the searchform at the bottom of the page. If you wish to unsubscribe from this list, send a message to [email protected] and include leave gw-info in the body of the message.
If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the searchform at the bottom of the page.
If you wish to unsubscribe from this list, send a message to[email protected] and include leave gw-info in the body of the message.
