Page 1 of 1
Posted: 10 Oct 2011, 19:24
by tanabarbier
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 !
Posted: 11 Oct 2011, 04:53
by woodslanding
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....
Posted: 11 Oct 2011, 05:22
by Floego
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.
Posted: 11 Oct 2011, 06:05
by woodslanding
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.....
Posted: 11 Oct 2011, 06:25
by tanabarbier
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.
Posted: 11 Oct 2011, 09:11
by senso
please report issues by mail!
Posted: 21 Oct 2011, 16:09
by jeanrene
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
Posted: 21 Oct 2011, 16:51
by nay-seven
yes, certainly a memory overload
but please report issues by mail!