Hackintosh - Salvage your HD PCI cards - You Can Do It Too!

[Ru_C]

Originally Posted by aaquilato

There are so many questions to ask Ru_C.
Let's start with these:
1) Where does the audio reside?
2) What version of PT are you running with ML?
3) Explain what you mean by "Switching the playback engine to native mode (using a USB interface)".
4) Where are you getting your clock reference? What interface are you using with your TDM engine?
5) What are your buffer settings? How much RAM have you allocated in PT?
What is your total RAM?

Can you attach screen shots of your TDM & Native playback set ups?
What about your audio midi setup in the OS.
Are you making changes there?

Hi Aaquilato, thanks for chipping in. I've now got PT10 HD 10.3.7 running great on a Lion partition (thanks to Meads setup instructions), but still have the problems described above with ML.

..but to answer your specific questions

1) On a separate internal SATA drive
2) PT 10.3.7 HD
3) Switching engines from using the HD card, to native output & running through a cheap 2 in/out sound card (an Alesis i/o2)
4) Clocking comes from my Digi192
5) total ram is 4gig (i know, i'm getting more). Settings i'm using are default, with a 1024 buffer.

It might be worth you starting a couple of pages back in this thread, as you can see i've been struggling with this for a while.

This 'stuttering' error when running under ML happens with only a single mono track of audio. Running under Lion, I can play back huge sessions without issue

I'm pretty sure this is a OS/Multibeast issue, rather than a PT one

[aaquilato]

"I'm pretty sure this is a OS/Multibeast issue, rather than a PT one"…

I'm positive it is. MultiBeast sucks on many levels.

It took me months of trial and error, reading everything I could find before I got ML & PT to play nice with each other.

Reading back through the string would be counterproductive so let's move forward if you'd like.

What version of MultiBeast did you use?
What motherboard are you using?

[YYR123]

First off guys hardware that is kosher in Lion may not be cool in ML

Everybody does understand that right- ???

If it's working with Lion but not ML I bet it's a hardware compatability issue

[aaquilato]

I beg to disagree.
If Ru_C has PT running on Lion it will run on ML.
I've spent many many hours sweating over the same issues.
In the end it's one tick in MultiBeast that corrects it.
And the sad and sorry thing is you have to figure it out on your own unless by some miracle you have the same build as someone else.

[Meads]

Originally Posted by aaquilato

I beg to disagree.
If Ru_C has PT running on Lion it will run on ML.
I've spent many many hours sweating over the same issues.
In the end it's one tick in MultiBeast that corrects it.
And the sad and sorry thing is you have to figure it out on your own unless by some miracle you have the same build as someone else.

I doubt that Multibeast will do any good here. This surely is a kext issue that Multibeast will not solve. I've been working with Ru on his build for a few days now, and we got a lot sorted out. But not the DigiDal.kext issue. That's a particularly bad one.

[aaquilato]

MultiBeast is problematic in it's updated for newer hardware.
I'm running ML and PT10/11 with an older version written for Lion.
The new ML version would not work with my MB.
This took me months to sort out.
I'm sure you read my rants on TonyMac's site.
Find an older version of MultiBeast....

[Meads]

Originally Posted by aaquilato

MultiBeast is problematic in it's updated for newer hardware.
I'm running ML and PT10/11 with an older version written for Lion.
The new ML version would not work with my MB.
This took me months to sort out.
I'm sure you read my rants on TonyMac's site.
Find an older version of MultiBeast....

This is not necessarily a solution. I just built a Haswell Hackintosh today with a board that's around since quite some time (GA-H87-Wifi), and I set it up with the most recent version of Multibeast for ML (5.5.5) with no issues at all. This has been the smoothest Hackintosh setup I ever did, and PT is happy.

Which kext exactly in the older versions of Multibeast do you think is responsible for these PT issues? Quite frankly, I never had a problem with PT on a Hackintosh build before. Once I got OSX to boot, everything PT has always been fine. And I built many of those with different boards already. Ru's build is the first one that behaves that way.
I thought it might be a problem with the legacy PCI TDM cards, since ML isn't designed to run on computers with those old PCI slots - is that correct? I'm not sure.

[aaquilato]

"I thought it might be a problem with the legacy PCI TDM cards, since ML isn't designed to run on computers with those old PCI slots - is that correct? I'm not sure."

That's the key Meads!! I know you know your stuff. I've read your posts.

FIRST THINGS FIRST… Ru_C NEEDS MORE RAM.
The Mac OS needs 4GB to operate and PT needs at least 4GB as well so before anything goes further more RAM is absolutely needed.

ML couldn't care less about PCIx or PCIe.
The MB has to run PCIx natively.
If Ru_C can run PT10HD TDM and Lion… can he?… then He can update the OS to ML. But doing it with the current version of MultiBeast probably won't work.

New versions of MultiBeast do not have the code written for PCIx.
That's where things get screwed up.
Look at my signature. I'm running ML on a NEW MB by Gigabyte but I had to use an older version of MultiBeast to get it all working.
I tried for the longest time and then I stumbled across a post by Freddar who (luckily) was building with the same MB.

Are you running a PCIx system with your Haswell build?
(GA-H87-Wifi), and Multibeast for ML (5.5.5)

"Which kext exactly in the older versions of Multibeast do you think is responsible for these PT issues?"
What MB is Ru_C using? There aren't many 3 slot PCIx MBs out there.
I moved from a H55-USB3 to the P75-D3 when I read that someone had successfully built an HD4 system. I waited a year before doing that.
And in that year the Mac OS changed and MultiBeast changed by many versions.

I would use the same version of Multibeast used for the Lion build.
That's where I would start and then go backwards or forwards a version or two until you find the right version that has the correct audio codec.
That's what I had to do.

[Meads]

Originally Posted by aaquilato

[B]
New versions of MultiBeast do not have the code written for PCIx.

Okay, this information is gold, thank you!
So, Ru, when you see this, do as the good man says and try your ML drive. Run Multibeast again with those options we chose, but this time use a Multibeast designed for Lion. Maybe that's all it takes.

To answer your question, aaquilato, Ru uses a GA-EP45-UD3R.

[Ru_C]

Originally Posted by Meads

Okay, this information is gold, thank you!
So, Ru, when you see this, do as the good man says and try your ML drive. Run Multibeast again with those options we chose, but this time use a Multibeast designed for Lion. Maybe that's all it takes.

To answer your question, aaquilato, Ru uses a GA-EP45-UD3R.

Ok, so this is very interesting. I'll try re-running multi beast on my ML drive, but i'll use the version that I used for Lion (4.7.0) rather than the one I originally used (5.5.4) & see what happens !

I'm happy to experiment with this now, as at least i've finally got everything up & running with Lion on another drive (2 in fact, just to be safe !)