internal error ?

tanabarbier · Unread post by **tanabarbier** » 10 Oct 2011, 19:24

Hi,
not realy a patching question, but I get this "Error: Internal" message a lot when trying to save a patch, a track, a workspace, and when it happens then I can't save anything more.
For all the testing I've done it seems to be due to something that have to do with audio buses in my case, but how could I fix or do anything regarding that ?
I know it is very vague, but I really don't get anything !

Anybody getting the same problem ?

thanks in advance !

woodslanding · Unread post by **woodslanding** » 11 Oct 2011, 04:53

yep, all the time. I get it in a lot more situations than just saving.

I have not been able to pin it down either....

Floego · Unread post by **Floego** » 11 Oct 2011, 05:22

IMHO many of the messages are more like warnings rather than fatal errors, in my experience a lot of errors are related to the action of moving/copying one patch or module from one place to another in the grid, the buses being the more delicate things.

woodslanding · Unread post by **woodslanding** » 11 Oct 2011, 06:05

yes, but how do you know which is which? Which is the one that will make it impossible to save your work?

I always saveAs and restart whenever I see one, otherwise I get burned. I also independently saveAs any patches I've been working on.....

tanabarbier · Unread post by **tanabarbier** » 11 Oct 2011, 06:25

Yes I agree, it happens in all kind of situations, but I'm looking for the one that keep me from saving my work like you said.
I can save my main workspace only if I take the master track off, and then no pb, but otherwise imposible. And then I can put it back when opening and it works fine. A bit strange.

YouTube · Unread post by **senso** » 11 Oct 2011, 09:11

please report issues by mail!

jeanrene · Unread post by **jeanrene** » 21 Oct 2011, 16:09

sometimes I have a frozen screen with an frozen mouse, no keyboard (no taskmanager). the only solution I've found is to unplug the power so I do not crashlogs. this bloking come only when I work on large patches, and I connect modules badly, an (infinite) and exponential number of data are created. I think it's the ram or cpu overloading, maybe an ram hardware error.
not when I use usine my computer seems to work fine, it work fine also in usine when I connect my modules correctly.

cpu protect is set to 95%, nb threads 8, usine pro 5.50.521
windows 7 64, core2duo 6gb of ram

nay-seven · Unread post by **nay-seven** » 21 Oct 2011, 16:51

yes, certainly a memory overload

but please report issues by mail!

Welcome to %s forums

internal error ?

Who is online

Login • Register