Unfortunately no better. In fact, worse. This time I tested it on my Windows 10 i7 16GB laptop. Started with an hour long standard wav file--44,100Hz @ 16bit. Tried to convert to a 192mbps 44,100 16bit mp3 (so no resampling or bit depth conversion) at "fastest encode". I cancelled it after 3%. Estimated time would have been 2.77 hours.

Both computers have very fast SSDs. MP3s are the only thing that seem to be broken for rendering. Every other file type is working fine.

@brent-warwick

Hi, although I am not a SF user, one statement in your first post caught my attention; you say you are using

Windows 10 April 2018 Update

I wonder whether that is the cause of your problem? More than one user on a variety of forums I visit has posted about a very wide range of problems occurring after the 1803 update to Win 10; more than one of those has been advised to roll back to the 1709 version. My impression is that those who can and do choose that soon discover that these recent "problems" disappear.

Jeff

Thanks Jeff, good theory. In my case though I’ve been experiencing these render problems before I upgraded Windows 10. Before that I was on the Anniversary Edition—same render times.

The odd thing is it’s happening on two separate computers. Both had SF11 Pro (now both uninstalled) before 12 and both currently have Vegas 14. Maybe that has something to do with it. I’ll let Magix chime in on that.

I'm having the same problem since upgrading to SF12. Also using Win 10. Very slow mp3 saves. Any suggestions? Never has this problem with previous versions of Soung Forge.

"Any suggestions?"
- Not for SF. Otherwise Vegas Pro or WinLAME.

My results:
Source: 57 min. stereo 48k/16 PCM file
Render to MP3 192kbs stereo CBR

SF Pro 12:(Win 10)  5:30
SF Pro 11: (Win 10) 4:25
SF Pro 10: (Vista) 8:05
Vegas Pro 9 [x86]: (Win 10)  0.33
Vegas Pro 9 (Vista)  0.41
WinLAME: (Vista) 1:30

My PC is a Dell XPS w. Win10, SSHD w/ 32GB RAM< The Vista PC had dual core w/ about 2.5 GB RAM

Rick, I understand your results and appreciate that you aren't seeing the same thing some other people are. I've contacted support and basically got the same answer: "Well, *WE* aren't seeing that soooooooo…yeah."

It's very frustrating that instead of anyone at Magix asking any questions or trying to troubleshoot the issue we're basically getting stonewalled because company personnel aren't seeing it. It's real, it's an issue, and it wasn't present in SF11 on the same exact computer. I even wrote support with some further clarification and details and never heard back. It's disappointing that the stance of Magix for new issues is to basically prove they can't replicate it and subsequently ignore it.

I'm not saying the problem does not exist, and based on my findings, SF is significantly slower than Vegas. As a SF forum moderator, the only thing I can do is bring this to the attention of the SF Pro 12 project manager, which I will do.

I agree with Brent. I have been using SF versions for many, many years. MP3 render times have never been anywhere as long as in SF12. I also had no change in Win 10 before upgrading to SF12. Magix needs to take another look at this last release - there's a bug in there for sure. If Magix does not listen to its users - they'll regret it later. SF users are usually very computer-literate. Magix should take heed.

Yes, that's the issue. 32bit worked great and immediately tried 64bit after and it was still non-functional. I guess I'll use 32 bit in the meantime and wait for a patch. Thank you for providing a workaround.

Yes, that's the issue. 32bit worked great and immediately tried 64bit after and it was still non-functional. I guess I'll use 32 bit in the meantime and wait for a patch. Thank you for providing a workaround.

Great to hear! yeah I was able to test a 3 times longer export in 64 so I was hoping that helps

Hi. ;Following on from this thread, where please can I download the 32 bit version so as to resolve this issue? I was only provided a download for the 64 bit release. Thank you.