2.5.4.132 Crashing Ableton Live
-
- KVRist
- 178 posts since 16 Nov, 2006
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.
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.
Mac Pro Quad 2.66 GHz. 9GB RAM
Snow Leopard 10.6.8/Pro Tools 8.0.5/Digi 002R
Live 9.1
Predator, Subboombass
Snow Leopard 10.6.8/Pro Tools 8.0.5/Digi 002R
Live 9.1
Predator, Subboombass
-
- KVRist
- 43 posts since 3 Jan, 2011
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
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
-
Janusz Grzybek Janusz Grzybek https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=255382
- KVRist
- 106 posts since 25 Apr, 2011 from Poland
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
Best,
Janusz
Computer: rack PC, Windows 10 64bit, Intel i7 2700K, 16 GB RAM, 250 GB & 500 GB SSD disks, HDD 1 TB 7200 RPM
DAW: Studio One 3 Pro, FL Studio Producer 20, Bitwig 2
Hardware: Yamaha 01X + 2 x Yamaha i88X, Nektar Panorama P4, Behringer BCR2000,
DAW: Studio One 3 Pro, FL Studio Producer 20, Bitwig 2
Hardware: Yamaha 01X + 2 x Yamaha i88X, Nektar Panorama P4, Behringer BCR2000,
-
Janusz Grzybek Janusz Grzybek https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=255382
- KVRist
- 106 posts since 25 Apr, 2011 from Poland
Oops, sorry for duplicate of this info... but I didn't noticed it before my post.NeP94 wrote:Also : please check v2.5.4.133 since it fixes a big cpu problem, maybe that's related to your problem
Janusz
Computer: rack PC, Windows 10 64bit, Intel i7 2700K, 16 GB RAM, 250 GB & 500 GB SSD disks, HDD 1 TB 7200 RPM
DAW: Studio One 3 Pro, FL Studio Producer 20, Bitwig 2
Hardware: Yamaha 01X + 2 x Yamaha i88X, Nektar Panorama P4, Behringer BCR2000,
DAW: Studio One 3 Pro, FL Studio Producer 20, Bitwig 2
Hardware: Yamaha 01X + 2 x Yamaha i88X, Nektar Panorama P4, Behringer BCR2000,
-
- KVRAF
- 7506 posts since 14 Nov, 2006 from Ankara, Turkey
Hi there!Gothboy wrote: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 will debug it on OSX tonight. BTW, RTAS is on the way
Works at KV331 Audio
SynthMaster voted #1 in MusicRadar's "Best Synth of 2019" poll
SynthMaster One voted #4 in MusicRadar's "Best Synth of 2019" poll
SynthMaster voted #1 in MusicRadar's "Best Synth of 2019" poll
SynthMaster One voted #4 in MusicRadar's "Best Synth of 2019" poll
-
- KVRist
- Topic Starter
- 178 posts since 16 Nov, 2006
[quote="kv331
I will debug it on OSX tonight. BTW, RTAS is on the way
[/quote]
WOOT!
I will debug it on OSX tonight. BTW, RTAS is on the way
WOOT!
Mac Pro Quad 2.66 GHz. 9GB RAM
Snow Leopard 10.6.8/Pro Tools 8.0.5/Digi 002R
Live 9.1
Predator, Subboombass
Snow Leopard 10.6.8/Pro Tools 8.0.5/Digi 002R
Live 9.1
Predator, Subboombass
-
thecontrolcentre thecontrolcentre https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=76240
- KVRAF
- 37262 posts since 27 Jul, 2005 from Scottish Borders
- KVRian
- 1112 posts since 26 Jun, 2008 from Czech Republic
No crashing on Win7 and Lve 8.1.3 either.
-
- KVRist
- Topic Starter
- 178 posts since 16 Nov, 2006
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?
Bulent?
Mac Pro Quad 2.66 GHz. 9GB RAM
Snow Leopard 10.6.8/Pro Tools 8.0.5/Digi 002R
Live 9.1
Predator, Subboombass
Snow Leopard 10.6.8/Pro Tools 8.0.5/Digi 002R
Live 9.1
Predator, Subboombass
-
- KVRAF
- 6374 posts since 8 Jun, 2009
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?
-
- KVRAF
- 7506 posts since 14 Nov, 2006 from Ankara, Turkey
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!
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!
Works at KV331 Audio
SynthMaster voted #1 in MusicRadar's "Best Synth of 2019" poll
SynthMaster One voted #4 in MusicRadar's "Best Synth of 2019" poll
SynthMaster voted #1 in MusicRadar's "Best Synth of 2019" poll
SynthMaster One voted #4 in MusicRadar's "Best Synth of 2019" poll
-
- KVRAF
- 6374 posts since 8 Jun, 2009
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.
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 Thu May 03, 2012 7:09 am, edited 1 time in total.
-
- KVRAF
- 7506 posts since 14 Nov, 2006 from Ankara, Turkey
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?
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?
Works at KV331 Audio
SynthMaster voted #1 in MusicRadar's "Best Synth of 2019" poll
SynthMaster One voted #4 in MusicRadar's "Best Synth of 2019" poll
SynthMaster voted #1 in MusicRadar's "Best Synth of 2019" poll
SynthMaster One voted #4 in MusicRadar's "Best Synth of 2019" poll
-
- KVRAF
- 6374 posts since 8 Jun, 2009
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.
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.
-
- KVRist
- Topic Starter
- 178 posts since 16 Nov, 2006
Live is at 8.3 right now....nowhere near 9 yet.Gamma-UT wrote: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 9.1.7.
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.
Mac Pro Quad 2.66 GHz. 9GB RAM
Snow Leopard 10.6.8/Pro Tools 8.0.5/Digi 002R
Live 9.1
Predator, Subboombass
Snow Leopard 10.6.8/Pro Tools 8.0.5/Digi 002R
Live 9.1
Predator, Subboombass
