Ableton Forum

Just wondering if anyone is using LIVE on a Mac with bootcamp in XP a lot, and what to expect when I set up my computer this week.

Thanks in advance,
AB

Expect Live on Windows XP. That's it.

There's nothing special about Boot Camp. It's just Windows XP.

ditto i luv it, rarely go to the osx side of town

anti-banausic wrote:Just wondering if anyone is using LIVE on a Mac with bootcamp in XP a lot, and what to expect when I set up my computer this week.

As clarification, it doesn't run XP "under" Boot Camp. Boot Camp is nothing other than a utility which allows you to create an XP Drivers disk, and then act as an OS switcher at startup. Once either OS launches, it's not different at all than just running that OS without BC.

So as mentioned, Live will run exactly the same as running it without the BC part for the same hardware.

stale bread wrote:ditto i luv it, rarely go to the osx side of town

wa wa wee wa! That's incredible. Why didn't you just get a PC notebook?

Shut up glu, we all already know your affinity.

I was just asking, because I will be running LIVE under both XP, and OSX, as well as Logic on my new computer, and just wanted to know.

Thanks for those that resonded with some amount of ingenuity.

Best,
AB

Seems pretty pointless.

I'm having a LOT of trouble with crashes and glitches in audio. Then again I haven't tweaked or streamlined XP. Windows is not a pleasant experience at all so far, apart from the abundance of freeware everything seems sub-par to OSX.

I've installed a bootcamp partition and use XP Pro SP2 and Live 6. 2GB important as XP was no where near as efficient as OSX with 512RAM. Now I'm using 2GB, I'm very impressed, excellent latency and low CPU usage in XP. I also use paralells to use soundforge within OSX and for futher integration between both operating systems. It is very cool to be a on mac since intel

I want to thank you guys for responding. Also wanted to apologize to glu, just a little tipsy last night. Didn't mean anything by it.

Also, if you are using the onboard sound and getting clicks and crackles, you probably want to get asio4all for when you boot up XP.

anti-banausic wrote:I want to thank you guys for responding. Also wanted to apologize to glu, just a little tipsy last night. Didn't mean anything by it.

Also, if you are using the onboard sound and getting clicks and crackles, you probably want to get asio4all for when you boot up XP.

haha I didn't catch that until now! I was actually naturally curious- don't think I haven't debated the same thing to myself 1000+ times, you should be able to tell by the 100 posts I have about custom PCs and bootcamp with Macs.

I would do it the other way around. rock a hackintosh on a dual(or quad) boot PC. BIOS will kill EFI anyday(yes EFI has a huge hole in it where an outside user (aka me at your local coffee shop) can clear NVRAM (disabling root password) and do an EFI update (flash your CMOS with a bad version) therefore never letting you turn on your shiny macbook ever again)... cant do that on my box. Also core audio searches for possible drivers (have you mac users ever gone through your kernel extensions and seen how they are written?) go to terminal login as root and nano any .plist inside a .kext. There are like 200 possible devID and VenIDs. I went through and made a hacked up driver for my realtek audiocard so it only will play 96k 32bit on my hackintosh with 1.32ms lateny (Still not my 0.27ms in XP). Im gonna keep playing with it hoping the shit dont get too hot...(lappy sitting on extra cooling pad and has side panel completely off! I shouldn't push my boxes so hard...)
But yeah Im rocking Live on both XP and OSX, Logic on OSX, and Ardour on Linux (which by the way I like and use more than Logic... so please check it out) and OSX is streamlined... Xbench score at 113 on PC. running FCP 5.1.2, Logic 7.2, Apeture 1.5.2, Photoshop CS3, Flex builder, Waves bundles, Nexus and so much more...


Moral of the story. A computer is a computer, A command line is a command line, a Kernel is a Kernel. Bootcamp allows Windows to run under EFI, BIOS lets anything run.

sudo rm -rf /System/Library/Extensions/You.kext
sudo rm -rf /System/Library/Extensions.kextcache
sudo rm -rf /System/Library/Extensions.mkext
sudo chown root /System/Library/Extensions
sudo chmod 755 /System/Library/Extensions
and reboot...

P.S. I just learned the mac mitm cmos flash trick this week from a kid in one of my networking classes. I haven't tried it yet (I don't hate noobs as much as some geeks that go to coffee shops just to jack passwords and wreak havoc). If I were you, I would look into 3rd party network monitoring apps, like littlesnitch and netbarrier X4. You only have about 5 seconds(if that) to see someones IP on a network before they can mitm (Man In The Middle for all the noobs) or Cain and Able or S-kill...
Just dont get on any open wifi networks EVER. Here in Portland there is city wide free wifi (at least downtown) and there is a crew that sits at portland coffee house hacking downtowners checking their bank balances on lunch and such gimmicks. Its a game now...
Mac has a serious security flaw that I see getting exploited more and more as they become the new "User Friendly" OS of choice.
I read somewhere that as Man keeps making computers more idiot proof, God keeps making bigger idiots.... Sorry this turned out to be a long post, Its been a really long week or so, Just took my last Final today of a 17 hr semester.... got straight As and have been so freaking busy.... I got a week off before I go into my next set of classes....

Verbal wrote:Seems pretty pointless.

He probably wants to use some VSTis that are on XP only. For example Fruityloops. Or wants to use other Pc audio apps not available on Apple and doesn't want to switch between OS.

Not has pointless has you think.

paradiddle wrote:

Verbal wrote:Seems pretty pointless.

He probably wants to use some VSTis that are on XP only. For example Fruityloops. Or wants to use other Pc audio apps not available on Apple and doesn't want to switch between OS.

Not has pointless has you think.

If you want to not have to change then you can use parallels or evenbetteryet...VMWare fusion. run an operating system within an operating system. Of course both OS are sharing resources so they are going slow but you can test out those plugs you've been dieing to hear. Even import a track (dont forget file naming conventions that mac forgets) effect it in XP, bounce it, and send it bac to mac for further processing.