Crashes (popular topic)

[Eric-Jensen]

I really like n-track, but after a month of using it, I've decided that crashes are just part of the package. If any window, any time, is closed with the 'X' button when there is an alternative way to do it within the window, down it goes. If I interrupt it in the midst of something, like playback, without first stopping it, down it goes. My favorite-if I'm working with a volume or pan envelope, accidentally get track properties, and close that window with 'X', crash! I'm guessing this is the drill for all users. CPU usage is fine-a P3 833 laptop, XP Pro, 256M rarely goes over 30% or so.

Am I a newbie missing something, or is using this program just a matter of programming myself to do it the way n-track wants to do it (and saving every step of the way)?

 

[caryindy]

Eric,

Sorry to hear about your crashes. When I first started using N-track, there was a time where I needed to save after every task because the program was crashing. With the latest builds available, the program is very stable.

I tried to recreate your crash situation and was not able to do it.

Couple of questions for you:
1. Which build of N-track are you using?
2. Which plug-ins are you running when your crashes happen?

 

[ataranto]

One thing you might try

I have XP Pro on my home box, which I use for programming (a field in which I'm also a newbie). I have quite a bit of stuff installed on it, some of which I'm certain has caused stability problems with other programs.

Go to Start -> Run -> msconfig, disable as many of the startup items as you feel comfortable disabling, and do the same for services. This process fixed an instability problem with a game of which I'm very fond; it also can free up a lot of RAM: SQL Server, IIS, etc. processes can be pretty resource-intensive. It's sort of like Safe Mode+. Close msconfig and restart; rerun msconfig and select "Normal Startup" when you want all isntalled services/startup items.

I haven't used a multitrack program on this machine yet; so while I can't comment on this specifically, I think the general principle may apply.

 

[Myx62]

Eric, Im not really sold on the windows XP. I use win 98SE with 1.1 gig celeron, 256 ram and my system is very stable.(I use n-track 3.0) I've had a few plugins that caused crash's and deleted them. The key is to start with a stable setup and when comp crash's check the plugins your using. Ive had problems with only a few DX and VST plugins. I just deleted them. No problems after that. Hope this helps.
Myx

 

[morindae]

Originally posted by Myx62

I've had a few plugins that caused crash's and deleted them. The key is to start with a stable setup and when comp crash's check the plugins your using. Ive had problems with only a few DX and VST plugins. I just deleted them. No problems after that. Hope this helps.

Eric, I think that Myx62 is correct. I use n-track with windows 98 and as soon as I got rid of my blueline plugins, I stopped having crashes. In fact, my system is very stable at the moment, which is a suprise, because n-track is supposed to run badly on '98.

 

[bdemenil]

I've been using ntrack for quite some time with xp - no problems here. I did have that problem you describe several versions ago - about a year to be exact.