Post tech support questions for SFX Machine Pro here.

Or you can always e-mail us at sfx@sfxmachine.com.

Hello Earl,

I think there may be a problem opening old documents that contain SFX Pro 1.1 on an intel Mac. I get garbage when the old document loads instead of my nicely configured settings.

Hmm... I thought this would be reverse-compatible, but the number of sliders has changed, so that may cause a problem. We may need to look at the version number when loading old presets.

Sorry for the trouble. I'll take a look at this after NAMM.

If you have a chance, I'd love to see a screenshot of the type of garbage you get, or a step-by-step description of how to reproduce the problem in Metro.

Best Regards,

Earl

Hi Earl,

To repro this you need to have the old version of SFX Pro (I'm not sure if I do, I will have to check). Load the old AU version, make some tweaks and save a document. Install the new version of SFX Pro and open the previously saved document. The previous settings are not preserved.

I have also noticed that the 'tempo sync' parameter does not seem to be retained when a document is reloaded (both AU & VST versions). I think there also may be a problem with total recall in 1.1.0 (AU Version only).

Jeremy

Today I opened a mix I did last fall and found it (I believe) had some issues
with regards to SFX Pro 1.10. The mix was done w/ 1.0 in Logic Pro 7.2.x in
OS10.4.x Today w/ Logic 7.2.3, OS10.4.8 and SFX 1.1.0, the factory presets
used were not correctly recalled, and the plug passed no sound. The preset
name partially appeared in one instance (not in the other), but the slider
params were not correctly labeled and in general the slider graphics looked
wonky. I tested a song that was made using 1.1.0 and the preset was working
normally.

Is this a known bug? Can I do anything remedy this? I don't know exactly which
chorus preset I used and what adjustments I made to the slider amounts so any
help you can give would be appreciated. This is the first SFX issue I've
had...

Thx,
-Russ

Hi Russ,

Yes, this is a known bug, sorry. SFX Machine Pro 1.1.0 added an additional slider, and the presets ended up not being compatible. You may be able to work around the problem for that particular mix by reinstalling SFX Machine Pro 1.0, http://www.sfxmachine.com/downloads/sfx_machine_pro_1.0.dmg . Or if you can send me a copy of the 1.0 preset that was used, I can convert it to 1.1.0. Another option is to just find a chorus preset that sounds like the original.

I hope this helps. Please feel free to e-mail me at sfx@sfxmachine.com if you have trouble with this.

Hi ! I bought the SFXmachine Pro Plugin on 13th of may... tested it on my old Pentium4 with Cubase5 and it ran smothly...

now i bought a new PC yesterday (Intel Quadcore I7-920)

and i am installing all new like Cubase5 and installed also my new SFXPro Plugin. but when i try to open it, it freezes Cubase... i even can't open it to put it my registration.

What can i do to install it on my new PC ? ? ? Why does it freeze Cubase5 now ? It worked with a PC with a small cpu and now i have some more power and it freezes ? Heeeellllllp !!!!!!

I am running Windows XP Profession SP2
Cubase5 with M-Audio Delta Audiophile 2496
(another soundcard for surround: M-Audio Revolution 7.1)

The PC is just brandnew... i just started to install all new so the system is fresh.

This is the second report we've gotten about this happening with Cubase 5, so it sounds like there's a problem. We'll look into this as soon as possible.

Is this the same version of Windows you were using before -- 32-bit in both cases? In other words, is the Intel Quadcore chip the only thing that's different?

Earl

Okay here is a workaround... thats how i did it and it seems to work.

Problem was that i couldnt register my plugin. and it was freezed when i touched it and crashed my Cubase5...



Now i used a small freewarehostprogramm (Savihost).
Its one Exe-file that you have to put into the vst-folder where the plugin
(in my case the sfxpro-machine is)

Now remaname the exe.file to the sfx-pro.dll name

so you still have the sfxpro.dll and also now a sfxpro.exe

start the sfxpro.exe and the plugin will run...
then there you can put in your registrationcode and thats it !
Works perfectly for me !!!
Now i can run it in my Cubase5 !!!

Ps.: with savihost you can run all vst plugins in standalone mode !!! without starting your VST-Host programm

didnt see that you already answered... Yes it is a new Machine with an I7-920 Cpu and Cubase... fresh installed... when i tried to run it it freezed cubase5
and the plugin didnt open... i tried now a workaround with "Savihost" a small freewareplugin host where you can run plugins standalone...see my posting before !!!

Now my plugin runs fine in Cubase5 with windows XP Professional (with Service Pack 2)

And to answer you question , yes it is still 32Bit !

Hope that helps other users... I didnt want to lose my SFXMAchine Pro... now that i just bought it !!!! ;-d

Thanks for this cool software and cya TweakerRay

That's very interesting... So it sounds like the problem is in the registration window.

Glad you got it working. Thanks for sharing the workaround! That will make it a lot easier to find the problem.

Earl

It looks like the Audio Unit version of SFX Machine Pro crashes immediately as soon as you go to the Preset Editor - this seems to happen only with the latest version(s) of Mac OS X, and maybe only on 64-bit machine. We're looking into the problem.

I don't check this forum very often, so feel free to e-mail us at support@sfxmachine.com.

We've just released SFX Machine Pro (for Mac) version 1.1.3, which fixes this problem. (The VST is the same as 1.1.2.)

If you previously installed SFX Machine Pro 1.1.3 for Mac on top of an existing 1.1.2 version, you will probably find that the installer did not actually overwrite the old version. Get Info will still show 1.1.2, because we (I) failed to update the version string, and Apple's installer did not actually overwrite the file, since it seemed to be the same version.

I've posted an SFX Machine Pro 1.1.3a installer to fix this problem. Sorry for the trouble.

If you're using our 32-bit VST plug-ins with a 64-bit host program, you could try jBridge (Windows), http://jstuff.wordpress.com/jbridge/ , or jBridgeM (Mac), http://jstuff.wordpress.com/jbridgem/ . They're inexpensive and I'm told they work well.