Subject:8.0d bug

Posted by: ByronSanto

Date:4/7/2006 8:55:47 PM

I just updated from 8.0b to 8.0d and now when I use a single plug-in the CPU usage does not work. It just stays at CPU %.

The plug-in CPU % usage does work in Plug-In Chainer.

Subject:RE: 8.0d bug

Reply by: JTelles

Date:4/8/2006 3:14:07 PM

The same is happening here...
JTelles

Subject:RE: 8.0d bug

Reply by: Geoff_Wood

Date:4/9/2006 4:32:29 AM

Me too. Any number of plugs, VST or DX, no CPU% number.

geoff

Subject:RE: 8.0d bug

Reply by: ByronSanto

Date:4/9/2006 9:16:12 AM

I sure hope this is an easy fix. I have SF 8.0d installed on my LapTop that I use to test/demo plug-ins & software before installing on my studio PC.

I'm somewhat hesitant about installing this Update on my studio PC untill I test it more.

Subject:RE: 8.0d bug

Reply by: drbam

Date:4/9/2006 1:58:19 PM

Yes, I'm seeing the same thing.

drbam

Subject:RE: 8.0d bug

Reply by: Chienworks

Date:4/10/2006 4:12:48 AM

I guess i have to ask that nagging question: how does this affect you getting your work done? If you have too many plugins for the processor to keep up, playback is going to stutter whether you can see the CPU% or not. Conversely, if you're not pegging the CPU then playback will be fine whether you see the CPU% or not. In either case, it makes no difference when saving a file as the computer will simply take as much time as it needs to process all the plugins properly.

Subject:RE: 8.0d bug

Reply by: drbam

Date:4/10/2006 6:35:35 AM

"I guess i have to ask that nagging question: how does this affect you getting your work done? If you have too many plugins for the processor to keep up, playback is going to stutter whether you can see the CPU% or not. Conversely, if you're not pegging the CPU then playback will be fine whether you see the CPU% or not."

True, it doesn't affect my workflow. But, sometimes I find it useful, if nothing else but to learn more about what efx or processing is doing what. AND, at this point, for me at least, its also a matter of principle. SF8 was full of bugs and even Sony admitted on this forum that it was released prematurely. The customer's sense of Sony's ongoing integrity, as well competency, is also part of the equation here. As a customer, this is something I'm interested in and pay attention to. I work hard to be an informed consumer and I choose to support those companies that demonstrate that they care about their customers and step up to the plate when mistakes are made. IMO, its the little things that count and issues like this CPU bug tend to give me pause because they often speak to, and are symbolic of larger systemic problems within an organization. I know that many folks simply don't give a damn about this kind of thing and only want a tool that helps them get their work done – period. Many of them would also shop at WalMart. I don't and won't. Again, its about principle.

Peace,

drbam

Subject:RE: 8.0d bug

Reply by: Ben 

Date:4/10/2006 7:00:51 AM

Well, to be fair to Sony drbam, I had an insane amount of problems with previous 8.0 releases and I'm really, really pleased that with 8.0d, Sound Forge finally seems to be stable again.

From a couple of days useage, I'm so far not experiencing any of the hanging/locking up problems I was having until now. And these were very frequent. So as far as I'm concerned, 8.0d is running very well and feels like the most solid release for a while.

So I can see that the CPU thing might be a tad annoying, but I don't see how it can be anywhere near a deal-breaker. Moreover, how when running an individual plugin these days, do you ever need to worry that the CPU might max out? SF 8 is now stable, and that's great news IMO.

Ben

Subject:RE: 8.0d bug

Reply by: drbam

Date:4/10/2006 8:19:50 AM

"Well, to be fair to Sony drbam, I had an insane amount of problems with previous 8.0 releases and I'm really, really pleased that with 8.0d, Sound Forge finally seems to be stable again."

I agree. This past weekend was the first time I used it without problems that interrupted my work. Of course, its been about a year after its release to experience this level of stability. If that's what you consider "fair", then I suppose we have different perspectives about what the word means. I think its a reasonable expectation that one should be able to successfully use this software before a year passes – wayyyy before a year passes. That has not been the case for me, or you. At any rate, we certainly don't need to beat this horse any further. We are way off topic and the bottom line is that any displeasure I may have with Sony's policies and practices are my problem.

drbam

Subject:RE: 8.0d bug

Reply by: Ben 

Date:4/10/2006 9:09:18 AM

