[realmusicians] Re: soundforge 7b setfiles
- From: "Tom Kingston" <tom.kingston@xxxxxxxxxxx>
- To: <realmusicians@xxxxxxxxxxxxx>
- Date: Mon, 12 Oct 2009 04:55:21 -0400
Hey Chris?
Haven't you run multiple versions of SF on your system? I tried installing 8
to look in to this problem for you and everything went wacko. When I
uninstalled it 9 was still messed up. So I had to uninstall that as well and
start over. Then I tried creating another user account and installing 8
within that one and 9 within the other. Same result. SF seems to install for
all users no matter what I do even though the setup and installation paths
are different. I even changed the "shared plug-ins" path to be within each
program folder and placed the impulses within them as well.
Any suggestions on how to get more than one version of this bloody program
workable on one machine would be greatly appreciated.
If all else fails I might try installing 9 and 10 on my other machine
because I can tell by programmatically digging down through the interface
that 9 was a major re-write from 8 and 10 is simply an upgrade of that.
Tom
----- Original Message -----
From: "Chris Belle" <cb1963@xxxxxxxxxxxxx>
Hey Tom,
We have a budding window-eyes user my fine student Eddie who is learning
to record his libraries of tapes and such just got him a lexicon alpha, a
nice simple usb interface for his fast laptop, it's a dual core machine.
I've banged on Doug long enough, I'm re-doing those setfiles to work with
7.
Now I've got a question for you.
And this is reaching way back, so if you can't remember, it's ok, you've
probably been to pluto and back twice by now 'grin'.
but you usually follow a very logical programming patern and I see it over
and over in these setfiles, hyperactive windows trigering user windows to
activate and do a certain action, this is in the plug-in windows.
Now, I saw a departure in the sf7delay.000 setfile, and you referenced
something called the delay editor, but the hyperactive window actually
triggered something else.
Is there a delay editor ie another section in there where we can do stuff?
Because the actual field which is next is mod rate, and for the life of
me, I can't get that hyperactive window to focus on that field, it won't
trigger, and I've tried all the tricks.
So far on all the other setfiles, I've had to move windows around a bit,
and assign some text strings in hyperactive windows for some controls that
just won't talk even when you activate a window around them, this is some
of the stuff that got broken between 6.1 and 7 yikes.
So what does the programming master say?
YOu may not even have a way to mess with 7 anymore, but the reason I like
7 is that it doesn't depend on dot net framework, and doesn't have that
bug in it with the stopping of loop preview which never worked right on
sf8 for me.
And they pulled the rug out from under you with 9 so, we need to get one
version really working right atleast, or be chasing our tails forever
'grin'.
Now, back to this mis-behaving field I can't pin down with a hyperactive
window in the delay, it's the multi-tap delay window.
I could use a field name, but
you can't do anything with that like activate a window or such.
So any ideas?
In this plug-in the hyperactive window c is triggering the wet out and the
very next one is for mod rate.
I can see the tag for the mod rate, and usually either lining up the
window with twice presses of the f5 and f6 will find the cordinates, or
going a bit above and to the left or right depending on whether your
defining a top or bottom cordinate can fix the problem but this one won't
work.
I can make a user window to track the value of the slider for the mod
rate.
But not for the hyperactive window to trigger it.
Help, help 'grin'.
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4484 (20091006) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Other related posts: