[docsavage20]

I've been using IQ4gui multiband dynamic eq VST plugin under
SoundForge. It was running okay until it started having issues. When I
try to use the high band in peak mode, it crashes every time. It
previously worked fine. Then suddenly it didn't. Tried rebooting, even
re-installing the .dll file for it. It now refuses to cooperate,
period.

Core2 Quad machine, running XP Pro SP3.

If anyone speaks error string, this is what came up. Any idea?

Many thanks.

This is the plugin - http://www.platinumears.com/iq4gui.html


Error string:

Sony Sound Forge 8.0
Version 8.0d (Build 128)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x683DEE2
In Module 'IQ4gui.dll' at Address 0x6760000 + 0xDDEE2
Thread: GUI ID=0x7E8 Stack=0x12F000-0x130000
Registers:
EAX=00000000 CS=001b EIP=0683dee2 EFLGS=00210246
EBX=067c8f90 SS=0023 ESP=0012f64c EBP=0012f714
ECX=00000000 DS=0023 ESI=064ffa08 FS=003b
EDX=00000000 ES=0023 EDI=064ffa08 GS=0000
Bytes at CS:EIP:
0683DEE2: 8B 39 8D 44 24 14 50 FF .9.DP.
0683DEEA: 57 30 8B 38 8B 58 04 8B W0.8.X..
Stack Dump:
0012F64C: 00000000
0012F650: 00000000
0012F654: 064FFA08 064E0000 + 1FA08
0012F658: 00000000
0012F65C: 067C8F90 06760000 + 68F90 (IQ4gui.dll)
0012F660: 00000000
0012F664: 00000308
0012F668: 00000187
0012F66C: 067C8FA8 06760000 + 68FA8 (IQ4gui.dll)
0012F670: 067C8FB7 06760000 + 68FB7 (IQ4gui.dll)
0012F674: 00000000
0012F678: 0012F68C 00030000 + FF68C
0012F67C: 064FF9B8 064E0000 + 1F9B8
0012F680: 00000099
0012F684: 06873F1A 06760000 + 113F1A (IQ4gui.dll)
0012F688: 00000001
0012F694: 00990328 008D0000 + C0328 (sfs4rw.dll)
0012F698: 064FF9B8 064E0000 + 1F9B8
0012F69C: 00000001
0012F6A0: 06856358 06760000 + F6358 (IQ4gui.dll)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 005A0BC8 00400000 + 1A0BC8 (Forge80.exe)
0012FFFC: 00000000

[polymod]

"docsavage20" wrote in message
...
I've been using IQ4gui multiband dynamic eq VST plugin under
SoundForge. It was running okay until it started having issues. When I
try to use the high band in peak mode, it crashes every time. It
previously worked fine. Then suddenly it didn't. Tried rebooting, even
re-installing the .dll file for it. It now refuses to cooperate,
period.

Core2 Quad machine, running XP Pro SP3.

If anyone speaks error string, this is what came up. Any idea?

Many thanks.

This is the plugin - http://www.platinumears.com/iq4gui.html

First thing I'd try is to go back to a restore point when the plug was
working.
Back up any files if needed.


Poly

[docsavage20]

On Dec 27, 11:19*am, "polymod" wrote:

First thing I'd try is to go back to a restore point when the plug was
working.
Back up any files if needed.

Poly


Tried it, didn't cure it. Reinstalled Soundforge, so far it appears to
be working okay again. Seems odd though that the system restore didn't
fix it since the issue didn't appear until today. Doesn't the system
restore revert most things back to whatever state they were in at the
restore point?

[Les Cargill[_4_]]

docsavage20 wrote:
On Dec 27, 11:19 am, "polymod" wrote:

First thing I'd try is to go back to a restore point when the plug was
working.
Back up any files if needed.

Poly


Tried it, didn't cure it. Reinstalled Soundforge, so far it appears to
be working okay again. Seems odd though that the system restore didn't
fix it since the issue didn't appear until today. Doesn't the system
restore revert most things back to whatever state they were in at the
restore point?