I absolutely agree - I think it's crazy we had to wait so long to get this fixed. The software's only now finally at the stage that I trust it not to crash. I am also constantly amazed at how they manage to 'break' things that were previously working - like this CPU thing. Indeed, until 8d, ALL previous versions of Sound Forge performed better than the current one, which is mad. One can kind of understand new features not working correctly, but old ones? That's nuts.

And no doubt in a few months they'll be pushing SF 9 at us! [rolls eyes...]

But, I am grateful it is finally working.

Ben

Subject:RE: 8.0d bug

Reply by: R0cky

Date:4/10/2006 12:43:42 PM

how many of you guys are using Echo drivers? In my case the Layla 3G.

Only 8.0a previews plugins on a clean system with only Sony Media apps installed. On 8.0b and 8.0d preview using the Echo drivers doesn't work correctly.

On 8.0d the echo ASIO drivers seem to preview ok, but not WDM or Pure Wave.

I also get the no CPU% bug.

I have been working with Tech Support on this but so far they haven't been able to reproduce it on their test setup. Anybody else have this problem?

thanks,
Rocky

Subject:RE: 8.0d bug

Reply by: JTelles

Date:4/10/2006 5:58:54 PM

I have Echo Mia here and no problems with previewing either in ASIO or Pure Wave/WDM.
JTelles

Subject:RE: 8.0d bug

Reply by: drbam

Date:4/10/2006 6:35:37 PM

I use a Layla 24 - latest drivers prior to the 3G release. No problem with Preview using PureWave drivers.

drbam

Subject:RE: 8.0d bug

Reply by: jaydeeee

Date:4/12/2006 2:30:20 AM

>>>Well, to be fair to Sony drbam, I had an insane amount of problems with previous 8.0 releases and I'm really, really pleased that with 8.0d, Sound Forge finally seems to be stable again.
<<<

try doing more than just editing a few files here and there.
Like working with many diff audio formats, editing multiple sample rates an sized files, and batch cvrting each day.
I don't agree - 8d is worse than 8a or b.

It's unacceptable to me at this point. Wavelab might be arriving soon, i got work to do. I need a godd**ned solid batch cvrtr at minimum.

Sony - PLEASE revisit early sfoudnrys 5.0 batch cvrtr...and see what they've done right. Maybe revive that app? because I've had it with 8.

Subject:RE: 8.0d bug

Reply by: mpd

Date:4/12/2006 11:42:40 AM

jaydeeee,

I think there is something in particular about the way you are using SF.

I have had SF8 open nearly all day the last week or so working on some long sessions from last week. I have also batched well over a thousand files this week, and the batch jobs have included a bunch of the processes / plugins that you have been having problems with.

Subject:RE: 8.0d bug

Reply by: Ben 

Date:4/12/2006 3:58:36 PM

>>> try doing more than just editing a few files here and there. <<<

Not necessary Joe - I hammer the thing. Always have. Lots of micro-editing, lots of plugins on small sections, lots of batch converting... across many files at once. With 8d, no problems so far.

B

Subject:RE: 8.0d bug

Reply by: R0cky

Date:4/13/2006 11:01:24 AM

I have had the SF8.0a and b batch converter fail serveral times running a simple script on a long list of files. It hangs on the next to last file and I have to kill it in task manager to recover.

The "next to last" file hang behavior has happened several times with different scripts running on different file lists.

Haven't tried it on 8.0d as I'm using 8.0a because of my problems with preview on the later releases.

Subject:RE: 8.0d bug

Reply by: jaydeeee

Date:4/14/2006 4:14:42 AM

>>>Not necessary Joe - I hammer the thing. Always have. Lots of micro-editing, lots of plugins on small sections, lots of batch converting... across many files at once. With 8d, no problems so far.<<<

Umm, no. Not when i can repro the problem each day. P4 systems (tip-top), new amd systems (also tip-top)...the results are the same - batch cvrtr in 8d is f'd (since 8a on).
i've been using forge since sfoundry forge 3, and this is the most screwed forge has ever been.

I'm not even using any plugins. I'm talking about editing a wide scale of sample rates, short .wavs, mp3 and mono .wavs, appending text to batches, etc...ad-nauseum.
d is the worst so far. I suspect problems with forge's handling of files in multiple folders deep, appending names, length of name, etc.

PLEASE EXPLAIN WHY I SEE ZERO-FEW PROBLEMS WITH SFOUNDRYS 5.0 BATCH CVRTR WITH THE SAME PROJECTS.

Subject:RE: 8.0d bug

Reply by: ByronSanto

