Hello,
I recently decided to move all the plugins that were still running on my receptor to my PC running cantabile. As result, the size of my session increased, and for one of them, Cantabile is crashing most of the time at then end of the loading (when Cantabile is rendering the session basically).
It is a quite big session, with 3 instances of Eastwest Play, 1 Kontakt, 1 Ivory Grand Piano, Korg M1, Korg WS, IK SampleTron, IK SampleMoog, Omnisphere ... about 2.5 Gb.
My config is a i7 920, with 12GB RAM, Raid SSD and a Saffire Pro 40 as audio interface. I ran a full memtest, disk test ... everything is looking perfectly ok.
At the moment, I'm using 1 rack per plugin ... is this a problem ? I tried to play with multiprocessor control, no effect
One thing really (but really) strange is the fact that adding global midi assignment seems to increase the problem ...
Does anyone has an idea ? I start to run out of idea about how to solve this problem.
NB: I generated a crash dump + log and sent it to Brad as well ... but as I understood he's pretty busy, perhaps someone would have a brillant idea
Strange crash with Cantabile Performer / win 7 64 bits
-
- KVRist
- 196 posts since 11 Sep, 2004 from Germany
Well, there is only one little idea from my side: you say you are using cantabile on a win7 64bit OS. Which version of cantabile are you using: 32 or 64bit? If it is the 32bit version the reason could most likely be the memory allocation problem as you use many plugs like omni and the like that can be true RAM-eaters.
If this could be the reason please let me know: I think we can find out how to solve this.
But as I said: only a little idea...
Kind regards, humphrey
If this could be the reason please let me know: I think we can find out how to solve this.
But as I said: only a little idea...
Kind regards, humphrey
hosts: c8.5, cantabile3.0, forte4.0, live 9, trakor
hardware: i7 4770k, i7 4702qm, all audio converters RME, KH120A
vsts / vstis: u-he, voxengo, fabfilter, izotope, lexicon, waves, spectrasonics, ni, steinberg, gsi, uvi, xfer & others
hardware: i7 4770k, i7 4702qm, all audio converters RME, KH120A
vsts / vstis: u-he, voxengo, fabfilter, izotope, lexicon, waves, spectrasonics, ni, steinberg, gsi, uvi, xfer & others
-
- KVRer
- Topic Starter
- 27 posts since 11 Jun, 2010
I'm using the 64 bit version ...humphrey wrote:Well, there is only one little idea from my side: you say you are using cantabile on a win7 64bit OS. Which version of cantabile are you using: 32 or 64bit? If it is the 32bit version the reason could most likely be the memory allocation problem as you use many plugs like omni and the like that can be true RAM-eaters.
If this could be the reason please let me know: I think we can find out how to solve this.
But as I said: only a little idea...
Kind regards, humphrey
BTW, I just did some test and when the session is loaded, in fact touching anything in Cantabile make it crashes ...
-
- KVRist
- 123 posts since 29 Jan, 2009 from Bridgeport, WV
I would rebuild the session plugin by plugin, rack by rack, saving/reloading with the addition of each new rack/plugin. This should narrow down the plugin that is causing the instability.
-
- KVRist
- 32 posts since 15 Nov, 2009
some other things to consider: are your plugins all 64 bit, or do you have some 32 bit plugins loaded with JBridge? there could be some instabilities created from that.
also, there are settings within Cantabile's audio engine you may want to look at such as Multi-Processor support setting (compatability mode, or agressive mode) which may or may not cause instabilities.
One of my main gripes i have with Cantabile is the inability to trace crashes. It's very much a trial and error approach. I sometimes have crashes that don't even spit out a crash log.
Also, i'm not so forgiving with the developer as many in this forum. To me Cantabile is basically unsupported, leaving all the guesswork to you and I. I don't care how busy someone is, bottom line everyone here has paid a fee for this software and we put our reputations on the line every time we get in front of an audience and play. We should all reasonbly expect some interaction from the developer, otherwise, stop charging money for Cantabile - unsupported shareware basically. Or sell the code base to another organization to continue.
sorry for the rant, i HATE Cantabile crashes....
also, there are settings within Cantabile's audio engine you may want to look at such as Multi-Processor support setting (compatability mode, or agressive mode) which may or may not cause instabilities.
One of my main gripes i have with Cantabile is the inability to trace crashes. It's very much a trial and error approach. I sometimes have crashes that don't even spit out a crash log.
Also, i'm not so forgiving with the developer as many in this forum. To me Cantabile is basically unsupported, leaving all the guesswork to you and I. I don't care how busy someone is, bottom line everyone here has paid a fee for this software and we put our reputations on the line every time we get in front of an audience and play. We should all reasonbly expect some interaction from the developer, otherwise, stop charging money for Cantabile - unsupported shareware basically. Or sell the code base to another organization to continue.
sorry for the rant, i HATE Cantabile crashes....
-
- KVRer
- Topic Starter
- 27 posts since 11 Jun, 2010
Hmm ... I tried this and rebuilding the session seams to have solve the issue ... the only thing I change is I group the Eastwest Play instances in one rack ...davinwv wrote:I would rebuild the session plugin by plugin, rack by rack, saving/reloading with the addition of each new rack/plugin. This should narrow down the plugin that is causing the instability.
I will try to continue testing it and keep you informed, but thank you for the good ideas !