How strong is your PC from Sonar 3?

[jerberson12]

How many tracks, online/realtime effects and DXi can you use from your Sonar 3 before you hit dropout?

Mine.............

P4 2.8Ghz HT
768 Mb Ram
Sonar 3.3.1

Tracks: 10 to 12
Online Effects: 2 effects each track
DXi: 2 DXi (VSampler and Battery)
Song Length: 4:12

More than that, PC surrenders.

 

[Qwerty]

How many angels dance on the head of a pin?

All plugins use resources differently, so it is impossible to compare.

I am a P4 3.0GHz with 1Gig of PC-3200 RAM. I got bored of importing tracks around 200 - it just works.

So said, if I use iZotope's Trash on a guitar track, then I will only get eight instances running before it dies. It all depends on your plugin load.

Q.

 

[moskus]

Athlon 1900+ (1.6 GHz), 1 gig RAM. 160 GB harddrive, Inca88 soundcard.

Audiotracks: 23
MIDI-tracks: 10
Softsynths: 1 (DR-008 running Drumkit from Hell) / 3 disabled and bounced (Edirol Orchestral, LiveSynth Pro, Native Instruments B4)
Plugins: Track EQs and compressors around half of the audiotracks.
Latency: 128 samples = 2.9 sec

... but that's pushing it.

 

[James Argo]

How many angels dance on the head of a pin?

All plugins use resources differently, so it is impossible to compare.

I am a P4 3.0GHz with 1Gig of PC-3200 RAM. I got bored of importing tracks around 200 - it just works.

So said, if I use iZotope's Trash on a guitar track, then I will only get eight instances running before it dies. It all depends on your plugin load.

Q.

Word!
And don't forget soundcard, driver, latency setting, buffer, etc etc...

Asus P4P800, P4 2,8GHz (1Mb), 1Gig PC3200, 2x80Gb, Delta1010LT, 24/48, latency 512, buffer 64.

24 MIDI, 18 Audio, DXi & DirX plugins here and there... What drop out?


Jaymz

 

[Qwerty]

OK -

When I go totally anal retentive and decide that I want to record a "perfect" take which will require absolutely no editting, it does slow down once I get to about 300 takes.

That means that after I hit stop on recording the last take of some loop recording, say 30 to 45 seconds and ten or so takes at it, instead of returning control immediately, I have to wait for about 20 seconds for the interface to display and be operable.

I can also get the same slow down when I have editted a couple of parts and there are MMMMAAAANNNNNNYYYYY slip edits and only maybe four tracks in the project. I think that has to do with the memory required to draw the waveforms. So said, these problems disappear once you bounce stuff back to tracks.

Ciao,

Q.

 

[moskus]

I can also get the same slow down when I have editted a couple of parts and there are MMMMAAAANNNNNNYYYYY slip edits and only maybe four tracks in the project.

Really? I've never had problems with Slip Editing. I use it alot...

 

[Qwerty]

Define a lot, lol.....

I am talking about an eight minute audio track, with edits on each beat. By the time I get to the end of that things start to get really slow............

Goddam wandering drummers!

Q.

 

[moskus]

Define a lot, lol.....

I am talking about an eight minute audio track, with edits on each beat. By the time I get to the end of that things start to get really slow............

Wow! Your drummer need help! Or a good click-track!

Slip-editing on EACH BEAT IN 8 MINUTES? Yes, I can imagine that would kill a computer...


May I recommend the DR-008 with the Drumkit from Hell?

 

[Qwerty]

Was the drummer. Past tense. Was the bass player. Past tense.

The drummer moved up the coast miles away and was in town for a weekend. He had never heard the songs, so we made him record them anyway. Some of it was his timing, other stuff is just us playing about with his looped stuff.

Q.