|
|
Re: Anyone know a fix for this error msg? [message #80822 is a reply to message #80820] |
Wed, 28 February 2007 16:34 |
John [1]
Messages: 2229 Registered: September 2005
|
Senior Member |
|
|
I have two entries:
I've dealt with this issue quite a bit.
I've even caused it on purpose to try to figure out how to fix
it.
(recording with looping on (with no punch points) will cause it)
Anyway, in ALL cases that I've seen, the error seems to be caused
by a corrupted segment on the playing field.. actually, I believe
it is caused by a corrupted crossfade, to be specific.
Whenever, I get this error, I remove the last take/edit from the
playing
field
(between the dialogs popping up), save, quite and restart paris.
At this point, the problem seems to go away.
Good luck!
Try increasing your disk cache and overview sizes in the Config menu. On
the problem project, clear the Undo buffer and delete the Markers.
I never have that problem anymore (like once every 6 months now) since I
increased my disk cache size to 128MB and my overview to 21000KB.
BT
Pablo wrote:
> My paris system has gotten into the habit of crashing
> very often, and the message I get is:
>
> _tptQueProject:Error in queing Project Error code 1879048233/70000029
>
> It automatically closes after this and I lose whatever I haven't
> saved (obviously). Today, while in the mixing stage of the recording,
> one of the songs did it as soon as I opened it. It used to do it while
> a song was playing or recording but this time it did it as soon
> as I opened it. I would click "ok" and it would keep coming up over and
> over so I would end task and restart only to get the same result.
> Eventually I just let it sit for a couple of minutes and it stopped
> doing it. Any idea what could have caused this? Or what causes
> all the other crashes I've had similiar to this one?
>
> I used to have this problem when I tried to use the wave editor
> so I stopped using that function. But I haven't gone near the
> wave editor since.
|
|
|
Re: Anyone know a fix for this error msg? [message #80826 is a reply to message #80822] |
Wed, 28 February 2007 15:49 |
Carl Amburn
Messages: 214 Registered: July 2005
|
Senior Member |
|
|
Thanks David and John. I upped my cache to 128, and my overview to 21000,
cleared my undo, and voilą. Really appreciate it.
still love this place, rock on,
-Carl
"john" <no@no.com> wrote in message news:45e61196$1@linux...
>
> I have two entries:
>
> I've dealt with this issue quite a bit.
>
> I've even caused it on purpose to try to figure out how to fix
> it.
> (recording with looping on (with no punch points) will cause
it)
>
> Anyway, in ALL cases that I've seen, the error seems to be
caused
> by a corrupted segment on the playing field.. actually, I
believe
> it is caused by a corrupted crossfade, to be specific.
>
> Whenever, I get this error, I remove the last take/edit from
the
> playing
> field
> (between the dialogs popping up), save, quite and restart
paris.
>
> At this point, the problem seems to go away.
>
> Good luck!
>
>
>
>
>
>
>
> Try increasing your disk cache and overview sizes in the Config menu. On
> the problem project, clear the Undo buffer and delete the Markers.
>
> I never have that problem anymore (like once every 6 months now) since I
> increased my disk cache size to 128MB and my overview to 21000KB.
>
> BT
>
> Pablo wrote:
> > My paris system has gotten into the habit of crashing
> > very often, and the message I get is:
> >
> > _tptQueProject:Error in queing Project Error code 1879048233/70000029
> >
> > It automatically closes after this and I lose whatever I haven't
> > saved (obviously). Today, while in the mixing stage of the recording,
> > one of the songs did it as soon as I opened it. It used to do it while
> > a song was playing or recording but this time it did it as soon
> > as I opened it. I would click "ok" and it would keep coming up over and
> > over so I would end task and restart only to get the same result.
> > Eventually I just let it sit for a couple of minutes and it stopped
> > doing it. Any idea what could have caused this? Or what causes
> > all the other crashes I've had similiar to this one?
> >
> > I used to have this problem when I tried to use the wave editor
> > so I stopped using that function. But I haven't gone near the
> > wave editor since.
>
|
|
|