Community Forums Archive

Go Back

Subject: Sound Forge Pro 11 After 5 years. Yea!
Posted by: Fccfirstclass
Date: 7/22/2013 5:55:45 AM

New plug ins. 64 bit. I am getting my upgrade.

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: sergiob
Date: 7/22/2013 6:43:12 AM

Where does it say 64bit? I found that it can record up to 64-bit/192 kHz audio but could not find whether the application itself is 64bit.

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: Dave W
Date: 7/22/2013 9:06:07 AM

I would feel better about giving Sony my money if they would have fixed some of the bugs in 10

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: sergiob
Date: 7/22/2013 9:09:14 AM

I just got off the phone with SCS Customer Service and the application is still 32bit. Not sure if I will upgrade.

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: colinu
Date: 7/22/2013 1:02:56 PM

I have been chomping at the bit for a new version of Sound Forge Pro. I must say that I am disappointed, and see no reason to upgrade.

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: Cielspacing
Date: 7/22/2013 1:43:08 PM

I have the same impression;
Zero interestest in upgradeing to SF11 as it is.

However I would be insterested in an attractively priced "crossgrade upgrade" to get Spectralayers v2... If it is in fact demonstrated that V2 has actually fixed the problems users had with v1.5 (as read in SL own forum).
Besides, there has been not much interest in V1 or V1.5 and so the Spectralayers forum has become paralized in the last months, thus no big chance to actually find if it does work for real and if its usage is practical enough.

In terms of pricing, as the offer stands now, it forces us Sounforge Users to either buy in the bundled "Mastering Suite", or to upgrade just Soundforge... no chance for actual SF users to access an offer on Spectralayers V2

Message last edited on 7/22/2013 2:13:30 PM by Cielspacing.
Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: Cielspacing
Date: 7/22/2013 2:09:18 PM

uHmm

I was strolling thru the offer email we received...
And having discarded the SF11 upgrade, I realised that if the Spectralayers 2 offer were:

•Upgrade from SpectraLayers Pro for only $149.95* – save $50
•Upgrade from Sound Forge Pro 10 for only $149.95* – save $50
•Buy SpectraLayers Pro 2 for only $349.95* – save $50

I might be interested in the second choice, as said above if SL proves to be workable.

Message last edited on 7/22/2013 2:10:03 PM by Cielspacing.
Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: 519tbarr
Date: 7/22/2013 2:44:01 PM

Wait???

One of the SCS forum members on facebook posted that this is indeed a 64x app??? Can SCS clarify this? And if so - please update the website to say Now 64x!!!

Waiting on an official response!

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: Mike / SCS
Date: 7/22/2013 3:18:35 PM

Hi, SFP11 is not 64-bit.

Both upgrades are amazing! And working together they are beyond amazing…

Mike (Product Manager for both and entirely unbiased)

Cheers! :-)

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: 519tbarr
Date: 7/22/2013 3:45:38 PM

Thanks for the clarification Mike.

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: iain_m
Date: 7/23/2013 7:10:46 AM

Mike, it would be very helpful to see a list of bugs fixed in the new release. Would that be possible please?

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: ChristoC
Date: 7/23/2013 5:16:53 PM


Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: iain_m
Date: 7/23/2013 5:24:54 PM

Yes, I looked at that - no mention of bugfixes.

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: pwppch
Date: 7/23/2013 6:44:09 PM

@iain_m

Since this was a new version, we typically don't enumerate issues related to a previous version.

If you have specific issues that you would like to know about, please ask.

Peter

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: Geoff_Wood
Date: 7/24/2013 6:11:03 PM

It is not a 64 bit application. Is there any actual reason that you feel it would benefit from being 64 bit ?

geoff

Message last edited on 7/24/2013 6:13:51 PM by Geoff_Wood.
Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: Vocalpoint
Date: 7/25/2013 10:29:55 AM

It is not a 64 bit application. Is there any actual reason that you feel it would benefit from being 64 bit ?

The most obvious reason is that many active DAW users are (and have been) migrating everything plugin-wise to 64 bit to accommodate said pure 64 bit hosts - like me for example :) I do not have a single 32bit plugin or audio application remaining on my DAW as of this writing.

So - SF 11 could be the best audio editor ever made yet since it can never accommodate my current plugin roster - that's an immediate no sale for me.