It's not clear what a restore point does - mainly reloads
a snapshot of the registry, I've always thought.

I'd call the plugin unusable. It's stepped on itself. The salitn
text from the core dump is "access violation".

--
Les Cargill

[Mike Rivers]

On 12/27/2012 11:13 AM, docsavage20 wrote:
I've been using IQ4gui multiband dynamic eq VST plugin under
SoundForge. It was running okay until it started having issues.

It's because of things like this that I don't have a
favorite EQ plug-in.

EAX=00000000 CS=001b EIP=0683dee2 EFLGS=00210246
EBX=067c8f90 SS=0023 ESP=0012f64c EBP=0012f714
ECX=00000000 DS=0023 ESI=064ffa08 FS=003b
EDX=00000000 ES=0023 EDI=064ffa08 GS=0000
Bytes at CS:EIP:
0683DEE2: 8B 39 8D 44 24 14 50 FF .9.DP.
0683DEEA: 57 30 8B 38 8B 58 04 8B W0.8.X..

Well, you see, when one of my equalizers stops working, I
can fix it with a voltmeter, an oscilloscope, and a
soldering iron (except for those pesky surface mounted
components that take a big magnifier and tiny tweezers).

Who other than perhaps a developer has ever figured out how
to fix something by looking at an error code dump?

You know the drill:
Remove all unnecessary services and close all other programs
Re-install the plug-in
Get the latest drivers for everything (even though the ones
you had were working fine)
Do a clean Windows install (even though there's nothing else
wrong)
Add more RAM (you can never have enough)
Check for updates for the program (just to be sure you're
always running new and unfamiliar software)

If that doesn't fix it, it isn't really broken

--
"Today's production equipment is IT based and cannot be
operated without a passing knowledge of computing, although
it seems that it can be operated without a passing knowledge
of audio." - John Watkinson

http://mikeriversaudio.wordpress.com - useful and
interesting audio stuff

[Scott Dorsey]

Mike Rivers wrote:

Well, you see, when one of my equalizers stops working, I
can fix it with a voltmeter, an oscilloscope, and a
soldering iron (except for those pesky surface mounted
components that take a big magnifier and tiny tweezers).

Who other than perhaps a developer has ever figured out how
to fix something by looking at an error code dump?

It's just one of the skills you need to develop to do maintenance in
the new world, same as using a soldering iron.

This message is saying that the application is trying to write to memory
that doesn't belong to it. This is either because some addresses have
got screwed up in linking or because something is writing over top of
the code segment and you're running your data.

The problem is without the source code you can't really tell what is going
on since you don't know what is at what address.. BUT, the people that
wrote the code have that and they can tell you if you give them that stack
trace.

You can insert my normal plea for open-source or at least properly documented
code with source available for the end-user, which is sort of like my normal
plea for schematics being available for hardware. It's the same thing... if
you know what is inside the box, it's not hard to work on. If you don't know
what is inside the box, you spend more time figuring out how it's supposed to
work than you do actually making it work.
--scott

--
"C'est un Nagra. C'est suisse, et tres, tres precis."

[Here In Oregon]

"Scott Dorsey" wrote in message

It's just one of the skills you need to develop to do maintenance in the
new world, same as using a soldering iron.


You can say that again.

+1

[Les Cargill[_4_]]

Scott Dorsey wrote:
snip

This message is saying that the application is trying to write to memory
that doesn't belong to it. This is either because some addresses have
got screwed up in linking or because something is writing over top of
the code segment and you're running your data.


It's an EQ. It has a bad array index calculation - probably going
negative. Unless there is actual tech support and you can file a bug
report, the EQ is officially unusable.

snip
--scott


--
Les Cargill

[Phil W[_3_]]

"docsavage20":

I've been using IQ4gui multiband dynamic eq VST plugin under
SoundForge. It was running okay until it started having issues. When I
try to use the high band in peak mode, it crashes every time. It
previously worked fine. Then suddenly it didn't. Tried rebooting, even
re-installing the .dll file for it. It now refuses to cooperate,
period.

