I just left a set open for a few hours and came back and now when I try to save it says "not enough memory available, please save now and quit" but it won't let me save in any way
EDIT: just happened again when recording from looper routed to a slot on another audio track - after I've recorded a clip of a few minutes I couldn't save it
[amo] 8b16: not enough memory available
Re: 8b16: not enough memory available
I just got this in a new set - dragged in a few plug-ins and tried to move looper to a new position
first it happened in a set it had happened in yesterday (another looper set) then I clicked file>new and started dragging in plug-ins
I did a bug reporting snap shot but it was 54MB
first it happened in a set it had happened in yesterday (another looper set) then I clicked file>new and started dragging in plug-ins
I did a bug reporting snap shot but it was 54MB
Re: [amo] 8b16: not enough memory available
Hi,
As the Looper writes its buffer into the memory, it could be possible you had a too long recording? I believe there is a limit but, how much memory do you have available?
Regards,
Amaury
As the Looper writes its buffer into the memory, it could be possible you had a too long recording? I believe there is a limit but, how much memory do you have available?
Regards,
Amaury
Ableton Product Team
Re: [amo] 8b16: not enough memory available
hiAmaury wrote:Hi,
As the Looper writes its buffer into the memory, it could be possible you had a too long recording? I believe there is a limit but, how much memory do you have available?
Regards,
Amaury
but in the second example I started a new set and got the error straight away
Re: [amo] 8b16: not enough memory available
Hi,
If you get that again, could you make a bug reporting snapshot and send it to [email protected] ?
Regards,
Amaury
If you get that again, could you make a bug reporting snapshot and send it to [email protected] ?
Regards,
Amaury
Ableton Product Team
Re: [amo] 8b16: not enough memory available
Well, this could well be related to the cleanup of memory used from a previous set
which is not really working properly
see http://forum.ableton.com/viewtopic.php?f=25&t=109399
Which explains that forge had the crash immediately on a new second set.
This is a serious issue and needs to be looked after. You can't expect users to exit live every time they close a set.
which is not really working properly
see http://forum.ableton.com/viewtopic.php?f=25&t=109399
Which explains that forge had the crash immediately on a new second set.
This is a serious issue and needs to be looked after. You can't expect users to exit live every time they close a set.