Hi Forum!
 
Been quiet of late as I have had no issues to complain about with X3e (although I lurk everyday naturally) 
 
I have been working on two feature films and I have an issue with exporting.
 
Feature A has about 70 tracks of audio, tons of clips with fades, lots of synths and plugs and therefore a lot of scope for buggy 3rd party behaviour. When I export the timeline as a stereo file to send a pass of the film to the director it will throw up "An unknown error" and fails the export. To troubleshoot the error I have to playback the entire film and find out where the audio engine stops in the timeline and fix the error (Usually by joining a couple of clips together or bouncing that tiny part of the timeline)
 
Its a very time consuming troubleshooting method. Wouldnt it be better if Sonar gave information as to where the export fails on the timeline? i.e "An unknown error has occurred at 01:02:34:23" or something similar? Is there a better way of finding out where this error is? When this happens in a music track I have written troubleshooting isnt as bad as the track is only 5 mins, but when you are working on a film its quite a task.
 
 

There's definitely room for better error reporting (trapping likely points where the error kicks off), not only would we thank them but I suspect Cakewalk's technical support dept would as well.
 
There is of course limitation that makes certain details impossible to log (third party plugins for instance should provide their own details if it is coded), but the application really should give a better idea rather than "unknown".
 
Often detailed error logging can reduce performance, but that could be switched on/off in preferences.

I agree - I suggest you file a feature request for that, as it seems like Sonar would know where it was when it failed.
 
If might even have information on which piece of the process failed, as well, and that would be hugely beneficial to the debugging process.
 
Bob Bone
 

Dayum!
 
"Coming SoonAt this time we are not accepting any new feature requests while we work on an improved feature request system and get caught up with our current set of feature requests."

markyzno
Dayum!
 
"Coming Soon
At this time we are not accepting any new feature requests while we work on an improved feature request system and get caught up with our current set of feature requests."

Been like that for ages.. I'm sure they are working on it, but rest assured I'm pretty sure I already threw in this exact feature request a while back.

CakeAlexS

markyzno
Dayum!
 
"Coming Soon
At this time we are not accepting any new feature requests while we work on an improved feature request system and get caught up with our current set of feature requests."

Been like that for ages.. I'm sure they are working on it, but rest assured I'm pretty sure I already threw in this exact feature request a while back.

Great Stuff Alex