Core2 Quad machine, running XP Pro SP3.

If anyone speaks error string, this is what came up. Any idea?

Many thanks.

This is the plugin - http://www.platinumears.com/iq4gui.html

Since this plug-in can be regarded to be "broken" - probably because of
coding errors, I would not rely on it anymore and get a substitute.

The free plug-in bundle from Melda Production includes a quite usable EQ.
http://www.meldaproduction.com/freevstplugins/

These folks also offer commercial plug-ins, so there´s a chance, that they
might (at least ought to) care more about the code quality.

Freeware is fine, as long as it´s well-programmed. ;-)


Phil

[Sean Conolly]

"Les Cargill" wrote in message
...
Scott Dorsey wrote:
snip

This message is saying that the application is trying to write to memory
that doesn't belong to it. This is either because some addresses have
got screwed up in linking or because something is writing over top of
the code segment and you're running your data.


It's an EQ. It has a bad array index calculation - probably going
negative. Unless there is actual tech support and you can file a bug
report, the EQ is officially unusable.

However, software doesn't wear out. If it worked before and it's not working
now it is almost certainly because the environment it's running in has
changed, maybe causing it do go down a different process path to reach this
error.

Are the graphics setting different? Hardware acceleration in use? Just
guessing from the references to 'gui' in the stack dump.

Sean

[Luxey]

80% of time it's graphiccs.

[Mike Rivers]

On 12/27/2012 11:17 PM, Phil W wrote:

Since this plug-in can be regarded to be "broken" - probably
because of coding errors, I would not rely on it anymore and
get a substitute.

"Broken" implies that it once wasn't broken. If it has
coding errors, it's poorly designed. If it stopped working
because something else on the system changed, then the
system, not the program, is broken.

Freeware is fine, as long as it´s well-programmed. ;-)

Doesn't the same apply to payware?

--
"Today's production equipment is IT based and cannot be
operated without a passing knowledge of computing, although
it seems that it can be operated without a passing knowledge
of audio." - John Watkinson

http://mikeriversaudio.wordpress.com - useful and
interesting audio stuff

[geoff]

"Mike Rivers" wrote in message
...
On 12/27/2012 11:17 PM, Phil W wrote:

Since this plug-in can be regarded to be "broken" - probably
because of coding errors, I would not rely on it anymore and
get a substitute.

"Broken" implies that it once wasn't broken. If it has coding errors, it's
poorly designed. If it stopped working because something else on the
system changed, then the system, not the program, is broken.

Or that the coding is fragile, and a legitimate change in the system else
may have broken it.


geoff

[docsavage20]

On Dec 27, 11:21*pm, "Sean Conolly" wrote:
"Les Cargill" wrote in message

It's an EQ. It has a bad array index calculation - probably going
negative. Unless there is actual tech support and you can file a bug
report, the EQ is officially unusable.


An odd thing I've noticed, if it was already included as part of a
processing chain, the instances within the chain work fine. If I try
to invoke a new instance of it, that's when I run into the problem. It
-does- work in a crippled fashion, except I can't invoke that one mode
on that channel.

[Les Cargill[_4_]]

docsavage20 wrote:
On Dec 27, 11:21 pm, "Sean Conolly" wrote:
"Les Cargill" wrote in message

It's an EQ. It has a bad array index calculation - probably going
negative. Unless there is actual tech support and you can file a bug
report, the EQ is officially unusable.


An odd thing I've noticed, if it was already included as part of a
processing chain, the instances within the chain work fine. If I try
to invoke a new instance of it, that's when I run into the problem. It
-does- work in a crippled fashion, except I can't invoke that one mode
on that channel.


What if you:

- Copy the project/song file to a new name.
- Delete the instance of the EQ in the new project and re-add it?

If that works okay, it almost sounds like there's a resource
conflict.

--
Les Cargill