I am sure there are other reasons - but a 32 bit app in a 64 bit world is an immediate show-stopper for me (and presumably many others) in my books.

Cheers,

VP

Message last edited on 7/25/2013 10:32:01 AM by Vocalpoint.
Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: sergiob
Date: 7/25/2013 12:56:48 PM

Well said Vocalpoint .

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: deusx
Date: 7/26/2013 4:55:04 AM

>>> I do not have a single 32bit plugin or audio application remaining on my DAW as of this writing<<<<

What's that have to do with Sound Forge? It doesn't really need any of those plugins ( 32 or 64 bit ) to do the job.

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: Vocalpoint
Date: 7/26/2013 9:48:04 AM

What's that have to do with Sound Forge? It doesn't really need any of those plugins ( 32 or 64 bit ) to do the job.

Well - that's your opinion I guess. If the included plugs do what you need them to do - good on ya.

But for my workflows - I "need" specific plugins - that in my opinion - far outweigh the quality of anything included with SF. And as they are all 64 bit - they require a 64bit host.

SF 11 - is not (and can never be) that host.

VP

Message last edited on 7/26/2013 11:03:25 AM by Vocalpoint.
Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: sergiob
Date: 7/26/2013 11:47:04 AM

"What's that have to do with Sound Forge? It doesn't really need any of those plugins ( 32 or 64 bit ) to do the job. "

There are things that SF alone cannot do like adding a console emulator effect or a tube saturation effect. If SF does not really need any of those plug-ins, then why does SF support VST and DXi plug-ins? SF can do a lot, but for me, it cannot do everything alone.

Message last edited on 7/26/2013 11:47:41 AM by sergiob.
Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: kbruff
Date: 7/26/2013 11:53:51 AM

Are there any 64 bit pluggins that do not have 32 bit version, which are lets say pro-grade?

I cant think of any...and admittedly I own a lot of the pro-stuff?

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: Vocalpoint
Date: 7/26/2013 2:16:46 PM

Not really what I am getting at....for me it's that both of my primary hosts cannot run 32 bit plugins - 64 bit only.

So in my case - there is no point to keeping any 32bit stuff on the machine - apps or otherwise since it can't be used any way.

VP



Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: kbruff
Date: 7/26/2013 4:18:35 PM

on a separate note is there well tested bridge for 64 bit down to 32 bit and reversed? Jbridge maybe - or is this only for generators, etc.?

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: Vocalpoint
Date: 7/26/2013 4:44:23 PM

on a separate note is there well tested bridge for 64 bit down to 32 bit and reversed? Jbridge maybe - or is this only for generators, etc.?

Yes - I believe JBridge can work both ways - but I am not a fan of any bridging whatsoever - it's a clunky band-aid of a solution to me.

Both Wavelab 8 and Studio One v2 are "pure" 64 bit apps in that they do not acknowledge 32bit plugs whatsoever so that made it even easier to "clean house" and just go 64 bit across the board.

Tis unfortunate that SF11 is already adrift in the past but with WL8 (x64) - I have a more than capable editor for pretty much everything I need to do - that can handle all my plugins with ease.

Cheers,

VP

Message last edited on 7/26/2013 4:45:47 PM by Vocalpoint.
Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: kbruff
Date: 7/26/2013 7:00:56 PM

I am in agreement with you, but admittedly I cant stand wavelab gui...I have the latest but surely it just seems graphically effort-ridden...if you will...

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: Vocalpoint
Date: 7/26/2013 11:25:48 PM

I am in agreement with you, but admittedly I cant stand wavelab gui...I have the latest but surely it just seems graphically effort-ridden...if you will...

Yep - the UI is still something outa of the 90's but it still kicks SF down in many areas.

Like I have said to others - "I don't have to like it - but it gets the job done".

Mind you - the WL8 GUI is much more enjoyable than WL7 was...I have moved all client production over to V8 now with no problems.

VP

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: Jace
Date: 7/28/2013 12:13:24 AM

i have found that the 64-bit version of Sonar will not start Sound Forge from the tools/utility menu for external editing of audio. It seems to be a bitness issue, because the 32-bit version still works properly. So... there's another reason for Sound Forge to be 64-bit. Running 32-bit software on 64-bit systems is slightly less CPU efficient, as well.

