Revision history for ErrorOhOhTwoNine
Additions:
Another possible fix for this error is to delete any virtual submixs and only keep card mixs. After trying BT's fix above "increased my disk cache size to 128MB and my overview to 21000KB" I still had the error but after deleting all virtual mixs, project plays perfect... go figure.
-- ManiTou (2009-06-30 20:37:33)
-- ManiTou (2009-06-30 20:37:33)
Additions:
**Postscript 11/17/08 - Edmund's take on this:**
Deletions:
Additions:
**Edmund's take on this:**
//Here's what Edmund thought was the problem, just for the record - "it sounds like you have a slightly corrupted playlist on one of the tracks. Try disabling playback one track at a time to isolate which one it is, then you can try changing the fades or some of the edits to narrow it down. If you send me the application debug messages I may be able to tell you more."//
//Here's what Edmund thought was the problem, just for the record - "it sounds like you have a slightly corrupted playlist on one of the tracks. Try disabling playback one track at a time to isolate which one it is, then you can try changing the fades or some of the edits to narrow it down. If you send me the application debug messages I may be able to tell you more."//
Deletions:
Additions:
every time I try to record. Does anyone know what this means? I did a search and found others who had
Try ''resetting the record path to a new empty folder''. Or if you are on the Mac and running anything before OS 9 you may have run
out of open files (MacOS limit). If this is the case try clearing unused files from the audio window.//
Try ''resetting the record path to a new empty folder''. Or if you are on the Mac and running anything before OS 9 you may have run
out of open files (MacOS limit). If this is the case try clearing unused files from the audio window.//
Deletions:
Does anyone know what this means? I did a search and found others who had
Try ''resetting the record path to a new empty folder''.
Or if you are on the Mac and running anything before OS 9 you may have run
out of open files (MacOS limit). If this is the case try clearing unused
files from the audio window.//
Additions:
[additional info via Edmund: if you encounter this on Mac OS 8.6 and earlier, upgrading to OS 9 gives you far more breathing space for max number of open files]
Deletions:
Additions:
[additional info: if you encounter this on Mac OS 8.6 and earlier, upgrading to OS 9 gives you far more breathing space for max number of open files]
Additions:
//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!
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!
Deletions:
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!
Revision [1140]
Edited on 2008-11-16 12:29:59 by admin [added multiple suggestions for error ...0029]Additions:
====Error ...0029 (ON PC)====
**Try:**
//Started to get error code: error in queing project. Error code 1879048233/70000029
every time I try to record.
Does anyone know what this means? I did a search and found others who had
the problem, but no answers as to why.
Try ''resetting the record path to a new empty folder''.
Or if you are on the Mac and running anything before OS 9 you may have run
out of open files (MacOS limit). If this is the case try clearing unused
files from the audio window.//
**Try:**
// Hey all, finally back, built a new computer, installed fios and finally got
around to setting up my news account again. Been a while. I keep getting
this error message after doing several cut and paste edits on a project. I
can reopen the project and play it from the middle, but if I attempt to que
it from the beginning the error message keeps popping up, forcing me to shut
down paris. HELP, this project is for Othello Molineaux's new cd.
_tptQueProject: Error in queing project Error Code 1879049233/70000029
That's a mouthfull! Thanks,
Rich//
//''Do a save as the moment it comes open to a new name. You're on 3.0, right?
Render those tracks before touching the play button. I'm betting you have
something funky in an edit on the play field somewhere. Pay attention to the
tasks/progress window, if it crashes again you'll want to know what it was
working on. Better yet, just render one track at a time. Also, don't let the
'dead space' below tracks 17/18 in the wave editors show, and if they do
then open/close that window.'' That's a known bug that BT discovered that
causes some wonkiness.
AA//
**Try:**
//from my notes of previous instances.....
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//
**Try:**
//Started to get error code: error in queing project. Error code 1879048233/70000029
every time I try to record.
Does anyone know what this means? I did a search and found others who had
the problem, but no answers as to why.
Try ''resetting the record path to a new empty folder''.
Or if you are on the Mac and running anything before OS 9 you may have run
out of open files (MacOS limit). If this is the case try clearing unused
files from the audio window.//
**Try:**
// Hey all, finally back, built a new computer, installed fios and finally got
around to setting up my news account again. Been a while. I keep getting
this error message after doing several cut and paste edits on a project. I
can reopen the project and play it from the middle, but if I attempt to que
it from the beginning the error message keeps popping up, forcing me to shut
down paris. HELP, this project is for Othello Molineaux's new cd.
_tptQueProject: Error in queing project Error Code 1879049233/70000029
That's a mouthfull! Thanks,
Rich//
//''Do a save as the moment it comes open to a new name. You're on 3.0, right?
Render those tracks before touching the play button. I'm betting you have
something funky in an edit on the play field somewhere. Pay attention to the
tasks/progress window, if it crashes again you'll want to know what it was
working on. Better yet, just render one track at a time. Also, don't let the
'dead space' below tracks 17/18 in the wave editors show, and if they do
then open/close that window.'' That's a known bug that BT discovered that
causes some wonkiness.
AA//
**Try:**
//from my notes of previous instances.....
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//
Deletions:
// > Started to get error code: error in queing project.
> Erroe code 1879048233/70000029 every time I try to record.
> Does anyone know what this means? I did a search and found others who
had the problem, but no answers as to why.
> Please help.
''Try resetting the record path to a new empty folder.''
Or ''if you are on the Mac and running anything before OS 9 you may have run
out of open files (MacOS limit). If this is the case try clearing unused
files from the audio window''.
------------------------
Edmund Pirali
Intelligent Devices, Inc.//
A word of clarification on Edmund's comment to Mac users who say "but - but - I have nowhere near the maximum number of files that Mac OS 8.6 permits open!" - oh, yes. You do. First of all, all audio files in your project are two files - an audio file and an .ovw (waveform overview) file, so double the amount of files in the audio bin to get a clearer picture. Additionally, in the course of normal operation, a Mac has up to a hundred files open simultaneously *before* you even boot an application. The Desktop is itself a file, for example. So you just might have more open than the Mac can handle. If you do complex projects, Mac OS9.x is strongly recommended.
