FAO Bootcamp users and LIVE (MacBook)

[muscleandhate]

How are you all finding performance in XP, and how does it compare to OSX?

I'm using a Macbook 2Ghz, with 512 RAM and a 5200 RPM Apple HD.

(Not my intention to start another argument, but I'm experiencing issues myself and am interested in fellow macheads point of views, so don't bother replying veggie).

[the unknown wanderer]

How are you all finding performance in XP, and how does it compare to OSX?

I'm using a Macbook 2Ghz, with 512 RAM and a 5200 RPM Apple HD.

(Not my intention to start another argument, but I'm experiencing issues myself and am interested in fellow macheads point of views, so don't bother replying veggie).

when i switched to my macbook i used xp to help with the transition, how ever i decided to give it all up and now i only use osx.

but this has to do with using the proper OS with its intended computer.

i never noticed any issues running two versions of live,

[the unknown wanderer]

How are you all finding performance in XP, and how does it compare to OSX?

I'm using a Macbook 2Ghz, with 512 RAM and a 5200 RPM Apple HD.

(Not my intention to start another argument, but I'm experiencing issues myself and am interested in fellow macheads point of views, so don't bother replying veggie).

i would also like to say that the problems you have experienced may be down to not having enough ram although 2gig is the maximum you can have, in a mac book. I would say its the MINIMUM you need also.

I have stripped mine down to the bare minimum processes running, and it uses 447mb of RAm and is just sitting idle If i load up live it can some time use anotherGIG depending on the project.

use the activity monitor to see what processes are running

[Michael-SW]

From the Live 5 performace thread, XP seems to be just slightly more efficient than OSX on the same MacBook.

[stinky]

I'm using bootcamp and the new Parallels Bootcamp beta, and they both run perfect. It was a bitch setting up both, however. I now have no crashes or hardware problems. You should probably reinstall the Macbook Drivers for XP. I had to do that 6 times because not all the drivers installed properly (i.e. wireless, firewire, etc.)

btw, if you have a firewire soundcard or firewire hd in SP2, I would suggest replacing your firewire drivers with the ones from SP1. There's a very detailed article on RME's site, and I had to jump through all sorts of wonderful loops and hoops to get my Saffire working on the windows side of my macbook. But, like I said, everything works. No crashes, and I use Abe daily. On XP and OSX. C yas.

[muscleandhate]

Hmm ok. So no one is experiencing pops and crackles in the audio? Honestly can't work out what the problem is, as it doesn't happen in OSX but does in XP.

[stinky]

yeah, on the internal soundcard, the windows drivers suck. i've experienced many pops and crackles. That's why I don't use it.

[muscleandhate]

I'm using a M-Audio USB Audiophile running at 128 latency and at 24bit.

[pev]

although 2gig is the maximum you can have, in a mac book. I would say its the MINIMUM you need also.
...
I have stripped mine down to the bare minimum processes running, and it uses 447mb of RAm and is just sitting idle If i load up live it can some time use anotherGIG depending on the project.

use the activity monitor to see what processes are running

Thats quite a sweeping statement and also very misleading. The memory allocated figure in the activity monitor is the memory allocated rather than active. You'll find the active amount of memory is very different. Inactive allocated memory isnt really an issue and is swapped out to VM and hence doesnt use RAM at all. The only metric you should use to decide whether your RAM is causing performance issues is the virtual memory paging figure. If your achine is doing a lot of VM paging (say, 100+ pages / sec) then you have a RAM bottleneck if not, its something else regardless of how much is shown to be allocated.

If you don't understand how this works you should read up on how virtual memory and paging work to understand it better as its very important when trying to understand performance issues!

~Pev