Best Core 2 Series Desktops-Results and Specs

[auxsend1]

Only thing to add is that my build is running 667 RAM, not 800. So yes, I would say that the P35 chipset is solid. May try 800 soon, and will post some Mbox 1 numbers very soon.

[sunburst79]

Only thing to add is that my build is running 667 RAM, not 800. So yes, I would say that the P35 chipset is solid. May try 800 soon, and will post some Mbox 1 numbers very soon.

I will be interested in how it runs a USB device. I updated the main page. I simply put the wrong memory speed in the previous post - Its been fixed.

Hopefully you will see the same boost Jamtime saw.

Thanks for listing the prices.

[auxsend1]

Just added this to the post above:

Update: Mbox 1 results. A little disappointing actually. Mbox 1 plugged into front USB port (seemed to get a few more dverbs than rear ports) resulted in:
221 dverbs
32 mono audio tracks, each w/ 5 mono dverbs, 12 aux tracks each with 5 mono dverbs. Then 1 more dverb on aux track #13. Recorded on separate internal audio drive for 5+ min.

Still, a decent result. I don't have an Mbox2, but I'm guessing results would be similar.

[Noviisi]

P35 vs P965. Auxsends1 P35 results are very good, Doogz had it up and running on a P35 board with Integrated graphics which has traditionally been a big no no with Protools. I was planning on going P965 for compatibility sake but Auxsend1s results now have me leaning towards P35. I'm more worried about the Agere based firewire controller chip on the the board than the P35 chipset.

So far P35 looks very good but keep in mind it is new

I suspect Q6600+P35+1066 will possibly top 275 Dverbs. That is just a guess however.

I also noticed that AGERE firewire controller. It would be nice to hear if it works steady with 002.
Other than that I really like how Asus P35 boards look.

[sunburst79]

Just added this to the post above:

Update: Mbox 1 results. A little disappointing actually. Mbox 1 plugged into front USB port (seemed to get a few more dverbs than rear ports) resulted in:
221 dverbs
32 mono audio tracks, each w/ 5 mono dverbs, 12 aux tracks each with 5 mono dverbs. Then 1 more dverb on aux track #13. Recorded on separate internal audio drive for 5+ min.

Still, a decent result. I don't have an Mbox2, but I'm guessing results would be similar.

I'm not disputing your results but I am finding this a little odd. Usually the Dverb results are pretty consistent from interface to interface. The nature of the Dverb test is such that it takes place (as far as I know) in the host computer. there has been some speculation that the MAudio stuff has slightly better device drivers but as far as I know that has never been conclusively proven either.

More importantly hows it play with Protools? sound quality? Hiss, pops, crackles? Any buffer errors while Recording/Playback etc? After the 910/915/925 series chipsets noise issues this one area where we need to be sure it works.

I'm pondering the lower Dverb count using USB, I'm wondering if its due to the fact that the M series USB stuff is all USB 1.0? Is there a legacy USB choice in BIOS?

Is it possible that some other peripheral is dragging the USB bus down?

[auxsend1]

Yeah I'm scratching my head on this one too. I think it's common to see a slight decrease comparing FW to USB interfaces, but not nearly this much (~12%). No other peripherals plugged in. USB keyboard, USB mouse, and the Mbox itself, that's it. There's no setting in the BIOS for hi-speed vs. full-speed. It's just either on or off. I even did a full uninstall/reinstall of Pro Tools to see if adding the Mbox drivers on top of the Mbox 2 Pro drivers had anything to do with it. Same result.

I'd be curious about other Core 2 Quad builds comparing FW to USB interface results. Perhaps this is the one weakness of the P35 chipset?

[NickH]

There has been some speculation that the M Audio stuff has slightly better Windows device drivers but as far as I know that has never been conclusively proven either.

I have found the opposite to be true...

I get a marked drop in performance on my laptop if I switch from the 002R on LE to the Transit on M-Powered, this isn’t subtle ether...

Cheers



N

[cranehazard]

What kind of results are you guys getting with the playback buffer set at 128 samples and 64 samples on the core 2 systems?

[sunburst79]

Yeah I'm scratching my head on this one too. I think it's common to see a slight decrease comparing FW to USB interfaces, but not nearly this much (~12%). No other peripherals plugged in. USB keyboard, USB mouse, and the Mbox itself, that's it. There's no setting in the BIOS for hi-speed vs. full-speed. It's just either on or off. I even did a full uninstall/reinstall of Pro Tools to see if adding the Mbox drivers on top of the Mbox 2 Pro drivers had anything to do with it. Same result.

I'd be curious about other Core 2 Quad builds comparing FW to USB interface results. Perhaps this is the one weakness of the P35 chipset?

I'm on the road this week if I get through the house this weekend I will try my MBox mini on my Daw and see if there is any change in Dverb counts. while its not a Core 2 System I have never tried my MBox Mini on my windows machine. I'm kind of curious if there would be a drop in Dverb counts. I agree that a drop from Fire Wire to USB is probably not uncommon somewhere in the 3-5 range would be normal I would think.

I assume that if you plug in the Mbox2 Pro the Dverb count goes right back up? If I was at home I might be tempted to overnight my Mbox Mini to you see if the newer interface did better. I probably wont be home till monday though ;(

Maybe another Core 2 owner that has both Interfaces can run some test's?

it would be good to know if the P965's show the same hit with USB.

[Ryan K]

Ryan K's Core 2 Duo

* Intel Core 2 Duo E6300 1.86GHz
* It's a Dell Dimension E520 (first time I didn't build it myself )
* 7600 GS XFX 256MB DDR2 HDMI
* 2GB DDR2 PC2-5300 NON-ECC
* Samsung 500 GB HD (SATA) (System)
* Samsung 250 GB HD (SATA) (Audio)
* TSSTcorp DVD+-R (came with the system)
* Whatever power supply came with it
* MBox2 Mini

Ran the Dverb test just as described in the first post... 24-48-1024 (CPU 90%) and recording on all audio tracks for 5 minutes.

Only 58

Is there anything simple I can do or get to get that Dverb count up?

-R