Seriously, why the heck isn't it 64-bit yet? My reasons for using Windows have really decreased over the years to "because i have legacy content in Windows-only software." Sound Forge remaining 32-bit isn't helping to keep me on Windows.

i didn't upgrade to version 10. i won't be buying this upgrade either. Nothing compelling. Sony's just keeping the product on the shelves, not really advancing anything. They're licensing iZotope code to update some native tools. They're adding a few little enhancements. Nothing's really going on here. It's stagnant. Kind of like Logic Pro X and Photoshop CS4-6. Software from the big boys these days is so stagnant. It's all about getting us to pay again, repeatedly, without giving us anything compelling. At this rate, the open source garbage might actually start to catch up.

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: Iacobus
Date: 7/28/2013 2:38:54 PM

From a usability standpoint, what else is there? Most of the features in any top-level program have "maxed out"; from there, it's just quality-of-life improvements (which is just fine by me). Whether or not anyone feels $199 is a justifiable upgrade price is up to them in the end.

I do like the new features, especially the waveform overview bar (a way to navigate the entire file without zooming out? Oh, yes, please.) and new the plug-in chain window. I'd like 64-bit too but I can wait; it's not like my creativity is stifled otherwise.

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: sergiob
Date: 7/29/2013 11:02:51 AM

>>i have found that the 64-bit version of Sonar will not start Sound Forge from the tools/utility menu for external editing of audio. It seems to be a bitness issue, because the 32-bit version still works properly.<<

It works for me and I'm using 64-bit Sonar in Windows 7.
Have you tried this http://www.cakewalk.com/Support/kb/reader.aspx/2007013099? The Sound Forge path in those instructions are different than mine (C:\Program Files (x86)\Sony\Sound Forge Pro 10.0\Forge100.exe).

I might upgrade if the price is U$99. I think that U$149.99 or more is too much.

Sergio

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: iain_m
Date: 7/29/2013 7:36:07 PM

Hi Peter,

The biggies for me in v10 are:
1) the bug where the batch processor apparently randomly saves files as silence
2) the bug with dragging CD tracks in the data window when crossfades exist between them.

I think you already have the details of (2) from an email conversation but let me know if you need the info again.

These are the two key issues that I'd like to see fixed in v11. (1) has been a major workflow blocker because I cannot trust the batch processor, and (2) has prevented me from moving my CD-creation tasks into Sound Forge.

I'd also appreciate more user-friendly clarity on the Sony site about the headline benefits from v11 - the phrase "modeless recording" doesn't really sell the sizzle.

Thanks for your time
Iain

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: kitekrazee
Date: 7/31/2013 10:29:33 AM

FL Studio is still a 32 bit app but has it's own bridge to load 64 bit plugins. I find it odd that a new release of any DAW software is not 64 bit.

I guess those of you who are still fans of Acid Pro, should not get your hopes up.

Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: Vocalpoint
Date: 7/31/2013 12:16:56 PM


FL Studio is still a 32 bit app but has it's own bridge to load 64 bit plugins.

Usually it's the other way around - 64 bit apps bridging 32 bit plugs. That said - bridging to me is just a band aid approach and tends to cause way more issues than it's worth.

Studio One and WL8 do not bridge so that ensures I am using a pure 64 bit path for everything...not to mention ditching all the old 32 bit crap.

I guess those of you who are still fans of Acid Pro, should not get your hopes up.

Trust me - I am not. :)

VP





Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: brothership
Date: 8/1/2013 1:31:59 PM

1) the bug where the batch processor apparently randomly saves files as silence

Happens to me as well. Also, when converting a large batch, multiple files sometimes aren't even processed.

Message last edited on 8/2/2013 3:50:14 PM by brothership.
Subject: RE: Sound Forge Pro 11 After 5 years. Yea!
Reply by: roblesinge
Date: 8/1/2013 1:57:36 PM

Yeah, I've run into this problem too. It seems to be purely random, or at least I can't figure out what causes it.

As a workaround, I wrote a script that checks a folder of files for silences by looking at the statistics for zero crossings. At first it was checking RMS level, but I was getting the occasional false positive with it.

I'd imagine it's a hard bug to fix, since it is so random.

Rob.

Go Back