Date:4/15/2006 7:19:37 AM

Has anyone noticed a higher CPU usage as well. I use SF on an older laptop to test plug-ins before purchasing/installing on my studio PC. Plug-ins that I use as a benchmark for testing newer plugs maxed out my CPU.

8.0b never did do that with these plugs????????????

Subject:RE: 8.0d bug

Reply by: Geoff_Wood

Date:4/17/2006 2:19:38 AM

"
PLEASE EXPLAIN WHY I SEE ZERO-FEW PROBLEMS WITH SFOUNDRYS 5.0 BATCH CVRTR WITH THE SAME PROJECTS. "

Something to do with scripting is stuffed up on your computer that BC5 doesn't utilise, and isn't stuiffed up on others peoples' computers ?

It would have to be something unique to your installs - some reg tweak or service disabled that has been done to all your PCs ?

Maybe something that YOU are doing - something that is subtly different to 5 and illegal/fatal (and not trapped) in 8 ? Something like non-pre-existant folders not be created automatically, lack of a path setting, using a common folder and no filename change after processing, or whatever.

Just grasping at straws here....

geoff

Subject:RE: 8.0d bug

Reply by: jaydeeee

Date:4/17/2006 4:11:13 PM

>>>Just grasping at straws here...<<<

That you are Geoff. That you are. :)

I'll chalk it up as, another persons described "hammering" (although possibly true) is different from the "hammering" of others.

Shortcut to the truth:
sfoundrys 5.0 batch cvrtr works. Sonys SF8?....shite.

Subject:RE: 8.0d bug

Reply by: kbruff

Date:4/18/2006 9:03:19 AM

Could you possibly roll back to Sound Forge batch Converter 5.0b instead?

Or can you write a script to (or pay someone to write you script) that will work for you, a lot of folks have sworn by the batch conversion abilities of Wavelab 6 -- I have used and it is very powerful tool, perhaps you should consider trying it until Sound Forge can work for you, it is worth it having two editors since when one is broken the other one usual keeps going.

Subject:RE: 8.0d bug

Reply by: jaydeeee

Date:4/18/2006 12:10:55 PM

No need to roll-back, I use foundry's 5.0 batch cvrtr now (it's it's own application). I'm posting this for sony's and others own info. I have zero to very little issues with foundrys 5.0 cvrtr....but in sf8 - crash city with the work I'm doing.

Yes, if I don't see a cvrtr fixes for 8 (and see a forge 9 before it)...Wavelab it is.

Subject:RE: 8.0d bug

Reply by: Geoff_Wood

Date:4/18/2006 5:33:22 PM

Still suggest you revisit your methodology wrt source/processed filenames, folders, temp folder, file open in another window (inlc Win Explorer) when processing, etc.

That you are having this problem on multiple machines and other people aren't says something to me.

geoff

Subject:RE: 8.0d bug

Reply by: jaydeeee

Date:4/19/2006 1:20:47 PM

Geoff, thanks for the response (really)...but it's not my methodology (nor any of the various systems I'll try it on). Really it isn't. It's flat out clear to this is a forge8 issue. Trust me, i'd be open to following thru if it were possible the problem is user error.

I'll use foundrys old 5.0 batcher (works absolutley perfect - same batching projects) for a while then it's on to wavelab. I've been a forge user forever, but i can't have this.

Subject:RE: 8.0d bug

Reply by: SHTUNOT

Date:4/19/2006 2:49:58 PM

Jay have you emailed your batch scripts to support so that they can take a look at it and see if there are any problems on their end using them?

Ed.

Subject:RE: 8.0d bug

Reply by: jaydeeee

Date:4/19/2006 3:06:30 PM

Yes I have in fact. No reply, but later an update came out (d).

It's a real figity one too - it would crash randomly at first...maybe a few more times even with 8d (much worse than 8b). Then - the same batch setup...would somehow batch thru just fine in 8d. Way too random I think for them to follow thru on.

My systems are completely tip-top (trust me), and with this batching...I'm not even using any in-line plugins. I've already stated where I "suspect" sf8's buggin out (see above).

again - take the exact same batch/setup and run it on foundry's 5.0 cvrtr...no probs. So I dunno, I can't play beta tester with all this work to do, ya know.

Subject:RE: 8.0d bug

Reply by: Illogical

Date:4/26/2006 1:24:51 PM

I've got the same CPU bug and 8.0d crashes a lot. I'm kinda regretting that I uninstalled SF Audio Studio at this point, not the same functionality, but at least it didn't crash all the time.