Crashes with plug-ins

  • Thread starter Thread starter Arranger
  • Start date Start date
A

Arranger

New member
Got the free download of n-Track. Got the free downloads of the ParEQ and Comp/Limiter. Every time I run the downloaded n-Track plug-ins it locks up and forces a shut down of n-Track.

Anyone else have this problem? Should I expect that purchasing n-Track and the seperate plug-ins will solve the issue?

Thanks!
 
I know with my old machine, there simply wasnt enough RAM or processor speed to run any effects...every time I tried, it would crash.

I don't know well enough if it is RAM or processor speed specifically that relates to plug-ins...but in either case a half decent machine is required I think.

So far on my new machine, n-track hasn't crashed yet. And I have really loaded up on tracks and effects (I haven't been using the n-track effects lately, but I did when I first put this machine together).

Now if I could only utilize these effects to make my music sound better, not worse! :D (ie I can't even figure out how to compress the shit out of everything :confused: )
 
I'm also experiencing this problem. I have an old 350 MHz pentium 2 with 128 or ram. I suspect -and hope-that the amount of ram is the problem. I really don't want to lay down the bucks for a new computer at the moment.
 
The old machine I was running was a Compaq, with 192 mb SDRam, and was rated at 533 Mhz. Pretty sure it was a PII. I could run some plugins, but say running three was pushing it. (three tracks, three plugins). Something like that. Having said this I also had a lot of other crap running on my machine, so it wasn't exactly optimized for audio. I could have pushed it a little further, but not a helluva lot.

My new computer has 512 mb DDRRAM, and is rated somewhere around 1.3Ghz. One of my crazy projects has about 20 tracks, half of them running effects. There is still a fair amount of room for more things. Plugins are most definately memory intensive, however.

One thing to do would be to record a track, add the neccesary plugins, then mix it down, and start over with that file. It'll then be viewed simply as a wave file, without plugins, therefor reducing memory load. Its a bitch, but about the only way around it that I know.

I know you said you cant afford a new machine, but in light of my new monster, its one of the best investments I have made. It really gives me the freedom to not worry about how much memory I have (to a certain degree), and lets me mess around with plugins while running n-track, without jumping and skipping and crashing.

Ok enough rambling :D.
 
Yeah, I hear you loud and clear on this one badassmak. I will have to splurge on a new computer later in the year. Until then I will push this one to the limit and learn to get the most out of these machines.
 
Old computer: P2 366mhz, 128 mb SDRAM and ntrack= crashes galore.

New computer: Celeron 1.7ghz, 256 DDRRAM and ntrack= works like a charm. With 4 tracks and 4 effects going doesn't even get to 30% cpu usage.

By the way, some of you might not like Dells, but I purchased my new computer at the Dell outlet site for $499 w/17" flat screen monitor and full warranty.
 
You guys with your old machines wouldn't happen to be running Windows 98, would you?
 
Yes Slackmaster, I'm running '98. Is there something about '98 that would cause problems with plugins. I am also having issues whenever I open songs that I've already worked on. The software will tell me that I have to locate files manually. I have no idea why that happens. Any information would be really helpful. Thanks for doing an excellent job on this forum.
 
You must log in or register to reply here.
Back
Top