Magix Release Soundforge Studio 12

Use code MAGIX15
 
Upgrade price was 9.99 GBP for me.  

I installed the demo, and it replaced my QuadCapture drivers in Sonar with MagixLowLatency drivers, which was a far cry from low latency. I was not able to select the QuadCapture drivers so I uninstalled Soundforge Studio 12. Everything is good now!

For some reason I wasn't able to select my drivers. Oh, well. Glad it worked out for you. 

kitekrazy1
Use code MAGIX15
Upgrade price was 9.99 GBP for me.  

Unfortunately the code doesn't work for me. I get a message that says a coupon can't be used for this purchase.
I can get it as an upgrade for 29.99 USD,  which is still a good price.

Upgraded to 12.  Been futzing with the preferences and such.  Seems to be a nice improvement over 10.
 
@Jim...thanks for the registry tips, ol pal!
 

Billy Buck

Was there a serial # for Elements?  

 
Yes, a few hours after I did the upgrade from the Magix site I received serial numbers and download links
for both SF 12 Studio & Audio Cleaning Lab and a separate serial number for Ozone Elements. I then went to
the Izotope website and downloaded the trial version and once installed used the same serial number to unlock it.
 

 
Acid Pro is on the horizon for 64 bit.   If they keep the same gui and add a dedicated midi window that may be my top choice for a DAW since I loved the workflow.

 
I still have ACID Pro 7 installed and use it from time to time. As a pure loop arrangement tool it is still the best IMO
and I do like the GUI and workflow. I will seriously take a fresh look at a 64bit ACID Pro 8 once it is released. If the upgrade price is reasonable and it is stable on my DAW I will probably upgrade. I remember first starting out with ACID Pro 1.0 back in 1999, so I am still quite familiar with it.
 
Cheers,
 
Billy Buck

Went back the my email the code was there.  I'm not fond of the Magix single machine license. Two machines is the norm these days. 

Hmm, can't upgrade from 10 pro to 12 studio (and 11 pro is still not x64? and only version 11?)

rsinger

kitekrazy1
Went back the my email the code was there.  I'm not fond of the Magix single machine license. Two machines is the norm these days. 

I agree, but Steinberg wavelab is the same. I have wavelab essentials on my laptop and soundforge studio on my DAW.
 

My Account includes a license for two machines now that I have upgraded.

rsinger
I agree, but Steinberg wavelab is the same. I have wavelab essentials on my laptop and soundforge studio on my DAW.
 

I have their dongle for Wavelab 8.5. I can use it anywhere I want.

Hmmm.....it could be a problem for me, because some of my recent plug-ins are 64-bit (or at least the version I installed).
 
I like Sound Forge though. Maybe they will introduce VST3 and CD/DVD/Media authoring in the next version. Or perhaps not, that's one of the selling points of Magix Samplitude.
 

More excited for Superior Drummer 3.

Jim Roseberry
To get rid of the Magix Low Latency ASIO driver:
 
Go into the Registry...
HKLM>Software>ASIO - delete the Magix Low Latency ASIO driver entry
HKLM>Software>WOW6432Node>ASIO - delete the Magix Low Latency ASIO driver entry
 
Note:
If you've got a piece of hardware that functions as an ASIO audio interface (and you know you don't want to use it), you can use this same procedure to eliminate that particular ASIO driver.

 
Thanks, Jim!  I know this is replying to a post from quite a while ago, but I'm super glad I found it as it solved a recent problem I'd been having with SONAR Platinum (most recent version), and which got even worse with Cakewalk by BandLab.
 
For context, I'd picked up Samplitude Pro X3 Suite when they had the "crazy deal" late last year.  I haven't had much time to try it out yet, and I'd been alternating between DAWs (SONAR, Cubase, Studio One) as I'd do new, or remix, projects. 
 
When I'd go back to SONAR, I'd often find that it had developed a new problem related to switching sample rates.  In the past, if I'd been operating at 44.1 kHz, and I loaded a 96 kHz project (most of my older projects are 44.1 kHz, while almost all my new projects are 96 kHz), there would be a brief burst of white noise as SONAR told my MOTU 828x interface to switch settings, but then things would work as per normal, with the occasional exception of needing to reassign the Master bus to the right hardware interface.  (I never pinned down when this happened and when it didn't, but it was pretty painless, so it was only a minor inconvenience.) 
 
Now, however, in SONAR, I'd get a cycle of events where it would have that burst of white noise, put a dialog box up that came and went too quickly for me to read, put the hourglass up for a while, and finally let in some user interface action for a very brief moment.  The exact order may have been different from what I am outlining, but the cycle was constant.  Eventually, I'd have to close SONAR, then jump through some hoops to set the sample rate (possibly also in the default settings as well as on the ASIO control panel for my device), then again try loading the project.  This issue also did affect some other DAWs, albeit in different ways (e.g. Studio One wouldn't even attempt to play audio).
 
When Cakewalk by BandLab came out a few days back, I found that the problem was more severe.  The cycle still occurred, and now the former dialog box became a little banner in the notifications area, which, thankfully, was now readable, saying something about the MAGIX Low Latency Driver.  But when I got to closing CbB, it would crash instead of just closing gracefully.  And again I'd have to figure out what specific hoops to jump through in each specific case.
 
With the newly readable banner in mind, I set out to searching for information about problems in this area and/or how to remove the MAGIX Low Latency Driver, since I doubt I actually need it for anything at this point (I wasn't even using it in Samplitude), and I eventually came across this thread.  Removing the driver per Jim's instructions resolves the switching sample rates issue in CbB (I'm assuming it will in SONAR, as well, but, short of finding issues in CbB that SONAR doesn't have, I intend to try using CbB instead of SONAR moving forward). 
 
While I do think SONAR and CbB (and some other DAWs -- Studio One, in particular) have an issue in this area, especially since I wasn't even using the MAGIX driver, I'm very happy to have this workaround/solution to stave off the frustration of having jump through hoops most every time I'd go back to SONAR to work on a project.

Sound Forge studio is not an upgrade to Sound Forge Pro (last version being 11) from Sony Creative.