Some has gone very wrong with Bounce to tracks

Please install X3D,
....and do it in a brand new project.
 
If no dice, please give us the specifics please. We need to know your system (please update your footer like mine), and give us full steps to reproduce please (you are not giving us any real info to go, there are a thousand scenarios you could be explaining).... Thanks..

>if there's a background process accessing the disk
 
Couple of utils as well:
 
http://technet.microsoft.com/en-gb/sysinternals/bb896645.aspx


http://technet.microsoft.com/en-gb/sysinternals/bb896653.aspx
 
 

luv it when someone "seems" to be posting a problem, gives no data surrounding the variables,uses hyperbolic language, then disappears for a long time after several suggestions/comments have been made... If ya got an issue, always tic "get instant notification" in the subscribe to thread thingy...seems the polite way to respect others time....

Disappears for a long time?  I just posted this last night. Since nothing else in my system has changed, only switching from X2 to X3, and X2 performs the bounce perfectly a few seconds.  I didn't think that giving complete system information was really necessary.  I guess I was wrong.  I apologize.
 
Sonar X3 latest patch, Windows 7 64 bit, Maudio Fast Track Ultra.
 
It is a single Kontakt 5 track I am trying to render.  24 bit 44.1.  I tried it again last night.  When I woke up this morning it was about 90% done.

I am using Kontakt 4 and X3a, b, c and now d and my bounces only take seconds.
 
Have you tried a new project with a single Kontakt 5 track and does it also take a long time? Also are there another programs running in the background such anti-virus/malware programs?

> Just Ad Aware
 
Are you sure you aren't running any other antivirus software? Never install 2 at the same.
 
I would consider another antivirus product other than ad-aware, I don't want to start a large conversation on what antivirus to use (this thread will explode), so let me just point you to this thread:
http://forum.cakewalk.com/Microsoft-Securtiy-Essentials-m2947912.aspx
 
Anyways enough to go on for the moment, just the beginning I suspect...
Please can you go through this thread from the beginning and keep us updated to what you have done, plenty of points here to take heed. Thanks..

I just bounce a Dim Pro track, (a Pad) about 1:54 in length and it took about 10 seconds, including drawing the waveform on the bounced track

Hi Marc2109
 
I would check a few things coming from X2. Seems that the configuration file has not read your audio device correctly. At least the basic settings. Usually the new install will read the audio settings and use them since X2 is assumed to be working.
 
If X2 is still installed and running on your computer go and check the following areas that I have noted below and write them down so you can use them as a comparison reference between X2 & X3.
 
Go to preferences and pay attention to the following areas.
#1 : File>Audio Data

• >Bit Depth
• >Render Bit Depth

#2 : Audio>Driver Settings

• Audio Bit depth
• Sampling Rate

All the bit depths have to be correct before any of the rendering and bouncing can operate correctly. I have also removed most of the options in the bounce to drop down list because I only use three mix down procedures.
 
I don't know if this will do the trick for you but it can't hurt to check these settings. I use these a lot and they are one of the best time savers that digital audio has to offer.
 
Good luck Marc!
 

Some things to try:
-export to a different hard drive
-make sure realtime bounce isn't checked
-look at the performance tab in task manager and see if you are running low on memory during the bounce
-bouncing another project and see if it exhibits the same problem
-uncheck the option to include fx in the bounce and see if it speeds up. if so some plugin may be causing the issue
-check if the project contains audio snap.
-reset your audio configuration (preferences | configuration | reset configuration )

Thanks for all the suggestions...I'm working through them.  Here are the results from tonight's tests:
 
I installed X3D, then created a 2 minutes Kontakt 5 Midi file in a new project.  It rendered in about 15 seconds.  I went back to the project i was working on with the 14 hour render, and picked a shorter midi track and started rendering it.  After 10 minutes it was about 5% done.  I made no audio settings changes from the new project to the old one.
 
I reset the audio configuration and tried again with the same results.
 
I tried a different project and a midi file about the same length as the troubled project track and it rendered in less that 30 seconds.
 
Help me think this through...if audio settings or the aud.ini file are the culprit, wouldn't i  have the slow render problem with both projects not just the old one?  I will still go back and make a careful comparison and delete the aud.ini.  
 
So far it looks like the problem is in the project itself.  Two different softsynth tracks with the same extremely slow render.  I still have over 80GB hd space on the drive.  The memory looks like its only taking about 25%.  If its an issue with this particular project, then I am in for an immense amount of work to fix it, since it contains over 30 softsynth tracks.
 
So trying to think ahead if this project can't be rendered to audio,  is there an easier way that writing down all the synths and patches used and copying the midi tracks into a new project and re-inserting all of the softsynths?  I bet I would still loose all my automation.

Do you have 64 bit audio engine enabled?  I have a couple of plug-ins which suffer from this when bouncing down with 64 bit audio engine on.

Marc2109
Actually I have no audio plugins in the project at this time.  However, I turned off the 64 bit audio engine and that seems to have fixed it.  Strange though  because I use that in X2 with no issue, and also other X3 projects.  OH well, at least its solved!!
 
Thanks everyone for your help!

Can we put [Solved] in the title?

Agree with resaving the project. Oft times the simple fact of physically changing the space on the HDD where the project is saved can make a world of difference.