Bulent,
Just downloaded the recent update 2.5.4.132 and it's crashing Ableton Live 8.2.7 REAL HARD>as in I had to use the power button on my Mac for a restart. All I did was try to play a few patches using the <> buttons. Can't use it because it crashes every time.

I really like synthmaster but I have to admit that it's pretty unstable under Ableton Live on MacOSX.
I had some crashes but the worst thing for me is the menu problem (Click on the third/fourth/etc.. item in any menu and you'll get the second item, you have to do it again each time..)

I saw that it was a bug in other DAWs before, but it seems that the trick used to fix is not the best (I'm a developer myself, I know sometimes the fixes can be tricky ;-p ) since it still occur in live (and still from a developer point of view : possible side effects in others daws if this is related to a memory leak and/or UI bad programming architecture)...

What's annoying me is that i have the sensation that kv331 is still focusing on new functionnalities. I think it's time for tracking bugfixes, SM is already so deep!

So i add +1000 to your post, even if I have not such a big problem. Please focus on bugfixes!!! SM on MacOSX/Ableton Live is a pretty good starting point to easily find bugs

Also : please check v2.5.4.133 since it fixes a big cpu problem, maybe that's related to your problem

Bulent already released build 133, because 132 had dangerous bug in oscillators. Please, try install build 133 and check behavior of this recent build with Live.

Best,
Janusz

Oops, sorry for duplicate of this info... but I didn't noticed it before my post.

Janusz

Hi there!

I will debug it on OSX tonight. BTW, RTAS is on the way

[quote="kv331
I will debug it on OSX tonight. BTW, RTAS is on the way [/quote]

WOOT!

Might be worth upgrading to Live 8.2.8 also ... works fine here on XP.

No crashing on Win7 and Lve 8.1.3 either.

Still crashing Live. I updated to Live 8.2.8 and then the new version of SM....still crashing it hard on a Midi track with the rec button on after htting the right preset > navigation button and then hitting a note. Ouch it crashed about 5 times before I just gave up. It may be working for you windows users but not on Snow Leopard Mac 10.6.8.

Bulent?

I'm getting the same kind of crashes in Live 8.3 on OS X 10.6.8. The version in the latest downloads comes up in the VST file info and info.plist in the AU package as 2.5.4.132, which supposedly is an old version - is the right version on the website?

we have the latest version on the web site. the version number on the plist file might be older.

If you can describe me the "flow/scenario" in detail please, I really would love to get rid of such issues. Also, a crash dump would help a LOT!

There's not much to describe: the plug-in crashes more or less instantly - on validation in Logic 9.1.7 and when instantiated on a track in Live 8.3. It takes the host down with it (it will also crash Live when it performs a VST scan).

From a clean install, it will attempt to do the initial waveform setup but I don't know if it ever completes because it will crash immediately afterwards. Looking at the crash log, which I will send over to you, it fails at the same point in both Logic 9.1.7 and Live 8.3.
Last edited by Gamma-UT on Wed May 02, 2012 11:09 pm; edited 1 time in total

This looks like a "permissions" issue!

Do you have write access for the synthmaster folders, particularly:

/Library/application support/kv331 audio/synthmaster/resources/

and all subfolders?

Try deleting

/Library/application support/kv331 audio/synthmaster/config/synthmasterconfig.txt

and try again?

After running OpenSnoop and noticing that it was trying to access an XML file that didn't exist, I reinstalled from clean and, this time, ran chown and chmod to ensure Live had write privileges (going for 777 for everything under App Support/KV331 just to be sure - I'll go change them back in a minute). This time, it was able to build the files and then launch.

The problem is that the installer is if the user does not have a user ID of 501 (my main account happens to have an ID of 504 for some reason - possibly because I've deleted some old accounts on a previous machine and then used Migration Assistant to get onto this one), the initial setup fails. This is presumably due to a bug in PackageMaker which is forcing the wrong ID on installation. The upshot is that, if it crashes the first time because it doesn't have write access to a folder set to 755 with the wrong user ID, the factory waveform XML file doesn't get created. Deleting the config.txt file unfortunately doesn't seem to force SynthMaster to reset itself to build these files if the permissions change after the first crash - it just gets stuck in the same loop.

It's not ideal, but would setting at least the Config and and Resources folders to 775 ease this issue? It's not the first plug-in installer I've found that sets the wrong user ID. But I've noticed that a number of vendors simply set the Component and VST packages to 777.

Live is at 8.3 right now....nowhere near 9 yet.

I don't know any of the above greek but just where are we as far latest version of SM? Has it been tested in Live I was getting the same crashes.