Comments

Strings137 wrote on 6/14/2002, 11:02 AM
SF: Any comments on this problem. Thanks.
SonyEPM wrote on 6/14/2002, 11:32 AM
We have tried to repro this several times, and cannot. The first time file>open is invoked from Forge, it takes a few seconds (like 3-5), and after that it is very fast.

Any other details you can provide would be helpful-
Strings137 wrote on 6/14/2002, 8:33 PM
Thanks for your fast response. I have tried it in every way possible to get it to work but it will not on my system. It works ok with version 3.0 if I do a clean re-install. I can get by without upgrading to 3.0b. When I have time I will continue trying to get it fixed. If I find the problem I will let you know. Again, thanks.
CAPNDigital wrote on 6/15/2002, 8:10 PM
Strings137 & SonicEPM

I have encountered the same problem and I have been working with SonicFoundry tech support emails... I have tried all suggestions and none have proven successful. We have been looking at Sound Forge as the culprit however, you may be onto something with your comments about "reinstalling VV3.0" and the problem correcting itself. I haven't tried that yet... btw the problem remained with reinstalling the Forge 5.0e update build - the only way to recover the Open Dialog feature was to reinstall my original build of Forge (5.0b) which came included with my Acid Pro 3.0 software disc.

BTW Sonic EPM, I have tried waiting several seconds (more like 10 - 15) and the Open Dialog never opens... all of this I included in my email conversations with JDogde@sonicfoundry.com

Strings137, I originally posted my problem in the Sound Forge forum - no replies yet - so I have been working with Joshua Dodge at tech support... you mail want to email him with your findings - jdodge@sonicfoundry.com

Chris
CAP'N Digital Productions
Strings137 wrote on 6/15/2002, 11:06 PM
Chris, thanks for the info. As soon as I try some more changes I will let you and Mr Dodge know if I find the cause of the problem. Are you using Pentium or AMD system. Thanks again.
CAPNDigital wrote on 6/17/2002, 9:07 PM
Strings137,

Sorry I forgot to include that info... I am using Pentium III / 633 - 256Ram (plus 64MB videoram) - WinME...

Thanks,

Chris
Crocodile wrote on 6/18/2002, 2:43 AM
Same problem here. Tried reinstalling both apps with no luck. The only way I can solve it, is to revert to the earlier version of Vegas (3.0a) then sound forge 5.0f works fine.

PIII 866
512 megs ram
XP home
asus CUSL2 main board
Crocodile wrote on 6/18/2002, 8:57 PM

got this from sonic today regarding our problem

Hello,
Thank you for the email. We have seen many things wrong with the
3.0B build of Vegas and have since pulled it from our web site. We would
recommend going back to the 3.0A build at this time, until we release a
newer build than 3.0B 128.
Sorry for the inconvenience.

Strings137 wrote on 6/18/2002, 10:06 PM
Thanks for the info. I won't have to pursue a fix for 3.0b.
CAPNDigital wrote on 6/18/2002, 11:16 PM
Strings137,

I am currently involved in some troubleshooting processes with Tech Support - based on the Sound Forge 5.0f and Vegas 3.0b problem. However, I have discovered that this problem is occuring during ANY Vegas 3.0 build and 5.0e or 5.0f...(5.0b build seems fine with ALL versions of Vegas, prior 5.0d build is next to try) I am still trying different combinations and will report all of my findings to SF Tech Support tomorrow.

Interesting that you mentioned reinstalling the original VV 3.0 build (prior to the first 3.0a update build) the problem resolved for you, it has not corrected the problem for me in either 5.0e or 5.0f builds of Sound Forge - again, I am trying numerous combinations of installs with both programs and builds...

Obviously if you have a combination that is working stick with it, and you may want to pass this combo info on to Tech Support...

Thanks for the info and feedback...

Chris

WinMe,PIII 633,256Ram/64Video,latest builds of VV and SF (and now some earlier builds)