I think that's the result of developers using the fastest hardware available (eg SSD drives) so performance issues on less bleeding edge hardware don't get noticed (and fixed) by them. Sad but true...djscorb wrote:It just seems ridiculous that any program should take so long to close after the project has already been saved
Using Terminal to start Ableton Live without bug reporting.
-
- KVRAF
- 16850 posts since 8 Mar, 2005 from Utrecht, Holland
We are the KVR collective. Resistance is futile. You will be assimilated. 
My MusicCalc is served over https!!
My MusicCalc is served over https!!
-
- KVRian
- Topic Starter
- 715 posts since 3 May, 2007 from UK
Yeah that makes sense I suppose. It feels strange that working in this way is the only option but what else can I do? it's either force quitting or losing hours of time a month pointlessly.
Cheers
Scorb
Cheers
Scorb
-
- KVRAF
- 6323 posts since 30 Dec, 2004 from London uk
I cant help with Live but it seems that you may be having sound card driver issues. Is it USB? Do you have power saving on USB enabled? that can cause trouble. Have your projects used a different sound card than you have now? It may be that Live is struggling with something to do with the sound, causing it to be slow to load or crash.
Thats the clue thereThis is the line of code in the log.txt that Live is hanging on when waiting to close. It's the same for both my desktop and Macbook so I can rule out bad memory and hardware I think.
761073 ms. Audio time allocations: EventBuffering: Capacity/Used/Failures: 26214/54/0
-
- KVRian
- Topic Starter
- 715 posts since 3 May, 2007 from UK
Hi there
Thanks for the response
I am using an Apogee One via USB and all the projects I am currently working on were started with this interface.
What I might try to do is disable the audio engine or unplug the interface before closing and see if that makes things faster.
Cheers, I didn't think of trying this and will report back my findings.
Scorb
Thanks for the response
I am using an Apogee One via USB and all the projects I am currently working on were started with this interface.
What I might try to do is disable the audio engine or unplug the interface before closing and see if that makes things faster.
Cheers, I didn't think of trying this and will report back my findings.
Scorb
-
- KVRian
- Topic Starter
- 715 posts since 3 May, 2007 from UK
Hmm
Unfortunately turning off the audio engine and/or unplugging the interface hasn't sped up the slow closing. I can only assume the apparent hanging is Live deallocating the resources used by the set.
Why it should take longer than when loading the set is still rather bewildering.
I noticed when looking at the log the other day that there are several lines of code similar to above and it either stops at the one I mentioned or another relating to midi events. It did the same on my macbook whether using the Apogee or the internal soundcard so must be considered "normal". The word "Failure" in the line of code did worry me at first but seeing as it showed on my other macs with different sets and interfaces too I guess it's not the problem.
Oh well, back to the drawing board.
Cheers again
Scorb
p.s. what would be useful is if anyone can actually confirm that Live is closing sets more slowly than it is opening them on their setups. Anyone prepared to do a quick test? Just time how long a reasonably intensive set takes to open and then again, how long it takes to close before you can either quit Live or close / create a new blank set. Thanks in advance!
Unfortunately turning off the audio engine and/or unplugging the interface hasn't sped up the slow closing. I can only assume the apparent hanging is Live deallocating the resources used by the set.
Why it should take longer than when loading the set is still rather bewildering.
I noticed when looking at the log the other day that there are several lines of code similar to above and it either stops at the one I mentioned or another relating to midi events. It did the same on my macbook whether using the Apogee or the internal soundcard so must be considered "normal". The word "Failure" in the line of code did worry me at first but seeing as it showed on my other macs with different sets and interfaces too I guess it's not the problem.
Oh well, back to the drawing board.
Cheers again
Scorb
p.s. what would be useful is if anyone can actually confirm that Live is closing sets more slowly than it is opening them on their setups. Anyone prepared to do a quick test? Just time how long a reasonably intensive set takes to open and then again, how long it takes to close before you can either quit Live or close / create a new blank set. Thanks in advance!
-
- KVRian
- Topic Starter
- 715 posts since 3 May, 2007 from UK
Hi
This section of the forum is not very well attended compared to efffects, instuments and hosts etc, so I might post the question as to whether Ableton takes longer to close sets than to open in the Hosts forum and see if I can get any more feedback about the issue.
This thread was more about terminal scripts for bypassing bug reporting and really the problem of Live's slow closing is not related to bug reports!
Cheers
Scorb
This section of the forum is not very well attended compared to efffects, instuments and hosts etc, so I might post the question as to whether Ableton takes longer to close sets than to open in the Hosts forum and see if I can get any more feedback about the issue.
This thread was more about terminal scripts for bypassing bug reporting and really the problem of Live's slow closing is not related to bug reports!
Cheers
Scorb
I once thought I had mono for an entire year. It turned out I was just really bored...